5
Runtime

This chapter describes how to use the Configuration Editor to configure the Siebel 7 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 Oracle Application Server InterConnect Configuration Editor User's Guide for more information on the Master Key.

Configuration Editor

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

1. Change directories to the ...\oai\9.0.4\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. For example, this is needed if you run two instances of the Siebel 7 adapter on the same machine. You can have two instances of the same type of adapter if these instances need to connect to different back-end system installations. To accomplish this, create a new profile using the configuration editor and enter 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 uses 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 7 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. All fields are case-sensitive.
   • Enterprise--Enter Siebel's Enterprise Server name, for example, siebel.

   • Gateway--Enter the name of the gateway, for example, SDK-Lab2. This can be an IP address or a gateway name.

   • AppServer--Enter the name of the application server where you have access to all the metadata for the Siebel system, for example, SDK-Lab2. The metadata is the information regarding the Business Services and Business Objects, which is the container for Business Components.

   • ObjectManager--Enter the name of Siebel's Object Management server, for example, SCCObjMgr.

   • Username--The user's name.

   • Password--The user password.

Verifying Your Siebel Information

To assist in connecting to a Siebel system, the following provides a brief description of Siebel terms and where you can locate information in a Siebel system.

• App Server--An Application server referring to the name of the Siebel Server. This is the name of host machine on which the Siebel server is installed.

• Gateway Server--A Gateway server is the name of the host on which the gateway server is running.

• Enterprise--An Enterprise refers to the name that was specified for the Enterprise server during a Siebel server installation.

• Enterprise server--An Enterprise server is a logical entity. It collectively represents the Siebel Servers (application servers) and Gateway server.

You can retrieve the name of the Gateway server, Siebel server, and Enterprise from the siebel.cfg file located in <siebel-root>/siebsrvr/BIN/ENU directory.

You can verify the Siebel user name and password by running Siebel Call Center. When you launch this application, enter a name and password (which has administrator privileges).

You can verify the Siebel Gateway, Enterprise, App server, and repository names with the corresponding entries in the siebel.cfg file.

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 the fields.

4. Select the version of the Siebel system you will access.

5. Check the Enable viewMode parameter in Query.

   When checked, a third parameter called viewMode is added to the Query operation. viewMode is a Siebel security feature. The value of the viewMode parameter determines the number of records returned by a query for a business component.

   When checked, the Siebel 7 adapter exposes the viewMode parameter in the query. At runtime, the Siebel 7 adapter fetches the value of the viewMode parameter (default is 0) and calls setViewMode on the Business Component before executing the Query.

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 a log in time out 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'. If a 'timeout' is issued you must login again.