Exporting a Synchronization Pipeline to Support DevOps and Promotion to Different Environments

 

 

Background

Many of the organizations that utilize the RadiantOne Identity Data Management (IDDM) platform have a requirement for a process for promoting Synchronization pipelines from different environments. A common scenario is a client who has four environments (DEV, TEST, UAT and PROD). From a DevOps perspective, the organization requires a set of steps to promote changes to a Synchronization pipeline from:

   DEV --> TEST --> UAT --> PROD 

A brief overview of the desired test/ POV setup is shown in Figure 1 below is an example of such a pipeline with Figure 2 highlighting the naming contexts utilized in the pipeline.

 

Figure 1. Sample Synchronization Pipeline

 

 

Figure 2. Naming Contexts

 

Prerequisites

The key prerequisites are:

  • Administrative access to the IDDM nodes in both source and target environments. In a Kubernetes deployment, this requires a shell to a fid pod.
  • Administrative login to IDDM.

Command Line Steps / Process

The tool used for configuring IDDM from command line is named vdsconfig.bat and located in <RLI_HOME>/bin on Windows or vdsconfig.sh located in $RLI_HOME/bin on Linux. For this example, we assume a Linux environment.

In the source environment, assuming that $RLI_HOME/bin is not in your PATH,  navigate to $RLI_HOME/bin

Run:

 ./vdsconfig.sh resource-export -name "o=to" --cross-environment -skip "o_from" -skip "o_to" -path “/tmp/dev_o_to.zip”

The parameters above skip both source and target contexts such that only the pipeline and its mappings will be exported.

Copy the “/tmp/dev_o_to.zip” to the target environment. When importing into the target environment, run:

./vdsconfig.sh resource-import -path “/tmp/dev_o_to.zip” -apply -interactive

Note that the command will ask about overwriting .jar files, this is to be expected and skipped. A dry run of the above command may be run by omitting the -apply flag.

After the import is complete, a restart of the FID node is needed.

Additional Information / Documentation

This article builds upon the formal product documentation on IDDM’s command line features detailed here --> https://developer.radiantlogic.com/idm/v7.4/command-line-configuration-guide/01-introduction/ specifically “Migration Commands".

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Articles in this section