Use this topic to install into an application server or
cluster the service integration bus (SIBus) Web services and
endpoint listener applications. These applications are copied to your file
system by the WebSphere Application Server installation program.
Before you begin
This topic assumes that you have already determined the set of standalone servers or clusters on which to install
the SIBus Web services and endpoint listener applications, and completed the steps and
prerequisites that are described in Installing the service integration technologies resource adapter.
By default, even if global security is enabled,
all your users can access any inbound service you deploy to an endpoint listener.
You change this default and restrict access as described in Password-protecting inbound services. For SOAP over JMS, you can make these security changes
after you have installed the endpoint listener application. However, if you
want to change the default SOAP over HTTP endpoint listener security role,
you must do so before you install the HTTP endpoint listener application.
Why and when to perform this task
The SIBus Web services application lets you configure and access Web services
through a service integration bus.
An endpoint listener is the point
(address) at which messages for an inbound service are received. The endpoint
listeners that are supplied with WebSphere Application Server support SOAP
over HTTP and SOAP over JMS bindings. For an overview of endpoint listeners,
see Endpoint listeners and inbound ports - entry points to the service integration bus.
The installation of endpoint listeners is optional. However, if you want to create inbound services,
you must install at least one endpoint listener.
You install the SIBus Web services
and endpoint listener applications by using the wsadmin scripting client to
run the sibwsInstall.jacl script. This script is provided
in the app_server_root/util directory,
where app_server_root is the
root directory for the installation of IBM WebSphere Application Server.
Complete the
following steps for every standalone server or cluster on which you want to install
the SIBus Web services or an endpoint listener application:
Steps for this task
- Open a command prompt, then change to the app_server_root/bin directory.
- Install the SIBus Web services application, or
an endpoint listener application.
Note: - You should include one of the three optional parameters that are indicated
by square brackets ("[ ]"). Use INSTALL to install the
SIBus Web services application; use either INSTALL_HTTP or INSTALL_JMS to
install an endpoint listener application. If you include no optional parameters,
the command assumes that you want to install the SIBus Web services application.
- This use of forward slashes ("/") is compulsory for this command,
even on Windows systems.
- If you want to change
the default HTTP endpoint listener security role, do so before you
install the SOAP over HTTP endpoint listener applications.
- Before you install the SOAP over JMS endpoint listener applications, you
should configure the
associated JMS resources. For SOAP over JMS, the installation command
assumes that you are deploying your endpoint listener application to use a
JMS activation specification with the default messaging provider. If you choose
to deploy your endpoint listener application to use a listener port or another
JMS provider (for example WebSphere MQ), and no JMS activation specifications
are defined, the command seems to fail. Ignore this apparent error, and complete
the subsequent (optional) step to change the listener bindings for the application.
To install the SIBus Web services application, or an endpoint listener
application, repeat one of the following steps for each application that you
want to install:
- If you are installing the application on a standalone server,
run the following command:
wsadmin -f app_server_root/util/sibwsInstall.jacl [INSTALL_HTTP | INSTALL_JMS | INSTALL]
-installRoot app_server_root_using_forward_slashes
-serverName server_name -nodeName node_name
Note: You
must include the serverName and nodeName parameters.
The application is installed on the specified server and node. The server
must not be a member of a cluster.
- If you are installing the application for deployment to a cluster,
run the following command:
wsadmin -f app_server_root/util/sibwsInstall.jacl [INSTALL_HTTP | INSTALL_JMS | INSTALL]
-installRoot app_server_root_using_forward_slashes
-clusterName cluster_name
Note: No nodeName is
required for installing the application for deployment to a cluster. If you
supply a node name, the command fails.
- Optional: If you have installed a synchronous SOAP
over JMS endpoint listener application, and you want to change the default
values for the activation specification (or listener port ),
modify the installed applications by completing the following steps for each
endpoint listener application:
- In the administrative console navigation pane, click Applications
> Enterprise Applications. A list of all installed enterprise
applications is displayed.
- Click the name of the endpoint listener application (for example SOAPJMSendpoint
listener1). Configuration details for the application
are displayed.
- Scroll down through the configuration details to the Additional
Properties pane, then click Provide listener bindings for message-driven
beans. The Binding enterprise beans to listener
port names or activation specification JNDI names pane is displayed.
- Under the Bindings section, select either Listener port or Activation
Specification.
- Change the activation specification JNDI name (or listener port
name) to the required value, then click OK to return
to the Additional Properties pane.
- Save your changes to the master configuration.
- Optional: If you have installed a synchronous SOAP
over JMS endpoint listener application, and you want to change the default
value for the reply queue connection factory, modify the installed application
by completing the following steps:
- In the administrative console navigation pane, click Applications
> Enterprise Applications. A list of all installed enterprise
applications is displayed.
- Click the name of the endpoint listener application (for example SOAPJMSendpoint
listener1). Configuration details for the application
are displayed.
- Scroll down through the configuration details to the Additional
Properties pane, then click Map resource env entry references to resources The Mapping resource environment references to resources pane
is displayed.
- Change the connection factory value from (for example) jms/SOAPJMSFactory1 to
the required value, then click OK to return to the
Additional Properties pane.
- Save your changes to the master configuration.
- Optional: If you have installed a synchronous SOAP
over JMS endpoint listener application, bind the JMS resources by stopping
then restarting the application server.
You are now ready to create a new endpoint listener configuration for each endpoint
listener application that you have installed.