API Server Registry Configuration
- Comment out the derby DB properties
- Change MySQL configurations
- registry.jdbc.url=jdbc:mysql://localhost:3306/experiment_catalog (replace ‘localhost’ with correct server name if the DB is in a different server)
- registry.jdbc.user=airavata
- registry.jdbc.password=airavata
- enable.sharing=true (This will set sharing within the gateway to be enabled. This is the advices mode)
- default.registry.gateway=php_reference_gateway (Give the gateway name you prefer. Default exists in the file)
- super.tenant.gatewayId=php_reference_gateway (Since you are hosting your own gateway this is the ID of your own gateway)
Application Catalog DB Configuration
- Comment out the derby DB properties
- Change MySQL configurations
Replica Catalog DB Configuration
- Comment out the derby DB properties
- Change MySQL configurations
Workflow Catalog DB Configuration
- Comment out the derby DB properties
- Change MySQL configurations
Sharing Catalog DB Configuration
- Comment out the derby DB properties
Sharing Registry Server Configuration
User Profile MongoDB Configuration
Server Module Configuration
- Make sure all servers required to start are added as given
- servers=credentialstore,apiserver,orchestrator,gfac
API Server Configurations
API Server SSL Configurations
- Give the correct path for key generation file. This is in the bin directory and it is shipped default with Airavata.
- apiserver.keystore=/home/airavata/LocalAiravata/apache-airavata-server-0.16-SNAPSHOT/bin/airavata.jks
Orchestrator Server Configurations
GFac Server Configurations
Registry Server Configurations
Airavata Workflow Interpreter Configurations
Job Scheduler can send informative email messages.........
Credential Store module Configuration
- Add the path to SSH key generation file
- E.g.: credential.store.keystore.url=/home/airavata/LocalAiravata/airavata-sym.jks
- Comment out the derby DB properties
- Change MySQL configurations
- credential.store.jdbc.url=jdbc:mysql://localhost:3306/credential_store
- credential.store.jdbc.user=airavata
- credential.store.jdbc.password=airavata
- credential.store.keystore.url=/home/airavata/production-deployment/airavata_sym.jks
Monitoring Module Configuration
- Add your email address, username and password for email monitoring. This is the email account the job status change emails will be received from compute resources.
- email.based.monitor.host=imap.gmail.com
- email.based.monitor.address=jobs@sample.org
- email.based.monitor.password=SamplePassword
AMQP Notification Configuration
- Users can use RabbitMQ as ‘Guest’ users. This is the easy method. For this uncomment
- To use as a ‘Production’ user
- Navigate to RabbitMQ bin folder.
- Make sure the RabbitMQ server is running. For production use rabbitmq-server -detached to start.
- Create a virtual-host and user with a password. Follow documentation in RabbitMQ Users & VirtualHost
- To create a user; rabbitmqctl add_user Username Password
- To create a vitrual-host rabbitmqctl add_vhost vhostauthvhost
- Provide permission to created ‘Username’ to the created vhost rabbitmqctl set_permissions -p messaging airavata “.*” “.*” ".*”
- Uncomment rabbitmq.broker.url=amqp://Username:Password@localhost:5672/Vhost. Add the created username, password and Vhost in the URL.
- If you need to stop RabbitMQ use rabbitmqctl stop
- If the RabbitMQ server stopped then the above user creation, vhost creation and permission granting commands need to run again after restarting the servers.
Zookeeper Server Configuration
- For ‘Production’ scenario make;
Aurora Scheduler Configuration
API Security Configuration
- Make sure
- api.secured=false
- TLS.enabled=false