WebSphere Application Server Version 6.1 Feature Pack for Web Services   
             オペレーティング・システム: z/OS

             目次と検索結果のパーソナライズ化
このトピックは、z/OS オペレーティング・システムにのみ適用されます。

生成された指示のサンプル: フェデレーテッド・アプリケーション・サーバー・ノード

この項では、 カスタマイズ・ダイアログの生成した指示がどのように見えるかのサンプルを紹介します。 これはサンプルにすぎません。 ユーザーのシステムを構成する際には、 ユーザー独自の変数から生成された指示を使用する必要があります。

注: このサンプルは、WebSphere Application Server for z/OS バージョン 6.0.2 の インストールに基づいています。バージョン 6 の別のリリースから生成された指示では、 内容が異なる場合があります。
-----------------------------------------------                                 
Instructions for customizing WebSphere for z/OS                                 
for Federate stand-alone Application Server node.                               
                                                                                
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                                                     
                                                                                
    'USERID.TODAY.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 an
      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.                                                               
                                                                                
+-----------+----------------------------------------------------------+        
| --------  | If your system is busy, you may want to include a rule   |
+-----------+ in your WLM policy that OMVS work for job BBON001        |
| Done:     | (such as the postinstaller step) is to run in a service  |
|           | class with a high service objective.                     |        
| By:       |                                                          |
+-----------+----------------------------------------------------------+        
| BBOWADDN  | User ID requirement: WSADMIN                             |        
+-----------+                                                          |        
|           | If you choose the start the node agent automatically,    |
| Done:     | the user ID used to run BBOWADDN will also need the      |
|           | authority to issue the MVS START command.                |        
|           |                                                          |        
|           |                                                          |        
|           | 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                              |        
+-----------+                                                          |        
| Done:     | Note: The node agent is automatically started by the node|
|           | federation process.  This step is information, for       |        
|           | starting the node agent at other times.                  |        
| By:       |                                                          |
|           | If your Application Server proc name is XXXXXXXX         |
|           | your Application Server node name (short)                |
|           | is YYYYYYYY and your Deployment Manager cell             |
|           | name (short) is ZZZZZZZZ, issue the MVS command:         |
|           |                                                          |        
|           |   START XXXXXXXX,JOBNAME=BBON001,                        |        
|           |         ENV=ZZZZZZZZ.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.                                            |        
|           |                                                          |        
| By:       | Example: If your Application Server proc name is         |
|           | XXXXXXXX, your Application Server node name (short) is   |
|           | YYYYYYYY your server short name is BBOS001, and your     |
|           | Deployment Manager cell name (short) is ZZZZZZZZ, issue  |
|           | the MVS command                                          |        
|           |                                                          |        
|           |   START XXXXXXXX,JOBNAME=BBOS001,                        |        
|           |         ENV=ZZZZZZZZ.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                           |        
|           |                                                          |        
+-----------+----------------------------------------------------------+        



関連資料
関連情報
生成済みカスタマイズ手順に従う: 統合アプリケーション・サーバー・ノード
参照トピック    

ご利用条件 | フィードバック

最終更新: Jan 21, 2008 4:10:06 PM EST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/rins_dialogsteps_sampinst5.html