IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced > Install IBM BPM Advanced > On Windows > Network deployment environment > Configure profiles and create an ND environment > Create an ND environment > Use the administrative console > Configure components > Configure optional components

Configure SCA support for a server or cluster

Use the SCA console page to enable a server or cluster in an ND environment to host service applications, their required messaging engines and destinations, or both.

Before configuring SCA support, determine the following:


Security role required for this task: You must be logged in as administrator or configurator to perform the following task.

Service applications require the use of one or more of the automatically created service integration buses, which must have configured messaging engines for destinations. By default, new servers and clusters in an ND configuration are not configured to host SCA applications and their destinations. To configure SCA support on your server or cluster...


Procedure

  1. From within the administrative console, click one of the following, depending on your scope:

  2. Click Support the Service Component Architecture components.

  3. In the Bus Member Location panel, specify where you want to host the destinations and messaging engines required by the SCA applications. There are two options:

    • Local. Specifies that you plan to host SCA applications, destinations, and messaging engines on the current server or cluster.
    • Remote. Specifies that you plan to host SCA applications on the current server or cluster while hosting destinations and messaging engines on a remote server or cluster (also referred to as a deployment target).

  4. (Remote bus member only) If you selected Remote in the previous step, specify the remote server or cluster you want to use to host application destinations and messaging engines. Use the drop-down menu to select an existing deployment target (one that is already configured as a member of the SCA system bus), or click New to select a new server or cluster from the Browse Deployment Target page.

    If you select a new server or cluster from the Browse Deployment Target page, the necessary messaging is automatically configured on that target when you complete the SCA configuration documented in this topic.

  5. Use the table in the System Bus Member panel to verify or modify the system bus data source configuration.

    1. Verify any default values in the Database name, Schema, Create Tables, User name Password, Server, and Provider fields. See the online help for detailed information about these fields and the values they accept.

    2. If no default values exist in these fields, or if the default values are incorrect, enter the appropriate values for the system bus data source. You can enter values directly in the field or by clicking Edit and making edits on the Data Source details page.

    3. Optional: Ensure that the data source can contact and authenticate with the database by clicking Test Connection.

  6. Use the table in the Application Bus Member panel to verify or modify the application bus data source configuration.

    1. Ensure the Enable the WebSphere Business Integration Adapter components option is selected.

      If you do not want to use the application bus, clear the Enable the WebSphere Business Integration Adapter components option and proceed to Step 7.

    2. Verify any default values in the Database name, Schema, Create Tables, User name Password, Server, and Provider fields. See the online help for detailed information about these fields and the values they accept.

    3. If no default values exist in these fields, or if the default values are incorrect, enter the appropriate values for the application bus data source. You can enter values directly in the field or by clicking Edit and making edits on the Data Source details page.

  7. Click OK to complete the SCA configuration.
  8. Save your changes. You can also optionally review the changes you have made.

Configure optional components