How to Install Exalate for Salesforce on Docker

How to Install Exalate for Salesforce on Docker

1. Create directory and create docker-compose.yml file

Create a directory to hold the docker-compose file:

cd ~
mkdir exalate-salesforce

Create or download a docker-compose.yml file

version: '2'

services:
  database:
    restart: unless-stopped
    image: postgres:12.19
    volumes:
      - ./persist/db:/var/lib/postgresql/data
      - ./createdb.sh:/docker-entrypoint-initdb.d/init-user-db.sh
    environment:
      - POSTGRES_PASSWORD=idalko
      - DB_NAME=salesforcenode
      - DB_USER=idalko
      - DB_PASS=idalko
    networks:
      - dbnet

  salesforce:
    restart: unless-stopped
    ports:
      - 9000:9002

    #
    # Change the image tag to the required version
    # Check Release History on docs.exalate.com for an overview
    #
    image: idalko/salesforcenode:5.12.0
    depends_on:
      - database #wait for postgres to be started, not for ready
    volumes:
      - ./persist/home:/opt/salesforcenode/data
    environment:
      # Add your environment settings here
      - SALESFORCENODE_PG_HOST=database
      - SALESFORCENODE_PG_DB=exalate?gssEncMode=disable
      - SALESFORCENODE_PG_USER=idalko
      - SALESFORCENODE_PG_PWD=idalko

     #As part of the security improvements, Exalate 5.6.0 and above validates the origin header
     #that the browser is sending upon every request to Exalate.
     #In order to validate the origin header, Exalate needs to know what is the URL 
     #leading to it.
     #When deploying Exalate to Docker one needs to put an environment variable NODE_SELF_URL.
     #Example:
     # When you deploy Exalate onto a server, you configure a DNS rule such that 
     #whenever people navigate to foo.com, they reach your server's Exalate. 
     #You set up SSL so that https://foo.com leads to your Exalate on your server.
     #Now you need to set environment variable 

      - NODE_SELF_URL=https://foo.com 

     #for your Exalate docker container.

    networks:
      - dbnet
      - default

networks:
  dbnet:
    driver: bridge
  default:
    driver: bridge
  

#!/bin/bash
 
TEST=`psql -U postgres <<-EOSQL
   SELECT 1 FROM pg_database WHERE datname='$DB_NAME';
EOSQL`
 
echo "******CREATING DOCKER DATABASE******"
if [[ $TEST == "1" ]]; then
    # database exists
    # $? is 0
    exit 0
else
psql -U postgres <<-EOSQL
   CREATE ROLE $DB_USER WITH LOGIN ENCRYPTED PASSWORD '${DB_PASS}' SUPERUSER;
EOSQL
 
psql -U postgres <<-EOSQL
   CREATE DATABASE $DB_NAME WITH OWNER $DB_USER ENCODING 'UNICODE' LC_COLLATE 'C' LC_CTYPE 'C' TEMPLATE template0;
EOSQL
 
psql -U postgres <<-EOSQL
   GRANT ALL PRIVILEGES ON DATABASE $DB_NAME TO $DB_USER;
EOSQL
fi
 
echo ""
echo "******DOCKER DATABASE CREATED******"
  

4. Start the Application

cd ~/exalate-salesforce
docker-compose up -d

After starting Exalate for Salesforce, you need to verify your instance. To do so, submit a support request to our Service Desk directly. 

5. Register the Node

To be able to fully use the functionality of your new node, it needs to be registered on the mapper.  This mapper acts as a DNS server, mapping tracker URLs to node URLs.

Please raise a ticket on the support portal providing the following:

• Exalate node URL
• Exalate node instance ID
• Salesforce instance URL

How to Manage the Application on Docker

Run Queries to the Application's Database

You can find all tables using PSQLs \dt+ command:

\dt+

All the Postgres SQL queries are permitted

To exit the application's DB:

\q
# \q exits the psql 
exit
# exits the postgres user session
exit
# exits the exalatesalesforcenode_database_1 bash session

Inspect the Application's Filesystem

cd ~/exalate-salesforce
docker exec -it exalatesalesforcenode_salesforcenode_1 bash

Remove the Application

cd ~/exalate-salesforce
docker-compose rm

Remove the Application Data

cd ~/exalate-salesforce
# docker volume ls | grep exalatesalesforcenode_vol |  awk '{ print $2 }' | xargs docker volume rm
docker volume rm exalatesalesforcenode_voldatabase
docker volume rm exalatesalesforcenode_volsalesforcenode

System Administration Tasks

With the Exalate for Jira Cloud is running on your environment, you are also required to do the mandatory system administration tasks

• Backup (& restore tests)
• Disaster recovery procedure
• Upgrades whenever needed

Upgrading Exalate on Docker

If you need to upgrade Exalate on Docker, here are the steps to follow:

1. Edit the YAML File:

   Open the docker-compose.yml file in a text editor and modify the image tag for the service you wish to upgrade.

   # use the latest version https://hub.docker.com/r/idalko/salesforcenode
   image: idalko/salesforcenode:latest
   depends_on:
   - database #wait for postgres to be started, not for ready
   

   Replace latest with the latest or desired version tag.

2. Pull the Latest Image:

   From the directory containing your docker-compose.yml file, pull the latest image.

   docker-compose pull
   

3. Recreate the Container:

   Using Docker Compose, you can easily recreate the container with the new image.

   docker-compose up -d
   

   The -d flag runs the containers in detached mode. Docker Compose automatically stops the old container and starts a new one based on the updated image.

4. Post-Upgrade Checks:

   After starting the upgraded container, check to make sure everything is running as expected:

• Log into the Exalate interface and verify that all your configurations, connections are intact.
• Test out a few synchronizations to make sure they work as expected.
• Check for any errors in the Docker logs or the Exalate logs.

Troubleshooting

Issues during the installation of the Exalate server for Salesforce

If you have issues during the installation of the Exalate app for Salesforce, you can find logs describing possible problems inside /tmp.

The name for the file is generated randomly and automatically by the OS, but you can find the file by the creation date.

Problems while running the Exalate server for Salesforce

Logs are generated under the directory: /opt/salesforcenode/data/logs.

Refer to these logs to get more information about possible problems and communicate with our support if you need any assistance.

Support

Please read our Support options.