Installing the SIBus Web services applications and resources

Install and configure, in one or more application servers or clusters, a selection of the service integration bus (SIBus) Web services applications and resources that are copied to your file system by the WebSphere® Application Server installation program.

Before you begin

Determine the roles that each server or cluster is to perform. For more information, see Planning your Bus-enabled Web services installation.

Every standalone server or cluster that is to play an SIBus Web services role must be a member of a service integration bus. For more information, see Configuring the members of a bus.

About this task

When you install WebSphere Application Server, the installation program does not install the SIBus Web services applications and resources; it copies them to your file system as detailed in Bus-enabled Web services installation files and locations. You install these applications as a separate step, using the wsadmin scripting client to run two Jacl scripts:
  • installSdoRepository.jacl
  • sibwsInstall.jacl
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:
  • SDO repository.
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.

Procedure

  1. Install and configure the SDO repository.
  2. Use the sibwsInstall.jacl script to install the service integration technologies resource adapter.
  3. Use the sibwsInstall.jacl script to install the SIBus Web services application and (optionally) one or more endpoint listener applications.
    Note:
    • If you want to create inbound services, install at least one endpoint listener.
    • This step includes the option to modify the endpoint listener application EAR file and change the default security role that is used to restrict access to the listener.

What to do next

You are now ready to Create a new endpoint listener configuration for each endpoint listener application that you have installed. If WebSphere Application Server global security is enabled, and you are working with secure service integration buses, you must also create the minimum security configuration that is required for SIBus Web services to work in a secure bus.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=tjw_install
File name: tjw_install.html