History Session Settings

In order to be able to use Valuemation Audit and History functionality, you have to make sure that several settings in following Valuemation configuration files are set right:

sessions.properties

• There have to be following two lines in the sessions.properties file (at the beginning of the file):

SessionName.HISTORY.mapping.*=ORACLE

This line determines which type of timestamp mapping should be used when reading from database:

ORACLE - stands for Oracle specific timestamp mapping

OTHER - stands for other than Oracle database specific timestamp mapping

Session.de.usu.s3.audit.derived.*=HISTORY

This line determines which session (in the example HISTORY) the technical object types from the stated package will use for the history data storage.

• Also the history database connection parameters have to be set in the sessions.properties:

### HOST / PORT / DATABASE / QAULIFIER

SessionName.HISTORY.host=vmdbsrv

SessionName.HISTORY.port=1521

SessionName.HISTORY.database=orcl

SessionName.HISTORY.tableQualifierMapping.TRENDQualifier=history

Note: If setting the sessions properties through the dbconfig.properties file, do not forget to set here the history database connection parameters too.

AuthenticationManager_jaas.config

For any Authentication Type that is going to be used for authentication during logging into Valuemation, one line must be added to their configurations:

de.usu.s3.authentication.DBLoginModule optional dbsessions="HISTORY" dbuser="system" dbpassword="693A6C37875494F00D189C70B4838A02";

dbsessions is a link to history session defined in the sessions.properties.

dbuser and dbpassword are the name an password to be used to connect to the history database.