Deploying business applications interactively

To change the data source, schema name, or table name at deployment time, you must use the wsadmin installInteractive script, because these settings cannot be changed if you use the administrative console to deploy the application.

Draft comment:
For 6.0.2: This is a new topic for BB LI 742 (WBI LI 340) - This topic can be extended to cover any (non-II4BPEL) BPC interactive install options.
If your business process application includes an information service activity, that uses SQL support features, and you want it to use a different data source, schema name, schema prefix , table name, or table prefix than was specified during modeling, you must install the application interactively.

You can change the value of any BPEL variables used in your model, if they are of type tSetReference and tDataSource at deployment time if you use the wsadmin interactive install.
You can install an application interactively by issuing the command:
wsadmin $AdminApp installInteractive application_name
where application_name is the name of the application.

Example: Changing data source values for initial variable values and statements that are used at process start or installation time

If the application includes variables of type tDataSource, the interactive installation will include prompts that allow you to change the data source JNDI names as illustrated below. Pressing Enter will accept the default value that is shown in square brackets. Entering a new value will change the value.

Task[24]: Updating data sources

Change data source values for initial variable values and statements used at process start or installation time

Process name:  Test					
Process start or installation time:  Process start	
Statement or variable:  Variable			
Data source name:  MyDataSource			
JNDI name:  [jdbc/sample]:jdbc/newName			
Process name:  Test
Process start or installation time:  Process start
Statement or variable:  Statement declaration
Data source name:  dataSourceValue
JNDI name:  [jdbc/oracleSample]:
Process name:  Test
Process start or installation time:  Process installation
Statement or variable:  Statement declaration
Data source name:  dataSourceValue
JNDI name:  [jdbc/sample]:
Draft comment:
6.0.2: Is this a good example? If it only illustrates changing the first of three variables - why show the two that we don't change? This example could be improved by deleting the last 10 lines. Reviewers: Do you agree?

Example: Changing set reference values that are used as initial values for BPEL variables

If the application includes variables of type tDataSource, the interactive installation will include prompts that allow you to change set reference values, as illustrated below. Pressing Enter will accept the default value that is shown in square brackets. Entering a new value will change the value.

Task[25]: Updating set references

Change set reference values used as initial values for BPEL variables

Process name:  Test
Variable:  SetRef
JNDI name:  [jdbc/sample]:
Schema name:  [IISAMPLE]:
Schema prefix:  []:
Table name:  [SETREFTAB]:
Table prefix:  []:
Draft comment:
6.0.2: Is this a good example? It does not illustrate changing any values! Would it be more realistic to also change the JNDI name here to jdbc/newName to match the change in the previous example? Reviewers: Do you agree?

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)