Configuring Oracle Configurator

Use the following procedure to apply the run changes for the configuration to the database. The runtime configuration changes must be done before you can launch Oracle Configurator.

To apply runtime Siebel configuration changes

1. Login to eCommunications/HTIM application from a Web browser.

2. Navigate to the Administration - Integration screen, then the WI Symbolic URL List view, and complete the following steps:

   1. From the Show drop-down list, select Host Administration.

   2. Add a new host entry with the following values:

      • Host Name: Oracle EBIZ host name:port number, for example, qapache.us.oracle.com:3710

      • Virtual Name: OracleConfigurator

   3. Select Symbolic URL Administration and add a record in the upper applet with the following values:

      • Name: OracleCfgURL (Note: This symbolic name is very important because server side business component code relies on this name)

      • URL: http://OracleConfigurator/OA_HTML/CfgSebl.jsp

      • Choose the host name: for example qapache.us.oracle.com:3710

      • Fixup Name: Default

      • SSO Disposition: IFRAME

   4. In the lower applet, add arguments to the URL as follows:

      Create a new record with the following values:

      • Name: InitMessage

      • Req Arg: checked

      • Argument Type: Profile Attribute

      • Argument Value: CZInitMessage

      • Append as argument: checked

      Add another new record with the following values:

      • Name: PostRequest

      • Required Arg: Checked

      • Argument Type: Command

      • Argument Value: PostRequest

      • Append as argument: Not-Checked

      Complete the following two steps to set up the SSO login into Oracle Applications. The SSO login is the preferred style to access Oracle Applications. If the SSO login is not set up, then the Siebel end user must know and enter Oracle login credentials at the login page.

   5. For the next two arguments enter the values for Argument Value as specified. UserLoginId and UserLoginPassword are function names used by Siebel SSO. These functions look up the Oracle login credentials for the current Siebel User. Putting anything else in requires that you log in to an Oracle Applications for Configurator session.

   6. Continue to add arguments to the same URL with the following values:

      • Name: username

      • Required Arg: Checked

      • Argument Type: Command

      • Argument Value: UserLoginId

      • Append as argument: Checked

   7. Add the final argument with the following values:

      • Name: password

      • Required Arg: Checked

      • Argument Type: Command

      • Argument Value: UserLoginPassword

      • Append as argument: Checked

   8. Select SSO Systems Admin List and add a record in the upper applet with the following values:

      • System Name: OracleConfigSSO

      • Symbolic URL Name: OracleCfgURL

      • Description: Logs in to the Oracle Configurator

   9. In the lower applet, SSO System Users add records for the Siebel users who invoke Oracle Configurator. The Siebel usernames are paired with Oracle login credentials. An example follows:

      • Siebel Login Name: sadmin

      • Login Name: operations

      • Password: welcome

3. Navigate to the Administration - Server Configuration screen, Servers, and then the Components view. Select the eCommunications Object Manager (ENU) component and select the Order Management - Enable Asset Based Ordering parameter and set this value to False to call Oracle Configurator instead calling Siebel Configurator.

   Select the HTIM Object Manager (ENU) component and select the Order Management - Enable Asset Based Ordering parameter and set this value to False to call Oracle Configurator instead of calling Siebel Configurator.

   The following workflows must be active in the Design Repository for Configurator to work:

   • Account - New Quote

   • Account - New Order

   • Goto*

   • PSP*

   • Product Compatibility*

   • Product Eligibility*

   • Product Reco*

   • *Pric*

   • Compatibility Multiple Popup Workflow

   • Config*

   • Check*

   These workflows are not workflows that were introduced as part of Oracle Configurator integration, but are existing ones.