The Configuration Wizard and WLST Offline support autoconfiguration for single-cluster domains. When creating two clusters, you need to manually correct the targets assigned for the resources, services, and applications, as illustrated in Example: How to Configure a Multi-Cluster Platform Domain Using WLST Offline.

Adding Application Resources Required by the WebLogic Workshop Runtime

If Web services are configured to support asynchronous requests, WebLogic Workshop creates asynchronous request and error queues in the development environment to handle the requests. For each pair of queue elements, you must create a pair of corresponding JMS queues on the target server, and associate the asynchronous error queue with the asynchronous queue.

WebLogic Workshop defines the asynchronous queues in the /META-INF/wlw-manifest.xml file with the following element names: <con:async-request-queue> and <con:async-request-error-queue>. The queues are named using the following format: web_app.queue.AsyncDispatcher and web_app.queue.AsyncDispatcher_error, where web_app specifies the name of the Web application.

If the target domain is clustered, you must configure the queues as distributed queues. If you are using multiple clusters, you must create an additional set of queues for each cluster.

Note: When you use WLST Offline to create the queues in a domain, the tool automatically configures each queue as a distributed queue and creates associated member queues on each Managed Server in the cluster. This must be done when creating the domain and before the cluster is created; this feature is not supported when updating an existing domain. For more information, see Autoconfiguration Using the Configuration Wizard and WLST Offline.

For an example of setting asynchronous dispatcher queues, see Configure the Asynchronous Dispatcher Queues Required by the Application.

You can configure the server dispatch policy for asynchronous requests using the <async-dispatch-policy> element in the wlw-config.xml configuration file. The <async-dispatch-policy> element associates a project's asynchronous requests with a server-defined dispatch policy. The dispatch policy designates which server execute thread pool the EJB should run in. The value provided for this element is used to generate an <async-dispatch-policy> entry in the weblogic-ejb-jar.xml configuration file for the AsyncDispatcher and AsyncErrorDispatcher message-driven beans. For more information, see the <asynch-dispatch-policy> element description in WebLogic Workshop Online Help.

Configuring Servers to Start in Production Mode

Set the startup mode to prod. For information about the differences between development and production modes, see Differences Between Configuration Startup Modes in Creating WebLogic Configurations Using the Configuration Wizard. For an example of configuring the server startup mode, see Set Domain Options.

Setting the SDK

Set the SDK to one that is supported on the platform you are using, and that is optimized for production-level performance. Ensure that you configure the same SDK across all server instances in a cluster. For a list of the Java SDKs that are supported for a specific platform, see Supported Configurations for WebLogic Platform 8.1. For an example of configuring the SDK see Set Domain Options.

Setting Up the Managed Servers on Remote Machines

Once you have configured the target domain, you need to set up the Managed Server directories on remote machines and optionally configure Node Manager.

• Setting Up the Managed Server Directories
• Configuring the Managed Server Start Attributes
• Configuring Node Manager

Setting Up the Managed Server Directories

To set up the Managed Server directories that run on remote machines:

If you will not be using Node Manager to manage a remote Managed Server, create a domain on that server. Ensure that you configure the same JDK across all server instances in a cluster and that you set the mode to prod.

If you will be using Node Managed, a remote Managed Server directory does not require the complete set of files that are located in the Administration Server directory, as the Administration Server maintains the configuration information for all Managed Servers within a domain.

If you use WebLogic Workshop wlw-runtime-config.xml configuration file, you must copy it to the root directory of each Managed Server in the cluster.
Ensure the key stores for the following security services are made available to the Managed Server.

Security Service Requiring Key Stores	Description
WebLogic Server security	Enables SSL transport traffic. For more information about WebLgoic Server security, see: "Secure Sockets Layer (SSL)" in Security Fundamentals in Introduction to WebLogic Security Configuring SSL in Managing WebLogic Security
Web service security	Enables message-level security for Web services. You must also ensure that the related WSSE policy files are made available to the Managed Servers. For more information about Web service security, see: Web Service Security in WebLogic Workshop Online Help "Overview of Web Services Security" in Configuring Security in Programming WebLogic Web Services Building a Secure Web Service using BEA's WebLogic Workshop at: http://dev2dev.bea.com/products/wlworkshop81/articles/sws_wlw.jsp
WSRP security	Enables security for the Web Services for Remote Portlets (WSRP) feature of WebLogic Portal. By default, the WSRP security keystore is stored in the wsrpKeystore.jks file. For more information about WSRP security, see Establishing WSRP Security in Using WSRP With WebLogic Portal.
Trading Partner security	Enables the security for Trading Partners. For more information, see Trading Partner Integration Security in Introducing Trading Partner Integration.


 

Configuring the Managed Server Start Attributes

You need to configure the ServerStart attributes for each Managed Server if you want to start the Managed Server remotely using Node Manager.

The following table defines the attributes that need to be set for each Managed Server. For information about the start attributes that can be set for a server using the WebLogic Server Administration Console, see ServerStart in WebLogic Server Configuration Reference.

The following table identifies the required CLASSPATH settings for the default domains.

Note: The classpath value may differ from that defined in the table, depending on your environment. To access the CLASSPATH information for your environment, start the Administration Server and capture the CLASSPATH information that displays to the command window (stdout).

Configuring Node Manager

Node Manager enables you to perform common operations for a Managed Server, regardless of its location with respect to its Administration Server. You can use Node Manager to perform the following operations:

• Start and stop remote Managed Servers.
• Monitor the health of Managed Servers and automatically kill server instances whose health state is "failed."
• Automatically restart Managed Servers that have failed, or have shutdown unexpectedly due to a system crash or reboot.

To take advantage of Node Manager capabilities, you must run a Node Manager process on each machine that hosts Managed Servers, and configure Node Manager to:

• Accept commands from a remote host

For example, you must configure a machine to use Node Manager and specify a value other than localhost for the listen address, as described in Considerations for Configuring and Targeting Resources.

• Support production security components
• Tailor the shutdown and monitoring behavior

For complete details about each of the steps required to configure Node Manager in a production environment, see "Configuration Checklist (Production Environment)" in "Configuring Node Manager" in Configuring, Stopping, and Starting Node Manager in Configuring and Managing WebLogic Server.

Example: How to Configure a Single-Cluster Platform Domain Using WLST Offline

The following example illustrates how to create a WebLogic Platform domain that contains a single cluster, as illustrated in Single-Cluster Platform Domain Example, using WLST Offline.

Steps include:

• Define WLST Variables
• Open the Template for Domain Creation
• Configure an Administrative Username and Password
• Configure the Administration Server
• Configure the Asynchronous Dispatcher Queues Required by the Application
• Configure the JDBC Connection Pools
• Configure the Cluster, Managed Servers, and Machines
• Set Domain Options
• Write the Domain and Close the Template

For more information about WLST Offline, see the documentation and examples provided with the WLST Offline kit at the following URL: https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=97

Define WLST Variables

You can define variables in the WLST Offline script and reference them using the WLST Offline commands to facilitate reuse of the scripts in different target environments. For example, you can "hard-code" the variable values within the script or pass the values to the WLST Offline script from the command line.

For example, if you define the following variables within the WLST Offline script to specify the WebLogic home directory, domain name, and domain template name:

weblogic_home="/bea/weblogic81"
domain_template="platform.jar"

You can then reference the variables in the script instead of the values. For example:

readTemplate(weblogic_home + '/common/templates/domains'+ domain_template)

Note: For readability, the following code excerpts use actual values and not variables.

Open the Template for Domain Creation

The following code excerpt opens the Basic WebLogic Platform Domain template for domain creation and sets the name of the domain using the cmo variable. The cmo variable stores the Current Management Object, which is set to the configuration bean instance to which you navigate using WLST Offline—in this case the root of all configuration management objects, DomainMBean.

readTemplate('/bea/weblogic81/common/templates/domains/platform.jar')

Configure an Administrative Username and Password

The following code excerpt sets the password for the pre-configured administrative account.

cd('/Security/platform/User/weblogic')
cmo.setPassword('password')

Configure the Administration Server

The following code excerpt configures the Administration Server by setting the listen address and port, enabling SSL, and setting the SSL port. To review considerations for configuring the Administration Server, see Considerations for Configuring and Targeting Resources.

cd('/Server/cgServer')
cmo.setListenAddress('host')
cmo.setListenPort(9301)

cd('SSL/cgServer')
cmo.setEnabled(1)
cmo.setListenPort(9302)

Configure the Asynchronous Dispatcher Queues Required by the Application

The following code excerpt configures a set of asynchronous dispatcher queues and their associated error queues, as required by the application. To determine if you need to create asynchronous dispatcher queues, review the contents of the wlw-manifest.xml file, which provides information about the server resources referenced by the application, as described in Adding Application Resources Required by the WebLogic Workshop Runtime.

  queueNames = 'IntApp.queue.AsyncDispatcher', \
    'PortApp.queue.AsyncDispatcher'

  # Predefined  JMS Server included in the domain template
  cd ('/JMSServer/cgJMSServer') 

  for qName in queueNames:
    errqName = qName + "_error"
    
    # Create asynchronous dispatcher error queue
    create(errqName, 'JMSQueue')
    cd ('JMSQueue/' + errqName)
    cmo.setJNDIName(errq	Name)
    errqMBean = cmo
    cd ('../..')

    # Create asynchronous dispatcher queue
    create(qName, 'JMSQueue')
    cd ('JMSQueue/' + qName)
    cmo.setJNDIName(qName)

    # Associate asynchronous dispatcher error queue
    cmo.setErrorDestination(errqMBean)
    cd ('../..')

Configure the JDBC Connection Pools

The following code excerpt configures the database type and related information to specify the production database for each of the four default JDBC connection pools, including bpmArchPool, cgJMSPool-nonXA, cgPool, and portalPool. To review considerations for configuring JDBC connection pools, see Considerations for Configuring and Targeting Resources.

cd ('/JDBCConnectionPool')
nonXApools = 'cgJMSPool-nonXA',
for pool in nonXApools:
   cd (pool)
   cmo.setDriverName('oracle.jdbc.driver.OracleDriver')
   cmo.setUserName('username')
   cmo.setPassword('password')
   cmo.setDbmsHost('myDBHost')
   cmo.setDbmsPort('1521')
   cmo.setDbmsName('myDB')
   cd ('..')

XApools = 'cgPool', 'bpmArchPool', 'portalPool'
for pool in XApools:
  cd (pool)
  cmo.setDriverName('oracle.jdbc.xa.client.OracleXADataSource')
  cmo.setUserName(`user')
  cmo.setPassword(`password')
  cmo.setDbmsHost('myDBHost')
  cmo.setDbmsPort('5321')
  cmo.setDbmsName('myDB')
  cmo.setSupportsLocalTransaction(1)
  cmo.setKeepXAConnTillTxComplete(1)
  cd ('..')

Configure the Cluster, Managed Servers, and Machines

The following code excerpt performs the following tasks:

• Configures one cluster.
• Configures two machines.
• Configures the Node Manager name, listen address, start properties—including BEA_HOME, JAVA_HOME, the directory root, and the CLASSPATH values—and the file containing the security policy for starting the server. For more information about configuring Node Manager, see Configuring Node Manager.
• Configures four Managed Servers, targeting them to a machine, and enables SSL to enable secure access to application resources.
• Tunes the default execution threads. For more information, see Tuning the Default Execute Queue Threads in WebLogic Server Performance and Tuning.

cd ('/')
# Define the servers
clusterConfig = 'platformCluster','multicast_addr',9101
ms1 = 'ms1','host1',9111,9112,'machine1'
ms2 = 'ms2','host2',9121,9122,'machine2'
ms3 = 'ms3','host3',9131,9132,'machine1'
ms4 = 'ms4','host4',9141,9142,'machine2'
mss = ms1, ms2, ms3, ms4

#Create the cluster
cl_name, mc_addr, mc_port = clusterConfig
cluster = create(cl_name, 'Cluster')

#Configure the machines
machine = None
prev_ms_machine = ""
cl_addr = ""
for msConfig in mss:
   ms_name, ms_addr, ms_port, ms_ssl_port, ms_machine = msConfig
   if ms_machine != "" and ms_machine != prev_ms_machine:
     prev_ms_machine = ms_machine
     machine = create(ms_machine, 'Machine')

     #Configure the Node Manager name and listen address
     cd('Machine/' + ms_machine + '/NodeManager/' + ms_machine)
     cmo.setName(ms_machine)
     cmo.setListenAddress(ms_addr)
     cd('../../../..')

   #Configure the Managed Server, target it to a machine 
   ms = create(ms_name,'Server')
   
   cd('Server/' + ms_name)
   cmo.setListenAddress(ms_addr)
   cmo.setListenPort(ms_port)
   if machine != None:
      cmo.setMachine(machine)
   cd('SSL/' + ms_name)
   cmo.setEnabled(1)
   cmo.setListenPort(ms_ssl_port)
   cd('../..')
   assign('Server', ms_name, 'Cluster', cl_name)

   # Configure Node Manager StartServer properties
   create(ms_name, 'ServerStart')
   cd('ServerStart/' + ms_name)
   cmo.setBeaHome('/bea')
   cmo.setJavaHome('/bea/weblogic81/jrockit81sp4_142_05')
   cmo.setRootDirectory('/bea/user_projects/domains/platform')
   # See Table 3-4 for CLASSPATH settings
   cmo.setClassPath(`classpath')
   cmo.setSecurityPolicyFile('/bea/weblogic81/server/lib/weblogic.policy')
   cmo.setArguments('-Xms512m -Xmx512m -da -Dwlw.iterativeDev=false
 -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.ProductionModeEnabled=true')
   cmo.setUsername('user')
   cmo.setPassword('password')

   cd('../..')
   # Tune execution threads
   cd('ExecuteQueue/weblogic.kernel.Default')
   cmo.setThreadCount(15)
   cmo.setThreadsIncrease(5)

   cd('../..')
   # Accumulate addresses and ports for setting cluster address
   cl_addr = cl_addr + ms_addr + ':' + str(ms_port) + ','

# Set the cluster address, multicast address, and multicast port
cl_addr = cl_addr[:-1] # slice off trailing','
cluster.setClusterAddress(cl_addr)
cluster.setMulticastAddress(mc_addr)
cluster.setMulticastPort(mc_port)

Configure the Web Proxy Server

The following code excerpt configures the Web proxy server. For more information, see Using Load Balancers and Web Proxy Servers.

create('platproxy','Server')
cd('/Server/platproxy')
cmo.setListenAddress('host')
cmo.setListenPort(9431)
# Set this server as the proxy server for the cluster
cd ('/Cluster/platformcluster')
cmo.setProxyServer('platproxy')

Set Domain Options

The following code excerpt sets the following domain options:

• CreateStartMenu—Specifies whether to create a Start Menu shortcut on a Windows platform.
• JavaHome—Specifies the home directory for the SDK to be used when starting the server.
• OverwriteDomain—Specifies whether to allow an existing domain to be overwritten. The default is false.
• ServerStartMode—Specifies the mode to use when starting the server for the newly created domain. This value can be dev (development) or prod (production). This value should be set to prod.

setOption('OverwriteDomain','true')
setOption('CreateStartMenu','false')
setOption('ServerStartMode','prod')
setOption('JavaHome','/bea/weblogic81/jrockit81sp4_142_05')

Write the Domain and Close the Template

The following code excerpt writes the domain to the specified directory and closes the configuration template.

writeDomain('/bea/user_projects/domains/platform')
closeTemplate()

Example: How to Configure a Multi-Domain Environment Using WLST Offline

This section describes how to configure an environment that consists of two domains—a Basic WebLogic Integration Domain and a Basic WebLogic Portal Domain—as illustrated in Multi-Domain Example.

Steps include:

• Create the Basic WebLogic Integration Domain
• Create the Basic WebLogic Portal Domain

For more information about using WLST Offline, see the documentation and examples provided with the WLST Offline kit at the following URL: https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=97

Create the Basic WebLogic Integration Domain

The process used to configure the Basic WebLogic Integration domain using WLST Offline is similar to the process illustrated in Example: How to Configure a Single-Cluster Platform Domain Using WLST Offline, with the following exceptions:

• When opening the template to create the domain, as described in Open the Template for Domain Creation, specify the Basic WebLogic Integration Domain template. For example:

readTemplate('/bea/weblogic81/common/templates/domains/wli.jar')

• When configuring the asynchronous dispatcher queues required by the application, as described in Configure the Asynchronous Dispatcher Queues Required by the Application, define the queueNames list as follows:

queueNames = 'IntApp.queue.AsyncDispatcher',

• When configuring the JDBC connection pools, as described in Configure the JDBC Connection Pools, define the XA connection pools list as follows:

XApools = 'cgPool', 'bpmArchPool'

Create the Basic WebLogic Portal Domain

The process used to configure the Basic WebLogic Portal domain using WLST Offline is similar to the process illustrated in Example: How to Configure a Single-Cluster Platform Domain Using WLST Offline, with the following exceptions:

• When opening the template to create the domain, as described in Open the Template for Domain Creation, specify the Basic WebLogic Portal Domain template. For example:

readTemplate('/bea/weblogic81/common/templates/domains/wlp.jar')

• When configuring the asynchronous dispatcher queues required by the application, as described in Configure the Asynchronous Dispatcher Queues Required by the Application, define the queueNames list as follows:

queueNames = 'PortApp.queue.AsyncDispatcher',

• When configuring the JDBC connection pools, as described in Configure the JDBC Connection Pools, define the XAPools list as follows:

XApools = 'cgPool', 'portalPool'

Example: How to Configure a Multi-Domain Environment Using the Configuration Wizard in Silent Mode

Clusterizing End2End on WebLogic Platform 8.1 on the dev2dev Web site provides an example of configuring a target domain using the Configuration Wizard in silent mode. You can access this article, and download its associated samples files at: http://dev2dev.bea.com/products/wlplatform81/articles/clusterizing_E2E.jsp

Note: Code samples and utilities are posted on dev2dev for your convenience. They are not products supported by BEA.

This article describes how to promote and extend the WebLogic Platform Tour from a development to a production environment, and describes how to configure the following two domains using the Configuration Wizard silent mode:

• WebLogic Portal domain for hosting WebLogic Portal applications
• WebLogic Integration domain for hosting WebLogic Integration applications

Note: This environment is depicted in Multi-Domain Example.

To view the Configuration Wizard silent mode scripts, download the E2ECluster.zip file that contains the sample code and extract the following files:

• integration_cluster_domain.cws—Creates a clustered domain for the sample using the Basic WebLogic Integration Domain template.
• portal_cluster_domain.cws—Creates a clustered domain for the sample using the Basic WebLogic Portal Domain template.

Note: The scripts are designed to be called from an Ant script. They reference properties, such as @DOMAIN_TEMPLATE@, that are resolved in a properties file imported to the Ant script. Using Ant scripting and properties in this way facilitates automation and reuse of the scripts in different target environments.

Example: How to Configure a Multi-Cluster Platform Domain Using WLST Offline

When you want to configure more than one cluster in a WebLogic Platform domain, you must explicitly retarget some of the resources, services, and applications. You must do this because of the following:

• The Configuration Wizard and WLST Offline support autoconfiguration for a single-cluster domain only. Autoconfiguration for a second cluster is not supported.
• There can be only one WebLogic Integration cluster in a domain. That is, there can be no WebLogic Integration resources in a second cluster.

The following example illustrates how to create a WebLogic Platform domain that contains two clusters, as illustrated in Multi-Cluster Platform Domain Example, using WLST Offline.

Steps include:

• Create a Domain With Two Clusters
• Correct Targets for the Resources, Services, and Applications
• Manually Edit the config.xml File to Add JMS Resources for the Second Cluster

Note: For readability, the following code excerpts use actual values and not variables. For information about using WLST variables, see Define WLST Variables.

For more information about using WLST Offline, see the documentation and examples provided with the WLST Offline kit at the following URL: https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=97

Create a Domain With Two Clusters

The process used to configure a multi-cluster domain using WLST Offline is similar to the process illustrated in Example: How to Configure a Single-Cluster Platform Domain Using WLST Offline, except that you need to create two clusters rather than a single cluster.

For example, the following code excerpt performs the following tasks:

• Configures two clusters—WebLogic Integration cluster and a WebLogic Portal cluster.
• Configures four machines, two for the WebLogic Integration cluster, two for the WebLogic Portal cluster.
• Configures the Node Manager name, listen address, start properties—including BEA_HOME, JAVA_HOME, the directory root, and the CLASSPATH values—and the file containing the security policy for starting the server. For more information about configuring Node Manager, see Configuring Node Manager.
• Configures the Managed Servers, targeting them to a machine, and enables SSL to enable secure access to application resources.
• Configures the JMS JDBC Store for the WebLogic Portal cluster.

Compare this code excerpt to the equivalent excerpt for the single cluster domain, described in Configure the Cluster, Managed Servers, and Machines.

cd ('/')
# Define the servers
wli_ms1 = 'wlims1','host1',9111,9112,'wlimachine1'
wli_ms2 = 'wlims2','host2',9121,9122,'wlimachine2'
wli_mss = wli_ms1,wli_ms2
wli_clusterConfig = 'wlicluster','multicast1_addr',9101,wli_mss

wlp_ms1 = 'wlpms1','host3',9211,9212,'wlpmachine1'
wlp_ms2 = 'wlpms2','host4',9221,9222,'wlpmachine2'
wlp_mss = wlp_ms1,wlp_ms2
wlp_clusterConfig = 'wlpcluster','multicast2_addr',9201,wlp_mss

#Create the two clusters
clusterConfigs = wli_clusterConfig,wlp_clusterConfig

machines_created = ""
for clusterConfig in clusterConfigs:
  cl_name, mc_addr, mc_port,mss = clusterConfig
  cluster = create(cl_name, 'Cluster')

  #Configure the machines
  machine = None
  cl_addr = ""

  for msConfig in mss:
    ms_name, ms_addr, ms_port, ms_ssl_port, ms_machine = msConfig

    # check for existence of ms_machine
    create_this_machine = 'yes'
    if machines_created == "":
      machines_created = ms_machine
    else:
      if machines_created.find(ms_machine) == -1:
        machines_created = machines_created + "," + ms_machine
      else:
        create_this_machine = 'no'

    if ms_machine != "" and create_this_machine == 'yes'
      machine = create(ms_machine, 'Machine')

      #Configure the Node Manager name and listen address
      cd('Machine/' + ms_machine + '/NodeManager/' + ms_machine)
      cmo.setName(ms_machine)
      cmo.setListenAddress(ms_addr)
      cd('../../../..')

    #Configure the Managed Server, target it to a machine   
    ms = create(ms_name,'Server')
    ms.setListenAddress(ms_addr)
    ms.setListenPort(ms_port)

    if machine != None:
      ms.setMachine(machine)
  
    cd('Server/' + ms_name + '/SSL/' + ms_name)
    cmo.setEnabled(1)
    cmo.setListenPort(ms_ssl_port)
    cd('../../../..')

    assign('Server', ms_name, 'Cluster', cl_name)

    # Configure Node Manager StartServer properties
    cd('Server/' + ms_name)
    create(ms_name, 'ServerStart')
    cd('ServerStart/' + ms_name)
    cmo.setBeaHome('/bea')
    cmo.setJavaHome('/bea/weblogic81/jrockit81sp4_142_05')
    cmo.setRootDirectory('/bea/user_projects/domains/platform')
    # See Table 3-4 for CLASSPATH settings
    cmo.setClassPath('classpath') 
    cmo.setSecurityPolicyFile('/bea/weblogic81/server/lib/weblogic.policy')
    cmo.setArguments('-Xms512m -Xmx512m -da -Dwlw.iterativeDev=false
 -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.ProductionModeEnabled=true')
    cmo.setUsername('user')
    cmo.setPassword('password')
    cd('../../../..')
    # Accumulate addresses and ports for setting cluster address
    cl_addr = cl_addr + ms_addr + ':' + str(ms_port) + ','

# Set the cluster address, multicast address, and multicast port
cl_addr = cl_addr[:-1] # slice off trailing ','
cluster.setClusterAddress(cl_addr)
cluster.setMulticastAddress(mc_addr)
cluster.setMulticastPort(mc_port)

#Configure the JMS JDBC Store for the WebLogic Portal Cluster
cd('/JDBCConnectionPool/cgJMSPool-nonXA')
connPoolMBean = cmo
cd('/JMSTemplate/TemporaryTmplt')
jmsTemplateMBean = cmo
cd('/')
jdbcstorePrefix = "cgJMSStore_wlp_auto_"
a = ['1', '2']
for n in a:
  storename = jdbcstorePrefix + n
  store = create(storename,"JMSJDBCStore")
  store.setConnectionPool(connPoolMBean)    
  store.setPrefixName('wlp_' + n)

Correct Targets for the Resources, Services, and Applications

The Configuration Wizard and WLST Offline support autoconfiguration for single-cluster domains only. When creating two clusters, you need to manually correct the targets assigned for the resources, services, and applications, as described in the following procedure. (For more information about autoconfiguration, see Autoconfiguration Using the Configuration Wizard and WLST Offline.

Note: For default targeting requirements, refer to Deployment Targeting Reference - Single Cluster WebLogic Platform Domain. To identify resources, services, and application product components, see Default Domain Resource Reference - By Product Component.

Correct the targets for the system resources.

For example, unassign the portalPool and bpmArchPool JDBC connection pools from the WebLogic Integration and WebLogic Portal clusters, respectively.

unassign('JDBCConnectionPool', 'portalPool', 'Target', wliClusterName)
unassign('JDBCConnectionPool', 'bpmArchPool', 'Target', wlpClusterName)

Correct the targets for the WebLogic services.

For example, unassign the WebLogic Integration startup and shutdown classes from the WebLogic Portal cluster.

WLIStartupShutdownClasses = (('ShutdownClass','WLI Shutdown Class'),\
   ('StartupClass','WLI Startup Class'),\
   ('StartupClass','WLI Post-Activation Startup Class'))
for classNVpair in WLIStartupShutdownClasses:
   cname,cvalue=classNVpair
   unassign(cname, cvalue, 'Target', wlpClusterName)

Correct the targets for the applications.
Unassign all applications from the following resources: Administration Server, First Managed Server defined for the WebLogic Integration cluster, and WebLogic Integration and WebLogic Portal clusters

For example:

unassignAll('Application', 'Target', adminName)
unassignAll('Application', 'Target', wlims1Name)
unassignAll('Application', 'Target', wliClusterName)
unassignAll('Application', 'Target', wlpClusterName)

Re-assign the applications to the appropriate targets.

WLST Offline does not support resource names that contain period (".") or slash ("/") characters. Therefore, you must temporarily substitute all period (".") and slash ("/") characters in application names when assigning them to targets. Once assigned, you must restore the original application name for the application to function properly within the domain. For example, in the following excerpt, the following temporary substitutions have been made:

• .workshop/worklist/EJB/ProjectBeans has been temporarily renamed as follows:
  _workshop_worklist_EJB_ProjectBeans
• .workshop/worklist/EJB/GenericStateless has been temporarily renamed as follows:
  _workshop_worklist_EJB_GenericStateless

For example:

assign('Application', 'B2BDefaultWebApp', 'Target', adminName)
assign('Application', 'WLI AI RAR Upload', 'Target', adminName)
assign('Application', 'wliconsole', 'Target', adminName)
assign('Application', 'B2BDefaultWebApp', 'Target', wliClusterName)
assign('Application', '_workshop_worklist_EJB_ProjectBeans',\ 'Target', wliClusterName)
assign('Application', '_workshop_worklist_EJB_GenericStateless',\ 'Target', wliClusterName)
assign('Application', 'worklist', 'Target', wliClusterName)
assign('Application', 'WLIAdmin', 'Target', wliClusterName)
assign('Application', 'WLI Admin Helper', 'Target', wliClusterName)
...

Manually Edit the config.xml File to Add JMS Resources for the Second Cluster

Manually edit the config.xml file to create the following resources for the second cluster, in this example, the WebLogic Portal cluster:

• JMS Server for each Managed Server

For example:

<JMSServer Name="cgJMSServer_wlp_auto_1"
   Store="cgJMSStore_wlp_auto_1" Targets="wlpms1 (migratable)">
   <JMSQueue JNDIName="jws.queue_wlp_auto_1"
      Name="cgJWSQueue_wlp_auto_1" RedeliveryLimit="2" 
      StoreEnabled="default"/>
</JMSServer>
<JMSServer Name="cgJMSServer_wlp_auto_2"
   Store="cgJMSStore_wlp_auto_2" Targets="wlpms2 (migratable)">
   <JMSQueue JNDIName="jws.queue_wlp_auto_2"
      Name="cgJWSQueue_wlp_auto_2" RedeliveryLimit="2" 
      StoreEnabled="default"/>
</JMSServer>

• Distributed queues

For example:

<JMSDistributedQueue JNDIName="jws.queue" 
   Name="dist_cgJWSQueue_wlp_auto" Targets="wlpcluster">
   <JMSDistributedQueueMember JMSQueue="cgJWSQueue_wlp_auto_1" 
       Name="cgJWSQueue_wlp_auto_1_OF_cgJMSServer_wlp_auto_1"/>
   <JMSDistributedQueueMember JMSQueue="cgJWSQueue_wlp_auto_2" 
       Name="cgJWSQueue_auto_2_OF_cgJMSServer_wlp_auto_2"/>
</JMSDistributedQueue>