Deployments

Deployment is a critical phase in integration creation, ensuring that configured chains are operationalized in environments. To use a chain, it must be deployed on an Engine Domain using a snapshot that captures its current state. The deployment process involves:

Update and Redeployment
When modifying a chain, redeployment is required to apply changes. QIP simplifies this through:

• Bulk Redeploy: Deploy multiple chains simultaneously with a single action, streamlining large-scale updates.

---

Logging Capabilities QIP provides robust logging to monitor and secure deployed chains:

• Runtime Configuration: Users can adjust logging settings (e.g., verbosity, output paths) dynamically while the chain is running.
• Data Masking: Sensitive parameters (e.g., passwords) can be masked in logs to prevent unauthorized access.
• Granular Control:
  • Apply logging levels (e.g., DEBUG, ERROR) to individual chains or groups for targeted monitoring.
  • Create masked fields in logs to hide private information automatically.

User Interface Overview

The third step in the workflow is to deploy a snapshot . To do this:

1. Click the Plus (+) button in the right-side action menu.
2. A popup window will appear, requiring two inputs:
   • Domain : Select the target domain where the snapshot will be deployed.
   • Snapshot : Choose the version of the snapshot to deploy (e.g., V1 , V2 ).

After clicking Deploy , a new deployment record appears with the following details:

• Snapshot : Displays the deployed version (e.g., V1.2 ).
• Domain : Shows the selected domain for deployment.
• Status : IP address indicating deployment success or failure via color-coded labels:
  • Green : Deployment completed successfully.
  • Red : Deployment failed.
• Created By : The user who initiated the deployment.
• Created At : The exact date and time of deployment.
• Actions : The only available action is Delete Deployment , which removes the deployment record (note: this does not affect the deployed chain itself).