Oracle® Insurance Rules Palette
The Build Manager will use the Web Application Utility to configure the Rules Palette environment properties and the remote debugging Web Service. When Rules Palette users create a new environment, they will need the server name, port number, and three sets of user IDs and passwords. The IDs and passwords needed are:
Palette Config user ID & password: contact the build manager.
database ID & password: contact the person who set-up the database.
IVS database ID & password: contact the person who set-up the IVS database.
Log in to the Web Application Utility using the following URL: http://host:port/PaletteConfig/. The host (server name) and port should be the same as the host and port of the application (OIPA or OINBU) being used. The default user name and password are provided in the Web Application Utility installation guide.
Log in to the Web Application Utility using the URL: http://host:port/PaletteConfig/.
Click Environment Options and then Edit.
Enter the information for the environment:
PaletteVersion: Enter the version of the Rules Palette that will be used.
Select the Yes radio button for IVS if using an IVS environment.
Enter the IVS environment information.
IvsDatabaseType: SqlServer2005, SqlServer, Oracle or DB2.
IvsDatabaseServer: Server where the database is located.
IvsDatabasePort: Port of the database.
IvsDatabaseSchema: Schema of the database.
IvsDatabaseUserName: Enter the IVS database user name.
IvsDatabasePassword: Enter the IVS database password.
IvsEnv: Name of the IVS environment that will be used.
IvsTrackNumber: Track number of the IVS environment that will be used.
The combination of IvsEnv, IvsTrackNumber and IvsSequence must be unique to each specific environment.
Select whether the environment should have New Business Underwriting functionality available.
Send the host, port and password information to the Rules Palette users so that they can set-up the environment.
Send the location of the jtds.jar file if users have a SQL Server database.
Copyright © 2009, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices