Previous Next JavaScript must be enabled to correctly display this content

## 4 Foundation Setup

This topic describes about the Foundation setup using Oracle Banking Microservices Architecture Installer.

Post completion of Download and Setup Installer tasks for VM identified for Foundation Setup, perform the below mentioned configurations.

- Update Properties File
  This topic provides the systematic instructions to update the Properties file for Foundation setup.
- Update Roles File
  This topic provides the systematic instructions to update the Roles file for Foundation setup.
- Execute Installer Script
  This topic provides the systematic instructions to execute Installer Script for Foundation setup.

### 4.1 Update Properties File

This topic provides the systematic instructions to update the Properties file for Foundation setup.

1. Launch WinSCP and login to Foundation VM with OS User (eg.: ofssobp).
2. Navigate to the path `/scratch/obma_installer/chef-repo/` and update the file `obma_properties.rb` with the following details.
3. Update the local user and its group.

       #Standard Values
       INSTALL_USER = "ofssobp"
       INSTALL_GROUP = "dba"
       USER_ROOT = "root"
       GROUP_ROOT = "root"
       INSTALL_BASE_DIR = "/scratch"
       EXTRACT_LOC = "/scratch/extract"

4. Verify the version of java, update if required, and ensure the same version is available in the software's directory.

       #Java Installation Details
       JAVA_INSTALLER_SOURCE = "filesystem"
       JAVA_INSTALLER_PATH = "/java/"
       #JAVA_INSTALLATION_DIR = "/scratch/app/product"
       JAVA_INSTALLATION_DIR = INSTALL_BASE_DIR + "obma"
       JAVA_VERSION = "1.8"
       JDK_INSTALLER_VERSION = "jdk1.8.0_281"
       JDK_INSTALLER_FILE = "jdk-8u281-linux-x64.tar.gz"
       CERTS_DIRNAME = INSTALL_BASE_DIR + "/ssl/"

5. If the zookeeper installation will be done in the same foundation VM, then, update the hostname.
6. Verify the version of the zookeeper installable, update if required, and ensure the same version is available in the software’s directory.

       #Zookeeper Installation Details
       ZOOKEEPER_HOST1 = "whf00jno.in.example.com"
       # ZOOKEEPER_HOST2 = "whf00dwv.in.example.com"
       # ZOOKEEPER_HOST3 = "whf001sz.in.example.com"
       PEER_PORT = 2891
       LEADER_PORT = 3881
       CLIENT_PORT = 2181
       #ZOOKEEPER_INSTALL_DIR = INSTALL_BASE_DIR + "/app/zookeeper"
       ZOOKEEPER_INSTALL_DIR = INSTALL_BASE_DIR + "/obma/zookeeper"
       ZOOKEEPER_INSTALL_USER_HOME = INSTALL_BASE_DIR
       ZOOKEEPER_VERSION = "apache-zookeeper-3.6.3-bin"
       ZOOKEEPER_INSTALLER_PATH = SOFTWARE_INSTALLER_HOME + "/zookeeper/"
       ZOOKEEPER_INSTALLER_FILE = "apache-zookeeper-3.6.3-bin.tar.gz"

7. If kafka installation will be done in the same foundation VM, then update the hostname.
8. Verify the version of the kafka installable, update if required, and ensure the same version is available in the software's directory.

       #Kafka Installation Details
       #KAFKA_INSTALL_DIR = INSTALL_BASE_DIR + "/app/kafka"
       KAFKA_INSTALL_DIR = INSTALL_BASE_DIR + "/obma/kafka"
       KAFKA_INSTALL_USER_HOME = INSTALL_BASE_DIR
       KAFKA_INSTALLER_PATH = SOFTWARE_INSTALLER_HOME + "/kafka"
       KAFKA_INSTALLER_FILE = "kafka_2.13-2.6.0.tgz"
       # KAFKA_VERSION = "2.13-2.6.0"
       KAFKA_SCALA_VERSION = "2.13"
       JMX_PORT = "9999"
       #Kafka Broker Configurations
       KAFKA_BROKER_ID = 1
       KAFKA_LISTEN_PORT = 9092
       LOG_RETENTION_HOURS = "168"
       LOG_RETENTION_CHECK_INTERVAL = "300000"
       LOG_SEGMENT_BYTES = "1073741824"
       LOG_RETENTION_BYTES = "1073741824"

       KAFKA_HOST = "whf00jno.in.example.com"
       KAFKA_PORT = 9092

9. Verify the version of Tesseract installable, update if required, and ensure the same version is available in the software's directory.

       #Tesseract Installation Details
       TESSERACT_INSTALL_USER_HOME = INSTALL_BASE_DIR
       TESSERACT_INSTALL_DIR = INSTALL_BASE_DIR + "/obma/tesseract"
       TESSERACT_INSTALLER_PATH = SOFTWARE_INSTALLER_HOME + "/tesseract"
       INSTALLER_ZIP = "tesseract-4.1.1.zip"

       LEPTONICA_INSTALLER_FILE = "leptonica-1.80.0.tar.gz"
       LEPTONICA_INSTALLER_VERSION = "leptonica-1.80.0"
       TESSERACT_INSTALLER_FILE = "tesseract-4.1.1.tar.gz"
       TESSERACT_INSTALLER_VERSION = "tesseract-4.1.1"

10. Update hostname for LDAP configuration.

        #LDAP Details
        LDAP_HOST = "ofss-mum-1315.snbomrshared1.gbucdsint02bom.oraclevcn.com"
        LDAP_PORT = "7002"

11. Verify the version of weblogic server, update if required, and ensure the same version is available in the software's directory.

        #Weblogic Infra Installation Details
        #WLS_INSTALL_USER_HOME = "/scratch"
        ORACLE_INVENTORY = "/scratch/app/oraInventory"
        WLS_VERSION = "12.2.1.4"
        WLS_INSTALLER_SOURCE = "filesystem"
        WLS_INSTALLER_PATH = "/wls/"
        WLS_PACKAGE_BASENAME = "fmw_12.2.1.4.0_infrastructure.jar"
        WLS_INSTALLER_FILE = "fmw_12.2.1.4.0_infrastructure_Disk1_1of1.zip"
        #WLS_INSTALL_DIR = "/app/product/fmw"
        WLS_INSTALL_DIR = INSTALL_BASE_DIR + "/obma"
        WLS_INSTALLER_TYPE = 'Fusion Middleware Infrastructure'

12. Update the hostname for plato configuration.

        #Product Specific Weblogic Server runtime parameters
        #PLATO_CONFIG_SERVICES_URI = "http://whf00jno.in.example.com"
        PLATO_CONFIG_SERVICES_PORT = "8001"
        APPLICATION_ENVIRONMENT = "DEV"
        APPLICATION_LOGGING_PATH = "/scratch/work_area/logs"
        PLATO_APIGATEWAY_URI = "http://whf00jno.in.example.com"

13. Update the flyway domain locations i.e., update the details of domain locations for all the products that are considered for installation.

        #FLYWAY_DOMAIN_LOCATIONS-
        "db/migration/domain/plato, db/migration/domain/sms, db/migration/domain/moc,
        db/migration/domain/cmc, db/migration/domain/obpy, db/migration/domain/obremo,
        db/migration/domain/obtfpm, db/migration/domain/obedx, db/migration/domain/oblm,
        db/migration/domain/obic, db/migration/domain/vamlm, db/migration/domain/oflo,
        db/migration/domain/obvam, db/migration/domain/obclpm, db/migration/domain/obcfpm,
        db/migration/domain/obpm, db/migration/domain/obcm, db/migration/domain/obscf,
        db/migration/domain/obscfcm

14. The default servers and their respective ports are already defined. Any new addition of server details needs to be appended here under “#Product specific Weblogic Server runtime parameters”.

        #PLATO CommonCore, SMS and Midoffice common Server ports details
        PLATO_CONFIG_SVCS_MAN_SERVER_LISTEN_PORT = "8001"
        PLATO_CONFIG_SVCS_MAN_SERVER_SSL_PORT = "8002"

        PLATO_DISCOVERY_SVCS_MAN_SERVER_LISTEN_PORT = "8003"
        PLATO_DISCOVERY_SVCS_MAN_SERVER_SSL_PORT = "8004"

        PLATO_API_GATEWAY_MAN_SERVER_LISTEN_PORT = "8005"
        PLATO_API_GATEWAY_MAN_SERVER_SSL_PORT = "8006"

15. The default datasources are already defined. Any new addition of datasource needs to be appended here under “#PLATO ComonCore, SMS and Midoffice Datasource and Datasource target details”

        #PLATO CommonCore, SMS and Midoffice Datasource and Datasource target details
        PLATO_SCHEMA = "PLATO"
        PLATO_JNDI = "jdbc/PLATO"
        PLATO_DS_TARGET = "cmc_cluster1,cmc_cluster2,cmc_cluster3,cmc_cluster4,moc_cluster,plato_o_cluster,
        plato_api_gateway_cluster,plato_others_cluster,plato_config_cluster,plato_orch_cluster,
        plato_ui_config_cluster,sms_cluster"

        PLATOSEC_SCHEMA = "PLATOSEC"
        PLATOSEC_JNDI = "jdbc/PLATO_SECURITY"
        PLATO_SECURITY_DS_TARGET = "plato_config_cluster,plato_api_gateway_cluster,plato_others_cluster"

        PLATO_UI_SCHEMA = "PLATO"
        PLATO_UI_JNDI = "jdbc/PLATO_UI_CONFIG"
        PLATO_UI_CONFIG_DS_TARGET = "plato_ui_config_cluster,cmc_cluster1,cmc_cluster2,cmc_cluster3,cmc_cluster4,
        moc_cluster,plato_others_cluster,plato_orch_cluster"

        SMS_SCHEMA = "SMS"
        SMS_JNDI = "jdbc/sms"
        SMS_DS_TARGET = "plato_orch_cluster,sms_cluster,cmc_cluster1,cmc_cluster2,cmc_cluster3,cmc_cluster4,
        moc_cluster,plato_others_cluster"

    Note:

    The password for all the default schema's is "wlcome1". In case there is change in the password for the schemas, user needs to update the same in databag. Refer Password Update in Databag section for more details.
16. Update the database details under “#Database details for weblogic datasource configuration”

        #Database details for Weblogic datasource configuration
        ORACLE_PDB_SID = "PBP0163A"
        ORACLE_PDB_HOSTNAME = "whf00ivq.in.example.com"
        ORACLE_PDB_PORT = "1521"
        ORACLE_DRIVER = "oracle.jdbc.driver.OracleDriver"

17. Also, there are attributes and values related to individual products. Verify the details for your product/s, and in case, any changes to the default values are required, update accordingly.

    Note:

    The below snapshot from Oracle Banking Cash Management product for reference.

    Figure 4-1 FLYWAY PLACEHOLDER

    Description of "Figure 4-1 FLYWAY PLACEHOLDER"

Parent topic: Foundation Setup

### 4.2 Update Roles File

This topic provides the systematic instructions to update the Roles file for Foundation setup.

Navigate to the path `/scratch/obma_installer/chef-repo/roles/` and update the file "`obma_mw.rb`" with the below details.

1. In case of addition or changes to the existing kafka topics, modify the same under “topics”.

   Figure 4-2 Kafka Topics

   Description of "Figure 4-2 Kafka Topics"
2. In case of addition or changes to the existing cluster configuration, modify the same under “cluster_config”.

   Figure 4-3 Cluster Configuration

   Description of "Figure 4-3 Cluster Configuration"
3. In case of addition or changes to the existing data source configuration, modify the same under “datasource_config”.

   Figure 4-4 Datasource Configuration

   Description of "Figure 4-4 Datasource Configuration"
4. In case of addition or changes to the existing services or war files, modify the same under “app_deployment”.

   Figure 4-5 Application Deployment

   Description of "Figure 4-5 Application Deployment"
5. Set the respective product installation as true, which will be configured as part of this Oracle Banking Microservices Architecture Environment Setup activity i.e. if “OBCFPM” will be installed, set the attribute “is_obcfpm_installation” to true.

   Figure 4-6 Environment Setup - True

   Description of "Figure 4-6 Environment Setup - True"
6. Similarly, set all the other product installation to true, if the same will be configured as part of the environment setup, else set the same as false.

   Figure 4-7 Environment Setup - False

   Description of "Figure 4-7 Environment Setup - False"
7. Navigate to the bottom of the file and verify the recipes to be executed. All the listed recipes will be executed in sequential order as shown below.

   Figure 4-8 Recipes List

   Description of "Figure 4-8 Recipes List"

   Note:

   Remove the `user_creation` and `ulimit` recipes from the above list since it is used for internal purpose only.

Parent topic: Foundation Setup

### 4.3 Execute Installer Script

This topic provides the systematic instructions to execute Installer Script for Foundation setup.

1. Launch putty and login to foundation VM with NIS user (eg.: dkarkera) and then switch to root user.
2. Navigate to the chef-repo path by executing the command,
   `cd /scratch/obma_installer/chef-repo`
3. Execute the installer script by executing the command `./obma_installer.sh`.

This will perform the silent installation of Oracle Banking Microservices Architecture foundation.

Parent topic: Foundation Setup