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.
Plan your SIBWS installation to determine, for each server, which subset of the applications to install.
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.
Complete the following steps for every server on which you want to install each SIBWS application: