WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Configuring SCA support for a server or cluster

Use the Service Component Architecture console page to enable a server or cluster in a network deployment environment to host service applications, their required messaging engines and destinations, or both.

Before you begin

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.

About this 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 a network deployment configuration are not configured to host SCA applications and their destinations.

To configure SCA support on your server or cluster, perform the following steps.
Procedure
  1. From within the administrative console, click one of the following, depending on your scope:
    • Servers > Application Servers > serverName > Service Component Architecture
    • Servers > Clusters > clusterName > Service Component Architecture
  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 Instance, 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.
      Restriction: In a WebSphere Process Server for z/OS clustered environment, the data sources needed by the WebSphere Process Server cluster are defined for you using driver type 2 under a DB2 Universal JDBC Driver Provider, at the cluster scope. You cannot test connections for a DB2 Universal JDBC Driver Provider data source with driver type 2 at the cluster level. When you use the Test Connection button on a cluster scope data source, the test occurs in the node agent, and you cannot test Type 2 data sources under a DB2 UDB Provider in the node agent. Testing a Type 2 data sources under a DB2 UDB Provider on the node agent will result in a java.sql.SQLException.The restriction on not being able to test type 2 JDBC data sources under the DB2 Universal JDBC provider at the cluster or node scopes also applies to for WebSphere Process Server for Multiplatforms, however, on WebSphere Process Server for Multiplatforms, you have a choice to not use DB2.
      Note: On any platform (z/OS or Multiplatform), when you create a WebSphere Process Server stand-alone server profile instead of a network deployment cell, the data sources are defined at the server's scope, so the restriction on testing the connection does not apply.
  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.
      Note: 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 Instance, 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.

What to do next

Next, you can continue configuration as required:

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/clusters/tadm_configscasupport.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).