Service Component Architecture

Use the Service Component Architecture page to configure a cluster or server to support WebSphere® Service Component Architecture (SCA) applications. Service applications are those that require the use of one or more of the following buses: SCA.APPLICATION.CellName.Bus, SCA.SYSTEM.CellName.Bus, or BPC.CellName.Bus.

To view this page in the administrative console, do one of the following:

By default, new servers and clusters in deployment manager and custom (managed node) profiles do not have SCA support configured. SCA support is already configured for any server that is part of a stand-alone server profile.

From this page, you can perform the following tasks:
Important: Although you can modify the data sources used for the SCA configuration in deployment manager or custom profiles, you cannot modify (or unconfigure) existing SCA support. In stand-alone server profiles, you cannot modify the configured data sources, either.

Links marked (online) require access to the Internet. Each link launches a search for the topic in the online information center. When search results are listed, select the topic that corresponds best to your configuration.

Check for updates to this topic (online)

Support the Service Component Architecture components

Select this check box if you want to deploy SCA applications to the current cluster or server.

By default, this option is cleared if you are using a deployment manager or custom (managed node) profile. If you are using a stand-alone server profile, SCA support is already configured and this check box is selected.

When you select Support the Service Component Architecture components, the Bus Member Location panel becomes active so you can specify where to host SCA application destinations and messaging engines.

Bus Member Location panel

Specifies whether the SCA system bus (and, optionally, the SCA application bus) destinations are hosted on the local deployment target or on a remote target. Use the Local and Remote radio buttons in this panel to indicate the appropriate location.

Bus members are always hosted locally for stand-alone server profiles.

Local

Select this radio button if you want to create and host SCA applications and their required messaging engines and Java Message Service (JMS) queue destinations on the current cluster or server.

When you select Local, the System Bus Member panel and Application Bus Member panel become active so you can create or modify the data source used for each service integration bus.

Remote

Select this radio button to host SCA applications on the local cluster or server while using a remote cluster or server to host the JMS queue destinations and messaging engines.

If you select Remote, use the associated drop-down list or New button to specify the remote location you want to use. The drop-down list shows all deployment targets that are configured as members of the SCA system bus, and the New button opens the Browse Deployment Target page so you can add a single server or cluster target to that list.
Note: If you use the Browse Deployment Target page to add a new target to the list and navigate away from the Service Component Architecture page before completing your SCA configuration, that target is removed from the list.

After you select a remote deployment target, the page displays the appropriate information for that target in the System Bus Member panel. If the application bus is enabled on the remote deployment target, the page also updates the table in the Application Bus Member panel. If the application bus is not enabled on the deployment target, you can enable it.

System Bus Member panel

Specifies the properties of the data source used by the SCA system bus. This panel is active whenever you are creating a new SCA configuration for the cluster or server and when you are editing the system bus data source properties for a previous SCA configuration.

Many fields in this panel contain default values based on the WebSphere Process Server and WebSphere Enterprise Service Bus Common database (by default, WPRCSDB) configured on the deployment target you have selected. You can accept these default values or edit them.

Note that the database configuration requirements on an i5/OS system can vary from those for other platforms; therefore, the valid and default values for fields on the System Bus Member panel may be slightly different from those for other platforms. Refer to the database configuration documentation in the WebSphere Process Server Information Center for detailed information about database and data source properties on an i5/OS system.

In addition to the fields, the System Bus Member panel contains two buttons:
  • Edit: Use the Edit button to modify the data source used for the system bus. Clicking it opens the data source configuration page.
  • Test Connection: Use the Test Connection button to verify that the data source can contact and authenticate with the database. If a component manages the data source, this test also verifies whether the data can be reached from the configured scope and, if applicable, whether the schema is configured correctly.

Refer to the following sections for detailed descriptions of each field in this panel. Note that you cannot edit these fields if you are using a stand-alone server profile.

Database name

Specifies the database name used for this data source. The value must be the name of an existing database.

If you have not yet configured a data source, Database name contains a default value based on the detected database configuration (for example, WPRCSDB for WebSphere Process Server and WebSphere Enterprise Service Bus configurations). You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

Schema

Enter the name of the database schema that contains the tables for the system bus data source. This field is required if you are creating a new data source with a database that supports schema names.

Each messaging engine stores its resources, such as tables, in a single schema. Each database schema is used by one messaging engine only. Although every messaging engine uses the same table names, its relationship with the schema gives each messaging engine exclusive use of its own tables.
Note:

Databases that support schemas often have different requirements for specifying the schema names. Refer to your database documentation and the database configuration topics in the WebSphere Process Server Information Center for more information about creating and using schemas with messaging engines.

If you have not yet configured a data source, Schema contains a default value based on the detected database configuration. This default value is unique among all data sources that use the specified database instance in the same cell. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

Create tables

Select this check box if you want the messaging engine to create the database tables for the data sources.

This check box is optional. If you do not select it, the database administrator must create the tables manually.

By default, this option is selected for a new configuration.

User name

Enter the user ID used to connect to the system bus data source.

This is a required field.

If you have not yet configured a data source, User name contains a default value based on the detected database configuration. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

Password

Enter the password for the user specified in the User name field.

This is a required field.

If you have not yet configured a data source, Password contains a default value based on the detected database configuration. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

Server

Specify the name of the database server used by the system bus.

If you have not yet configured a data source, Server contains a default value based on the detected database configuration. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

Provider

Specify the database provider type used to create the messaging resources for the system bus. The Java Database Connectivity (JDBC) provider you select determines the type of database you can use for the data source.

If you have not yet configured a data source, Provider contains a default value based on the detected database configuration. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

If you are using a file store for your messaging engine, Provider is automatically set to File Store. The file store option is available only during installation of a stand-alone server profile.

This field is required to create a new service integration bus data source for the cluster or server. You cannot change this value once the system bus messaging engine is configured.

Application Bus Member panel

Specifies the properties of the data source used by the SCA application bus. This panel is active whenever you are creating a new SCA configuration for the cluster or server and when you are editing the application bus data source properties for a previous SCA configuration.

Many fields in this panel contain default values based on the WebSphere Process Server and WebSphere Enterprise Service Bus Common database (by default, WPRCSDB) configured on the deployment target you have selected. You can accept these default values or edit them.

Note that the database configuration requirements on an i5/OS system can vary from those for other platforms; therefore, the valid and default values for the fields on the Application Bus Member panel may be slightly different than those for other platforms. Refer to the database configuration documentation in the WebSphere Process Server Information Center for detailed information about database and data source properties on an i5/OS system.

In addition to the fields, the Application Bus Member panel contains two buttons:
  • Edit: Use the Edit button to modify the data source used for the application bus. Click this button to open the data source configuration page.
  • Test Connection: Use the Test Connection button to verify that the data source can contact and authenticate with the database. If a component manages the data source, this test also verifies whether the data can be reached from the configured scope and, if applicable, whether the schema is configured correctly.

Refer to the following sections for detailed descriptions of each field in this panel. Note that you cannot edit these fields if you are using a stand-alone server profile.

Enable the WebSphere Business Integration Adapter components

Select this check box to configure SCA application bus support for WebSphere Business Integration Adapters.

By default, this option is selected when you are creating a new SCA configuration. It is required if you plan to deploy SCA applications that use WebSphere Business Integration Adapters to your chosen deployment target.
Note: If you are not sure whether you plan to deploy these types of SCA applications, consider selecting this option simply to ensure the support is available if needed.

Database Instance

Specifies the database instance used for this data source. The value must be the name of an existing database instance (for example, WPRCSDB).

If you have not yet configured a data source, Database Instance contains a default value based on the detected database configuration. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

Schema

Enter the name of the database schema that contains the tables for the application bus data source. This field is required if you are creating a new data source with a database that supports schema names.

Each messaging engine stores its resources, such as tables, in a single schema. Each database schema is used by one messaging engine only. Although every messaging engine uses the same table names, its relationship with the schema gives each messaging engine exclusive use of its own tables.
Note: Databases that support schemas often have different requirements for specifying the schema names. Refer to your database documentation and the database configuration topics in the WebSphere Process Server Information Center for more information about creating and using schemas with messaging engines.

If you have not yet configured a data source, Schema contains a default value based on the detected database configuration. This default value is unique among all data sources that use the specified database instance in the same cell. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

Create tables

Select this check box if you want the messaging engine to create the database tables for the data sources.

This check box is optional. If you do not select it, the database administrator must create the tables manually.

By default, this option is selected for a new configuration.

User name

Enter the user ID used to connect to the application bus data source.

This is a required field.

If you have not yet configured a data source, User name contains a default value based on the detected database configuration. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

Password

Enter the password for the user specified in the User name field.

This is a required field.

If you have not yet configured a data source, Password contains a default value based on the detected database configuration. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

Server

Specify the name of the database server used by the application bus.

If you have not yet configured a data source, Server contains a default value based on the detected database configuration. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

Provider

Specify the database provider type used to create the messaging resources for the application bus. The JDBC provider you select determines the type of database you can use for the data source.

If you have not yet configured a data source, Provider contains a default value based on the detected database configuration. You can change the default value by directly editing it within the field or by clicking Edit and updating the data source properties.

If you are using a file store for your messaging engine, Provider is automatically set to File Store. The file store option is available only during installation of a stand-alone server profile.

This field is required to create a new service integration bus data source for the cluster or server. You cannot change this value once the application bus messaging engine is configured.