Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Purpose

...

  • Place all files provided with therelease in any folder (preferably /root) on all the machines where the application is being deployed.

  • Go to the folder where you copied all the tar files and load them in running following command (the command starts after $ sign):

...

DB_URL

URL of the database for the microservice.

For MSSQL:
://<>/<>   

Example:

://192.168.1.92:1433/

://192.168.1.92:1433/

DB_DRIVER

Database driver.

For MSSQL:


DB_DIALECT

Database dialect.


For MSSQL:


DB_USER

Database which has full access on the configured DB

DB_PASS

Database password corresponding to the above user

TZ

configuration. Use the TZ database name for your region from the following URL:

https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List

PRIM_IP

IP of the Primary machine in the HA cluster OR IP of the machine

Example:

192.168.1.76

SEC_IP

IP of the Secondary machine in the HA cluster.

Use the same value as of PRIM_IP if not deployed in HA

Example:

192.168.1.80

...

For Supervisor Tools


Download this folder, update the translations in it in the respective JSON files and place it in the root directory of the machine (all the machines if deploying in HA).  The following files refer to their corresponding languages as below:

...

For CIM (if installed)

Download this folder, update the translations in it in the respective JSON files and place it in the root directory of the machine (all the machines if deploying in HA).  The following files refer to their corresponding languages as below:

...

"max-file": "3"

}

}

Execution

CentOS

  • Start the HA cluster on all the machines with the following command:

...

If everything goes well, you should be able to access the application on http://Virtual-IP:8080/umm OR https://Virtual-IP:8443/ummafter the application boot time (takes around 3 minutes on a 2 core machine).

...

  1. Download the latest gadget’s specifications files from here and extract files on the desired directory.

  2. Open the EFGadget.js file and update the URL with your virtual-IP and port of umm service as per your deployment on line 64 as below:


  3. Run FileZilla or any other FTP client and log in to finesse using following credentials

    1. Host: IP of the finesse where gadget is deployed

    2. Username: 3rdpartygadget  

    3. Password: ask the Finesse administrator for the password

    4. port: 22

  4. Create a folder e.g. EFGadget into the files directory on finesse server and upload the specifications files on finesse server.

  5. Repeat the same steps for deploying the gadget on the secondary Finesse server.

  6. Open cfadmin for your finesse using https://finesse.ip:8445/cfadmin, login and follow the steps below to add the supervisor tools gadget in your team:

    1. Click on Team Resources tab on top

    2. Click on the team for which you want to add the gadget

    3. Scroll down the “Desktop Layout XML” part at the bottom of the screen and locate <role>supervisor</role> and add the following line after the <tabs>tag.

      <tab>

                   <id>ST</id>

                   <label>Supervisor Tools</label>

                   <columns>

                       <column>

                           <gadgets>

                               <gadget>/3rdpartygadget/files/<folder>/EFGadget.xml</gadget>

                           </gadgets>

                       </column>

                   </columns>

               </tab>

...