Package com.xebialabs.deployit.plugin.was

The Deployit plugin for WebSphere Application Server.

See:
Description

Package com.xebialabs.deployit.plugin.was Description

The Deployit plugin for WebSphere Application Server.

This is the standard Deployit plugin for functionality related to IBM WebSphere Application Server (further referenced in this documentation as WAS), optionally in combination with Apache web servers >= 2.x. It provides support for WAS-specific components and allows users to deploy applications containing WebSphere resources to a WAS Network Deployment environment.

Supported middleware

This plugin supports WebSphere Application Server (WAS) versions 6.1 to 7.0 in a Network Deployment Configuration.

Requirements

The plugin executes its deployment and configuration tasks by connecting to the target host systems and executing WSADMIN commands there. This implies that the following must be possible:

• creating a connection to the host on which the "deployment manager" is running, using the Host's specified connection methods
• starting [WAS_PROFILE_ROOT]/[DMGR_PROFILE]/bin/wsadmin.sh (or on Windows wsadmin.bat) on the target host server under the user Deployit uses to connect to the host (or the SUDO user, if specified)

In addition, if the plugin is being used in an Apache/WAS environment in order to configure the Apache WebSphere plugin:

• the Apache server must have the correct version of the WAS plugin installed and activated (see IBM reference documentation)
• Apache must be configured to include all *.conf files in a certain directory in its configuration
• it must be possible to create a connection from the Deployit server to the Apache server(s) being administered
• the user under which Deployit connects to the Apache servers (or the SUDO user, if specified) must be able to create, modify and delete files in the Apache configuration directory referred to above
• this user must also be able to stop, start and restart Apache (uses apachectl)

If Deployit is intended to be used to manage existing WAS Clusters (i.e. ones not created by Deployit), the clusters' servers must be named according to the convention clustername_nodename_Cloneindex, e.g. was-cluster_was-node_Clone2.

Components

WAS middleware environments are modelled on the basis of the following Configuration Items (CIs):

• WAS Cell
• WAS Node
• WAS Cluster
• WAS Managed Apache WebServer

Further, the plugin provides CIs for the following WAS-related resources:

• JDBC DataSource
• JMS WebSphere MQSeries Queue Connection Factory
• JMS WebSphere MQSeries Topic Connection Factory
• JMS WebSphere MQSeries Queue
• JMS WebSphere MQSeries Topic

Supported scenarios

The plugin supports:

• the initial deployment, re- and undeployment of deployment packages to/from WAS environments via the WAS Deployment RunBook
• the creating and deletion of Clusters and modification of their settings via the WAS Cluster RunBook
• the creating and deletion of Clusters and modification of their settings via the WAS Managed Apache Web Server RunBook

For details of the exact components supported, sequence in which steps are carried out, limitations etc. please consult the documentation of the appropriate run book.

Mapping

The plugin contains the following Deployable artifacts mappings:

• WAS Ear Mapping maps an EAR to a WAS Cluster
• WAS War Mapping maps a WAR to a WAS Cluster

All WAS-related resources can be mapped wit the WAS resource mapping to:

• A specified WAS Cluster within the target WAS Cell.

Known limitations

The plugin does not currently support

• Installation, maintenance or removal of WebSphere installations and profiles.

If you have questions, comments or feedback please contact the WebSphere development team at XebiaLabs.

Version:

1.2