Deploying composite and supplemental query tables

Use an administrative script to deploy supplemental and composite query tables before using them in Business Process Choreographer. Before query tables can be used with the query table API they must be deployed on the related Business Process Choreographer container. Query tables do not need to be started, and the server or cluster does not need to be restarted for them to be available after deployment.

Before you begin

The following conditions must be met:

Run the script in connected mode, that is, the application server must be running. Do not use the wsadmin -conntype none option.
If Business Process Choreographer is configured on a cluster, then at least one cluster member must be running.
If WebSphere® administrative security is enabled, and your user ID does not have administrator or deployer authority, include the wsadmin -user and -password options to specify a user ID that has administrator or deployer authority.
If you are not working with the default profile, use the wsadmin -profileName profile option to specify the profile.

About this task

Complete the following steps to deploy composite and supplemental query tables in Business Process Choreographer.

Procedure

Change to the Business Process Choreographer subdirectory where the administrative script is located. Enter the following command:
```
smpe_root/ProcessChoreographer/admin
```
- In the directory:
  install_root/ProcessChoreographer/admin
- In the directory:
  install_root\ProcessChoreographer\admin
To deploy a query table file or a JAR file: Enter the following command:
```
install_root/bin/wsadmin.sh –f manageQueryTable.py
       [ ([-node nodeName] -server serverName) | (-cluster clusterName) ]
       -deploy qtdFile | jarFile
```
Enter the following command:
```
install_root/bin/wsadmin.sh –f manageQueryTable.py
       [ ([-node nodeName] -server serverName) | (-cluster clusterName) ]
       -deploy qtdFile | jarFile
```
Enter the following command:
```
install_root\bin\wsadmin –f manageQueryTable.py
       [ ([-node nodeName] -server serverName) | (-cluster clusterName) ]
       -deploy qtdFile | jarFile
```
Where:
-node nodeName

The name of the node where Business Process Choreographer is configured. This is optional when specifying the server name. The default is the local node.

-server serverName

The name of the server where Business Process Choreographer is configured. This is required if a cluster is not specified.

-cluster clusterName

The name of the cluster where Business Process Choreographer is configured. This is required if Business Process Choreographer is configured on a cluster.

-deploy qtdFile | jarFile

The file name, including the fully qualified path, of either the query table definition XML file to be deployed or a JAR file that contains the definitions. Use this option to deploy a query table. On Windows, you must use either "/" or "\\\\" as the path separator. For example, to specify the file c:\temp\myQueryTable.qtd you must specify it as c:/temp/myQueryTable.qtd or c:\\\\temp\\\\myQueryTable.qtd.

Example

For example: This topic applies only to the z/OS platform

Enter the following command: This topic applies only to the z/OS platform

wsadmin.sh –f manageQueryTable.py –server server1 –deploy sample.qtd

This topic applies only to the Distributed platforms For Linux operating system For UNIX operating system Enter the following command:

wsadmin.sh –f manageQueryTable.py –server server1 –deploy sample.qtd

This topic applies only to the Distributed platforms For Windows operating system Enter the following command:

wsadmin –f manageQueryTable.py –server server1 –deploy sample.qtd