Managing properties in the database

Note: The Override capability in managing properties in a database enables you to override the value of a property within a certain context. The Sterling™ Order Management System Software application reads a property's overridden value when an API or Agent is called in the context of that property. However, in other scenarios, the property's base value is read. The property management feature provides two types of overrides: User Override and Server Override.

• The User Override capability allows a user to override the value of a property in the user's context. When an API is called in the context of a user, it reads the overridden value and proceeds with the same. However, when the same API is called by another user, the application reads the property's base value. The user override behavior is not available when an API is called from the Sterling HTTP API Tester. The user information captured in the API Tester is only for the purpose of authentication.
• Server Overrides can be defined for an agent server instance. In this case, the agent server JVM has to be started with a name by setting the JVM level argument, 'jvminstance'. The property values are overridden against the jvminstance name. When an agent runs within this agent server, it reads the overridden value. However, when the same agent runs within another agent server, it reads the property's base value.