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:
- Where to host the messaging engines and destinations (use either
a local or remote bus member).
- Whether you need to configure the SCA system bus only, or whether
you also need to configure the SCA application bus. The application
bus is configured by default and is required if you plan to deploy
SCA applications that use WebSphere® Business Integration
Adapters.
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
- From within the administrative console, click one of the
following, depending on your scope:
- Click Support the Service Component Architecture
components.
- 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)
- (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.
- Use the table in the System Bus Member panel
to verify or modify the system bus data source configuration.
- 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.
- 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.
- 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.
- Use the table in the Application Bus Member panel to verify
or modify the application bus data source configuration.
- 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.
- 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.
- 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.
- Click OK to complete the
SCA configuration.
- Save your changes. You can also optionally review
the changes you have made.
What to do next
Next, you can continue configuration as required: