Action:

wp_common_deploy_release

Summary:

Execute mode: deploys entire IBM WebSphere Portal configuration. Cleans up IBM WebSphere Portal database. For more details, see the help for wp_common_deploy_cleanup_wp_db. Copies all war files from <WP_DEPLOYMENT_HOME_DIR[1]>/portlets/media/ to <WP_HOME>/installableApps/. Deploys all artifacts defined in <RELEASE_FILES_DIR[6]>/release.xml using the xmlaccess tool.

Import mode: imports entire IBM WebSphere Portal configuration. Cleans up IBM WebSphere Portal database. For more details, see the help for wp_common_deploy_cleanup_wp_db. If <RELEASE_FILES_DIR[6]>/release.xml is available, copies it to <RELEASE_FILES_DIR[6]>/release_previous.xml.

Exports IBM WebSphere Portal release to file <RELEASE_FILES_DIR[6]>/release.xml using the xmlaccess tool.

Compare mode: compares generated release file with the previous one in <RELEASE_FILES_DIR[6]>/release.xml.

Promote mode: copies <RELEASE_FILES_DIR[6]>/release.xml from the scope specified in the -opt parameters into the current scope passing through a filter. [8]

Then promote mode copies all war files in <WP_DEPLOYMENT_HOME_DIR[1]>/portlets/media from the scope specified in the -opt parameters into the current scope without passing through a filter.

Required Data:

   Provide values for the following variables:
         
   The war modules should be placed here:
      <WP_DEPLOYMENT_HOME_DIR[1]>/portlets/media

   In <cell path>/configure.properties [7]
      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 [7]
      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 [7]
      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 the xmlaccess execution, please see the xmlaccess 
   output file:
      LOG_HOME/execute_release.xml - for execute mode
      LOG_HOME/env_release.xml - for compare mode
   See also: The IBM WebSphere Portal Information Center
         
   [1] WP_DEPLOYMENT_HOME_DIR path:
       clustered:      
          <cell path>/clusters/<WP_CLUSTER_NAME> [7]
       non-clustered: 
          <node path>/servers/<PRIMARY_SERVER>[7]
 
   [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] RELEASE_FILES_DIR path: [1]
   
       virtual portals: <WP_DEPLOYMENT_HOME_DIR>/virtualportal/<VIRTUAL_PORTAL>
       main portals:    <WP_DEPLOYMENT_HOME_DIR>
           
   [7] 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 
   
   [8] Refer to the Rational Automation Framework 
       Information Center for more information on promote mode filters.

Related Actions:

   wp_common_deploy_cleanup_wp_db
   wp_common_deploy_release_dif