See
jpechane@jpechane:~/releases/er4$ grep -ir 'datasource jndi' full/jboss-eap-6.1/standalone/configuration/standalone.xml 
                <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">
                <datasource jndi-name="java:jboss/datasources/jbpmDS" pool-name="jbpmDS" enabled="true" use-java-context="true">
                <datasource jndi-name="java:jboss/GadgetServer" pool-name="GadgetServer" enabled="true" use-java-context="true">
                <datasource jndi-name="java:jboss/datasource/OverlordRTGov" pool-name="OverlordRTGov" enabled="true" use-java-context="true">

I'd expect there will be also a datasource named bpelDS and the BPEL component will use it.

As it was decided that bz969008 is no longer a beta blocker and we are happy to deliver a product to customer that will
 1) allow him to install and configure FSW for some of the databases
 2) require him to manually modify BPEL component to use the database he is using for the other components

then I am removing the beta blocker form this one too.

(In reply to Jiri Pechanec from comment #2)
> As it was decided that bz969008 is no longer a beta blocker and we are happy
> to deliver a product to customer that will
...
>  2) require him to manually modify BPEL component to use the database he is
> using for the other components


As it was explained yesterday, I did not leave the PM discussion with the understanding that one must manually modify a BPEL component.  If that's the case this should still be considered a beta blocker.

The fix has been done as part of 969008.

*** This bug has been marked as a duplicate of bug 969008 ***