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.

Before you start this task, make sure that all of the following is true:

1. The administrative server of the WAS has been started:

   • If the portal runs in a base appserver node, make sure that the administration server is running. The default name is server1.

   • If the 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 WAS administrative user ID.

To redeploy the portal EAR file...

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:

   UNIX: ./wsadmin.sh -user admin_user_id -password admin_password -c '$AdminApp install temp_directory/wps.ear {-update -appname wps -deployejb -deployejb.classpath wps_home/base/wp.base/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/base/wp.base/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\base\wp.base\shared\app\wp.base.jar}"

   Where:

   • For i5/OS:

     profile_root is the name of the WAS profile directory where the portal is installed; for example wp_profile.

   • admin_user_id is the WAS administrator user ID.

   • admin_password is the WAS administrator password.

   • temp_directory is the temporary directory to which you copied the updated portal EAR file.

     For Windows you might need to use a slash rather than a backslash as a path separator.

   • wps_home is the portal installation directory.

   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.

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

Parent topic:

Secure WSRP by WS-Security for a Producer portal

Previous topic:

Export the modified portal EAR file from the assembly tool

---