6 Integration Gateway Services Installation Tasks

The RIB Integration Gateway Services (IGS) component is an optional sub-system and should be installed only after the core RIB components have been installed and verified.

The IGS provides an integration infrastructure for external (third party) system connectivity to the Oracle retail Integration Bus (RIB) in the form of a tested set of Web service providers and the configurations to connect to RIB 13.1. So it should be installed only if there is a requirement to do so.

Note: See the RIB Implementation Guide - Integration Gateway Services for details and considerations before attempting installation.

Prerequisites

The RIB Integration Gateway Service (IGS) component requires Oracle WebLogic Server 10g Release 3 (10.3).

Before installation, read the RIB Implementation Guide for the considerations and planning steps needed for the RIB IGS deployment to WebLogic Server.

Note: This release of IGS does not support message flows that are configured for multiple JMS. See the RIB Implementation Guide for details.

Prepare Oracle WebLogic Server

The installation and base configuration of the Oracle WebLogic Server is beyond the scope of this document. Work with the Application Server Administration team to determine the physical and logical placement of the RIB IGS component within the WebLogic Server deployment.

Note: See the Oracle® WebLogic Server 10g Release 3 (10.3) Installation Guide.

Note: For illustrations of the applications screens used to prepare the Oracle WebLogic Server, see Appendix D - "Integration Gateway Services .ear File Installation."

Create the RIB IGS WebLogic Managed Server

This section describes the process of preparing the Oracle® WebLogic Server to install the igs-service.

1. Every .ear file or ejb-jar file containing the services should be deployed on its own WebLogic server.

2. When naming the WebLogic instance, it is recommended (but not required) that the .ear file name is used (without the extension), along with underscore, wls_instance.

   For example, if the .ear file name is igs-service.ear, the instance name would be igs-service_wls_instance.

Note: See Oracle® WebLogic Server 10g Release 3 (10.3) xxxx.

Create RIB AQ JMS Datasource for IGS

1. Verify that RIB JMS is installed, configured, and running.

2. Using the WebLogic Server Administration Console, create a datasource.

   
   

   Note: See Oracle® WebLogic Server 10g Release 3 (10.3) Documentation - Administration.

   
   

   1. Navigate to datasources screen using Services > JDBC > Data Sources menu.

   2. Click on New and enter the following values in the respective fields:

      Field Name	Value
      Name	igs-ojms-managed-datasource
      JNDI Name	IGSOracleAQJmsDs
      Database Type	Oracle
      Database Driver	Oracle's Driver(thin)

      
      

   3. Uncheck "Supports Global Transactions."

   4. Fill in the database details for the RIB AQ JMS:

      Field Name	Example	Comment
      Database Name	ora11g	AQ Database instance name
      Host Name	linux1.us.oracle.com	Database system
      Port	1521	Database listener port
      Database User Name	RIBAQ	AQ user
      Password	RIBAQ	AQ user password

      
      

   5. Verify the configuration details.

   6. Test configuration to make sure that the server is able to connect to the database.

   7. Select the target server. This is the managed server created for the igs-service. For example, igs-service_wls_instance.

   8. Click Finish. The newly created datasource should show in the list of datasources.

Prepare to Deploy the IGS Application

1. Download the IntegrationGatewayService13.1.0ForAll13.1.0Apps.tar. The recommended location is the reserved location in rib-home. For example: /Rib1310ForAll13xxApps/rib-home/tools-home/integration-bus-gateway-services

   
   

   Note: The files must be accessible to the Oracle® WebLogic Server Administration during the deployment step. Accordingly, they must be located on either the WebLogic Server host, or on the host where the browser used to connect to the Administration Console is invoked.

   
   

2. Extract the contents of the .tar file.

   > tar -xvf IntegrationGatewayService13.1.0ForAll13.1.0Apps_eng_ga.tar

Deploy the IGS Application

Using the Oracle® WebLogic Server Administration Console, complete the following steps.

Note: See Oracle® WebLogic Server 10g Release 3 (10.3) Documentation - Administration .

1. Navigate to the Deployments page.

2. Click Install.

   
   

   Note: If the application has already been installed, see the section, "Redeploy the IGS Application".

   
   

3. The "Locate deployment to install and prepare for deployment" page appears. Follow the instructions to locate the igs-service.ear file on the WebLogic server host.

   If rib-home is located on a different host than the Oracle WebLogic Server, follow these instructions to upload the file:

   1. Select upload files.

   2. On the "Upload a Deployment to the admin server" page, use the browse button to locate the igs-service .ear file in the "Deployment Archive."

4. Select the igs-service.ear.

5. Click Next and move to "Choose targeting style."

6. Select "Install this deployment as an application."

7. Click Next and move to "Optional Settings."

8. Click Next and move to "Review your choices and click Finish."

9. Select "No, I will review the configuration later."

10. Click Finish to deploy the application.

Redeploy the IGS Application

If the igs-service application has already been deployed, complete the following steps:

1. If the igs-service application is running, select "Stop" and "When work completes" or "Force Stop Now." The choice depends on the environment. The recommended option in every case is "When work completes."

2. Select "Delete."

3. The "Summary of Deployments" should now not include the igs-service.

4. Resume the steps in the "Deploy the IGS Application"section, above.

Verify the IGS Application Installation Using the Administration Console

To verify the IGS installations using the Oracle WebLogic Administration Console, complete the following steps:

Note: For the Test Client link to be visible the server must be in Development mode. For more details on this and the use of the Administration Console see Appendix D - "Integration Gateway Services .ear File Installation."

Note: See Oracle® WebLogic Server 10g Release 3 (10.3) Documentation - Administration Console.

1. Navigate to the "Deployments" page.

2. Locate the igs-service on the "Summary of Deployments" page.

3. Click the "+" next to the ig-service to expand the tree.

4. Locate the "Web Services" section.

5. Click on any web service (for example, "ASNInPublishingService") to move to a "Settings for ASNInPublishingService" page.

6. Select the "Testing" tab.

7. Click the "+" next to the service name to expand the tree.

8. Locate the "Test Client" link and select to move to the "WebLogic Test Client" page.

9. Select "Ping" operation. Fill in test data in string arg0: text box and click the Ping button.

10. The test page will show the request message and the response message.

Note: For more detailed verification testing, refer to the RIB Operations Guide - Integration Gateway Service Testing.