OpenText Active Community - Trading Grid - OpenText Developer Admin - IM Developer Administration Integration and Automation

Common Integration Use Cases Between OpenText Active Community - Trading Grid and OpenText Developer Admin - IM Developer Administration

1. Publish Integration Environment Readiness Updates to Trading Partners

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Active Community - Trading Grid

When integration teams create or update APIs, credentials, certificates, or messaging artifacts in the developer administration environment, key readiness updates can be posted to the Trading Grid community for affected trading partners. This gives partners early visibility into upcoming changes, test windows, and deployment timelines.

• Reduces partner confusion during integration changes
• Improves coordination for testing and cutover activities
• Supports faster issue resolution by sharing environment status in one place

2. Share API and Connectivity Configuration Requests for Partner Onboarding

Data flow: OpenText Active Community - Trading Grid ? OpenText Developer Admin - IM Developer Administration

Business users or partner managers can submit onboarding requests, configuration questions, or connectivity requirements through the Trading Grid community. Integration administrators then use those requests to create or update developer environment settings, credentials, and integration artifacts.

• Creates a structured intake process for partner onboarding
• Improves traceability from business request to technical setup
• Shortens onboarding cycles by centralizing requirements gathering

3. Coordinate Testing and Certification Activities for New Integrations

Data flow: Bi-directional

During partner certification, the Trading Grid community can be used to coordinate test plans, defect discussions, and approval status, while Developer Admin manages the technical setup needed for test execution. Test results, environment changes, and certification milestones can be exchanged between both platforms to keep business and technical teams aligned.

• Supports controlled partner certification workflows
• Provides a shared record of test issues and resolutions
• Helps ensure only approved integrations move to production

4. Manage Credential and Access Change Notifications

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Active Community - Trading Grid

When credentials, certificates, API keys, or access policies are updated in the developer administration environment, notifications can be posted to the Trading Grid community for internal teams and external partners. This is especially useful when changes affect message delivery, authentication, or endpoint access.

• Reduces service interruptions caused by uncommunicated changes
• Improves security governance through controlled communication
• Helps partners update their systems before production impact occurs

5. Centralize Issue Escalation from Partner Collaboration to Technical Administration

Data flow: OpenText Active Community - Trading Grid ? OpenText Developer Admin - IM Developer Administration

Trading partners can raise transaction failures, mapping issues, or connectivity problems in the community environment. Integration support teams can then translate those issues into technical actions in Developer Admin, such as reviewing configurations, adjusting endpoints, or updating integration artifacts.

• Improves response time for B2B transaction issues
• Creates a clear handoff from business support to technical administration
• Helps maintain a documented audit trail of issue handling

6. Distribute Version and Deployment Information for Integration Artifacts

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Active Community - Trading Grid

When integration artifacts such as mappings, message definitions, or API versions are promoted or changed, Developer Admin can trigger updates to the Trading Grid community. Partners receive the latest version details, deployment notes, and any required action items in a shared collaboration space.

• Prevents partners from using outdated specifications
• Supports controlled rollout of integration changes
• Improves transparency across the partner ecosystem

7. Track Environment Segregation and Approval Status for Production Promotion

Data flow: Bi-directional

Developer Admin can manage development and test environment controls, while Trading Grid can capture business approvals, partner acknowledgements, and go-live readiness confirmations. Together, they support a formal promotion process from development to production with clear accountability.

• Enforces separation between technical configuration and business approval
• Reduces risk during production cutover
• Provides a shared view of deployment readiness across teams

8. Maintain a Shared Knowledge Base for Partner Integration Support

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Active Community - Trading Grid

Common integration setup details, troubleshooting steps, credential requirements, and environment-specific instructions can be published from Developer Admin into the Trading Grid community. This gives support teams and partners a consistent reference for resolving recurring issues without repeated manual intervention.

• Reduces support volume for repeat integration questions
• Improves self-service for trading partners
• Standardizes operational guidance across teams