In a Standalone WebSphere installation, there is no need to do anything else in the WebSphere Integrated Solutions Console (ISC). However, in a Network Deployment installation, some extra steps have to be done in the WebSphere ISC.
Resolution
1.Change in the following portal-ext property, adapting it to your Websphere's server name. By default, it is set to server1:
auto.deploy.websphere.wsadmin.app.manager.query=type=ApplicationManager,process=server1,*
In a Network Deployment installation, you should set the name of your Deployment Manager server:
auto.deploy.websphere.wsadmin.app.manager.query=type=ApplicationManager,process=dmgr,*
2. If security is enabled in your WebSphere installation, set the credentials for the Administrator user in the connector's properties file. This will allow the connection from wsadmin to the server to be succesful.
Usually, WebSphere uses SOAP connections from wsadmin to the server. In this case, set these properties in the soap.client.props file:
com.ibm.SOAP.loginUserid=wasadmin
com.ibm.SOAP.loginPassword=password
3. Copy your plugin to Liferay's deploy directory.
4. In a Standalone installation, the deployment is complete. The plugin will be deployed as a Web application into WebSphere and then start.
In a Network Deployment installation, the plugin will de deployed and started in the Deployment manager server. From the Websphere ISC, change the scope of the application to the servers where Liferay is installed.
Additional Information
In a Linux environment, these new features only work with a patch provided by support.
If a plugin needs to be redeployed, the wsadmin Jython script included in the Liferay platform expects the plugin to be started. If the plugin is stopped at Websphere ISC, the autodeploy will fail.