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 network configuration. If you have a cluster environment, redeploy the portal EAR file to the Network Deployment machine. Before starting, verify all of the following is true:

  1. The administrative server of the WAS 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 cell, verify the Deployment Manager 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 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 Dmgr to synchronize the update across each node in the cluster. - Invoke the command as follows:

    • UNIX™: ./wsadmin.sh -user admin_user_id -password foo -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 IBM i: 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.

      • foo 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

Secure WSRP by WS-Security for a Producer portal


Previous

Export the modified portal EAR file from the assembly tool

  By defect 288573: Removed backslash from the commands in step 3.


+

Search Tips   |   Advanced Search