Patria Tech Docs

Patria Tech Docs

Runbook: Sensedia Integrations — Deploy an integration

Runbook: Sensedia Integrations — Deploy an integration

FieldValue
SystemSensedia Integrations
ProcedureDeploy an integration flow to Production
OwnerIT Production
Estimated time20–30 minutes
Maintenance window required?No
Approval required?Yes — per change management process

Pre-conditions

Before running this runbook, verify:

  • Active username and password on the Sensedia platform.
  • Access to the Patria tenant with deploy permissions in Production.
  • The integration flow source file has been reviewed and approved.
  • The release number to deploy has been confirmed.
  • All datasources required by the flow are configured in Production.

Rollback plan

Warning

Before executing: Ensure the rollback is viable before starting. The undeploy procedure is in runbook-undeploy.md.

If an error occurs after the deploy, run the undeploy runbook to revert the integration flow to its previous state.

Procedure

Step 1 — Log in to the platform

Open a browser and navigate to: https://signin.platform-production.sensedia.com/tenant-signin

In the Tenant Alias field, enter Patria and click Go to your account. Enter your username and password, then confirm the login.

Expected result: The My Products screen loads successfully.

Step 2 — Navigate to Integration Flows

On the My Products screen, click the red Integrations tile. In the left-hand menu, select Integration Flows.

Expected result: The list of available integration flows is displayed.

Step 3 — Open the flow

Use the search box to find the integration flow to deploy, then click on its name to open it.

Expected result: The flow opens in the Sensedia editor.

Step 4 — Configure environment variables in Production (if applicable)

If the flow requires new or updated environment variables:

  1. Click the <> button (code mode) in the top toolbar.
  2. In the left panel, under Flow Variables, select the Production environment.
  3. Create or update each variable with its name and value.

Expected result: Variables are saved under the Production environment.

Step 5 — Deploy the flow

  1. Click the rocket icon on the right side of the screen.
  2. In the panel that opens:
    • Environment: select Production.
    • Release: select the desired release.
  3. Click Deploy to start the deployment.

Expected result: The deploy process starts without errors.

Step 6 — Validate the deployment

  1. Click the three-button menu next to the rocket icon.
  2. Select Deployments to go to the deployments page.
  3. Verify that the deployment shows the status DEPLOYED.

Warning

If the status is not DEPLOYED, do not continue. Record the error and run the undeploy runbook before proceeding.

Expected result: The flow appears with status DEPLOYED in Production for the selected release.

Step 7 — Final verification

  • The integration flow shows status DEPLOYED in Production.
  • The deployed release is the correct one.
  • If the flow replaces an existing process on another platform (e.g., Pentaho), verify that the previous schedule has been disabled.
  • Notify the functional team that the flow was deployed successfully.

Troubleshooting

Error / SymptomLikely causeSolution
Status other than DEPLOYEDError in the flow or in the datasourcesReview execution logs; run the undeploy runbook and fix the issue before retrying
Environment variables not availableVariables not configured for the Production environmentReturn to step 4 and create the missing variables
Desired release not listedThe release was not previously publishedVerify with the development team that the release exists on the platform
Authentication error on the platformExpired credentials or revoked accessRequest a credential reset or access renewal via ServiceNow

References