WebSphere Deployer Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID websphere-deployer Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
1.2
Jan 18, 2014
1.509.4
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Greg Peters (id: n/a)
Usage Installations 2013-Nov 19
2013-Dec 37
2014-Jan 69
2014-Feb 136
2014-Mar 157

This is a collection of two separate plugins that provide deployment functionality to most versions of IBM WebSphere Application Server and IBM WebSphere Liberty Profile.

Plugin Features

  • Deployment to a running remote or local instance of WebSphere 6.0.x - 8.5.x
  • Deployment to a running remote or local instance of WebSphere Liberty Edition 8.x.x
  • Support for deployments when SSL is activated on WebSphere (Global Security)
  • Support for most versions of WebSphere (Liberty,ND,Extreme Scale, Express, Standard, etc...)
  • Support for deploying to different WebSphere instances/types per build
  • Support for node, cell, and server level deployments
  • Support for pre-compiling JSPs on WebSphere during deployment (When stress testing as part of build process)
  • Support for disabling JSP reloading (When stress testing as part of build process)
  • Support for not starting application after deployment
  • Supports fully stopping, uninstalling, installing and starting application during deployment process
  • Smart detection of existing deployed application state (to prevent failures when a system admin stops your application without you knowing)

Configuration Steps

You will most likely run out of PermGen space if you're using the default JVM values on your application server/servlet container that's hosting Jenkins (Please update your JVM memory requirements).

  • NOTE: Make sure the application server/servlet container is not running Jenkins as 'root' user. This can cause file permissions issues with maven or other tools and prevent deployable artifacts from making it to the final build location. You can try, but it may not work correctly.

Deploying to IBM WebSphere Liberty Profile
Deploying to IBM WebSphere Application Server

Required Libraries For Deployments To IBM WebSphere Application Server

Jar File Source Location Destination Required
com.ibm.ws.admin.client_*.jar
$WAS_INSTALL_ROOT/runtimes $USER_HOME/.jenkins/plugins/websphere-deployer/WEB-INF/lib

Yes
com.ibm.ws.orb_*.jar (if not IBM JRE) $WAS_INSTALL_ROOT/runtimes $USER_HOME/.jenkins/plugins/websphere-deployer/WEB-INF/lib Yes (otherwise 'No' if running under IBM J9 JRE)

Required Libraries For Deployments To IBM WebSphere Liberty Profile

Jar File Source Location Destination Required
com.ibm.websphere.appserver.api.basics_*.jar $LIBERTY_INSTALL_ROOT/dev/api/ibm $USER_HOME/.jenkins/plugins/websphere-deployer/WEB-INF/lib Yes
com.ibm.websphere.appserver.api.endpoint_*.jar $LIBERTY_INSTALL_ROOT/dev/api/ibm $USER_HOME/.jenkins/plugins/websphere-deployer/WEB-INF/lib Yes
com.ibm.websphere.appserver.api.restConnector_*.jar $LIBERTY_INSTALL_ROOT/dev/api/ibm $USER_HOME/.jenkins/plugins/websphere-deployer/WEB-INF/lib
Yes
restConnector.jar $LIBERTY_INSTALL_ROOT/clients $USER_HOME/.jenkins/plugins/websphere-deployer/WEB-INF/lib
Yes

FAQ

1) Why does my test connection connect successfully but my install/upload fails?

    The connection simply uses IBM standard APIs to connect via JMX over the specified SOAP port, when deploying an artifact, the artifacts are uploaded using the WebSphere Administration Console via an HTTP/S connection. This upload is performed by the IBM APIs behind the scenes.

    a). Make sure you can ping the administration console via IP address, long DNS & short DNS within your domain (Reference: http://www-01.ibm.com/support/docview.wss?uid=swg21450962)
    b). Make sure the certificate used by the WebSphere Administration Console(i.e. https://<websphere:9043/ibm/console) is trusted by the server that Jenkins is running under
    c). Make sure you can telnet to the the WebSphere Administration Console port (typically 9043). This is the port used for uploading artifacts to WebSphere

Issues or Feature Requests

Go to: https://issues.jenkins-ci.org/
Select the 'WebSphere Deployer' component

Roadmap

  • Fix path issue when locating artifacts to deploy
  • Provide support for Liberty Profile (support confirmed, will be available soon)
  • Provide support for EAR/WAR/WAB/OSGI deployments to Liberty Profile (support confirmed, will be available soon)
  • Remove external dependency on client jars for each configuration (to simplify initial configuration)
  • Send notifications when application fails to start (outside of build process)
  • Add cluster support (release v1.3)
  • Support for WAR deployments on WebSphere Application Servers (Full Profile)

Change Log

Version 1.2

Support for WebSphere Liberty Profile
Fixed path issues with WebSphere Application Server (full profile)

Version 1.1

Initial release performed

Version 1.0

Beta Testing Passed for WebSphere v8.5.5 for both remote and local deployments

Labels

Edit
plugin-post-build plugin-post-build Delete
plugin-notifier plugin-notifier Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment