Application components that communicate only with the Oracle WebLogic server depend on the Oracle WebLogic Server to communicate directly with the database. Table 2-2 describes system applications that communicate with the Oracle WebLogic server.

These components are managed by configuration files that have identical, or almost identical, content. Each INI file provides the following types of information for the associated EXE:

• An Oracle WebLogic Server profile name

  For example:

  [Application Servers]
  J2EEProfiles= 'MSS63'

• An Oracle WebLogic Server port ID

  For example:

  [J2EEProfile MSS63]
  url=https://server.us.example.com:8630

Table 2-3 describes system applications that communicate with the database.

You can create a tbs_db.ini file to enable the tbs_util.exe and npasplit.exe files to communicate with the database through one file, using a shared INI parameter. Doing so allows you to make changes to only the tbs_db.ini file, which is shared by the other three files. Following is an example of a tbs_db.ini file:

[DBMS_Profiles]
Profiles= 'MSSPROD'

[Profile MSSPROD] 
DBMS=ORA 
Database=Oracle 
UserId= 
DatabasePassword= 
LogPassword= 
ServerName=M63PROD
LogId= 
Lock= 
DbParm=DisableBind=0,DelimitIdentifier='No',CommitOnDisconnect='No' 
PRomPt=1 
AutoCommit=0 
url=http://192.0.2.62:9638

lerg.ini, tbs_util.ini, and npasplit.ini include any changes that are in the tbs_db.ini file when a Sharedini= parameter is added to them, because the parameter indicates that the tbs_db.ini file should be referenced. Following is a model npasplit.ini file:

[DBMS_Profiles]
SharedIni=\\path\TBS_db.ini

Where path represents the path to the tbs_db.ini file.

Following is a sample tbs_util.ini file that uses the shared reference:

[DBMS_Profiles]
SharedIni=\\srvpldevsrvc1\testing\6.3.x_ini\tbs_db.ini

When changes are made to the location of the database or the Oracle WebLogic server, changes must be made in the MetaSolv Solution INI files. The INI files provide information about the names you want to appear in the log on database list.

Template copies of these files are copied to the /appserver/config directory on the Oracle WebLogic server by the installer. The installer edits these files to include specifications for each specific Oracle WebLogic server.

Several gateway.ini parameters can have a significant negative impact on Oracle WebLogic server performance. They are:

• CacheRefreshMode [CA]

• DBPollingInterval [Event2]

• DBPollingInterval [Events]

• PrintExportObjects [Gateway]

See "Parameters for gateway.ini File" for details.

When you install the application server, the session_password and jndi_password are encrypted in the [Session] and [JNDI] sections respectively in the gateway.ini file. The encrypted passwords are prefixed with {AES}.

For example:

[Gateway]
APPJMSUser=app_jms
APPJMSPwd=
[Session]
User=app_api
Password=
[JNDI]
User=administrator
Password=
Factory=weblogic.jndi.WLInitialContextFactory
URL=t3://srvsunpluto:7001

After the application server is installed, you may opt to change the passwords for different users of the application server. If you change the user passwords for the application server, you must encrypt your new passwords, and then copy the encrypted passwords in the [Session], [Gateway], and [JNDI] sections of /appserver/gateway/gateway.ini file. See "Sample installed gateway.ini File" for more information.

To encrypt the new password using MetaSolv Solution Utilities:

1. Start the MetaSolv Solution Utilities application. See "Using the MetaSolv Solution Utilities" for more information.

2. From the File menu, select Security, and then select Encrypt Passwords.

   The Encrypt Passwords dialog box appears.

3. In the Password in Text field, enter your new password.

4. Click Encrypt.

   The encrypted password appears in the Encrypted Word field.

5. Copy the encrypted password and paste it in the appropriate section of gateway.ini file.

6. Restart the application server.

Set all logging levels to error in the loggingconfig.xml for normal use. Change the severity only during troubleshooting. For information about the loggingconfig.xml file parameters, see "Annotated Logging Configuration Files".

Under some conditions, changes must be made to parameters in configuration files. You will make changes when your environment changes, when instructed to make changes by Oracle Global Customer Support, or when using the logging files to track problems.

For details about configuration and deployment at your site, see your site's deployment diagram.

To edit the INI or XML configuration files:

1. Backup the configuration file.

2. Open and edit the file by using any common editor, such as Notepad.

3. Shut down and restart the Oracle WebLogic server unless changing the loggingconfig.xml file.

For Oracle WebLogic Server-related changes, check the upper left corner in the WebLogic Server Administration Console where a message is displayed that informs you whether you need to restart the server or not.

Configuration files include specific information about the environment, such as machine names, database IDs, and so on. Use Table 2-5 as a guide to changing your configuration files if environment changes are made.

Some MetaSolv Solution configuration files reside on the client. They are:

• jmaster.ini

• lerg.ini

• npasplit.ini

• tbs.ini

• tbs_util.ini

Other configuration files reside on the Oracle WebLogic server.

To change any configuration file:

1. Locate the file on the Oracle WebLogic server.

2. Open the file using Notepad or any text editor.

3. Enter your changes and save the file.

4. Deliver the file to the client machines manually.

5. (Applicable only to the gateway.ini file) Restart the Oracle WebLogic server.

   Note:

   When you suspend and resume a MetaSolv Solution polling server process, that process does not re-read the gateway.ini settings that affect its operation. To put changes into effect, you must shut down and restart the Oracle WebLogic server.