WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

SIBWS - Completing the installation

Use this topic to install and configure, in an application server, the service integration bus Web services enablement (SIBWS) applications. These applications are copied to your file system by the WebSphere Application Server installation program.

Before you begin

Plan your SIBWS installation to determine, for each server, which subset of the applications to install.

Why and when to perform this task

When you install WebSphere Application Server , the installation program does not install the SIBWS and associated applications. When you run the installation program, the files that are required for running the SIBWS are copied into your file system under install_root, where install_root is the root directory for the installation of IBM WebSphere Application Server.

For a list of the SIBWS files and their locations, see SIBWS installation files and locations.

You finish the SIBWS installation by using the wsadmin scripting client to run Jacl scripts. The Jacl scripts take different parameters, depending upon which application you are installing.

When you have determined the roles for a given server, you run the installSdoRepository.jacl script to create and install the Service Data Objects (SDO) repository. Then (depending upon the chosen roles) you might also run the sibwsInstall.jacl script several times to install the service integration technologies resource adapter, the SIBWS application, and one or more endpoint listener applications. You repeat this installation process for every server that is to play one or more SIBWS roles. In all cases, the script tries to install and run the application. If you run the script and it fails to complete, fix the problem then re-run the script. Warnings are displayed, indicating that certain actions are already completed (for example "duplicate applications"), but the script still completes.

As part of the SIBWS installation process, you also configure two aspects of security: After you complete the SIBWS installation, you can take a number of additional steps to further secure the SIBWS. These steps are described in Securing Web services through service integration technologies.

Complete the following steps for every server on which you want to install each SIBWS application:

Steps for this task

  1. Select or create a service integration bus.
  2. Select or add a server as a member of the bus.

    When you add a member to a bus, a messaging engine for the member is created automatically.

  3. Use the installSdoRepository.jacl script to create and install the SDO repository.

    The SIBWS uses an SDO repository for storing and serving WSDL definitions.

  4. Use the sibwsInstall.jacl script to install the service integration technologies resource adapter.

    The SIBWS uses the resource adapter to invoke Web services at outbound ports.

  5. Use the sibwsInstall.jacl script to install the SIBWS application and (optionally) one or more endpoint listener applications.

    If you want to create inbound services, install at least one endpoint listener.

  6. Optional: If WebSphere Application Server global security is enabled, and you are working with secure service integration buses, configure the SIBWS to work in a secure bus.

    This topic describes the minimum security configuration that is required forthe SIBWS to work in a secure service integration bus.

You are now ready to administer the SIBWS core resources.
Related concepts
Planning your SIBWS installation

Task topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\tasks\tjw_install.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)