Access the Application
Before any users can access the OIPA application and Web Application Utility, you must configure the Web Application Utility environment and create at least one user for each application.
Connect to the Web Application Utility for the First Time
- In your browser, go to the URL of the Web Application Utility (in the general format of http://<server_name>:<port>/PaletteConfig/, where the <server_name> and <port> are determined by your local installation).
- The server presents a screen for you to configure the environment and set up the first user.
Note:This screen is displayed only on the first access, before any users have been created. After one or more users are created, you will always see the login screen when you connect to this server.
Create First Web Application Utility User
The first section in the initial screen requires you to create the first Web Application Utility user:
- Enter a user name in the PaletteConfigUserName field.
- Enter a password in the PaletteConfigPassword field.
- Re-enter the password in the PaletteConfigPasswordConfirm field.
Note: The first Web Application Utility user will have an "administrator" role by default. Any subsequent users that are created can be either administrators or non-administrators. Non-administrator users will only have the ability to download the Palette and change their password.
Configure Environment Details
The Environment Details section of the initial screen contains fields for defining the Web Application Utility operating environment.
Web Application Utility Environment Details in Initial Screen
- Enter the information for these environment details:
- PaletteVersion – enter the complete version number, such as 11.1.0.0. This is used to ensure the corresponding OIPA version is used.
- ApplicationEnvType – either Development or Production.
- PASConfigurationCacheClear – select the option.
- EncryptionType – select the password encryption algorithm.
- EncryptionIterationCount – enter the number of iterations of the encryption algorithm as an integer value from 1000 to 9999.
- Leave the following fields empty for now. (you can fill in this information later using the steps in step 4 of the procedure in Edit Environment Options in the Web Application Utility):
- DebuggerWebServiceUrl
- DebugUserName
- DebugPassword
- Fill in the rest of the fields:
- ApplicationDatabaseType –SqlServer, Oracle or DB2.
- ApplicationDatabaseServer – hostname where the database is located.
- ApplicationDatabasePort – database listener port.
- ApplicationDatabaseName – name of the database. (Only used for SqlServer and DB2)
- ApplicationDatabaseSchema – schema of the database. (Only used for DB2)
- ApplicationSID – SID of the database. (Only used for Oracle)
- ApplicationDatabaseUserName – enter the OIPA database user name. This information can be obtained from the database administrator.
- ApplicationDatabasePassword – enter the OIPA database password. This information can be obtained from the database administrator.
- Consider the IVS radio button options:
- If IVS is needed, select Yes.
- If IVS is not needed, select No.
- Enter the IVS environment information.
- IvsDatabaseType – select SqlServer, Oracle or DB2.
- IvsDatabaseServer – enter the hostname where the database is located.
- IvsDatabasePort – enter the database listener port.
- IvsDatabaseName – name of the database. (Only used for SqlServer and DB2)
- IvsDatabaseSchema – schema of the database. (Only used for DB2)
- IvsSID – SID of the database. (Only used for Oracle)
- IvsDatabaseUserName – enter the IVS database user name. This information can be obtained from the database administrator.
- IvsDatabasePassword – enter the IVS database password. This information can be obtained from the database administrator.
- IvsEnv – enter a name for the IVS environment that will be used.
- IvsTrackNumber – enter a track number for the IVS environment that will be used.
- IvsSequence – enter the environment's position within the IVS/Release Management track.
Note: The combination of IvsEnv, IvsTrackNumber and IvsSequence must be unique to each specific environment.
Configure Palette Options
The Palette Options section of the initial screen allows you to control the use of optional Rules Palette functionality. If the functionality is not turned on in this location, it will not be visible to the users in the Rules Palette.
- Consider the NBU radio button options:
- If NBU functionality is needed, select Yes.
- If NBU functionality is not needed, select No.
- Consider the UseProducts radio button options.
- If using products, then select Yes.
- If products are not being used, then select No.
- If you set the IVS radio button option to "Yes" (in the Environment Details section), the ReleaseManagement radio button option is displayed:
- If release management is not being used, then select Off.
- If using release management, then select On. The ReleaseManagementEntryEnv radio button appears. This is only visible when "Release Management" is set to On.
Release ManagementEntryEnv Radio Button Active
- If this environment is the Release Management Entry environment, then select True.
- If this is a Release Management Target environment, leave the setting at False. (The default setting is False.)
Create First Rules Palette User
The last section in the initial screen requires you to create the first Rules Palette user. When you hit the "Save" button after entering all environment details, the following screen will appear if there no existing Rules Palette users.
First Rules Palette User Section in Initial Screen
- Select the user role for the first user.
Important: This only appears for IVS environment setups with existing roles. It only displays roles with rights to create new users. If no roles exist, one will be created with all rights and the PaletteUserRole field will not appear.
- Enter a user name in the PaletteUserName field.
- Enter a password in the PalettePassword field.
- Re-enter the password in the PalettePasswordConfirm field.
- Click Save.