Using Maven to deploy to Weblogic clusters

Question

org.codehaus.mojo WebLogic-Maven-plugin 2.9.1

We are currently successfully using the weblogic maven plugin to deploy on our local instances of WebLogic 9.2.

When we try to deploy to a remote environment, we have a problem. We use two clusters with an administration server and a managed server on one machine and another managed server on a separate machine.

When your plugin downloads the application to the administrator server, it does not copy it to the second managed server on a separate computer. This causes the second managed server to be a problem, because it cannot find the application in the place where the administrator server saved it on its own machine.

Configuration below

<configuration> <adminServerHostName>${weblogic.adminServerHostName}</adminServerHostName> <adminServerPort>${weblogic.adminServerPort}</adminServerPort> <adminServerProtocol>${weblogic.adminServerProtocol}</adminServerProtocol> <userId>${weblogic.userId}</userId> <password>${weblogic.password}</password> <upload>${weblogic.upload}</upload> <remote>${weblogic.remote}</remote> <verbose>${weblogic.verbose}</verbose> <debug>${weblogic.debug}</debug> <stage>${weblogic.stage}</stage> <targetNames>${weblogic.targetNames}</targetNames> <exploded>${weblogic.exploded}</exploded> </configuration> <profile> <id>localhost</id> <properties> <weblogic.adminServerHostName>localhost</weblogic.adminServerHostName> <weblogic.adminServerPort>7001</weblogic.adminServerPort> <weblogic.adminServerProtocol>t3</weblogic.adminServerProtocol> <weblogic.userId>weblogic</weblogic.userId> <weblogic.password>weblogic</weblogic.password> <weblogic.upload>false</weblogic.upload> <weblogic.remote>false</weblogic.remote> <weblogic.verbose>true</weblogic.verbose> <weblogic.debug>true</weblogic.debug> <weblogic.stage>false</weblogic.stage> <weblogic.targetNames>AdminServer</weblogic.targetNames> <weblogic.exploded>false</weblogic.exploded> </properties> </profile> <profile> <id>dev</id> <properties> <weblogic.adminServerHostName>******</weblogic.adminServerHostName> <weblogic.adminServerPort>9141</weblogic.adminServerPort> <weblogic.adminServerProtocol>t3</weblogic.adminServerProtocol> <weblogic.userId>******</weblogic.userId> <weblogic.password>******</weblogic.password> <weblogic.upload>true</weblogic.upload> <weblogic.remote>true</weblogic.remote> <weblogic.verbose>true</weblogic.verbose> <weblogic.debug>true</weblogic.debug> <weblogic.stage>true</weblogic.stage> <weblogic.targetNames>dev_cluster01</weblogic.targetNames> <weblogic.exploded>false</weblogic.exploded> </properties> </profile> 

Answer 1

This may not apply because my experience has ever been with WebLogic 10, but ...

Make sure that the cluster is configured correctly, because it must be WebLogic (and not Maven or any plug-in), which is responsible for distributing the deployed application to each managed server. The maven plugin should only ever be deployed to the admin server, and WebLogic handles all the other magic to make sure that every managed server that it knows about also gets the application deployed. I do not think the fact that you are using MOJO matters.

Also, make sure that NodeManager is configured correctly and that it is running. NodeManager (at least on WebLogic 10) is responsible for all communication between nodes. The NodeManager process may freeze or kill on a managed server that is not receiving the application. However, it is unlikely that you tried to deploy from the Admin console, which you stated that you tried in your comments on the original question.

Hope this leads you in the right direction.