Siebel In-Memory Next Best Action Guide > Setting Up Siebel In-Memory Next Best Action >

Integrating the Oracle Real-Time Decisions Server with the Siebel Application

This task is a step in Process of Setting Up Siebel In-Memory Next Best Action. Use the following procedure to integrate the Oracle Real-Time Decisions Server with the Siebel application.

To integrate the Oracle Real-Time Decisions Server with the Siebel application

1. Within the Siebel application, navigate to the Administration - Web Services screen, then the Outbound Web Services view.
2. Within the Outbound Web Services list applet, query for *sigma* in the Namespace field.
3. For the ExternalChoiceService, update the Address field in the Service Port applet (the middle applet) to point to the appropriate RTD server (for example, http://<server name>:<port number>/soap/services/ExternalChoice), and click the Clear Cache button.
4. Navigate to the Administration - Integration screen, WI Symbolic URL List, and then the Host Administration view.
5. Within the Host Administration list, query for RTD_SERVER in the Virtual Name field.
6. Specify the host name of the RTD Server in the Name field: <server name>:<port number>.
7. Navigate to the Administration - Integration screen, WI Symbolic URL List, and then the Symbolic URL Administration view.
8. Within the Symbolic URL Administration list applet, query for *RTD* in the URL field.

   The query should return seven symbolic URL records.

9. For each of these symbolic URL records, update the app argument value with the Inline Service name that you plan to use, such as SiebelB2C or SiebelB2B.
10. Change the user name and password for all of the records.
11. Navigate to the Administration - Server Configuration screen, Servers, and then the Parameters view.
12. Within the Server Parameters list applet, query for RTD* in the Parameter field.

    The query should return four RTD parameter records.

13. Specify the following values for the four parameters:
    • RTD Application Name: Enter the RTD Application Name, such as B2C.
    • RTD SOAP URL: Enter the RTD Server URL and port, such as http://<machine name>:<port number>/rtis/sdwp
    • RTD Session Cookie Name: JSESSIONID (the default value)
    • RTD Web Service Timeout: 3000 (this is the default value, but it can be changed)

      NOTE:  Follow Step 14 to Step 17 only if you want to enable the default runtime events.

14. Navigate to the Administration - Runtime Events screen, then the Action Sets view.
15. Within the Action Sets view, query for RTD* in the Name field.

    The query should return four RTD parameter records.

16. Set the Active field to TRUE to make the Action Set records active. Do this only for the Inline Services that you are using. For example, only set the B2C records as active when you are using the SiebelB2C Inline Service.

    NOTE:  Do not activate any of the RTD Informant: Offer Event Interested or RTD Informant: Offer Event Not Interested runtime events. These runtime events are no longer supported.

17. Select Reload Runtime Events from the menu to clear the cache.