Oracle® Insurance Rules Palette
An environment connection is needed in order for the Rules Palette to communicate with the database that stores the application configuration.
Creating an environment connection in the Rules Palette involves two steps. First, establish a name for the environment. Next, confirm the database credentials. The actual database properties are pre-populated by the Web Application Utility, which is a tool used by the Build Manager. Confirm the database information by entering the user name and password.
There are two database sections: an application database and an Internal Versioning System (IVS) database. Connecting to an IVS database allows versions of the configuration to be stored so that previous versions can be reverted to if necessary.
The Build Manager will send the information needed to set-up an environment connection.
Currently Environment properties are stored locally in the Rules Palette’s “asenv.properties” file. If a user attempts to change the environment properties manually in the “asenv.properties” file (outside of the Web Application Utility), then a warning message will appear when the user tries to log into the environment. This occurs because the Rules Palette checks the properties settings saved in the Web Application Utility each time a user logs on. If the properties in the asenv.properites file do not match what is stored in the Web Application Utility, then the following error message will appear:
Environment Properties do not match. Logon will continue and properties will be reset.
All Rules Palette properties must be updated through the Web Application Utility.
When a user is logged into an environment, there are three right-click options available.
When a user is logged out of an environment, there are three right-click options available.
Copyright © 2009, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices