Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Redeploying the portal EAR file

After you have modified the portal EAR file for WS-Security token authentication and exported it from the assembly tool, you can now redeploy the file.

Redeploy the portal EAR file, wps.ear, according to your network configuration. If you have a cluster environment, redeploy the portal EAR file to the Network Deployment (ND) machine.

1. The administrative server of the WebSphere Application Server has been started:

   • If your portal runs in a base application server node, make sure that the administration server is running. The default name is server1.
   • If your portal runs in a Network Deployment (ND) cell, make sure that the Deployment Manager (DM) and all node agents are running.
2. You are logged in by using the WebSphere Application Server administrative user ID.

To redeploy the portal EAR file, proceed by the following steps:

1. Delete the original file wps.ear file from the temporary directory where you initially exported it.
2. Copy the modified wps.ear file into the temporary directory.
3. Update the portal EAR file wps.ear by using the wsadmin command. If you have a cluster environment, update the EAR in the Deployment Manager to synchronize the update across each node in the cluster. Make sure that all commands are entered on one line. Invoke the command as follows:

   • Linux: ./wsadmin.sh -user admin_user_id -password admin_password -c '$AdminApp install temp_directory/wps.ear {-update -appname wps -deployejb -deployejb.classpath wps_home/shared/app/wp.base.jar}'
   • i5/OS: wsadmin -profileName profile_root -user admin_user_id -password admin_password -c '$AdminApp install temp_directory/wps.ear {-update -appname wps -deployejb -deployejb.classpath wps_home/shared/app/wp.base.jar}'
   • Windows: wsadmin.bat -user admin_user_id -password admin_password -c "$AdminApp install temp_directory\wps.ear {-update -appname wps -deployejb -deployejb.classpath wps_home\shared\app\wp.base.jar}"

   Where:

   • For i5/OS: profile_root is the name of the WebSphere Application Server profile directory where the portal is installed; for example wp_profile.
   • admin_user_id is the WebSphere Application Server administrator user ID.
   • admin_password is the WebSphere Application Server administrator password.
   • temp_directory is the temporary directory to which you copied the updated portal EAR file. Note: For Windows you might need to use a slash rather than a backslash as a path separator.
   • wps_home is the portal installation directory.
   Note: Updates to the configuration of a portal cluster must occur on the Deployment Manager and be resynchronized with the other nodes in the cluster. If updates are made to individual nodes in the cluster, the updates will be lost when the master configuration on the Deployment Manager resynchronizes with the nodes again.
4. Restart the portal. In a cluster configuration, restart the portal on each node.