1
Introduction to the Configuration Editor

A profile is a group of settings edited by the configuration editors that can be attached to a service to specify start up conditions during runtime. Oracle Application Server InterConnect Configuration Editor allows you to create and edit these profiles.

The following topics are discussed in this chapter:

• Using the Master Key Setting Tool

• Setting the Master Key

• Multiple Users Using a Windows Development Machine (R/3 Specific)

Using the Master Key Setting Tool

Profiles are sensitive to the Master Key setting. The role of the Master Key is to encrypt security and password information, for example, for R/3 or PeopleSoft^TM, provided in the Configuration Editor for a specific profile.

The iStudio browser uses the iStudio profile to access to various service provider systems. If using a shared machine, and User1 has set a Master Key, ensure to set the Master Key same as that of User1 before accessing the Configuration Editor. It is also recommended to set the Master Key when you are exporting an iStudio profile to another machine.

Setting the Master Key

Use the Master Key Setting Tool to set the master key string. To start the Master Key Setting Tool, type the following command at the command prompt:

chsetkey

• On Windows--The browser brings up the Master Key Setting Tool dialog, which prompts you to enter the master encryption key.

• On Unix--The Master Key Setting Tool prompts you for a Master Key at the command prompt.

  Figure 1-1 Master Key Setting Tool Dialog

  

  Text description of the illustration masterkey.gif

You can use any alpha/numeric combination for the Master Key. After setting the new Master Key, the new key is active and replaces any other key previously set. If you are exporting the profile after you have set the master key, make sure to use the same key when importing the profile on the other machines.

If you have previously used iStudio to expose components or to create events and procedures, you do not have to redo any of your work. Setting the new key is transparent to any work previously done.

Multiple Users Using a Windows Development Machine (R/3 Specific)

If more than one person uses the same Windows Development machine, the information in the default and reference login to R/3 is permanently corrupted. The following example explains this statement:

1. User1 logs onto an Windows machine and sets the settings in the Configuration Editor.

2. User1 logs out.

3. User2 logs in and accesses the profile settings. The information in the Default and Reference logins are corrupt.

4. User2 logs out.

5. User1 logs in again and accesses the Configuration Editor. The values in the Default and Reference logins are corrupt.

Work Around

The following example provides a workaround for the corruption of the default and reference log in:

1. User1 logs onto an Windows machine and creates a profile or uses an existing profile.

2. User1 uses the Master Key utility to enter a key.

3. User1 logs off.

4. User2 logs on.

5. Before User2 accesses any product features such as the Configuration Editor, User2 must use the Master Key utility to enter the same key that User1 had created. From then on, there is no further corruption of data.

   Note: Any additional user on that machine must use the same procedure as User2.