IBM BPM, V8.0.1, All platforms > Administer the IT infrastructure > Administer Business Process Choreographer > Use scripts to administer Business Process Choreographer > Administer query tables
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.
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.
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.
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.
INSTALL_ROOT/bin/wsadmin.sh –f manageQueryTable.py [ ([-node nodeName] -server serverName) | (-cluster clusterName) ] -deploy qtdFile | jarFile
INSTALL_ROOT/bin/wsadmin.sh –f manageQueryTable.py [ ([-node nodeName] -server serverName) | (-cluster clusterName) ] -deploy qtdFile | jarFile
INSTALL_ROOT\bin\wsadmin –f manageQueryTable.py [ ([-node nodeName] -server serverName) | (-cluster clusterName) ] -deploy qtdFile | jarFileWhere:
- -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, 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.
wsadmin.sh –f manageQueryTable.py –server server1 –deploy sample.qtd
wsadmin.sh –f manageQueryTable.py –server server1 –deploy sample.qtd
wsadmin –f manageQueryTable.py –server server1 –deploy sample.qtd
Related concepts:
Supplemental query tables
Composite query tables
Related tasks:
Update composite and supplemental query tables
Retrieving a list of query tables
Retrieving the XML definitions of query tables
Undeploying composite and supplemental query tables