[
http://jira.codehaus.org/browse/MWAS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197418#action_197418
]
Josh Joy commented on MWAS-56:
------------------------------
Yup, this is really nice description
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/rxml_taskoptions.html
It also demonstrates how to use the "+" syntax to bind to multiple servers.
In regards to tests, I looked thru the project code, though I can't think of a
nice way to have Integration tests since it requires an IBM HTTP server to bind
to.... do you have any suggestions?
I can say though we have been using this patch for the past 3 weeks with no
issues :)
Heres a sample of how I've configured it for our server. I have a generic
deploy script to be able to plugin in artifact information, then pass that to
the plugin. I use maven-dependency-plugin to get the artifact from our company
repository.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>copy</id>
<phase>compile</phase>
<goals>
<goal>copy</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>${deployable.groupId}</groupId>
<artifactId>${deployable.artifactId}</artifactId>
<version>${deployable.artifactid.version}</version>
<type>${deployable.type}</type>
<overWrite>true</overWrite>
<destFileName>deploy.ear</destFileName>
</artifactItem>
</artifactItems>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>was6-maven-plugin</artifactId>
<version>1.2-SNAPSHOT</version>
<executions>
<execution>
<id>integration-test</id>
<phase>integration-test</phase>
<goals>
<goal>wsDefaultBindings</goal>
<goal>wsUninstallApp</goal>
<goal>installApp</goal>
<goal>wsStartApp</goal>
</goals>
</execution>
</executions>
<configuration>
<was6.virtualHost>default_host</was6.virtualHost>
<verbose>true</verbose>
<wasHome>${was6.home}</wasHome>
<host>${was6.host}</host>
<port>${was6.port}</port>
<conntype>SOAP</conntype>
<earFile>${project.build.outputDirectory}/../dependency/deploy.ear</earFile>
<applicationName>${deployable.artifactId}</applicationName>
<updateExisting>false</updateExisting>
<was6.mapModulesToServers>{"Examples Application"
examples.war,WEB-INF\web.xml
WebSphere:cell=mycell,node=mynode,server=server2+WebSphere:cell=mycell,node=yournode,server=server1}}</was6.mapModulesToServers>
</configuration>
</plugin>
> allow ability when deploying to map to HTTP server and application server
> for module
> -------------------------------------------------------------------------------------
>
> Key: MWAS-56
> URL: http://jira.codehaus.org/browse/MWAS-56
> Project: Maven 2.x WebSphere 6 Plugin
> Issue Type: Improvement
> Affects Versions: 1.2
> Environment: when using IBM HTTP Server
> Reporter: Josh Joy
> Assignee: David J. M. Karlsen
> Attachments: wasv6-maven-plugin.txt
>
>
> when using IBM HTTP Server, there is a Websphere option in the Admin console
> "Map modules to servers". If IBM HTTP Server is setup and configured, there
> is an option to bind to both HTTP Server and the application server. The
> Websphere option is "-MapModulesToServers". This patch provides another
> configuration parameter to the plugin "mapModulesToServers".
> For example, to use it
> <configuration>
> ....
> <was6.mapModulesToServers>{{SOMEWEB SOMEWEB.war,WEB-INF/web.xml
> WebSphere:cell=SOMEHOST-SOMECELL,node=SOMEHTTPSERVER,server=webserver1+WebSphere:cell=SOMECELL,node=SOMENODE,server=server1}}</was6.mapModulesToServers>
> ...
> </configuration>
> These parameters can be found from the Websphere configuration and vary
> server to server. The exact mapping typically can be extraced from the Admin
> Console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
