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


zWESBConfig.sh script

Use these scripts to configure and augment the WebSphere® ESB for z/OS® installation. Run the script on each node in your configuration, including the deployment manager.

Purpose

The zWESBConfig.sh script configures your server as an enterprise service bus.

Syntax

Read syntax diagramSkip visual syntax diagram
>>-zWESBConfig.sh----------------------------------------------->

>--+- -prereqonly----------------------------------+------------>
   '- -augment-- -response--response_file_location-'   

   .---------------------.   
   V                     |   
>----+-----------------+-+-------------------------------------->
     '--Zkeyword=value-'     

>--+------------------------------------+----------------------><
   |          .-*=all=disabled--------. |   
   '- -trace--+-----------------------+-'   
              +-*=all=enabled---------+     
              '-Installer=all=enabled-'     

Parameters

-prereqonly
This parameter validates the prerequisites and verifies arguments.
-augment
This parameter configures the WebSphere Application Server for z/OS installation to be a WebSphere ESB for z/OS installation.
-response
The absolute path of the response file that contains the properties for your product configuration. The path shown in the syntax diagram is the location to the response file that you use if you are creating a deployment manager for a network deployment configuration using DB2®.
-Zkeyword=value
Overrides keyword values in the response file. You can specify the -Z parameter multiple times, once for each keyword that you want to override. For example, -ZnodeName=NODE1.
-trace
The command writes to the appropriate trace file. You can enter one of the following values:
  • To record no trace information, type *=all=disabled. If you do not specify the -trace parameter, this value is used by default.
  • To record all trace information, type *=all=enabled.
  • To record trace information about only the Installer group of Java™ classes, type Installer=all=enabled. The trace is written to /logs/wbi/zWESBConfig.trace

Example

The following command configures a deployment manager node that uses DB2 with a response file that is located at /u/clare/DmgrDB2.rsp:

Troubleshooting

Verify arguments and environment

To avoid errors, verify the arguments that you use in the command:
  1. Verify that one and only one of the arguments (-prereqonly or -augment) is specified.
  2. Verify that the -response argument and its parameter value are specified and that the response file that is specified in the value exists. Check that the response file is in EBCDIC. format.
  3. Verify that any -Z arguments contain an equal sign (=).
  4. If the -trace argument is specified, verify a value is also specified.
  5. Verify that any unrecognized keywords are not specified.
  6. Verify that the prerequisite WebSphere Application Server is at the supported level.

Augment profile(s)

  1. Enables profile augmentation using (WSPROFILE) scripted actions.

    This is accomplished by invoking the Profile Updater and passing it a profileTemplate directory.

    Which profileTemplate is passed is based on the templatePath value in the response file, which is referenced in the zWESBConfig.sh command line.

    As with all response file properties, the templatePath value may be overridden using the -Z argument on the command line.

    The default response file templatePath is: templatePath=/WebSphere/V6R2/AppServer/profileTemplates/default.wbiserver.

    For more detailed information about the profileTemplate property, see the Response file values.


reference Reference 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/rins_zos_configscript.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).