How to Administer the Axon vapp

Transcription

1 How to Administer the Axon vapp Copyright Informatica LLC Informatica, the Informatica logo, Intelligent Data Lake, Big Data Mangement, and Live Data Map are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at

2 Abstract This document describes how to administer the Axon vapp after you deploy it in your VMware environment. Supported Versions Informatica Axon Informatica Axon HotFix 1 Table of Contents Overview Axon vapp Architecture Manage Services Manage Database Backup Restore Backups Log Files vapp DNS Configuration Modify the Gateway Configuration File Overview Informatica Axon is a knowledge repository and data governance tool. You can deploy Axon as a VMware vapp. After deployment, you can administer the vapp by connecting to the virtual machine using Putty via SSH. Axon vapp Architecture The vapp that you deploy consists of a fully contained virtual machine that runs the Axon components. The virtual machine runs CentOS version 6.8. The following image shows the architecture of the Axon vapp: 2

3 Manage Services You can start, stop, or restart the microservices of the Axon components using command line programs. The following table lists the commands that you must execute to start or stop the microservices: Task List all services that are currently running. List all options for the document upload microservice Start, stop, and restart the document upload microservice List all options for the notification microservice Start, stop, restart, and get status for the notification microservice List all options for the change request microservice Start, stop, restart, and get status for the change request microservice List all options for the Apache service Command $ sudo service --status-all $ service axon_document_upload_microservice $ sudo service axon_document_upload_microservice [start stop restart status] $ service axon_notification_microservice $ sudo service axon_notification_microservice [start stop restart status] $ service axon_changerequest_microservice $ sudo service axon_changerequest_microservice [start stop restart status] $ service httpd 3

4 Task Start, stop restart, and get status of the Apache service List all options for Orientdb database service Start, stop, restart, and get status and help for the Orientdb database service List all options for Camunda workflow service Start, stop, and restart Camunda workflow service List all options for the OdbConsumer service Start, stop, restart, and get status for the OdbConsumer service List all options for Memcached memory object caching system Start, stop, restart, and get status for memcached memory object caching system List all options for RabbitMQ server Start, stop, and get status of RabbitMQ server List all options for Tomcat Start, stop, restart and get status for Tomcat Command $ sudo service httpd [start stop restart status] $ service orientdb $ sudo service orientdb [start stop restart status help] $ service camunda $ sudo service camunda [start stop restart] $ service OdbConsumer $ sudo service OdbConsumer [start stop restart status] $ service memcached $ sudo service memcached [start stop restart status] $ service rabbitmq-server $ sudo /sbin/service rabbitmq-server [start stop status] $ service tomcat $ sudo service tomcat [start stop restart status] Manage Database Backup The Axon vapp uses PostgreSQL and MongoDB databases. Axon is configured with cron jobs that back up the PostgreSQL and MongoDB databases. The following directories store the cron jobs: /etc/cron.d/mongodb_backup /etc/cron.d/postgres_dbs_backup The cronjobs are configured to take backups everyday at 2 am. Each backup file is stored in a directory that has a unique timestamp. The following directories store the PostgreSQL and MongoDB backups: /home/admin/postgres_backups /home/admin/mongodb_backups The following cronjob runs at 3 am everyday, and deletes the backups that are older than 10 days: /etc/cron.d/cleanup_old_backups 4

5 Advanced Backup To improve the backup recovery, you might want to change the location of the backup directory to a location outside the virtual machine. You can change the backup directory to a location on a SAN or NAS filesystem mounted on the virtual machine. The BASE_DIR environment variable in the scripts and cron jobs points to the /home/admin directory by default. You must change this to the external filesystem if you want to change the backup directory. The PostgreSQL user must have the permission to write to the external filesystem. If you cannot back up the databases to an external SAN or NAS filesystem, then you must regularly copy the backup files to a filesystem or object storage repository, which is outside the virtual machine. Note: Contact Informatica if you need to increase the frequency of the backups or change the backup directory to an external filesystem. Restore Backups You can restore PostgreSQL and MongoDB backups from the backup directories. The backup directory can be on the Axon virtual machine or an external filesystem. 1. Open Putty and connect to the Axon virtual machine using SSH as the root user. The following is the default password for the root user: "Y9=/(.Q@&4\Fwa 2. Run the following command as the Postgres to restore the PostgreSQL backup: $ psql -f /path/to/<backupfile>.sql postgres 3. Run the following command to restore the MongoDB backup: $ mongorestore /path/to/document_prod/ Note: DOCUMENT_PROD is the directory that contains the backup data in the YYYY_MM_DD_HHMMSS format. Log Files Axon generates a number of log files. The files are in different directories. The following tables lists the directories where the various components of Axon store log files: Component Axon Core Axon Core Apache Axon Core Change Request Microservice Change Request Microservice Notification Microservice Notification Microservice Log File Directory /opt/axon/app/logs/prod.log /opt/axon/app/logs/prod_errors* /etc/httpd/logs/*access_log* /etc/httpd/logs/*error_log* /opt/axon_changerequest_microservice/log/start.log /opt/axon_changerequest_microservice/log/*change_request.log /opt/axon_notification_microservice/log/start.log /opt/axon_notification_microservice/log/*notification.log 5

6 Component Document Upload Microservice Document Upload Microservice Camunda Camunda SOLR SOLR MongoDB OrientDB RabbitMQ Log File Directory /opt/axon_document_upload_microservice/log/start.log /opt/axon_document_upload_microservice/log/*document_upload.log /opt/camunda/server/apache-tomcat /logs/catalina.* /opt/camunda/server/apache-tomcat /logs/*access_log* /usr/share/tomcat/logs/catalina.* /usr/share/tomcat/logs/*access_log* /var/log/mongodb/mongodb.log* /opt/orientdb/log/orient-server.log* /var/log/rabbitmq/rabbit*.log vapp DNS Configuration The Axon virtual machine is configured with a Domain Name Server (DNS) setting. You should change the DNS configuration after deployment. The following configuration file contains the DNS setting of the Axon virtual machine: [centos@axon3 ~]$ cat /etc/resolv.conf The following table contains the default DNS configuration of the Axon virtual machine: DNS Configuration Nameserver Nameserver To change the default DNS configuration, see the How to Deploy Axon on VMware vcenter How-to article Modify the Gateway Configuration File The Axon virtual machine ships with an gateway that is different from gateway of your organization. You must update the gateway configuration file for notifications to work correctly. 1. Log in to the Axon virtual machine using Putty via SSH. 2. Change the path to the following directory: /opt/axon/app/config/ 3. Edit the following gateway configuration file: parameters.yml 6

7 4. Modify the following parameters in the yml file: Parameter host mailer_transport mailer_host mailer_user mailer_password Value hostname of your Axon virtual machine in the following format: Type of server, for example: gmail server name. For example, smtp.gmail.com server user name. For example, server password. For example, =m8k8)kpz mailer_port server port. For example, 465 disable_delivery false 5. Execute the following script to clear the caches and use the new configuration: /home/centos/masterlesspuppet/modules/profiles/files/deployment_scripts/axoncore-full-etl.sh Author Pratap J Lead Technical Writer 7