Redeploying the portal EAR file

After modifying the portal EAR file for WS-Security token authentication, and exporting it from the assembly tool, we can now redeploy the file. For a cluster environment, redeploy the portal EAR file to the Network Deployment (ND) machine.

Before starting, verify:

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

   • If the portal runs in a base application server node, verify the administration server is running. The default name is server1.

   • If the portal runs in a Network Deployment (ND) cell, verify the dmgr (DM) and all node agents are running.

2. You are logged in using the WAS admin user ID.

To redeploy the portal EAR file...

1. Delete the original 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 using wsadmin.

    ./wsadmin.sh -user admin_user_id \
                 -password foo \
                 -c '$AdminApp install /tmp/wps.ear {-update -appname wps -deployejb -deployejb.classpath wps_home/base/wp.base/shared/app/wp.base.jar}' 
   

   For a cluster environment, update the EAR in the dmgr to synchronize the update across each node in the cluster.

   Updates to the configuration of a portal cluster must occur on the dmgr 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 dmgr resynchronizes with the nodes again.

4. Restart the portal.

After completing this task and all previous ones, you have configured security using WS-Security token authentication for using WSRP in the portal.

Parent: Secure WSRP by WS-Security for a Producer portal
Previous: Export the modified portal EAR file from the assembly tool