| Oracle® Real-Time Decisions for Siebel E-Commerce Installation and Reference Guide Version 2.2.1 Part Number E12261-01 |
|
|
View PDF |
| Oracle® Real-Time Decisions for Siebel E-Commerce Installation and Reference Guide Version 2.2.1 Part Number E12261-01 |
|
|
View PDF |
This chapter describes the steps required to install Oracle Real-Time Decisions for Siebel E-Commerce.
As prerequisites, you must have installed one of the Oracle RTD supported J2EE application servers, and you must have successfully deployed the Oracle RTD server on to this application server. Before starting the installation, verify that Oracle RTD is running and that the server logs do not contain any errors.
For information on installing the Oracle RTD Server, please refer to Oracle Real-Time Decisions Installation and Administration of Oracle RTD, which is available with the Oracle RTD platform software.
The chapter describes how to set up the Oracle RTD-specific portion of the overall Siebel E-Commerce application, that is, the RTD Siebel ECommerce Inline Service.
Note:
Details on the integration to Oracle RTD from the front end application can be found in the Siebel E-Commerce Administration Guide, in the section "Setting Up Hot Offers for Siebel E-Commerce."Setting up the Inline Service for the Siebel E-Commerce application involves the following tasks:
Section 1.1, "Configuring JDBC Data Source for Access to Siebel OLTP Data"
Section 1.2, "Importing the RTD Siebel ECommerce Inline Service into Oracle RTD Decision Studio"
Section 1.3, "Verifying the Setup of the Siebel Data Source"
Section 1.4, "Deploying the RTD Siebel ECommerce Inline Service to the Oracle RTD Server"
Section 1.5, "Specifying the List of Trusted Hosts for Decision Service Requests"
Section 1.6, "Testing the Deployed Inline Service Via Web Service Calls"
Section 1.7, "Setting Up the RTD_WEB_HISTORY Table (Optional)"
The following JDBC data sources are required for this application:
| Data Source Name | Type | Description |
|---|---|---|
| SDDS | System | Stores the deployed projects, run-time sessions and model learnings. This data source should have already been configured as part of the Oracle RTD server setup. |
| Siebel | Source | Used to fill the Oracle RTD session entities such as the customer and asset entities from the Siebel OLTP. |
Create the Siebel data source by selecting the steps appropriate to the application server you are using, from the following list:
For instructions on how to install and deploy Oracle RTD Server through the WebSphere admin console, see the Oracle RTD platform document Oracle Real-Time Decisions Installation and Administration of Oracle RTD, Section 4.
The following steps describe how to create the Siebel data source and register it with the Oracle RTD server:
Create the Siebel data source within WebSphere, as described in Section 7.2 of Oracle Real-Time Decisions Installation and Administration of Oracle RTD. The data source parameters required (database host, name, port, username, password, and so on) are those of the Siebel OLTP database.
In section 7.2.1, steps 13b and 13c, be sure to enter Siebel as the data source name and the JNDI name.
This data source will be used by Oracle RTD to query the Siebel OLTP and to populate information entities such as the customer, agent and products owned.
Create resource references to the Siebel data source. This process is described in Section 7.2 of Oracle Real-Time Decisions Installation and Administration of Oracle RTD.
Restart the application server.
For instructions on how to install and deploy Oracle RTD server through the WebLogic admin console, see the Oracle RTD platform document Oracle Real-Time Decisions Installation and Administration of Oracle RTD, Section 5.
The following steps describe how to create the Siebel data source and register it with the Oracle RTD server:
Create the Siebel data source within WebLogic, as described in Section 7.3 of Oracle Real-Time Decisions Installation and Administration of Oracle RTD. The data source parameters required (database host, name, port, username, password, and so on) are those of the Siebel OLTP database.
In section 7.3.2, steps 4a and 4b, be sure to enter Siebel as the data source name and the JNDI name.
This data source will be used by Oracle RTD to query the Siebel OLTP and to populate information entities such as the customer, agent and products owned.
Create resource references to the Siebel data source. This process is described in Section 7.3 of Oracle Real-Time Decisions Installation and Administration of Oracle RTD.
Restart the application server.
For instructions on how to install and deploy Oracle RTD server through the Oracle Enterprise Manager console, see the Oracle RTD platform document Oracle Real-Time Decisions Installation and Administration of Oracle RTD, Section 3.
The following steps describe how to create the Siebel data source and register it with the Oracle RTD server:
Create the Siebel data source within OC4J, as described in Section 7.1 of Oracle Real-Time Decisions Installation and Administration of Oracle RTD. The data source parameters required (database host, name, port, username, password, and so on) are those of the Siebel OLTP database.
In section 7.1.2, steps 11a and 11b, be sure to enter Siebel as the data source name and the JNDI name.
This data source will be used by Oracle RTD to query the Siebel OLTP and to populate information entities such as the customer, agent and products owned.
Create resource references to the Siebel data source. This process is described in Section 7.1 of Oracle Real-Time Decisions Installation and Administration of Oracle RTD.
Restart the application server.
The RTD Siebel ECommerce Inline Service is packaged in a zip file which contains XML and Java files organized in a directory structure. To load, view, and edit the Inline Service, use the Oracle RTD client tool Decision Studio.
To set up the RTD Siebel ECommerce Inline Service, you must import the Inline Service project into Decision Studio, as follows:
Create a directory for your Inline Services, for example, C:\RTD_ILS.
This directory will be referred to as RTD_ILS_HOME in this documentation.
From the Oracle RTD Applications software directory, Oracle Real-Time Decisions for Siebel E-Commerce, unzip the application zip file, RTD_Siebel_ECommerce.zip, into RTD_ILS_HOME.
This creates the directory RTD_Siebel_ECommerce under RTD_ILS_HOME.
In Decision Studio, select File > Import.
From the Import window, select Existing Projects into Workspace.
If not already visible in the Projects area of the Import Projects dialog box, click the Browse button, and locate RTD_Siebel_ECommerce under RTD_ILS_HOME, for example C:\RTD_ILS\RTD_Siebel_ECommerce.
Select the directory RTD_Siebel_ECommerce in the file dialog box and click Ok.
Confirm that the RTD_eCommerce Inline Service project name appears in the project window and is checked True.
Click the Finish button to load the project into Decision Studio.
The next step is to verify that the Siebel data source is accessible by the Oracle RTD server. This verifies that you have set up the Oracle RTD data source properly as described in Section 1.1, "Configuring JDBC Data Source for Access to Siebel OLTP Data."
Perform the following steps:
In the RTD_eCommerce Inline Service project, expand the Data Sources folder and double click Assets DS.
Click the Import button in the configuration window.
Select the active Oracle RTD server from the dialog box that pops up and click Next.
If the JDBC data source was configured correctly, the application enables you to select Siebel as a data source and then to display the list of tables in the OLTP.
If this is not the case, check the configuration of your JDBC data source, and if necessary perform the configuration again.
Click the Cancel button, since there is no need to re-import the data source.
The RTD Siebel ECommerce Inline Service is now ready to be deployed to the Oracle RTD server, as follows:
Click Deploy, located in the Decision Studio toolbar.
If multiple projects are open in Decision Studio, ensure that the correct Inline Service project, RTD_eCommerce, is selected.
Ensure that the deployment state is set to Development.
Click Deploy.
If the Inline Service deploys successfully, the message "RTD_eCommerce deployed successfully" appears in the bottom status bar.
Before the Oracle RTD server can accept requests, the list of trusted hosts must be updated to include IP addresses where requests will originate. The instructions to achieve this goal appear in the section that follows.
If both the E-Commerce server and the Oracle RTD server are installed on the same physical computer, this section can be bypassed. If the servers reside on different computers (or belong under different IP addresses), the IP address of the E-Commerce server must be added to a list of trusted hosts for Oracle RTD Decision Service requests.
Similarly, if Oracle RTD Decision Studio (or Oracle RTD Load Generator) is located on a different computer from that of the Oracle RTD Server, and you want to send sample requests using the Test View in Decision Studio, then the IP address of the computer that hosts either or both of Decision Studio and Load Generator will also need to be added to the list of trusted hosts. The list is stored within the Oracle RTD server and maintained through Oracle RTD's JMX administration console (JConsole) as described later in this section.
To specify a list of trusted hosts for Oracle RTD Decision Service requests, perform the following steps:
If you are using OC4J or WebLogic, open JConsole by running JAVA_HOME/bin/jconsole.exe.
If you are using WebSphere, run the batch script you created during JConsole configuration.
For more information about accessing JConsole, see the Oracle RTD platform document Oracle Real-Time Decisions Installation and Administration of Oracle RTD.
Click the Remote tab.
Enter the appropriate port number (typically 12345) and the administrator credentials that you created during installation.
Click Connect.
Click the MBean tab.
Navigate the path OracleRTD > SDClusterPropertyManager > Cluster MBean.
Ensure that the RestrictDSClients attribute is set to true.
This attribute ensures that the Decision Service only accepts requests from its own host, or from the list of hosts identified in the TrustedDSClients attribute.
Update the TrustedDSClients attribute to include a semicolon-separated list of IP addresses of the hosts from which you want Decision Service to accept requests.
You must specify IP addresses. Do not specify host names.
When the data source connectivity has been verified, and the Inline Service has been deployed, the next step is to do a dry run of the application using the Oracle RTD Decision Studio's built-in Test View.
After integration has been set up with the E-Commerce front end, integration calls to Oracle RTD can also be initiated there as well.
Within the JMX console, set the logging level to DEBUG.
Debug statements have been incorporated into the inline service that help trace the execution of each informant. Setting the log mode to DEBUG will allow the user to see these statements in the Oracle RTD server log.
Navigate to the Test tab on the lower quadrant of Oracle RTD Decision Studio.
If this tab is hidden, from the Oracle RTD Decision Studio's main menu, select Window > Show View >Test to expose it.
Select Update Customer Profile from the Integration Point dropdown.
For this test, fill in any value for the Web Session Id attribute.
From the Account Id attribute, select a real ROW_ID value for any account record found in the Siebel OLTP.
Leave the other attributes blank.
Click the Play button and a web services call is made to the Oracle RTD Server.
The Log tab displays the output results. Verify that customer values returned in the output are the same values found in the OLTP. For example, validate that the customer's State and Zipcode is correct.
Verify that customer values returned in the output are the same values found in the OLTP.
For example, validate that the customer's State and Zipcode are correct.
If the test fails, examine the exception stack trace from either the server command window, if one exists, or from the Oracle RTD server.log file.
This log contains information useful in debugging the problem.
For typical locations of the Oracle RTD server.log file, see section 6.1.2 of Oracle Real-Time Decisions Installation and Administration of Oracle RTD.
The RTD_WEB_HISTORY table is a unique table created in the RTD schema (SDDS) specifically for the Siebel E-Commerce solution. When utilized, it stores a transaction of each web session started in Oracle RTD along with key data about the session itself. Each time the session closes or times out, Oracle RTD writes a record to this table.
The logic to write to this table can be found in the "cleanup logic" section of the Session entity.
To create and enable the RTD_WEB_HISTORY table, perform the following steps:
From the RTD_ILS_HOME\RTD_Siebel_ECommerce directory created for the RTD Siebel E-Commerce Inline Service, navigate to the etc folder.
Inside the etc folder, there are several SQL scripts entitled Create RTD Web History...
Select the appropriate script for the database type used for your Oracle RTD database.
Run the script to create the RTD_WEB_HISTORY table in Oracle RTD's SDDS database.
To run the script, use a SQL editor appropriate to your database type.
After the table is created, validate that the RTD server can see this table following a similar procedure to the one outlined in Section 1.3, "Verifying the Setup of the Siebel Data Source."
To enable Oracle RTD to write to this table through the supplied logic, the Application parameter Enable RTD Web History must be set to True in the Inline Service.
Note that in the released version of the RTD Siebel ECommerce Inline Service, the value of Enable RTD Web History is set to True.
After the RTD_WEB_HISTORY table is created, a record for each Oracle RTD session will be stored in this table, which can then be used by the Web Interaction Entity.
If you need more columns in this table, you can modify the SQL script to add the additional columns. You will also need to modify the Log Writer and Insert Message Result functions included as part of the Inline Service, so that Oracle RTD can write data to these new columns.
