About this task
On
every
standalone server
or cluster that
is to play an SIBus Web services role:
- You run the installSdoRepository.jacl script
one time, to create and install a Service Data Objects (SDO) repository
(used for storing and serving WSDL definitions).
- You run the sibwsInstall.jacl script several
times, to install a selection of the following applications:
- The service integration technologies resource adapter
- The SIBus Web services application
- One or more endpoint listener applications
Which of these applications you install depends upon the SIBus
Web services role or roles that the
standalone server
or cluster is to play:
- Endpoint
- If you want your server or cluster to
act as an endpoint, install the following resources:
- SDO repository
- Resource adapter
- SIBus Web services application
- Endpoint listener application
- Service invoker
- If you want your server or cluster to
act as a service invoker (that is, an outbound port), install the
following resources:
- SDO repository
- Resource adapter
- SIBus Web services application
- Mediation point
- If you want your server or cluster to
provide a mediation point for Web services, install the following
resources:
- SDO repository
- Resource adapter
- SIBus Web services application
- Configuration connection point
- If you want your deployment manager or unfederated standalone
server to act as a configuration connection point, install the following
resource:
You might also want to configure two aspects
of security at this time:
- You can modify the endpoint listener application
EAR file, to change the default security role that is used to restrict
access to the listener. If you want to do this, you must do it before
you install the endpoint listener application.
- You can configure an authentication alias for use by the resource
adapter and the installed endpoint listeners when communicating with
other elements of a secure service integration bus.
To install the SIBus Web services applications on a
standalone server
or cluster,
complete the following steps:
Tip: Both the Jacl scripts
try to install and run the application. If you run a script and it
fails to complete, fix the problem then rerun the script. Warnings
are displayed, indicating that certain actions are already completed
(for example "duplicate applications"), but the script still
completes. When
you install an application to a cluster, the Jacl script installs
the application, synchronizes the affected nodes and attempts to start
the application on each server in the cluster. You should check that
the applications are running as expected. The applications only start
on servers that are running.