OpenText Core Content - Metadata - OpenText Developer Admin - IM Developer Administration Integration and Automation

Common Integration Use Cases Between OpenText Core Content - Metadata and OpenText Developer Admin - IM Developer Administration

1. Synchronize integration artifact metadata with content governance standards

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Core Content - Metadata

When integration teams create APIs, messaging flows, or Trading Grid artifacts in Developer Admin, key descriptive attributes such as solution name, environment, owner, system dependency, and support group can be pushed into Core Content metadata templates. This ensures integration assets are stored and classified using the same governance model as business content.

• Improves discoverability of integration assets across teams
• Supports consistent naming and classification for audits and operational reviews
• Reduces time spent searching for the correct interface or credential set

2. Enforce metadata rules for integration documentation and runbooks

Data flow: OpenText Core Content - Metadata ? OpenText Developer Admin - IM Developer Administration

Metadata definitions from Core Content can be used to validate required fields for integration documentation, deployment runbooks, and API specifications managed in Developer Admin. For example, every integration package can be required to include business owner, technical owner, environment, change ticket, and retention category before promotion.

• Prevents incomplete or noncompliant integration records
• Creates a controlled approval process for deployment readiness
• Improves operational handoff between development, support, and governance teams

3. Link API and messaging credentials to governed content records

Data flow: Bi-directional

Developer Admin manages credentials and integration artifacts, while Core Content stores the associated governance metadata such as sensitivity level, expiration date, and approved usage. A bi-directional integration can keep credential records aligned with content classification so that sensitive interfaces are tracked and reviewed according to policy.

• Strengthens control over privileged integration access
• Enables expiration and renewal tracking for credentials
• Supports compliance reporting for regulated environments

4. Publish integration environment inventories for audit and reporting

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Core Content - Metadata

Developer Admin can feed environment inventory data into Core Content, including development, test, and production endpoints, interface versions, and deployment status. Core Content metadata then provides structured reporting for audit teams, architecture teams, and operations managers.

• Provides a single view of active integration environments
• Helps identify unsupported or orphaned interfaces
• Accelerates audit preparation and internal control reviews

5. Classify integration artifacts by business process and data domain

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Core Content - Metadata

Integration artifacts managed in Developer Admin can be tagged in Core Content by business process, such as order management, supplier onboarding, or invoice processing, and by data domain such as customer, product, or finance. This makes it easier for business and IT stakeholders to understand which integrations support which operational workflows.

• Improves alignment between technical assets and business services
• Supports impact analysis during process or system changes
• Helps prioritize maintenance based on business criticality

6. Control promotion of integration packages through metadata-based approvals

Data flow: OpenText Core Content - Metadata ? OpenText Developer Admin - IM Developer Administration

Core Content can store approval metadata such as review status, compliance signoff, and release authorization. Developer Admin can consume these metadata values to determine whether an integration package is eligible to move from development to test or production.

• Creates a governed release workflow for integration changes
• Reduces risk of unauthorized deployments
• Improves traceability from approval to implementation

7. Maintain searchable records of integration dependencies and ownership

Data flow: Bi-directional

Developer Admin can provide technical dependency details, while Core Content stores ownership, retention, and classification metadata. Together, the platforms can maintain a searchable catalog of integration dependencies, making it easier to identify who owns an interface, what systems it connects, and what content or data it affects.

• Speeds up incident resolution and escalation
• Supports change impact analysis across connected systems
• Improves accountability for integration lifecycle management