Working on Multiple Development Databases

In an environment where Valuemation customization tasks are performed on several development databases, the need to coordinate the logging information will arise.

Several databases would mean several independent AMT_Log tables. This would make the log useless for the task of warning the user when he or she is about to make changes to a recently changed object. (As the information about the change - together with the changed object itself - would "live independently" in several databases)

The solution is to share one AMT_Log table between several databases. One of these databases is considered the main database containing the shared AMT_Log table.

All of the remaining databases have to be configured in the following way:

1. A new session must be configured. This session will point to the main database.
2. Log object type in each of the databases must be linked to the new session, hence drawing data from the main database.

Regarding each of the two steps:

• Configure a new session. Let's call it LOG SESSION.

  We will need to modify two files located in your Valuemation root folder:

  a) sessions_.properties file for the database system which you use. In our examples we will use sessions_oracle.properties used for Oracle.

  b) dbconfig.properties

  Do the following:

  a) sessions_.properties (e.g. sessions_oracle.properties)

  Create the new session. This can be done by copying another session and editing it so that it reflects the new session name. (See Example 1)

  b) dbconfig.properties

  Add a session connection for the LOG SESSION and connect it to the main database. This could be done by copying an existing session connection, editing its name and specifying correct information for connection to the main database. (See Example 2).

• In order to link the Log object type to the new session, the following line must be added to sessions_.properties file (the one edited in the previous step):

  Session.de.usu.s3.bo.generic.Log=LOG_SESSION (See Example3 for Oracle)

Examples:

• Example 1: New session (in sessions_oracle.properties)
• Example 2: Connection to the new session (in dbconfig.properties)
• Example 3: Linking the Log object type to the new session (in sessions_oracle.properties)