9.6 Conductor Installation

This topic provides the systematic instructions to install conductor.

Before proceeding, ensure that the below steps are done.

  • Make sure that the datasource jdbc/PLATO-O is created. The maximum capacity attribute of the datasource connection pool must be greater than 100.
  • Make sure that the Domain and cluster configuration steps are completed.

    Note:

    The conductor-server.war file needs to be deployed on a separate manged server due to its load and size.
  1. Set the required properties in the config.properties file found in {unzip the file} THIRD_PARTY_SOFTWARES\CONDUCTOR_SERVER\CONFIG.
    Refer to the following table to find the description of properties in the config.properties. This file should be placed at <<CONFIG.PROPERTIES LOCATION >>.
  2. An additional environment variable is required for setting up the conductor. Include the below mentioned –Dparam along with the existing environment variables.
    -Dconductor.properties = << CONFIG.PROPERTIES LOCATION >>/config.properties
  3. Deploy the conductor-server.war file in the weblogic.
    To deploy application, refer to Deploy Application section in Configuration and Deployment Guide.
  4. To control the Log Level, the following property has to be added as a –Dparam along with the existing environment variables:
    -Dplato.conductor.logging.level = << LOG-LEVEL >>

    By default, the log level is “DEBUG”. To obtain only ERROR logs value has to be given as “ERROR” and to completely switch of conductor logs, the value has to be set as “OFF”.

    Table 9-6 config.properties

    Property Name Property Description
    flyway.enabled Set this to true to enable flyway and false to disable flyway.
    flyway.setbaselineOnMigrate Set this to true to enable flyway baselineOnMigrate and false to disable.
    eureka.registration.enabled
    rpm -ivh
    		 Should be set to true to enable discovery registration.
    eureka.hostName plato-o
    eureka.instanceId plato-o:<port-number>
    eureka.serviceUrl.default Discovery service URL (http://<hostname>:<port>/plato-discovery-service/eureka)
    eureka.registerWithEureka true
    eureka.name plato-o
    eureka.vipAddress plato-o
    eureka.port Port Number on which the conductor server war file is deployed.
    conductor.entity.list DEFAULTENTITY~jdbc/PLATO-O

    DEFAULTENTITY is entity Id

    jdbc/PLATO-O is JNDI name of Conductor Datasource

    The entity added, need to make changes in this property. Multiple entities can be added using “,” as a delimiter.

    For example, ENTITY1~jdbc/PLATO-O1, ENTITY2~jdbc/PLATO-O2
    workflow.elasticsearch.instanceType EXTERNAL
    multi.entity.enabled By default, it is false.

    To enable multi-entity, set it to true.
    decider.sweep.disable true
    db oracle
    isSSLenabled

    By default, it is false.

    To enable SSL, set it to true
    security.protocol

    Kafka SSL property. Valid only if SSL is enabled.

    Value has to be set as SASL_SSL

    ssl.truststore.location
    ssl.truststore.password
    sasl.mechanism
    sasl.jaas.config

    All are kafka SSL related properties. These are valid only if SSL is enabled.

    ALL ARE ENVIRONMENT SPECIFIC.

    Note:

    If ssl enabled is true then: For plato-orch-service, in properties table update the key

    plato.orchestration.uri as https
    example: plato.orchestrator.uri = https://100.76.138.119/plato-orch/api/

    If ssl enabled is false then: For plato-orch-service, in properties table update the key

    plato.orchestration.uri as http
    example: plato.orchestrator.uri = http://100.76.138.119/plato-orch/api/

Parent topic: Oracle Banking Microservices Architecture Software Deployment