OpenText Developer Admin - IM Developer Administration - PoolParty Integration and Automation

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

1. Semantic enrichment of integration metadata

Data flow: OpenText Developer Admin - IM Developer Administration to PoolParty

Integration teams can publish API definitions, message schemas, endpoint descriptions, and integration artifact metadata from OpenText Developer Admin - IM Developer Administration into PoolParty for semantic tagging and classification. PoolParty can then enrich this content with controlled vocabulary, business terms, and ontology-based labels.

• Improves searchability of integration assets across development teams
• Helps architects and developers find reusable APIs and mappings faster
• Reduces duplicate integration work by making existing assets easier to discover

2. Business glossary alignment for APIs and integration artifacts

Data flow: Bi-directional

OpenText Developer Admin - IM Developer Administration can send technical metadata such as API names, message fields, and credential references to PoolParty, while PoolParty returns approved business terms and semantic classifications. This creates a consistent link between technical integration objects and business vocabulary.

• Supports governance by aligning technical and business language
• Improves communication between integration, data governance, and business teams
• Helps standardize naming conventions across Trading Grid solutions

3. Automated classification of integration documents and runbooks

Data flow: OpenText Developer Admin - IM Developer Administration to PoolParty

Operational documents such as interface specifications, deployment notes, and developer runbooks managed in OpenText can be sent to PoolParty for semantic classification. PoolParty can assign categories such as domain, process, system, or data sensitivity to improve retrieval and governance.

• Speeds up document discovery for support and delivery teams
• Improves consistency in document tagging across projects
• Supports audit readiness by making documentation easier to locate

4. Semantic search across integration assets and knowledge graphs

Data flow: OpenText Developer Admin - IM Developer Administration to PoolParty

Integration metadata from OpenText can be indexed in PoolParty?s knowledge graph to enable semantic search across APIs, credentials-related references, integration endpoints, and related artifacts. Users can search by business concept rather than exact technical name.

• Reduces time spent locating the correct integration component
• Improves reuse of existing services and mappings
• Supports onboarding of new developers and integration analysts

5. Governance of sensitive integration metadata

Data flow: Bi-directional

OpenText Developer Admin - IM Developer Administration manages developer-level controls, credentials, and environment separation, while PoolParty can classify metadata based on sensitivity, domain, or regulatory relevance. The combined solution can help determine which integration artifacts require restricted access or additional review.

• Strengthens governance for sensitive APIs and configuration data
• Supports role-based handling of integration metadata
• Helps compliance teams identify regulated content faster

6. Cross-team onboarding for integration and knowledge management

Data flow: OpenText Developer Admin - IM Developer Administration to PoolParty

When new integration projects are created in OpenText, key metadata can be pushed to PoolParty to generate a semantic knowledge layer for onboarding. Business analysts, architects, and support teams can quickly understand what an integration does, which systems it touches, and what business terms it uses.

• Shortens onboarding time for new team members
• Improves handoffs between development, operations, and governance teams
• Creates a shared view of integration landscape and business context

7. Metadata-driven impact analysis for change management

Data flow: Bi-directional

Changes in OpenText-managed integration artifacts, such as updated API versions or modified message structures, can be matched in PoolParty against related business terms, domains, and linked content. This helps teams assess which business areas, documents, or downstream processes may be affected before deployment.

• Improves change impact visibility
• Reduces risk during integration updates
• Supports more informed release planning and stakeholder communication