2.4 Install Compliance Studio on the Secondary Server

To install Compliance Studio on the Secondary server:

Note:

If the load balancer is enabled for PGX, then the PGX load balancer URL should be provided in the PGX_SERVER_URL parameter of the config.sh file which is available in the <COMPLIANCE_STUDIO_INSTALLATION_PATH>/bin directory.

For example, PGX_SERVER_URL=http://<PGX_LB_HOSTNAME>:<PGX_LB_PORT>

This configuration has to be done before installing Compliance Studio on the Secondary server and this is required only for the Graph pipeline/ PGX server.

  1. Compliance Studio can be installed on the Secondary server either as a fresh installation or cloned from the Primary server.
    • Install Compliance Studio (fresh installation) on the Secondary server. For more information on how to install, see the OFS Compliance Studio Installation Guide.
    • For cloning files from the Primary server, see the Setup Compliance Studio Instance for Cloning the Filesystem section in the OFS Compliance Studio Installation Guide.

      Note:

      Ensure that the following resources are shared/synced between the Primary and Secondary servers for an HA configuration:
      • Database (Studio, ER/FSDF, Graph, and Atomic Schemas)
      • OpenSearch Cluster

      After successful installation/cloning, ensure that all the services are started and the logs are clean.

  2. Open the additional_config.sh file in the following path and update the parameters as mentioned in the following table.

    Table 2-4 Parameter of additional_config.sh file

    File Path Parameter
    <COMPLIANCE_STUDIO_INSTALLATION _PATH>/bin PGX_INTERPRETER_OPTS="$PGX_INTERPRE TER_OPTS -DAPP_BASE_NAME='pgx- interpreter' -Dgraph- service.url=https:// <COMPLIANCE_STUDIO_SERVER_IP_ADDRES S>:7059/graph-service
  3. Open the application.yml file in the following path and update the parameters as mentioned in the following table.

    Table 2-5 Parameter of application.yml file

    File Path Parameter
    <COMPLIANCE_STUDIO_INSTALLATION _PATH>/deployed/mmg-home/mmg- studio/conf mmgserviceUrl=https:// <LOAD_BALANCER_HOSTNAME>:7002/cs
  4. Open the application.properties file in the following path and update the parameters as mentioned in the following table.

    Table 2-6 Parameter of application.properties file

    File Path Parameter
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-gateway/conf mmg.gateway.url=https://<LB_URL>/
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/mmg-home/mmg-ui/conf BASE_URL=https:// <LOAD_BALANCER_HOSTNAME>:7002/cs
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/mmg-home/mmg-ui/conf DP_UI_URL=https:// <LOAD_BALANCER_HOSTNAME>:7063/ pipelineserviceui/pmf/dp/index.jsp
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/mmg-home/mmg-ui/conf MATCHSRVC_UI_URL=https:// <LOAD_BALANCER_HOSTNAME>/fcc/ graphmatchruleset.jsp
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/mmg-home/mmg-ui/conf LOADINDEX_UI_URL=https:// <LOAD_BALANCER_HOSTNAME>/fcc/ createindex.jsp
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-pipeline/ pipeline/pipelinegateway/conf pipelineservice.uri=https:// <LOAD_BALANCER_HOSTNAME>:18005/ pipelineservice/
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-pipeline/ pipeline/pipelinegateway/conf datapipelineservice.uri=https:// <LOAD_BALANCER_HOSTNAME>:18006/ datapipelineservice
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-pipeline/ pipeline/data-metadata-job-<version>/conf pipeline.url=https:// <LOAD_BALANCER_HOSTNAME>:18005/ pipelineservice
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-pipeline/ pipeline/pipeline-service-<version>/conf pipeline.url=https:// <LOAD_BALANCER_HOSTNAME>:18005/ pipelineservice
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-pipeline/ pipeline/pipeline-service-<version>/conf datapipeline.url=https:// <LOAD_BALANCER_HOSTNAME>:18006/ datapipelineservice
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-pipeline/ pipeline/pipeline-service-<version>/conf gatewayUrl=https:// <LOAD_BALANCER_HOSTNAME>:18006
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-pipeline/ pipeline/data-pipeline-service-<version>/ conf mmg.url=https:// <LOAD_BALANCER_HOSTNAME>:7002/cs
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-pipeline/ pipeline/data-pipeline-service-<version>/ conf pipeline.url=https:// <LOAD_BALANCER_HOSTNAME>:18005/ pipelineservice
    <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-pipeline/ pipeline/data-pipeline-service-<version>/ conf datapipeline.url=https:// <LOAD_BALANCER_HOSTNAME>:18006/ datapipelineservice
  5. Restart Compliance Studio to reflect the updated configuration. To restart the Compliance Studio on the Secondary server, execute the following command.
    ./compliance-studio.sh -–restart