Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-36116

During deployment Liferay does not take into account the WebSphere A.S. process it is running on.

    Details

      Description

      Given:
      -WebSphere profile containing two or more "WebSphere application servers" (process)
      -Liferay portal running on an process (AS instance) different from the default one (ex. server2)

      Liferay is not able to hot deploy plugins properly.

      Note: deploying plugin on multiple WAS processes has its rules: plugin can not be deployed under the same name. Therefore, the same plugin has to be deployed under different name. Furthermore, we should be able to pass different properties to wsadmin script, to we can connect to desired server; for example, to use different port.

      Example:

      auto.deploy.dest.dir=${liferay.home}/websphere-deploy
      auto.deploy.websphere.wsadmin.app.manager.query=type=ApplicationManager,process=server2,*
      
      # NEW PROPERTIES
      auto.deploy.websphere.wsadmin.app.name.suffix=server02
      auto.deploy.websphere.wsadmin.properties.file.name=/path/WebSphere/AppServer/profiles/AppSrv05/properties/wsadmin2.properties
      

      Attached is the wsadmin2.properties; changed only the port to connect to.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  6 years, 10 weeks, 4 days ago

                  Packages

                  Version Package
                  6.1.2 CE GA3
                  6.1.30 EE GA3
                  6.2.0 CE M6