5
Runtime

This chapter describes how to use the Configuration Editor to configure the Siebel adapter. The Configuration Editor is only used at runtime.

The following topics are discussed:

• Configuration Editor

• Log On Siebel

• General

  Note: Profiles and Deployment are sensitive to the Master Key setting. If using a shared machine, before accessing the Configuration Editor, ensure the Master Key either is set to that of User1 or create a new Master Key for your profiles. Refer to the Oracle9iAS InterConnect Configuration Editor User's Guide for more information on the Master Key.

Configuration Editor

To configure settings for the Siebel adapter you must access the Siebel Configuration Editor as follows:

1. Change directories to the ...\oai\9.0.2\config\configeditor using a DOS prompt.

2. Type configeditor and press Enter.

   The Configuration Editor displays.

3. Click Profile.

4. Select the iStudio profile.

   Note: Under some circumstances you may wish to run your adapter under a profile other than iStudio. This may be needed, for example, if you want to run two instances of the Siebel adapter on the same machine. You may want to have two instances of the same type of adapter if these instances need to connect to different backend system installations. To accomplish this you need to create a new profile using the configuration editor and fill in the settings for this new profile. The name of the new profile should be the same as the name of the application. For example if your application is called APP2, create a profile called APP2. Now APP2 will use the settings in the profile called APP2 whenever it runs.

   Figure 5-1 Configuration Settings Editor Default Dropdown Menu

   

   Text description of the illustration configedprofile.gif

5. Expand Siebel to edit the configuration settings for the iStudio profile.

Log On Siebel

The Default Login to Siebel allows you to program your application to automatically connect to Siebel servers. The login credentials under both Repository credentials and Default Runtime Credentials branches are used by the Siebel adapter. The default credentials are used at runtime to submit requests to the business functions.

Note: Follow the same procedure to modify the repository credentials.

The Default Login to Siebel authenticates your runtime credentials. From the Configuration Editor main menu:

1. In the left panel, expand Default Runtime Credentials.

2. Click Use Global Settings to edit the configuration settings for your profile.

3. Click Default Runtime Credentials.

   The Configuration Settings Editor login dialog displays in the right panel.

   Figure 5-2 Configuration Settings Editor Login Dialog

   

   Text description of the illustration configedlogin.gif

4. Enter the information in the following fields:
   • Enterprise--The Siebel system Enterprise Server.

   • Gateway--The name of the gateway. This can be an IP address or a gateway name.

   • AppServer--The name of the Application server. This is where there is granted access to all the metadata for the Siebel system. The metadata is the information regarding the Business Services, Business Objects, and the Business Components.

   • ObjectManager--The name of the Object Management server.

   • Username--The username.

   • Password--The user password.

General

In the General section, you can modify where to locate the Siebel Repository, the Login Time Out interval. From the Configuration Settings Editor main dialog:

1. Click to expand General.

2. Click to uncheck Use Global Settings.

3. Click General.

   In the dialog to the right, you can edit three fields.

Siebel Repository

Enter the name of the repository where the Siebel Repository files are located. The Siebel Repository contains Business Service methods, Business Components, and typed method arguments.

Figure 5-3 Configuration Settings Editor Timeout

Text description of the illustration configedtimeout.gif

Login Time Out (in seconds)

This variable determines how long you have to wait for a response before the system timesout. This value must be set between 10 and 300 seconds. Networks with a higher load should have this timeout variable set to a higher limit to allow enough time for the request to process.

The purpose of having Login timeout is to keep the threads from deadlocking. If there is no response within the specified time, the system stops sending packets and issues a 'timeout'. At that point, you need to reinitiate a login.