More on Invoking BPEL from Java
I just updated the
sample java app that invokes BPEL to allow you to customise the parameters from an HTML screen. THis is useful because I can now easily play with different parameters, getting different bits wrong and examining the results. Very useful when a customer complains about a problem invoking BPEL and I can recreate the error and tell them what they are doing wrong within a couple of minutes.
Enough of that, lets talk a bit more about why you want the different ways of invoking BPEL.
Basically by deploying it in different ways you can alter the amount of additional configuration information you need in your application. The table below summarises the different ways the BPEL client can be deployed and what additional information is needed for each mechanism.
| Deployment | Parameters | Notes |
| Child |
| Nice and easy to set up. |
| Local |
| No harder than child configuration really as the Provider URL will not change unless you change the name of the BPEL PM application. |
| Remote |
| Lots to change when moving from test to production |
This becomes an issue as you move from test to production. If you deploy locally or as a child then there is no change in configuration moving from test to production except for the BPEL domain name and password. If use a hostname of localhost with local deployment then you have no more configuration changes to make than you need with child deployment.
If you run remotely then you need to configure the JNDI connection as well as the BPEL configuration. However if you don't know what the final deployment scenario is going to be then this is the way to set it up as it will work with any deployment at the expense of additional configuration when moving from test to production.
