Oracle® Insurance Rules Palette 10.1.2.0 E59346-01

Build Manager Environment Creation

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. 

Web Application Utility

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.

Steps for Build Manager to Set-up Environment Properties

1. Log in to the Web Application Utility using the URL: http://host:port/PaletteConfig/. 

2. Click Environment Options and then Edit.

3. Enter the information for the environment:

1. PaletteVersion: Enter the version of the Rules Palette that will be used.   

2. ApplicationEnvType: Either Development or Production for the type of environment. 
3. EncryptionType: Select the type of encryption to be used for the environment's password.
4. EncryptionIterationCount: Select the iteration count to be used with the selected encryption type.
5. DebuggerWebserviceUrl: URL for the Web Service used to connect for remote debugging. The host and port information must match the host and port information for the OIPA or OINBU application you are using. Ex: http://<host>:<port>/ PASJava/service/DebuggerService?wsdl  
6. DebugUserName: Enter the debug user name. This is a created in the Application Security section of Rules Palette. Add a user and grant debugger security privilleges.  
7. DebugPassword: Enter the debug password. 
8. ApplicationDatabaseType: Either SqlServer2005, SqlServer, Oracle or DB2. 
9. ApplicationDatabaseServer: Enter the server where the database is located. 
10. ApplicationDatabasePort: Enter the port for the database. 
11. ApplicationSID: Enter the SID. Only needed for Oracle.
12. Application Database Schema: Enter the schema of the database. Only needed for DB2 and Oracle.
13. ApplicationDatabaseUserName: Enter the database user name.
14. ApplicationDatabasePassword: Enter the database password. 

4. Select the Yes radio button for IVS if using an IVS environment.

5. Enter the IVS environment information.

1. IvsDatabaseType: SqlServer2005, SqlServer, Oracle or DB2. 

2. IvsDatabaseServer: Server where the database is located. 

3. IvsDatabasePort: Port of the database. 

4. IvsSID: The SID of the IVS database. Only needed for Oracle.

5. IvsDatabaseSchema: Schema of the database. 

6. IvsDatabaseUserName:  Enter the IVS database user name.

7. IvsDatabasePassword:  Enter the IVS database password.

8. IvsEnv: Name of the IVS environment that will be used. 

9. IvsTrackNumber: Track number of the IVS environment that will be used.  

10. IvsSequence: Defines the position of the environment in the Release Management track. Release packages will need to be deployed to environments with an IVS Sequence of "2" before those with an IVS Sequence of "3" and so on.

The combination of IvsEnv, IvsTrackNumber and IvsSequence must be unique to each specific environment.

6. Select whether the environment should have New Business Underwriting functionality available.

7. Select whether the environment should use Products.
8. Select whether the environment should use Release Management.
9. If Release Management was turned on in the previous step, select whether the environment is a Release Management Entry Environment.

Palette Options fields on Web Application Utility

10. Select Save.  

11. 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.