Azure Blob Storage - OpenText Developer Admin - IM Developer Administration Integration and Automation

Common Integration Use Cases Between Azure Blob Storage and OpenText Developer Admin - IM Developer Administration

1. Centralized storage for integration artifacts and deployment packages

Data flow: OpenText Developer Admin - IM Developer Administration ? Azure Blob Storage

Integration teams can export API definitions, message mappings, configuration bundles, certificates, and deployment packages from OpenText Developer Admin into Azure Blob Storage for centralized retention and distribution. This creates a controlled repository for versioned artifacts that can be shared across development, test, and release teams.

Business value: Improves traceability, simplifies handoff between teams, and reduces the risk of lost or inconsistent integration assets.

2. Secure retrieval of large files for integration testing

Data flow: Azure Blob Storage ? OpenText Developer Admin - IM Developer Administration

Large test files such as EDI payloads, XML batches, flat files, or sample transaction sets can be stored in Azure Blob Storage and referenced by OpenText-managed integration environments during development and QA testing. This avoids loading large files directly into admin tools and supports repeatable test execution.

Business value: Speeds up testing cycles, reduces local storage dependency, and supports realistic end-to-end validation with production-like data volumes.

3. Controlled promotion of integration configuration between environments

Data flow: OpenText Developer Admin - IM Developer Administration ? Azure Blob Storage

Development teams can export environment-specific integration configurations from OpenText Developer Admin to Azure Blob Storage, where release managers can review, approve, and promote them into higher environments. The reverse flow can also be used to retrieve approved configuration packages for deployment.

Business value: Strengthens separation of duties, improves governance, and reduces manual deployment errors across development, test, and production.

4. Archiving and audit retention of integration change history

Data flow: OpenText Developer Admin - IM Developer Administration ? Azure Blob Storage

Changes to APIs, credentials, routing rules, and integration artifacts can be periodically exported and archived in Azure Blob Storage for audit and compliance purposes. This supports long-term retention of configuration history outside the operational environment.

Business value: Helps meet audit requirements, supports incident investigation, and provides a reliable historical record of integration changes.

5. Distribution of shared integration assets to distributed teams

Data flow: Azure Blob Storage ? OpenText Developer Admin - IM Developer Administration

Reusable assets such as certificates, schema files, partner-specific templates, and onboarding documents can be stored in Azure Blob Storage and made available to integration developers working in OpenText-managed environments. This is especially useful for geographically distributed teams or partner onboarding programs.

Business value: Reduces duplication of effort, standardizes reusable components, and accelerates onboarding of new developers and partners.

6. Backup and recovery of critical integration metadata

Data flow: OpenText Developer Admin - IM Developer Administration ? Azure Blob Storage

Critical metadata such as API credentials, endpoint configurations, and messaging setup details can be backed up from OpenText Developer Admin into Azure Blob Storage on a scheduled basis. In the event of a platform issue or accidental deletion, teams can restore known-good configurations more quickly.

Business value: Improves resilience, shortens recovery time, and reduces operational risk for business-critical integrations.

7. Large-scale partner onboarding package management

Data flow: Azure Blob Storage ? OpenText Developer Admin - IM Developer Administration

Partner onboarding materials, sample payloads, interface specifications, and environment setup files can be stored in Azure Blob Storage and linked to OpenText-managed integration workflows. OpenText teams can then use these assets to configure and validate partner connections more efficiently.

Business value: Accelerates partner onboarding, improves consistency in setup, and reduces back-and-forth between business, technical, and support teams.

8. Separation of development and production file handling

Data flow: OpenText Developer Admin - IM Developer Administration ? Azure Blob Storage

Development and test environments can use Azure Blob Storage as a staging layer for files and configuration packages before they are approved for production use in OpenText-managed integration environments. This supports controlled movement of files and artifacts across the lifecycle.

Business value: Enforces environment separation, supports governance controls, and helps prevent accidental use of production data or settings in non-production environments.