Package com.xebialabs.deployit.plugin.osb

The Deployit plugin for Oracle Service Bus.

See:
Description

Package com.xebialabs.deployit.plugin.osb Description

The Deployit plugin for Oracle Service Bus.

This is the standard Deployit plugin for functionality related to Oracle Service Bus (further referenced in this documentation as OSB). It provides support for WebLogic OSB-specific components and allows users to import and customize OSB resources to a WebLogic Deployment environment.

Supported middleware

This plugin supports Oracle Service Bus (OSB) version 3.0

Requirements

The plugin executes its import and customization 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 OSB(which is also a WLS domain) 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

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

• Osb Domain
• Osb Jar
• Osb Jar Mapping
• Osb Customization File

Supported scenarios

The plugin supports all the standard WLS scenarios, and the following ones in addition to that:

• importing of the OSB jar(the deployment step), deletion of the imported OSB jar(the undeployment step) and customization of resources present in the OSB jar via the OSB Deployment 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

The plugin supports all the standard WLS mappings. In addition to that OsbJar in a deployment package can be mapped to:

• a specified OSB domain in the target environment

Known limitations

In addition to the limitations known for the WLS limitations, the following limitation applies for OSB plugin:

• it does not currently support modification or deletion of OSB domains
• since the import or customization of the OSB jar is done after the deployments of other packages present in the same deployment package, there might be a time-window when certain OSB-dependent package (already deployed successfully in previous steps) doesn't work. Once import/customization of the OSB jar is complete, these OSB dependent deployed packages should start to work again.

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

Version:

1.2