The deployment manager manages the network deployment cell.
All nodes in a network deployment configuration use DB2® database
objects.
Before you begin
Before you configure the deployment manager node you must
have completed the following tasks:
- Create a deployment manager node in WebSphere® Application Server. See Creating a network deployment cell.
- Install WebSphere ESB on the deployment manager node.
- Back up the data sets that contain the deployment manager configuration.
- Create a response file for a deployment manager with a DB2 database,
either by using the sample files.
Procedure
- Stop the server.
- Increase the OMVS time limit to allow the product configuration
script time to complete. In an MVS™ console
enter the following command:
SETOMVS MAXCPUTIME=86400
- Access the USS command shell, then switch to the
administrator user ID. For example:
su wsadmin
- Change directory to the deployment manager bin directory:
cd /WebSphere/V6R1/DeploymentManager/bin
- Run the zWESBConfig.sh configuration script.
You can use JCL to run the configuration on the deployment
manager node; see JCL for augmenting a deployment manager node for an example JCL script.
Alternatively, you can run the configuration script directly from
USS with the absolute path of your edited response file. For example:
zWESBConfig.sh -augment -response /working_directory_path/DmgrDB2.rsp
where working_directory_path is the location of the DmgrDB2.rsp file that you have edited.
- Wait for the configuration to run.
When the script has finished running, review the messages that are
written to the console. If the script has run successfully, no error
messages are displayed and the informational messages state augmenting profile(s) complete.
- Back up the data sets that contain the deployment manager
configuration.
Results
The deployment manager is configured with
WebSphere ESB.
What to do next
You can now create the DB2 common
database using one of the following methods:
- Run the DDL scripts that were generated by the configuration script
using SPUFI, DSNTEP2, or DBUtility.sh This method is more complex
because you create the database using one DDL script, then later populate
it by running other DDL scripts. This method does, however, enable
you to specify that the database objects are created in multiple databases,
instead of them all being created in the single common database. See Creating the DB2 databases and storage groups using SPUFI, DSNTEP2, or DButility.sh.