You can use this command instead of the administrative console
to configure a cluster to run Service Component Architecture (SCA) applications
that use JMS resources. You can specify
a number of commands in a file to batch a large number of configurations without
having to navigate the administrative console panels.
Before you begin
The configSCAJMSForCluster command
is run using the AdminTask object of the wsadmin scripting client.
Use
the following command to list all the SCA administrative commands.
wsadmin> $AdminTask help SCAAdminCommands
Use the following command to get detailed help on
a particular command.
wsadmin> $AdminTask help command_name
Syntax
$AdminTask configSCAJMSForCluster {-paramName paramValue ...}
Purpose
Use the configSCAJMSForCluster command
to prepare a cluster to support SCA applications that use JMS resources. This wsadmin command
is an alternative to using the administrative console to perform the configuration.
Required Parameters
- -clusterName nameofCluster
- A required parameter that identifies the cluster that you are configuring.
Parameters
- -appBusDataSource SCAApplicationBusSource
- An existing data source that you are using for the SCA.APPLICATION bus.
- -remoteMELocation remoteMELocation
- The location of a remote messaging engine. Specify this parameter if the
SCA modules deployed on this server are to use their queue destinations hosted
on a messaging engine in another server or cluster.
Specify
remoteMELocation in
one of the following ways:
- WebSphere:cluster=clustername
- WebSphere:node=nodeName,server=serverName
- -meAuthAlias userid
- An existing authentication alias used to access the messaging engine.
- -appBusSchemaName appMEBusSchema
- The schema name for the SCA.APPLICATION bus messaging engine. The default
for this parameter is IBMWSSIB.
- -createTables true | false
- An optional parameter that specifies whether to create tables for the
messaging engine data store. The default value for this parameter is true.
Examples
The following example illustrates how to
configure the cluster
mySCAAppCluster for SCA using
the remote messaging engine
NJMECluster:
$AdminTask configSCAJMSForCluster {-clusterName mySCAAppCluster
-remoteMELocation WebSphere:cluster=NJMECluster -meAuthAlias mySCAAlias
-appBusSchemaName NYSysSchema}
$AdminConfig save
The following example illustrates how to configure
the cluster
newSCAAppCluster on node
bgmCluster for
SCA using a local messaging engine.
$AdminTask configSCAJMSForCluster {-clusterName newSCAAppCluster
-busDataSource jdbc/localBus -appBusSchemaName BGMSysSchema}
$AdminConfig save