Configure WebLogic JMS Servers

Application Release Automation: Configuring WebLogic JMS Server

This section describes the configuration steps required to configure a WebLogic JMS Server (JMSServer) when using the WebLogic plugin. This configuration is then used during deployment to create/modify the WebLogic JMSServer. A domain can contain zero or more JMSServers; the creation of just one JMSServer is shown here but this is easily extended to multiple JMSServers. The Jython variable JMSServerList is used to pass the list of zero or more JMSServers to be created.

Before you begin

Open or create a new Jython environment-specific configuration file. This file will contain the configuration settings that will describe the WebLogic JMSServer being created. Any change made to the JMSServer properties in this file will be reflected in the JMSServer created/modified by the tool.

About this task

This task creates the minimum set required for the creation of a WebLogic domain. Only one domain may be created per configuration file.

Procedure

Open the environment-specific py file and import the JMSServer template. This pre-populated template is typically populated with default values or None (Jython value for null) or a pre-defined name. The pre-defined names should typically be overridden in the environment-specific py file. Where a None value exists, the tool will preserve the default value setting.

from templates.JMSServerTemplate import *

A pre-requisite is that the configuration for a Domain and an AdminServer have already been completed in the Jython file. Other pre-requisites depend on the configuration parameters used for the JMSServer, such as the Server/Cluster that the resource is targeted to or JDBCResource/FileStore to be used as PersistentStore. Make a copy of the JMSServer Template using the provided deepcopy function and assign an appropriate name to it; it can be any name of your choice. There can be multiple JMSServers objects and we will show afterwards how a list of your JMSServers is created.

JMSServer1 = copy.deepcopy(JMSServerTemplate)

Change the required set of parameters of the JMSServer template copy by accessing the parameters using Jython syntax. The parameters set will reflect the JMSServer configuration that you want to create. Once the JMSServer properties are set, the instance has to be added to the JMSServer list so it's eligible for creation. The list is what is read by the tool.

JMSServerList = [JMSServer1,]

Example

The example below shows the configuration required to create a new JMSServer with the name JMSServer1. We also show the setting of some other JMSServer parameters. Open and view the JMSServer template (JMSServerTemplate.py) file for a list of all the parameters that may be set and to understand the syntax to be used to set each property.

JMSServer1 = copy.deepcopy(JMSServerTemplate)
JMSServer1['Name'] = 'GenericJMSServer'
JMSServer1['Targets'].append({'Name': 'ClusteredManagedServer1', 'Type': 'Servers'})
JMSServer1['PersistentStore'] = 'MV_JDBCStore'

JMSServerList = [JMSServer1,]

What to do next

You can now configure the other domain objects, such as WebLogic JMSSystemResources which are targeted to this JMSServer.