Action: wp_common_deploy_global_settings

Summary:
   Manages the IBM WebSphere Portal global settings.
      
   Execute: Deploys all global settings defined in 
            <WP_DEPLOYMENT_HOME_DIR[1]>/release_segments/global_settings.xml 
            to the IBM WebSphere Portal.
      
   Import: Imports all global settings to the 
           <WP_DEPLOYMENT_HOME_DIR[1]>/release_segments/global_settings.xml 
           from IBM WebSphere Portal.
      
   Compare: Compares the current action configuration on IBM WebSphere Portal 
            with the previous saved configuration.
      
   Promote: Copies global_settings.xml from 
            <SOURCE_WP_DEPLOYMENT_HOME_DIR[1]>/release_segments
            to <WP_DEPLOYMENT_HOME_DIR[1]>/release_segments
            passing through a filter.[7]
   
Required Data:
   Specify -v <VIRTUAL_PORTAL> to target a specific virtual portal.
      
   Provide values for the following variables:
      
   In <cell path>/configure.properties [6]
      WP_VERSION    IBM WebSphere Portal version. Example: 61
      WP_USERNAME   IBM WebSphere Portal admin user name. Example: wpsbind
      WP_PASSWORD   IBM WebSphere Portal admin user password.
         
   In <node path>/install.properties [6]
      HOST_NAME          Target host name.
      WP_HOME[2]         The installation path of IBM WebSphere Portal. 
                         Example: /opt/IBM/WebSphere/PortalServer
      WAS_PROF_HOME[3]   IBM WebSphere Application Server profile path. 
                         Example: /opt/IBM/WebSphere/profiles/node01
      WAS_HOME           Installation path of IBM WebSphere Application 
                         server. Example: /apps/WebSphere/AppServer
         
   In <node path>/configure.properties [6]
      WP_CONTEXT_ROOT     IBM WebSphere Portal context root for login. 
               Pattern: http://<hostname>:<port>/<context_root>/portal
      WP_CLUSTER_NAME[4]  The IBM WebSphere Portal cluster name. 
                          Example: portal_cluster
      PRIMARY_SERVER[5]   The primary server name on this node. 
                          Example: WebSphere_Portal

Supported Modes: 
   import, execute, compare, promote

Supported Scopes:
   node

Notes:
   For more information on xmlaccess execution, see the xmlaccess 
   output file:
      LOG_HOME/global_settings.xml - for execute mode
      LOG_HOME/env_global_settings.xml - for compare mode
   See also: IBM WebSphere Portal Information Center 
          
   [1] WP_DEPLOYMENT_HOME_DIR path:
       clustered:      
          <cell path>/clusters/<WP_CLUSTER_NAME> [6]
       with virtual portal:  
          <cell path>/clusters/<WP_CLUSTER_NAME>/virtualportal/<VIRTUAL_PORTAL> [6]
       non-clustered: 
          <node path>/servers/<PRIMARY_SERVER>[6]
       with virtual portal: 
          <node path>/servers/<PRIMARY_SERVER>/virtualportal/<VIRTUAL_PORTAL>[6]
   [2] Required for IBM WebSphere Portal 6.0
   
   [3] Required for IBM WebSphere Portal 6.1
   
   [4] Required for clustered environments.
   
   [5] Required for non-clustered environments.
   
   [6] 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
          
   [7] Refer to the Rational Automation Framework for WebSphere 
       Information Center for more information on promote mode filters.