Hi Jiri

The instructions provided in https://docs.jboss.org/author/display/SWITCHYARD/Update+BPEL+component+database explain how to do your (a), (b) and (c), so I am not sure what the issue is here?

OOTB it uses in-memory h2, without any explicit configuration. But if for example MySQL is required, then the instructions explain how to define the datasource and overridden properties within the standalone*.xml file. So it is not necessary for a user to edit the bpel,properties file - this file simply defines the property defaults.

If the issue is that you have tried those instructions and they don't appear to work, then can you provide additional details to help reproduce, and a server.log with debug logging.

Thanks.

Hi,

I am speaking here about user experience (or admin experience). SOA-P comes with 3-4 different datasources and unless we made the configuration central it will be way too hard to install and administrate it.

I've already raised issue for components with similar behaviour too.

Ok understand.

Is there a particular database being targeted for the OOTB experience?

Well,

I've seen in DR6 that overlord-rtgov and gadget server has configuration property files place in configuration directory.

I think it would make sens to do the same for BPEL too.

It should be noted that placing property files within the configuration directory should not be the final solution to this issue.  The intention is to modularise these deployments and it would be much better if the configuration was handled through the upcoming extension module.

I don't think there is an issue here regarding configuration files, as any property changes can be applied within the standalone.xml.

In that case we should remove the property file from the configuration directory and rely on the standalone.xml.

Sorry wasn't clear, there isn't a property file in the configuration directory currently - only one inside a riftsaw jar (called bpel.properties) which is simply used to provide the default values, which can then be overridden by values in the standalone.xml.

Apologies, I think I have been confusing the issue by originally responding to Jirka's comment regarding the existing property files within the configuration directory.

We should not be adding a property file for BPEL, given that it is already supported through the standalone.xml, and we should be looking to remove the configuration files for the overlord-rtov/gadget server.

Not a Blocker, not really an issue as the configuration can be done through standalone.xml (Kevin Conner)

Based off this Bpel configuration:
https://docs.jboss.org/author/display/SWITCHYARD/Update+BPEL+component+database


I have created CLI script to create the BpelDS datasource.  The CLI cannot update the existing module.xml configuration, it does not support update functionality currently.  The module.xml will need to be updated with xslt (which can be run from the installer).

(In reply to Steve Johnson from comment #16)
> Based off this Bpel configuration:
> https://docs.jboss.org/author/display/SWITCHYARD/
> Update+BPEL+component+database
> 
> 
> I have created CLI script to create the BpelDS datasource.  The CLI cannot
> update the existing module.xml configuration, it does not support update
> functionality currently.  The module.xml will need to be updated with xslt
> (which can be run from the installer).

Ignore please.  module.xml does not need to be modified.

Correct CLI configuration for DataSource and Module has now be added.

Requires updates to installer to call these scripts.

Need the ER7 build to test the changes.

*** Bug 1014072 has been marked as a duplicate of this bug. ***

This issue needs to be verified on ER7-2.

Verified in ER7