OpenText Developer Admin - IM Developer Administration - OpenText Information Archive Integration and Automation

Common Integration Use Cases Between OpenText Developer Admin - IM Developer Administration and OpenText Information Archive

1. Automated archiving of integration artifacts and configuration history

Direction: OpenText Developer Admin - IM Developer Administration ? OpenText Information Archive

Integration teams can automatically archive older API definitions, mapping specifications, credential change logs, deployment packages, and environment configuration snapshots from the developer administration platform into OpenText Information Archive. This preserves a complete audit trail of integration changes without keeping inactive artifacts in the live development environment.

• Supports compliance and internal audit requirements for change traceability
• Reduces clutter in active integration repositories
• Helps teams recover historical configurations during incident analysis or rollback planning

2. Retention of retired integration projects and legacy Trading Grid solutions

Direction: OpenText Developer Admin - IM Developer Administration ? OpenText Information Archive

When a Trading Grid solution or integration project is decommissioned, its related developer administration records can be archived for long-term retention. This includes project metadata, endpoint definitions, security settings, and release history, allowing the organization to retire the operational environment while preserving evidence and reference data.

• Enables safe decommissioning of obsolete integration environments
• Reduces infrastructure and support costs
• Maintains access to historical integration records for audits, legal review, and troubleshooting

3. Controlled access to archived integration documentation for support teams

Direction: OpenText Information Archive ? OpenText Developer Admin - IM Developer Administration

Support and integration operations teams can retrieve archived API specifications, interface agreements, and prior environment settings from OpenText Information Archive when investigating production issues or onboarding a new developer. The developer administration platform can provide a controlled access point to relevant archived records without exposing the full archive repository.

• Speeds up root cause analysis for integration incidents
• Improves onboarding and knowledge transfer across teams
• Limits access to only approved historical artifacts

4. Archiving of credential and access governance records

Direction: OpenText Developer Admin - IM Developer Administration ? OpenText Information Archive

Organizations can archive credential issuance records, access approvals, environment promotion logs, and administrative actions from the developer administration platform into OpenText Information Archive. This creates a durable record of who accessed or changed integration assets and when those changes occurred.

• Supports security audits and segregation of duties reviews
• Provides evidence for regulatory and internal control requirements
• Helps track administrative activity across development and production environments

5. Preservation of integration test evidence and release approvals

Direction: OpenText Developer Admin - IM Developer Administration ? OpenText Information Archive

Before integration changes are promoted, test evidence, validation results, and release approval records can be archived for long-term retention. This is especially useful in regulated industries where proof of testing and approval must be retained for multiple years.

• Creates a permanent record of release readiness
• Reduces manual handling of compliance evidence
• Improves governance across development, QA, and operations teams

6. Retrieval of archived business records referenced by integration workflows

Direction: OpenText Information Archive ? OpenText Developer Admin - IM Developer Administration

Integration developers can configure workflows so that archived documents, transaction records, or historical business files stored in OpenText Information Archive are referenced by integration processes managed through the developer administration platform. This allows applications to access retained content without restoring it to a live operational system.

• Supports legacy application retirement while preserving business access
• Reduces dependency on old source systems
• Improves user access to retained records through governed integration services

7. Bi-directional governance for lifecycle management of integration assets and archived content

Direction: Bi-directional

OpenText Developer Admin - IM Developer Administration can manage the creation, update, and retirement of integration artifacts, while OpenText Information Archive stores the long-term record of those assets and related business content. Together, they support a full lifecycle model where active integration objects remain in the developer environment and inactive or regulated records move into archive under policy control.

• Aligns operational integration management with retention policy enforcement
• Improves separation between active and historical content
• Provides a consistent governance model across development, operations, and compliance teams