Understand Application Services and Component

After installation, three different containers are spun up on your machine.

• qualys-client-service-1
• jira-client-service-1
• redis-client-service-1

Jira Connector Services

Let's see what the newly spun up containerized services are capable of.

Qualys Client service:

Qualys Client Service brings data from Qualys platform and transforms the data into JSON periodically. These files are placed in the output directory of the mounted Jira Connector volume.

Jira Client Service:

1. Based on your Jira Instance type, the Jira Client performs the following actions:
   • Jira onCloud: Create custom issue types and custom fields into your Jira instance with respect to your preferred ticketing scheme.
   • Jira onPremise: Begins fetching issue types and custom field information from your Jira Instance.

     The above actions are a one-time task for the Jira Client Service.

2. Next, the Jira Client reads the JSON files in the output directory of the mounted Jira connector volume to create, update or transition tickets into your Jira Instance. 

Redis Client Service:

The Redis client container runs the Redis Database where the KnowledgeBase data is stored.

From v1.3.0 onwards, the Redis Client also stores the ticket metadata.

Application Service Configuration

Now that you know what the installed services do, let's look at the configurations required for the services to perform the above actions.

• The Jira connector mounts a docker volume named 'qualys-jira-volume' in your environment. You can check the volume by executing the command, docker volume ls
• The Docker volume, by default, is located at '/var/lib/docker/volume/qualys-jira-volume' unless the Docker environment has custom settings.
• You can check the docker volume path by executing the command, docker volume inspect <volume-name>
• The docker volume contains a directory '_data' which has the following dedicated child directories.
  1. config
  2. db
  3. logs
  4. output
  5. templates
  6. checkpoint
  7. error
  8. profilequeue
  9. jiraconnectorconfig
  10. tmp
• The Jira connector also creates a network in your environment named 'qualys-jira-connector', this network us used by both containerized services to communicate with each other. You can verify this by executing the command, docker network ls.

Now that your Jira Connector is up and running with all the necessary files, let's check the available Configurations for Ticketing Schemes and the Config JSON file.

Related Topic

Configurations