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

Update composite and supplemental query tables

Use an administrative script to update composite and supplemental query tables in Business Process Choreographer. Updates to query tables can be made while applications are running, and they are available after the update, without restarting the server or cluster.

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 operator, administrator, or deployer authority, include the wsadmin -user and -password options to specify a user ID that has operator, 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 update composite and supplemental query tables in Business Process Choreographer.

Procedure

1. 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

2. Update the query table using either a query table definition XML file or a JAR file that contains the definitions. If property files are already deployed, they will be overwritten.
   

    INSTALL_ROOT/bin/wsadmin.sh –f manageQueryTable.py
          [ ([-node  nodeName] -server  serverName) | (-cluster  clusterName) ]
            -update definition  qtdFile |  jarFile

   

    INSTALL_ROOT/bin/wsadmin.sh –f manageQueryTable.py
          [ ([-node  nodeName] -server  serverName) | (-cluster  clusterName) ]
            -update definition  qtdFile |  jarFile

   

    INSTALL_ROOT\bin\wsadmin –f manageQueryTable.py
          [ ([-node  nodeName] -server  serverName) | (-cluster  clusterName) ]
            -update definition  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.

   -update definition qtdFile | jarFile

   The file name, including the fully qualified path, of either the query table definition XML file to be updated or a JAR file that contains the definitions. Use this option to update an existing 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.

   If a JAR file is provided, it can contain multiple QTD files and property files for each QTD file, which contain display names and descriptions. Use the Query Table Builder to export query table definitions as a JAR file.

   For example.
   

   wsadmin.sh –f manageQueryTable.py –server server1 
              –update definition sample_v2.qtd

   

   wsadmin.sh –f manageQueryTable.py –server server1 
              –update definition sample_v2.qtd

   

   wsadmin –f manageQueryTable.py –server server1 
           –update definition sample_v2.qtd

Administer query tables

Related concepts:
Composite query tables
Supplemental query tables

Related tasks:
Retrieving a list of query tables
Retrieving the XML definitions of query tables
Deploying composite and supplemental query tables
Undeploying composite and supplemental query tables