WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Configuring an empty node with WebSphere ESB

You must configure an empty WebSphere® Application Server node with WebSphere ESB for z/OS® functions before you federate the empty node to the deployment manager.

Before you begin

Important: Do not federate the managed node to the deployment manager at this stage.
Before you configure the empty node you must have completed the following steps:
Procedure
  1. Run the zWESBConfig.sh configuration script.

    You can use JCL to run the configuration on the empty node; see JCL for augmenting an empty 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/ManagedDB2.rsp
    Where working_directory_path is the location of the ManagedDB2.rsp file that you have edited.

    For more information about the command, see zWESBConfig.sh script.

  2. Wait for the configuration to run.
  3. Optional: Back up the file system that contains the empty node configuration.

Results

The empty node has now been configured with WebSphere ESB for z/OS functions.

What to do next

You can now create other empty nodes, in the same way, as required. Then, federate each of the empty nodes to the deployment manager cell; see Federating the empty node into the deployment manager cell.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/tins_zos_add_wps_emn.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).