PUBLIC - Liferay Portal Community Edition
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-27657

Use wsadmin so that Liferay running on WebSphere will support hot deploy

    Details

    • Branch Version/s:
      6.1.x, 6.0.x
    • Backported to Branch:
      Committed
    • Business Value:
      5
    • Similar Issues:
      Show 4 results 

      Description

      WAS 6 and 7 do not support hot deploy.

      Add a new property:

      #
      # WebSphere 6 and 7 do not support the ability to hot deploy a WAR. The
      # portal will attempt to use the wsadmin script to install a hot deployed
      # plugin at runtime if this property is set. The wsadmin script uses this
      # property to query the WebSphere application manager. Set this property
      # to a blank value to disable this feature.
      #
      #auto.deploy.websphere.wsadmin.app.manager.query=
      auto.deploy.websphere.wsadmin.app.manager.query=type=ApplicationManager,process=server1,*
      

      Now, Liferay users on WAS 6 and 7 can enjoy hot deploy like all the other app servers.

        Issue Links

          Activity

          Hide
          Denis Signoretto added a comment -

          Actually current implementation don't works on WAS Linux installations. I get this error on Linux.

          com.liferay.portal.kernel.deploy.auto.AutoDeployException: java.io.IOException: Cannot run program "/opt/ibm/websphere/appserver\bin\wsadmin.bat": java.io.IOException: error=2, No such file or directory

          Show
          Denis Signoretto added a comment - Actually current implementation don't works on WAS Linux installations. I get this error on Linux. com.liferay.portal.kernel.deploy.auto.AutoDeployException: java.io.IOException: Cannot run program "/opt/ibm/websphere/appserver\bin\wsadmin.bat": java.io.IOException: error=2, No such file or directory
          Hide
          Kenji Heigel added a comment -

          FAILED Manual Testing using the following steps:

          1. Add the following properties in portal-ext.properties
            auto.deploy.websphere.wsadmin.app.manager.query=type=ApplicationManager,process=server1,*
            
          2. Start Liferay in WebSphere
          3. Drag and drop chat portlet and flash portlet to home/deploy
          4. Check the Update Manager
          5. Go back to liferay.com and try to add the flash portlet to a page

          Failed on:
          WebSphere 7.0 + MySQL 5. Portal 6.0.x EE GIT ID: 23e4b185c8bdb2c40e438d392866a4b46404bd75.
          Plugins 6.0.x EE GIT ID: aa1b89a0b369ddabf07e99750cdc06558decaadf.

          After deploying the chat and flash portlets, the Update Manager shows the portlets' status as "Installation in progress." After waiting for a few minutes, the status still remains the same and portlets are not available. Upon restarting Liferay on WebSphere, checking Update Manager does not show the Chat or Flash portlets at all.

          Fixed on:
          WebSphere 7.0 + MySQL 5.0. Portal 6.1.x EE GIT ID: 4f905fa40f72822a6d243ee99a95795823ad30bb.
          Plugins 6.1.x EE GIT ID: bb15e6019a7b646c3b0160863005be3b2f064e7d.

          Using the same procedure, I tested the deployment in EE 6.1.x. In Update Manager, the portlets' statuses are "Up to Date." The Chat portlet is available, and the Flash portlet can be added to a page.

          Show
          Kenji Heigel added a comment - FAILED Manual Testing using the following steps: Add the following properties in portal-ext.properties auto.deploy.websphere.wsadmin.app.manager.query=type=ApplicationManager,process=server1,* Start Liferay in WebSphere Drag and drop chat portlet and flash portlet to home/deploy Check the Update Manager Go back to liferay.com and try to add the flash portlet to a page Failed on: WebSphere 7.0 + MySQL 5. Portal 6.0.x EE GIT ID: 23e4b185c8bdb2c40e438d392866a4b46404bd75. Plugins 6.0.x EE GIT ID: aa1b89a0b369ddabf07e99750cdc06558decaadf. After deploying the chat and flash portlets, the Update Manager shows the portlets' status as "Installation in progress." After waiting for a few minutes, the status still remains the same and portlets are not available. Upon restarting Liferay on WebSphere, checking Update Manager does not show the Chat or Flash portlets at all. Fixed on: WebSphere 7.0 + MySQL 5.0. Portal 6.1.x EE GIT ID: 4f905fa40f72822a6d243ee99a95795823ad30bb. Plugins 6.1.x EE GIT ID: bb15e6019a7b646c3b0160863005be3b2f064e7d. Using the same procedure, I tested the deployment in EE 6.1.x. In Update Manager, the portlets' statuses are "Up to Date." The Chat portlet is available, and the Flash portlet can be added to a page.
          Hide
          Denis Signoretto added a comment -

          Hi Kenji,

          did you set the property: auto.deploy.websphere.dest.dir=$

          {env.USER_INSTALL_ROOT}

          /liferay/wsadmin-deploy ?
          does the wsadmin-deploy dir exist? (the directory used by websphere deploy scripts to pick up generated war packages)

          Regards,
          Denis.

          Show
          Denis Signoretto added a comment - Hi Kenji, did you set the property: auto.deploy.websphere.dest.dir=$ {env.USER_INSTALL_ROOT} /liferay/wsadmin-deploy ? does the wsadmin-deploy dir exist? (the directory used by websphere deploy scripts to pick up generated war packages) Regards, Denis.
          Hide
          Leonardo Costantini added a comment -

          Hi all,
          I simply think you cannot run this file "/opt/ibm/websphere/appserver\bin\wsadmin.bat"
          It should end with .sh at least on any *nix (opt/ibm/websphere/appserver/bin/wsadmin.sh)
          and, depending how your are calling the execution of the file... maybe you should replace \ with / in the path... (but this could be uneeded...)

          bye,
          Leonardo

          Show
          Leonardo Costantini added a comment - Hi all, I simply think you cannot run this file "/opt/ibm/websphere/appserver\bin\wsadmin.bat" It should end with .sh at least on any *nix (opt/ibm/websphere/appserver/bin/wsadmin.sh) and, depending how your are calling the execution of the file... maybe you should replace \ with / in the path... (but this could be uneeded...) bye, Leonardo

            People

            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:

                Development

                  Structure Helper Panel