Installing the SIBus Web services and endpoint listener applications

Use this topic to install into an application server 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 servers 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.

About 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 server on which you want to install the SIBus Web services or an endpoint listener application:

Procedure

  1. Open a command prompt, then change to the app_server_root/bin directory.
  2. To install the SIBus Web services application or an endpoint listener application, repeat the following command for each application that you want to install.
    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:
    • 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.
    • 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.
    • This use of the / (forward slash) character 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.
  3. 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:
    1. In the administrative console navigation pane, click Applications > Enterprise Applications. A list of all installed enterprise applications is displayed.
    2. Click the name of the endpoint listener application (for example SOAPJMSendpoint listener1). Configuration details for the application are displayed.
    3. 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.
    4. Under the Bindings section, select either Listener port or Activation Specification.
    5. Change the activation specification JNDI name (or listener port name) to the required value, then click OK to return to the Additional Properties pane.
    6. Save your changes to the master configuration.
  4. 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:
    1. In the administrative console navigation pane, click Applications > Enterprise Applications. A list of all installed enterprise applications is displayed.
    2. Click the name of the endpoint listener application (for example SOAPJMSendpoint listener1). Configuration details for the application are displayed.
    3. 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.
    4. Change the connection factory value from (for example) jms/SOAPJMSFactory1 to the required value, then click OK to return to the Additional Properties pane.
    5. Save your changes to the master configuration.
  5. Optional: If you have installed a synchronous SOAP over JMS endpoint listener application, bind the JMS resources by stopping then restarting the application server.

What to do next

You are now ready to create a new endpoint listener configuration for each endpoint listener application that you have installed.




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 5:25:00 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-base-dist&topic=tjw_install_sibws_epl
File name: tjw_install_sibws_epl.html