This article presents a sample of what the Customization Dialog's generated instructions might look like. This is a sample only--you must use the instructions generated from your own variables when configuring your system.
----------------------------------------------- The customization dialog has created jobs based on the information you provided. These instructions tell you how to modify the operating system and run the jobs to customize WebSphere for z/OS. RULES: 1. If you created the target data sets (*.CNTL and *.DATA) on another (driving) system, you must copy them to the target system and give them the same data set names. 2. You must perform these instructions on your target system. 3. Update TCP/IP by reserving the following ports for WebSphere for z/OS: SOAP JMX Connector port - 9360 Node Discovery port - 7272 Node Multicast Discovery Port - 5000 Node Agent's ORB port - 2809 High Availability Manager Communication port - 9354 Application server's ORB Port - 9810 View member BBOTCPIA in 'DATASET.CNTL'. Add the contents of this member to the PORT section of the file referenced by the DD statement for the TCP/IP profile in the TCP/IP start procedure. Cut and paste from this member into the data set used by your installation. Note: The addNode process introduces a special utility server to the node. This utility server is called a nodeagent and exists to support administrative functions on the node. By default the nodeagent takes over ORB port 2809. Note on WebSphere z/OS the ORB port doubles as the INS CosNaming bootstrap port. By default, this port (2809) was assigned to the application server. Normally you want the nodeagent to be the INS CosNaming bootstrap point for the entire node, so that RMI/IIOP clients that do not override the INS CosNaming bootstrap defaults can locate within the namespace, EJBs installed on any server on that node. In order for the nodeagent to take over port 2809, the application server must be assigned a new ORB port. The default new ORB port for the application server is 9810. The nodeagent will take over a application server's ORB port if and only if the nodeagent's ORB port is equal to an application server's ORB port. You can specify the nodeagent's ORB port in the 'ORB port' field. You can specify the new ORB port for the application server in the 'Appplication Server's ORB Port' field. ATTENTION: Skip this step if the ports are already defined in the TCP/IP profile. 4. You must first complete the customization of a stand-alone application server and the customization of a deployment manager server before starting these instructions. Also, ensure that the deployment manager server has been started before starting these instructions. +-----------+----------------------------------------------------------+ | | User ID requirement: Authority to define a log stream. | +-----------+ | | Done: | NOTE: if you are not using logstream for transaction XA, | | | you can skip this step. | | | | | By: | The process used to Federate an existing Application | | | Server causes the user data of this application server to| | | be changed. | | | | | | | | | NOTE 2: STOP server prior to running BBOLOGSD. | | | BBOLOGSD will fail if the server is active. | | | | | | Please run the following two jobs that were generated | | | during stand-alone application server configuration: | | | | | | BBOLOGSD -- this will delete the logstreams that were | | | allocated by BBOLOGSA earlier. | | | | | | BBOLOGSA -- this will create a new logstream with the | | | application servers new user data. | | | | | | This is done so that IXGLOGR will not attempt to connect | | | this new server to an old logstream which would produce | | | an error. | | | | +-----------+----------------------------------------------------------+ | BBOWADDN | User ID requirement: WSADMIN | +-----------+ | | Done: | Add the application server(s) associated with the stand- | | | alone application server node to the deployment manager's| | | cell. | | By: | | | | ATTENTION: Before you run this job (BBOWADDN) to | | | federate the stand-alone application server node, you | | | must have started the stand-alone Application server | | | that you are federating at least once so the applyPTF | | | step runs. Otherwise, the BBOWADDN job will fail with | | | an error such as: | | | java.lang.NullPointerException at | | | com.ibm.ws.management.tools.NodeFederationUtility | | | .createNDProductFile(NodeFederationUtility.java:1929)| | | | | | Note: Run this job only once for each node that you | | | federate, regardless of how many application servers the | | | node contains. | | | | | | RESULT: Upon successful completion of this job, you will | | | see the following message in SYSPRINT: | | | | | | ADMU0003I: Node <nodename> has been successfully | | | federated. | | | | +-----------+----------------------------------------------------------+ | -------- | Start the node agent server | +-----------+ | | | Note: The node agent is automatically started by the node| | | federation process. This step is information, for | | | starting the node agent at other times. | | | | | | If your application server proc name is XXXXXXXX | | | and your application server node name (short) | | | is YYYYYYYY, issue the MVS command | | Done: | | | | START XXXXXXXX,JOBNAME=BBON001, | | By: | ENV=MCLXCF01.YYYYYYYY.BBON001 | | | | | | This command starts the node agent server. | | | | | | RESULT: The following message appears on the console and | | | in the job log of BBON001. | | | | | | BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR | | | z/OS CONTROL PROCESS BBON001. | | | | +-----------+----------------------------------------------------------+ | -------- | Start the application server (optional) | +-----------+ | | Done: | Note: You must start the node agent before you start the | | | application server, if the node agent has not already | | | been started | | | | | | Example: If your application server proc name is | | | XXXXXXXX, your application server node name (short) is | | | YYYYYYYY, and your server short name is BBOS001, issue | | | the MVS command | | By: | | | | START XXXXXXXX,JOBNAME=BBOS001, | | | ENV=MCLXCF01.YYYYYYYY.BBOS001 | | | | | | This command starts the application server. | | | | | | RESULT: The following message appears on the console and | | | in the job log of BBOS001. | | | | | | BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR | | | z/OS CONTROL PROCESS BBOS001 | | | | +-----------+----------------------------------------------------------+