Package com.xebialabs.deployit.plugin.wls

The Deployit plugin for Oracle WebLogic Server.

See:
Description

Interface Summary

CustomWlsOrders

Class Summary

WlsConventions

A factory for Deployit WLS conventions like filestore paths etc.

Enum Summary

DeploymentStrategy

Several Strategy are available: CLASSIC : stopApp, undeployApp, deployApp,startApp STOP_START : stopServer, undeployApp(s), deployApp(s),startServer SIDE_BY_SIDE : deployApp(s), startApp, wait and stopApp, undeploy * CLASSIC : stopApp, undeployApp, deployApp,startApp

Package com.xebialabs.deployit.plugin.wls Description

The Deployit plugin for Oracle WebLogic Server.

This is the standard Deployit plugin for functionality related to Oracle WebLogic Server, optionally in combination with Apache web servers. It provides support for WebLogic-specific components and allows users to deploy applications containing WebLogic resources to a WebLogic Server environment.

Supported middleware

This plugin supports Oracle WebLogic Server (WLS) versions 9.x to 10.3.

Furthermore, it is possible to deploy packages that make use only of WebLogic Server-related resources to Oracle WebLogic Portal (WLP), Oracle ServiceBus (OSB) and Oracle WebLogic Integration (WLI) platforms.

Requirements

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

• creating a connection to the host on which the admin server(s) of the WLS Domain(s) being administered are running, using the Host's specified connection methods
• starting WLST on the target admin 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/WLS environment in order to configure the Apache WebLogic plugin:

• the Apache server must have the correct version of the WebLogic plugin installed and activated
• 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

Components

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

• WLS Domain
• WLS Cluster
• WLS Server (both Managed and admin}
• Migratable Target

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

• JDBC DataSource
• Mail Sessions
• JMS Server with the option to create either a backing File Store or
• JMS Module
• JMS Queue
• JMS Queue Template
• JMS Queue Connection Factory JDBC Store
• Foreign JMS Server
• Foreign JMS Destination
• Foreign JMS Connection Factory
• Work Manager
• Maximum Thread Constraint

Subdeployments are created automatically as a consequence of targeting JMS resources. They cannot be created independently.

In environments where WLS is combined with Apache (e.g. if JEE applications running in WLS are to be "fronted" by web servers), the plugin also supports application-specific configuration of the Apache WebLogic plugin. This is accomplished by including an com.xebialabs.deployit.plugin.wls.ci.ApacheHttpdWlsPluginConfiguration CI with the relevant settings in the deployment package.

Supported scenarios

The plugin supports

• the initial deployment, re- and undeployment of deployment packages to/from WLS environments via the WLS Deployment runbook
• the creating and deletion of Managed Servers and modification of their settings via the WLS Server runbook

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

Mapping

EARs, WARs, EJB JARs and shared libraries in a deployment package can be mapped to:

• a specified domain in the target environment
• a specified cluster within the target domain
• a specified server (incl. the admin server) within the target domain

If the target environment contains Apache web servers and the deployment package contains Apache WebLogic Plugin configuration(s), each plugin configuration may be targeted at one or web servers.

JDBC DataSources and Mail Sessions can be targeted to:

• a specified cluster within the target domain
• a specified server (incl. the admin server) within the target domain

JMS Servers can be mapped to:

• a Managed Server within the target domain
• a Migratable Target within the target domain

JMS Resources can be mapped to:

• a JMS Server within the target domain

Known limitations

The plugin does not currently support

• installation, maintenance or removal of Oracle WebLogic Server itself
• modification or deletion of domains
• creation, modification or deletion of clusters

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