configSCAAsyncForCluster command

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.

Use the configSCAAsyncForCluster command to prepare a cluster to support SCA applications. This wsadmin command is an alternative to using the administrative console to perform the configuration.

After using the command, save your changes to the master configuration using one of the following commands:

For Jython:
```
AdminConfig.save()
```
For Jacl:
```
$AdminConfig save
```

Required parameters

-clusterName nameofCluster

A required parameter that identifies the cluster that you are configuring.

-meAuthAlias myAlias

An existing authentication alias used to access the messaging engine.

-remoteMELocation remoteMELocation

The location of a remote messaging engine. Specify remoteMELocation in one of the following ways:

WebSphere:cluster=clustername
WebSphere:node=nodeName,server=serverName

-systemBusDataSource nameOfSystemBusSource

An existing data source you are using for the SCA system bus.

-systemBusSchemaName nameOfSystemBusSchema

The schema name for the system bus messaging engine. The default for this parameter is IBMWSSIB.

Optional parameters

-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.
-systemBusId cellname | nameForSystemBus: An optional parameter that specifies the ID to be used for the SCA system bus name. The default is cellname.

Examples

The following example illustrates how to configure the cluster mySCAAppCluster for SCA using the remote messaging engine NJMECluster:

Jython example:

AdminTask.configSCAAsyncForCluster('[-clusterName mySCAAppCluster 
   -remoteMELocation WebSphere:cluster=NJMECluster -meAuthAlias myAlias 
   -systemBusSchemaName NYSysSchema]')

Jacl example:

$AdminTask configSCAAsyncForCluster {-clusterName mySCAAppCluster 
   -remoteMELocation WebSphere:cluster=NJMECluster -meAuthAlias myAlias 
   -systemBusSchemaName NYSysSchema}

The following example illustrates how to configure the cluster newSCAAppCluster on node bgmCluster for SCA using a local messaging engine.

Jython example:

AdminTask.configSCAAsyncForCluster('[-clusterName newSCAAppCluster 
	 -systemBusDataSource jdbc/localBus -systemBusSchemaName BGMSysSchema]')

Jacl example:

$AdminTask configSCAAsyncForCluster {-clusterName newSCAAppCluster 
	 -SystemBusDataSource jdbc/localBus -systemBusSchemaName BGMSysSchema}