IBM SG24-6526-00 manual WebSphere administration, adminNodeName , -import , and -substitute

3.6.4 WebSphere administration

This section covers the topics related to WebSphere.

Starting the administration server

QEJBSBS must be running. If the default instance is not required, QEJBADMIN and QEJBMNTR may be ended. Follow these steps:

1.Sign on as QSECOFR.

2.To start a WebSphere instance called test, call program STRWSSVR:

CALL PGM(OSLOMD3/STRWSSVR) PARM(TEST)

3.Jobs TESTADMIN and TESTMNTR should be displayed in the QEJBSBS subsystem. Check the job log of TESTADMIN and wait for the message “WebSphere administration server TESTADMIN ready”, similar to the default system.

WebSphere cannot start until the administration server is ready.

Importing the configuration file

Attention: To import the configuration file, the WebSphere instance must be running. However, the console must not be running.

Follow these steps:

1.The import tool needs to run within Qshell. Run the start Qshell command, and after each command, wait for $ signs to appear.

STRQSH

2.Switch the current directory within Qshell: cd /QIBM/ProdData/WebASAdv/bin

3.Import the configuration file Config.xml from OrderManagement/Config.

4.To use the delivered file to configure the test instance running on port 902 on an iSeries, use the following command, substituting your server name for iSeries:

XMLConfig -adminNodeName <iSeries> -import /OrderManagement/test/Config/Config.xml -instance test -nameServiceHost <iSeries> -nameServicePort 902

Notes:

￿Leave a space before each - sign. Leave a space after each keyword, for example

-adminNodeName ,-import , and -substitute .

￿There is only one pair of quotes around the entire substitution string.

The config.xml file contains the following variables, which are substituted on the import command and replaced with real names:

￿$NodeName$: This is the WebSphere node name. It is usually the system name, but it is case sensitive.

￿$dir$: This is the root directory for the installation. This is the directory that contains the

subdirectories: cfg, deployed, and log. For an instance called test, this could be /OrderManagement/test. The EJBs to be deployed are in /OrderManagement/Test/Deployed.

Chapter 3. Installing and setting up call.connect 65