wp_common_deploy_portal_war_module
Deploys a war module into the IBM WebSphere Portal. It requires the -w PORTAL_WAR_MODULE argument and it should be performed at the node level on the primary node.
TARGET copies PORTAL_WAR_MODULE.war from <WP_DEPLOYMENT_HOME_DIR[1]>/portlets/media/ to <WP_HOME>/installableApps/
Then it deploys the PORTAL_WAR_MODULE.war using xmlaccess
This action cleans up the IBM WebSphere Portal database before deploying the application. For more details on this action, see the wp_common_deploy_cleanup_wp_db help.
Promote mode copies <PORTAL_WAR_MODULE>.war from the scope specified in the -opt parameters into the current scope without passing through a filter.
Then promote mode copies <PORTAL_WAR_MODULE>.xml from the scope specified in the -opt parameters into the current scope passing through a filter.[7]
Provide values for the following variables:
The war modules should be placed here:
<WP_DEPLOYMENT_HOME_DIR[1]>/portlets/media/PORTAL_WAR_MODULE.war
The PORTAL_WAR_MODULE.xml that describes it should be here:
<WP_DEPLOYMENT_HOME_DIR[1]>/portlets/properties/<PORTAL_WAR_MODULE>
There is a sample PORTAL_WAR_MODULE.xml here:
RAFW_HOME/samples/xml/wp/SampleWarModule.xml
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
execute, promote
node
In <WP_DEPLOYMENT_HOME_DIR[1]>/portlets/properties/<PORTAL_WAR_MODULE>.xml
there is a uid field which must match the uid attribute of portlet-app in
portlet.xml contained in <PORTAL_WAR_MODULE>.war
The uid can be retrieved by looking in the portlet.xml file or by running
wp_common_deploy_web_app in import mode, and then looking in the exported xml
file for the name of the web module. Using wp_common_deploy_web_app to
obtain the uid of the web-app can only be done if the war module has been
previously deployed to the portal.
For more information on the xmlaccess execution, see the xmlaccess
output file:
LOG_HOME/deploy_PORTAL_WAR_MODULE.xml
See also: The IBM WebSphere Portal Information Center
[1] WP_DEPLOYMENT_HOME_DIR path: [6]
clustered environments: <cell path>/clusters/<WP_CLUSTER_NAME>
non-clustered environments: <node path>/servers/<PRIMARY_SERVER>
[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
Information Center for more information on promote mode filters.
After deploying portal war modules to a clustered environment, the
application will not be started. In a clustered environment, run these
actions in a sequence:
was_common_configure_synchronize_nodes
- to synchronize the nodes
wp_common_configure_activate_portlets
- to start the deployed portlet applications
wp_common_deploy_cleanup_wp_db
was_common_configure_synchronize_nodes
wp_common_configure_activate_portlets