Portlet deployment error

Resolve a portlet deployment error that occurred while upgrading IBM® Sametime® Gateway 9.0.1 to FP1.

About this task

If the portlet redeploy process fails because it cannot copy the file RTCAdminPortlet.was to its new location, you might receive the message 0 files were copied during the upgrade. You can often resolve the problem by running the reDeploySTGW script again.

If rerunning the script does not resolve the problem, it might be due to the portlet being only partially removed. For example, the DMGR process might have retained one or more JAR files in the portlet directory's isclite.ear\RTCAdminPortlet.war\WEB-INF\lib subdirectory. In this case, the portlet cannot be deployed because the Integrated Solutions Console repository retains the previous registration, and the duplicate application error is produced.

Resolve the problem by removing, and then reinstalling, the administration console portlet.

Procedure

  1. Change to the WAS_INSTALL\AppServer\bin directory.
  2. Remove the administrative console by running the following command:
    • Linux™: wsadmin.sh -f deployConsole.py remove
    • Windows™: wsadmin.bat -f deployConsole.py remove
  3. Install the administrative console by running the following command:
    • Linux: wsadmin.sh -f deployConsole.py install
    • Windows: wsadmin.bat -f deployConsole.py install
  4. Install the Sametime Gateway Administration portlet by running the following command:
    • Linux: wsadmin.sh -f installPortlet.jacl
    • Windows: wsadmin.bat -f installPortlet.jacl
  5. Restart the WebSphere® Application Server (for a standalone server) or the deployment manager (for a clustered environment).