configSCAAsyncForServer command

Use the configSCAAsyncForServer command instead of the administrative console to configure a specific server 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 configSCAAsyncForServer command to prepare a server 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

-serverName nameofserver: A required parameter that identifies the server you are configuring
-nodeName nameofnode: A required parameter that identifies the node to which the server belongs.

Optional parameters

-systemBusDataSource nameOfSystemBusSource

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

-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

-meAuthAlias myAlias

An existing authentication alias used to access the messaging engine.

-systemBusSchemaName nameOfSystemBusSchema

The schema name for the system 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.

-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 server mySCAAppServer on node NYServerFarm for SCA using the remote messaging engine NJMECluster:

Jython example:

AdminTask.configSCAAsyncForServer('[-serverName mySCAAppServer 
   -nodeName NYServerFarm -remoteDestLocation WebSphere:cluster=NJMECluster 
   -meAuthAlias myAlias -systemBusSchemaName NYSysSchema]')

Jacl example:

$AdminTask configSCAAsyncForServer {-serverName mySCAAppServer 
   -nodeName NYServerFarm -remoteDestLocation WebSphere:cluster=NJMECluster 
   -meAuthAlias myAlias -systemBusSchemaName NYSysSchema}

The following example illustrates how to configure the server newSCAAppServer on node bgmServerFarm for SCA using a local messaging engine.

Jython example:

AdminTask.configSCAAsyncForServer('[-serverName newSCAAppServer 
   -nodeName bgmServerFarm -systemBbusDataSource jdbc/localBus 
   -systemBusSchemaName BGMSysSchema]')

Jacl example:

$AdminTask configSCAAsyncForServer {-serverName newSCAAppServer 
   -nodeName bgmServerFarm -systemBbusDataSource jdbc/localBus 
   -systemBusSchemaName BGMSysSchema}