Verify the following:
- Your user ID has administrative rights.
- The user ID you configured to access the database has the rights to run
the statements in the DDL file.
- The DDL file is accessible from the application server.
If you need to add tables to the Business Process Choreographer run-time
database, for example, the table for an entity bean in your application, you
can use the runDllFile.jacl script that runs a DDL file on
the database.
- Change to the Business Process Choreographer utilities directory
where the scripts are located. On Windows systems,
enter:
cd install_root\ProcessChoreographer\util
On UNIX and Linux systems enter:cd install_root/ProcessChoreographer/util
- Add the tables to the database.
On
Windows systems, enter one of the following commands:
install_root\bin\wsadmin -f runDdlFile.jacl
-server serverName
-filename ddlFile
install_root\bin\wsadmin -f runDdlFile.jacl
-node nodeName
-server serverName
-filename ddlFile
install_root\bin\wsadmin -f runDdlFile.jacl
-cluster clusterName
-filename ddlFile
On UNIX and Linux systems, enter one of the following commands:
install_root/bin/wsadmin -f runDdlFile.jacl
-server serverName
-filename ddlFile
install_root/bin/wsadmin -f runDdlFile.jacl
-node nodeName
-server serverName
-filename ddlFile
install_root/bin/wsadmin -f runDdlFile.jacl
-cluster clusterName
-filename ddlFile
Where:
- clusterName
- The name of the cluster. Required if the business process container is
configured for a WebSphere cluster.
- nodeName
- Optional when specifying the server name. This name identifies the node.
The default is the local node.
- serverName
- The name of the server. Required if the cluster name is not specified.
- ddlFile
- The name of a DDL file that is local to the application server.
The staff assignments that belong to this process template are refreshed.