You can use this command instead of the administrative console
to configure a cluster to run Service Component Architecture (SCA) applications. 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.
Attention: This
command has been deprecated.
Purpose
Use the configSCAForCluster command
to prepare a cluster to support SCA applications. This wsadmin command
is an alternative to using the administrative console to perform the configuration.
Syntax
$AdminTask configSCAForCluster { -clusterName nameofCluster-systemBusDataSource SCASystemBusSource -appBusDataSource SCAApplicationBusSource-remoteDestLocation remoteMELocation -meAuthAlias userid -systemBusSchemaName systemMEBusSchema -appBusSchemaName appBusSchema -createTables true | false}
Parameters
- -clusterName nameofCluster
- A required parameter that identifies the cluster that you are configuring.
- -systemBusDataSource SCASystemBusSource
- An existing data source you are using for the SCA system bus.
- -appBusDataSource SCAApplicationBusSource
- An existing data source you are using for the SCA application bus.
- -remoteDestLocation remoteMELocation
- The location of a remote messaging engine. 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.
- -systemBusSchemaName systemMEBusSchema
- The schema name for the system bus messaging engine. The default for this
parameter is IBMWSSIB.
- -appBusSchemaName appBusSchema
- The schema name for the application bus messaging engine. The default
for this parameter is IBMWSSIB.
- -createTables true | false
- A parameter that specifies whether to create tables for the messaging
engine data store. The default value for this parameter is true.
Notes: - When using a remote messaging engine, specify -remoteDestLocation;
otherwise specify -systemBusDataSource and -appBusDataSource.
- If you specify -systemBusDataSource and -appBusDataSource as
the same data store, then you must use different schemas for -systemBusSchemaName and -appBusSchemaName.
Examples
The following example illustrates how to
configure the cluster
mySCAAppCluster on node
NYCluster for
SCA using the remote messaging engine
NJMECluster:
$AdminTask configSCAForCluster {-clusterName mySCAAppCluster -nodeName NYCluster
-remoteDestLocation WebSphere:cluster=NJMECluster -meAuthAlias -systemBusSchemaName
NYSysSchema -appBusSchemaName NYAppSchema}
$AdminConfig save
The following example illustrates how to configure
the cluster
newSCAAppCluster on node
bgmCluster for
SCA using a local messaging engine.
$AdminTask configSCAForCluster {-clusterName newSCAAppCluster -nodeName bgmCluster
-systemBusDataSource jdbc/localBus -appBusDataSource jdbc/localBus
-systemBusSchemaName BGMSysSchema -appBusSchemaName BGMAppSchema}
$AdminConfig save