Installing and Configuring the Staging Server
By default, all Integrity Lifecycle Manager servers are installed as production servers. To create a staging server, you install another Integrity Lifecycle Manager server on a separate machine.
After installing the second Integrity Lifecycle Manager server, configure additional properties to have it operate as a staging server. Configure the following properties in the installdir/config/properties/is.properties file:
|
Properties To Modify
|
Defined Values
|
|
mksis.adminStagingServer=
|
Allows Integrity Lifecycle Manager server to function as production server or staging server. Valid options are true or false. If false, Integrity Lifecycle Manager server functions as standard production server (default). If true, Integrity Lifecycle Manager server functions as staging server that can be used to test workflow configuration and migrate it to production server.
|
|
mksis.adminStagingServerDisplayName=
|
Display name of staging server. For example, if you are using a two staging server configuration, each servers can be named Development Server and Test Server. If no value specified, display name is Staging Server.
In the title bar of the Integrity Lifecycle Manager administration client, the name of the staging server displays. For example, if you specify the staging server name as My Server, the following displays:
Administration jriley@abcFinancial:7001 (My Server - Locked)
If you do not specify a name, the following displays:
Administration jriley@abcFinancial:7001 (Staging Server - Locked)
|
|
On a production server, Locked appears only if the staging server is manually locked.
|
|
|
|
The names of the staging server properties are case-sensitive. For example, you must use mksis.im.prodServer rather than mksis.im.prodserver.
|
|
|
To configure the staging server, configure the following properties in the installdir/config/properties/im.properties file:
|
|
Properties To Modify
|
Defined Values
|
|
mksis.im.prodServer=
|
Host name of production Integrity Lifecycle Manager server.
|
|
mksis.im.prodPort=
|
Port number to connect to on production server.
|
|
mksis.im.prodUser=
|
Login ID of administrator used when the staging server performs verifications and comparisons between the staging and production servers.
|
|
The Admin Migration Wizard allows you to specify a login ID and password for the administrator migrating workflow and document admin provided objects.
|
|
|
mksis.im.prodPassword=
|
Password of administrator used when the staging server performs verifications and comparisons between the staging and production servers.
|
|
Password encryption is enabled for this password if you have encryption enabled on Integrity Lifecycle Manager server.
|
|
|
mksis.im.allowPartialAdminMigration=
|
If true, permits ability to migrate individually specified objects from staging server to production server.
|
|
This property is modified under > > in the Integrity Lifecycle Manager administration client.
|
|
|
mksis.im.allowAdminDeletionWithAdminMigration
|
If true, permits you to delete admin objects on a staging server, even if that object has been migrated to the production server. By default, you may only delete admin objects if they have not been migrated to the production server. This prevents deadlock situations from occurring during an admin migration.
|
|
This property is modified under > > in the Integrity Lifecycle Manager administration client.
|
|
E-mail Notification Upon Lock Break
As administrator, you can ensure that you are notified whenever an administrative lock is broken by editing the following property under > > in the Integrity Lifecycle Manager administration client:
mksis.im.notificationsOnAdminLockBreak==value
where value is a comma-separated list of e-mail addresses for the administrators to be notified whenever an administrative lock is released.
Copying Integrity Lifecycle Manager Database
Before creating a copy of your database, you should back up the existing production database and then restore a copy for use by the staging server. Follow the copying procedures recommended for the specific database you are using.
