Server considerations for migration
Migration is sometimes required because the operating system or the hardware on which Bravura Security Fabric is currently running is reaching or past the end of its life cycle. In some cases, older target system components and client components may work with newer versions of Bravura Security Fabric . During testing, you can confirm if this is possible in your environment; however, it is recommended that all components should be of the same version.
Bravura Security recommends you test at least one target of each type that you are planning to migrate. This will require installing all clients used in production. If you have scripted targets, test all scripts to make sure they work in the new environment. Ensure they work with the IDMLib installed with the upgraded version.
The primary reason for this test is to discover and correct the issues that are unique to your Bravura Security Fabric .
After all functional testing is complete, you can leverage the existing test Bravura Security Fabric server to ease the deployment into production.
There are two complications:
The dataset in the databases is constantly changing. Users are changing the data in the databases through normal use of Bravura Security Fabric .
The target and client components in production are highly distributed and in constant use. It is highly recommended that the target and client components version match the version of the production Bravura Security Fabric server. Check the "Connector Pack Integration Guide" to determine requirements for each type of target.
These complications make a Bravura Security Fabric service outage necessary, to freeze the dataset in the databases. The outage also puts the new version of the Bravura Security Fabric server, target and client components, into production at the same time.
To minimize the length of the service outage, perform as much work as possible on the test server, in a test environment with test target and client components, and develop a clear step-by-step change control plan.
After successful testing, the service outage can start while the dataset from the databases is frozen and migrated and the target and client tools are deployed. This will require coordination with all target system and client system administrators.
In some cases, older target system components and client components may work with newer versions of Bravura Security Fabric . During testing, you can confirm if this is possible in your environment; however, it is recommended that all components should be of the same version.
Note
Verify that the new server has the same time and timezone configured as the old server. This will prevent artificial time gaps or overlaps in the timestamps recorded in the backend database and in the product logs. If possible, configure the same NTP server for all servers which make up the old and new instance, including application nodes, backend database servers and proxies.