Versions Compared

Old Version 5

changes.mady.by.user David E Tanner

Saved on

compared with

New Version Current

changes.mady.by.user David E Tanner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Panel

How to configure your application to use the ROLES production database.

The migration to using the ROLES production database is done in your application's property file.  There are 3 new entries and 2 changes to existing properties that musts be made.

  1. The new properties
    • roles.function.category - this property may already exist in your properties file but it's value may have to be changed.
    • roles.proxy.user - this is a new property.
    • webservices.mitrolesws.url - this property may already exist in your properties file but it's value may have to be changed.

  2. The properties to be changed are:
    • webservices.keyStore - this property already exists in your properties file but it's value may have to be changed.
    • webservices.mitroles.url - this property already exists in your properties file but its value may have to be changed.
Panel

The property values that are to be used

The values of each of the above properties are dependent on what keyStore that you have configured in your applicaiton's properties file.

  1. If your are currently using the registrar.jks keystore, the values for the new/changed properties are as follows:
    Code Block
    roles.function.category=REG
roles.proxy.user=REG$PRD
webservices.mitrolesws.url=https://mv-ezproxy-com.ezproxyberklee.flo.org/rolesws/services/roles
webservices.keyStore=/path/to/registrar.jks
webservices.mitroles.url=https://mv-ezproxy-com.ezproxyberklee.flo.org/uaws/services/ua
    Be sure to change /path/to in the above to the actual path to the registrar.jks keystore.
    If you do not have the registrar.jks keystore, you can use this link to download the keystore .

  2. If your are currently using the sfs.jks keystore, the values for the new/changed properties are as follows:
    Code Block
    roles.function.category=SFS
roles.proxy.user=SFS$PRD
webservices.mitrolesws.url=https://mv-ezproxy-com.ezproxyberklee.flo.org/rolesws/services/roles
webservices.keyStore=/path/to/sfs.jks
webservices.mitroles.url=https://mv-ezproxy-com.ezproxyberklee.flo.org/uaws/services/ua
    Be sure to change /path/to in the above to the actual path to the sfs.jks keystore.
    If you do not have the sfs.jks keystore, you can use this link to download the keystore .

  3. If your are currently using the gradadm.jks keystore, the values for the new/changed properties are as follows:
    Code Block
    roles.function.category=GRAD
roles.proxy.user=GRAD$PRD
webservices.mitrolesws.url=https://mv-ezproxy-com.ezproxyberklee.flo.org/rolesws/services/roles
webservices.keyStore=/path/to/gradadm.jks
webservices.mitroles.url=https://mv-ezproxy-com.ezproxyberklee.flo.org/uaws/services/ua
    Be sure to change /path/to in the above to the actual path to the gradadm.jks keystore.
    If you do not have the gradadm.jks keystore, you can use this link to download the keystore