Action:

was_common_configure_vhosts

Summary:

Manages virtual host configuration in IBM WebSphere Application Server.

Details:

   Supports all currently supported versions of WebSphere Application Server. 

   On execution, this action configures Virtual Hosts for the virtual hosts 
   included in the vhosts.xml file.[1]

Usage Examples:

 
   Import mode imports an existing virtual host configuration from WebSphere. 

   Execute mode updates an existing virtual host configuration in WebSphere. 
   The existing configuration is deleted and replaced.

   Augment mode adds a virtual host configuration to the existing 
   configuration in WebSphere. The existing WebSphere configuration is not 
   updated, deleted, or replaced.

   Compare mode displays the differences between virtual host configuration 
   at the current scope in the environment tree and the configuration at the 
   same scope in the WebSphere cell. 

   Promote mode copies virtual host entries from the 
   scope specified in the -opt parameters into the current scope
   passing through a filter.[6][7]

Required Data:

   This action is executed at the current scope and uses configuration 
   data in the vhosts section of the vhosts.xml file at the
   current scope.[2]  

   Augment mode uses the configuration data in the augment/vhosts.xml 
   file.[2][3][4]        

   The configuration for virtual host entries is stored in the vhosts.xml 
   file. For example configuration data, see the vhosts section in the 
   samples:
      
   RAFW_HOME/samples/xml/was/60/vhosts.xml
   RAFW_HOME/samples/xml/was/61/vhosts.xml
   RAFW_HOME/samples/xml/was/70/vhosts.xml
      
   configure.properties at the cell scope defines the following 
   properties: [2]
      WAS_USERNAME          IBM WebSphere Application Server administrator's 
                            user name. 
                            Example: wasbind
      WAS_PASSWORD          IBM WebSphere Application Server administrator's
                            user password.
      BASE_SOAP_PORT        SOAP port for Stand Alone environments.
      ND_SOAP_PORT          SOAP port for Network Deployment environments.
      BASE_WAS_PROF_HOME[5] IBM WebSphere Application Server stand-alone 
                            profile home. 
                            Example: /opt/AppServer/profiles/standAlone
      ND_WAS_PROF_HOME[5]   IBM WebSphere Application Server DMGR profile 
                            home. 
                            Example: /opt/WebSphere/AppServer/profiles/dmgr

Supported Modes:

import, execute, compare, augment, promote

Supported Scopes:

cell

Notes:

   [1] The vhosts.xml file is an automation framework file. 

   [2] The scope is relative to the environment tree path:
       RAFW_HOME/user/environments.
          
       cell path:    ENV_NAME/cells/CELL_NAME
       cluster path: <cell path>/clusters/CLUSTER_NAME 
       node path:    <cell path>/nodes/NODE_NAME 
       server path:  <node_path>/servers/SERVER_NAME  

   [3] The augment mode directory defaults to "augment".
       To override the augment mode directory supply:
          -opt augmentDir=<dir>   
             
   [4] The vhosts_augment.xml file is an automation framework for 
       WebSphere file.
         
   [5] Use BASE_WAS_PROF_HOME  for stand-alone environments at any scope.
           ND_WAS_PROF_HOME    for Network Deployment environments at cell 
                                  scope.

   [6] To promote entries in an augment file, specify 
       the option -opt augmentDir=<dir> and the vhost_augment.xml
       in <dir> will be used during promotion.
             
   [7] Refer to the Rational Automation Framework information center 
       for more information on promote mode filters.