Ellipse Gradient for Header

Informatica Intelligent Data Management Cloud Integration Guide

Integrate IDMC with enterprise systems through service-specific REST APIs, asynchronous jobs, event-driven patterns, files, databases, and Secure Agent-based data movement.

Informatica Intelligent Data Management Cloud integration options at a glance

IDMC provides service-specific REST APIs for authentication, asset operations, task execution, job monitoring, and administration. It also supports asynchronous and batch execution through Data Integration tasks, file and cloud-storage exchanges, database connections, and Secure Agent runtimes. Application Integration provides event-driven and HTTP invocation patterns, although webhook coverage is not universal across IDMC assets. Authentication may use OAuth 2.0 or an IDMC login/session flow, with permissions controlled by roles and asset access. Martini can consume these APIs, receive supported callbacks, orchestrate polling workflows, transform payloads, coordinate files, and expose controlled APIs for downstream applications.

Integration pointSupported by Informatica Intelligent Data Management Cloud?Common use casesHow Martini supports it
REST APIsYesAuthenticate, list and inspect assets, manage connections, start tasks, retrieve job status, and perform service-specific operations.Martini can consume the applicable IDMC REST API, map responses, apply business rules, and expose a simplified API to other systems.
Bulk, asynchronous, and batch APIsYesStart mapping tasks or taskflows, process large data volumes through IDMC execution, and monitor queued or running jobs.Martini can submit jobs, persist job identifiers, poll with backoff, apply timeout rules, and route success or failure outcomes.
Webhooks and outbound callbacksLimitedApplication Integration supports selected event-driven and HTTP invocation patterns, but coverage varies by service and event.Martini can receive confirmed callback traffic or use scheduled polling when no suitable outbound event exists.
File and attachment integrationLimitedExchange flat files through data-integration assets, Secure Agents, cloud storage connections, and agreed staging locations.Martini can validate files, enforce naming and completion rules, coordinate staging, and archive or quarantine results.
Database and analytics accessLimitedConnect IDMC workflows to external databases and analytical platforms through configured connections and Secure Agents.Martini can coordinate IDMC database-oriented tasks or separately connect to supported target databases; direct access to IDMC control-plane metadata is not assumed.
AuthenticationYesUse OAuth 2.0 or service-specific IDMC login/session authentication, with roles, scopes, asset permissions, and service-account controls.Martini can keep tokens, sessions, client credentials, URLs, and other values in environment-specific secret configuration.
SOAP APIsLegacySome Application Integration or historical Informatica interfaces may use SOAP, but REST is the preferred starting point for new IDMC platform integrations.Martini can consume SOAP services when an official service-specific requirement exists, while treating REST as the default.
GraphQL APIsNot confirmedGraphQL is not confirmed as a general-purpose IDMC platform interface and should be verified for any individual service.Martini can consume GraphQL where a specific confirmed endpoint exists, but an IDMC GraphQL integration should not be assumed.

How Informatica Intelligent Data Management Cloud exposes data and business events

IDMC REST APIs

IDMC REST APIs provide service-specific operations for authentication, asset metadata, connections, task execution, job monitoring, and administration. Available resources, URLs, payloads, and permissions vary across Informatica Cloud Platform, Cloud Data Integration, Application Integration, API management, MDM, and data-quality services.

Martini implementation pattern

Martini implementation pattern: Martini stores the regional base URL and authentication configuration as environment settings, calls the relevant REST endpoint, maps the response into a canonical model, and applies service-specific authorization and validation rules.

Implementation sequence

Resolve the organization’s regional API and service URLs
Authenticate using the applicable OAuth or IDMC session flow
Call the selected asset, task, or job endpoint
Map the response to a canonical integration model
Route authorization, validation, and service errors separately

Asynchronous and batch execution

IDMC is designed for task-based and asynchronous data-integration execution. Mapping Tasks and Taskflows can process data through Secure Agents, files, cloud storage, databases, and application connections while platform APIs control submission and monitoring.

Martini implementation pattern

Martini implementation pattern: Martini starts a task or taskflow, stores the returned job identifier, polls status at bounded intervals, and produces separate success, failure, cancellation, and timeout outcomes.

Implementation sequence

Validate task parameters and runtime requirements
Submit the Mapping Task or Taskflow
Persist the returned job identifier and correlation key
Poll execution status with bounded backoff
Publish the final status and preserve diagnostic details

IDMC event and callback patterns

Application Integration supports event-driven and HTTP invocation patterns, but IDMC does not provide a universal webhook for every asset or platform event. Event types, delivery behavior, retries, and payload identifiers must be confirmed for the selected service.

Martini implementation pattern

Martini implementation pattern: Martini receives only confirmed callback or event traffic, validates the event and correlation data, and falls back to scheduled polling when the required event is unavailable.

Implementation sequence

Confirm the service-specific event and delivery contract
Receive the callback or event notification
Validate authentication, payload structure, and correlation data
Retrieve current resource or job state when required
Process the event idempotently and record delivery outcome

IDMC file-based integration

IDMC supports flat-file and cloud-storage integration through data-integration assets, Secure Agents, and configured connections. This is not a universal attachment API for all IDMC objects.

Martini implementation pattern

Martini implementation pattern: Martini validates an inbound or outbound file, places it in the agreed staging location, invokes or monitors the IDMC process, and moves the file to archive or quarantine based on the result.

Implementation sequence

Detect or receive the business file
Validate naming, encoding, structure, and completion markers
Place the file in the agreed staging location
Trigger or monitor the IDMC task
Archive successful files and quarantine failed files

Common Informatica Intelligent Data Management Cloud integration patterns

Pattern 1: Orchestrate an IDMC data-integration job

When to use this pattern

Use this pattern when another business process must start an IDMC Mapping Task or Taskflow and wait for a controlled completion result. The flow separates submission from execution monitoring and handles queued, running, successful, failed, canceled, and timed-out states.

Integration direction
Martini
Informatica Intelligent Data Management Cloud
Operations platform
Example Mapping
Informatica Intelligent Data Management Cloud FieldCanonical FieldTarget Field
taskNameintegration.assetNamejob.assetName
jobIdintegration.executionIdoperation.correlationId
statusintegration.executionStatusoperation.status
errorMessageintegration.failureReasonoperation.error
Martini implementation pattern

A scheduled or API-triggered Martini workflow validates parameters, calls the IDMC REST endpoint, stores the returned job ID, polls with backoff, and applies business rules for timeout and retry. It then writes a normalized execution record and sends failures to operational handling.

Martini capabilities used
  • workflows
  • API consumption
  • scheduling
  • data mapping
  • business rules
  • error handling

Pattern 2: Expose a controlled API for IDMC task execution

When to use this pattern

Use this pattern when applications need to request a business operation without receiving direct access to regional IDMC URLs, credentials, asset paths, or administrative APIs. The API can accept a customer, region, reporting period, or other business-level parameter.

Integration direction
Calling application
Martini
Informatica Intelligent Data Management Cloud
Example Mapping
Informatica Intelligent Data Management Cloud FieldCanonical FieldTarget Field
reportingPeriodexecution.parameters.periodIDMC task parameter
businessUnitexecution.parameters.businessUnitIDMC task parameter
requestIdexecution.correlationIdIDMC job correlation
acceptedexecution.acceptedAPI response.accepted
Martini implementation pattern

Martini exposes a REST API, validates and authorizes the request, maps business inputs to IDMC task parameters, invokes the selected endpoint, and returns a controlled accepted or rejected response. Duplicate request keys are checked before submission.

Martini capabilities used
  • API exposure
  • workflows
  • authentication and authorization
  • data mapping
  • validation
  • idempotency rules

Pattern 3: Synchronize IDMC job status with ServiceNow

When to use this pattern

Use this pattern when platform and task execution status must be visible in an operations platform. It is useful for failed jobs, Secure Agent availability issues, runtime duration reporting, and operational runbooks.

Integration direction
Informatica Intelligent Data Management Cloud
Martini
ServiceNow
Example Mapping
Informatica Intelligent Data Management Cloud FieldCanonical FieldTarget Field
jobNameoperation.nameServiceNow short_description
statusoperation.statusServiceNow state
errorMessageoperation.failureReasonServiceNow description
jobIdoperation.externalIdServiceNow correlation field
Martini implementation pattern

A scheduled Martini workflow retrieves recent jobs using the appropriate IDMC API, filters by time window and asset scope, maps statuses and diagnostics, and upserts ServiceNow records using the job ID or another durable correlation key. Transient API failures are retried, while permission and validation errors are escalated.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination
  • data mapping
  • upsert logic
  • retry and error handling

Pattern 4: Coordinate an IDMC file exchange

When to use this pattern

Use this pattern when IDMC processes files from cloud storage, a staging location, or a Secure Agent-accessible endpoint. It adds controls for incomplete files, duplicate names, schema validation, archival, and replay.

Integration direction
Amazon S3
Martini
Informatica Intelligent Data Management Cloud
Example Mapping
Informatica Intelligent Data Management Cloud FieldCanonical FieldTarget Field
objectKeyfile.nameIDMC source path
contentLengthfile.sizevalidation.expectedSize
businessDatefile.partitionDatetask parameter
checksumfile.integrityHashprocessing.correlation
Martini implementation pattern

Martini detects or receives the file, validates its structure and completion marker, checks duplicate processing state, places it in the agreed location, and triggers or monitors IDMC execution. Successful files are archived and failed files quarantined with a replayable correlation key.

Martini capabilities used
  • workflows
  • file handling
  • validation
  • business rules
  • API consumption
  • error handling

Applications commonly integrated with Informatica Intelligent Data Management Cloud

IDMC commonly participates in enterprise data, application, and operational workflows. The exact objects and operations depend on the selected IDMC service, connector, Secure Agent, authentication model, and licensed capabilities.

Application Scenario Direction Martini Pattern
Salesforce Synchronize Accounts, Contacts, Leads, Opportunities, and related CRM data for data quality, analytics, and downstream operations. Salesforce → Informatica Intelligent Data Management Cloud → Martini Martini can invoke IDMC-controlled processes, normalize completion and error results, and route curated Salesforce-related data or job status to downstream systems.
ServiceNow Exchange incidents, users, configuration data, and service-management information with enterprise integration and data-governance processes. ServiceNow → Informatica Intelligent Data Management Cloud → Martini A Martini workflow can start or monitor an IDMC task, map job outcomes and error details, and create or update ServiceNow operational records.
SAP S/4HANA Coordinate finance, procurement, sales, supply-chain, and master-data processes with governed enterprise data flows. SAP S/4HANA → Informatica Intelligent Data Management Cloud → Martini Martini can invoke IDMC taskflows for batch processing, pass controlled parameters, monitor asynchronous jobs, and publish normalized outcomes.
Workday Synchronize worker, organization, position, and workforce-related data with enterprise applications and data platforms. Workday → Informatica Intelligent Data Management Cloud → Martini Martini can coordinate scheduled IDMC executions, apply parameter and response mappings, and route successful or failed runs to operational consumers.
Snowflake Load curated, governed, or replicated data into a cloud warehouse and coordinate reference-data flows. Informatica Intelligent Data Management Cloud → Snowflake → Martini IDMC can perform the high-volume data movement while Martini controls task submission, polling, business validation, and downstream notification.
Amazon S3 Stage files and exchange data sets for batch ingestion, export, archival, or replay workflows. Amazon S3 → Informatica Intelligent Data Management Cloud → Martini Martini can validate names and completion markers, coordinate staging, trigger an IDMC task, and move successful or failed files to archive or quarantine locations.
Microsoft Dynamics 365 Integrate customer, sales, service, and operational data with data-quality and master-data processes. Microsoft Dynamics 365 → Informatica Intelligent Data Management Cloud → Martini Martini can orchestrate the relevant IDMC process, transform status and parameter data, and expose a controlled result to Dynamics-related operations.
Oracle Database Consolidate operational data, perform transformations, and move governed data between databases and enterprise applications. Oracle Database → Informatica Intelligent Data Management Cloud → Martini IDMC can execute database-oriented mappings through configured connections and Secure Agents, while Martini manages invocation, validation, retries, and operational reporting.

How to build a Informatica Intelligent Data Management Cloud integration in Martini

Objective

Establish the service-specific IDMC connection using the correct regional URL, authentication flow, roles, and asset permissions.

Instructions in Martini

  • Identify the required IDMC API family and regional endpoints.
  • Configure OAuth 2.0 or the required login/session flow.
  • Store credentials, tokens, sessions, and URLs in environment-specific secrets and configuration.
  • Use a dedicated service account with least-privilege permissions.

Objective

Select an API request, scheduler, confirmed callback, or file event based on the IDMC service and operational requirements.

Instructions in Martini

  • Use an API trigger for business-controlled execution requests.
  • Use a scheduler for polling jobs or running recurring coordination processes.
  • Use callbacks only when the selected IDMC service documents the event and delivery behavior.
  • Use file detection and completion markers for file-based exchanges.

Objective

Call the relevant IDMC endpoint or obtain the file and establish a durable correlation context.

Instructions in Martini

  • Retrieve the required asset, task, job, or file information.
  • Handle pagination and filtering for asset or job history endpoints.
  • Persist job IDs, request IDs, file identifiers, and source watermarks.
  • Do not treat task acceptance as proof that processing has completed.

Objective

Coordinate submission, polling, dependent actions, and outcome routing in a maintainable Martini workflow.

Instructions in Martini

  • Separate job submission from asynchronous monitoring.
  • Poll with bounded intervals and exponential backoff.
  • Apply maximum wait and timeout rules.
  • Route queued, running, successful, failed, canceled, and timed-out states distinctly.

Objective

Convert IDMC responses, task parameters, files, and operational results into canonical models for target systems.

Instructions in Martini

  • Map asset names, job IDs, statuses, timestamps, errors, and runtime details.
  • Validate required fields and normalize service-specific status values.
  • Apply JSON, XML, or file transformations as required by the endpoint.
  • Preserve diagnostic fields needed for support and replay.

Objective

Prevent unsafe execution and duplicate processing while enforcing organization-specific controls.

Instructions in Martini

  • Validate task parameters, asset scope, runtime selection, and file readiness.
  • Check correlation keys before submitting a new job.
  • Do not retry permanent authentication, authorization, or validation errors.
  • Enforce file retention, archive, quarantine, and replay rules.

Common Informatica Intelligent Data Management Cloud data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
OrganizationsRepresent the top-level IDMC tenant containing users, assets, runtime resources, and service entitlements.Identity administration, governance platforms, operations systemsMartini can retrieve organization metadata through the applicable REST API and map it to an internal tenant or administration model.
UsersRepresent human or service identities with roles and permissions.Identity platforms, service-management systems, audit storesMartini can synchronize permitted user metadata while protecting credentials and applying service-account filtering.
Secure Agents and Secure Agent GroupsRepresent runtime components that execute workloads and reach private systems.Operations platforms, monitoring systems, network-control processesMartini can retrieve runtime status, correlate it with job failures, and route availability issues for operational handling.
ConnectionsDefine access to databases, applications, files, cloud storage, and other endpoints.Configuration repositories, governance systems, operations platformsMartini can inspect or orchestrate connection-related API operations without exposing stored credentials in payloads or logs.
MappingsDefine sources, transformations, lookups, and targets for reusable data flows.Data catalogs, deployment processes, governance repositoriesMartini can retrieve metadata, validate references, and coordinate execution without assuming direct access to Informatica control-plane storage.
Mapping TasksExecute a Mapping, often as a batch or asynchronous data-integration operation.Data warehouses, applications, files, databases, monitoring systemsMartini can submit a Mapping Task, persist its job identifier, monitor state, and publish a normalized execution result.

Authentication and security considerations

Service-specific authentication

IDMC authentication varies by API family and may use OAuth 2.0, client credentials, scopes, access tokens, or an IDMC login/session flow. Basic credentials may be used to obtain a session or for selected operations, but they should not be treated as the general-purpose preferred pattern.

Secrets and permissions

Martini should keep client secrets, tokens, session identifiers, passwords, regional URLs, and other credentials in environment-specific secret configuration. IDMC roles, service-account permissions, organization settings, asset permissions, and Secure Agent access all affect the result of an integration.

Network and runtime controls

Secure Agent groups, private connectivity, allowlists, certificates, proxies, and network routes can determine whether an IDMC task reaches a target system. Do not expose credentials in workflow payloads or logs.

Operational considerations for Informatica Intelligent Data Management Cloud integrations

Endpoints, pagination, and limits

IDMC organizations may use regional login, API, and product-service hosts. Store these as configuration. Implement endpoint-specific pagination, filtering, request limits, and concurrency controls rather than assuming a first page contains all assets or jobs.

Asynchronous execution

Persist the IDMC job identifier and poll with backoff. Distinguish queued, running, successful, failed, canceled, and timed-out states, and enforce a maximum wait time.

Idempotency and retries

A timeout during submission may leave a job running. Use business correlation keys, deterministic file markers, source watermarks, or target-side deduplication before retrying. Retry transient network, availability, and rate-limit failures, but not permanent authorization or validation errors.

Runtime and schema changes

Monitor Secure Agent and Agent Group availability, validate connection references, and test changes to mappings, taskflows, parameters, and API responses before production deployment. Preserve HTTP status, Informatica error details, job IDs, and correlation identifiers for troubleshooting.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration beyond individual API calls

Martini provides workflows for coordinating IDMC task submission, asynchronous monitoring, file processing, downstream updates, and operational notifications without embedding the entire process in a script.

Reusable integration behavior

Teams can centralize authentication, endpoint configuration, mappings, validation, retry rules, idempotency controls, and error routing across multiple IDMC services and enterprise applications.

Controlled APIs and maintainability

Martini can expose a business-level API that hides regional IDMC endpoints and credentials while preserving explicit authorization and validation. This creates a governed interface for applications that need to start or monitor IDMC operations.

Frequently asked questions

How can Informatica Intelligent Data Management Cloud be integrated with enterprise systems?

IDMC can be integrated through service-specific REST APIs, asynchronous task and job execution, Application Integration event or HTTP patterns, file and cloud-storage exchanges, and database or application connections executed through Secure Agents. The appropriate mechanism depends on the IDMC product and service involved.

Can Martini integrate with Informatica Intelligent Data Management Cloud?

Yes. Martini can consume the applicable IDMC REST APIs, submit and monitor tasks, receive confirmed callback traffic, coordinate files, transform responses, and expose controlled APIs for IDMC operations. No dedicated native Martini connector is documented in the supplied research.

Do I need a connector to integrate Informatica Intelligent Data Management Cloud with Martini?

No. A dedicated Informatica Intelligent Data Management Cloud connector is not required. Martini can use IDMC’s confirmed native REST APIs, service-specific event or callback mechanisms, file endpoints, authentication methods, and other supported integration endpoints.

Is there any extra Lonti cost to integrate Informatica Intelligent Data Management Cloud with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate IDMC. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from Informatica, cloud infrastructure, Secure Agent deployment, or other third-party systems depending on subscription, usage, and deployment model.

Which IDMC integration methods should a new implementation use?

REST APIs are the preferred starting point for platform administration, asset operations, task execution, and job monitoring. Use IDMC batch and asynchronous task execution for high-volume data movement, and use files, cloud storage, databases, and Secure Agents where appropriate. SOAP is a legacy or service-specific option, while GraphQL is not confirmed as a general IDMC interface.

Does IDMC provide webhooks or event notifications for task and asset events?

Application Integration supports event-driven and HTTP invocation patterns, but webhook coverage is service- and event-specific rather than universal across IDMC assets. Confirm the event type, delivery model, retry behavior, and event identifier. Martini can use scheduled polling when no suitable outbound event exists.

How does Martini synchronize IDMC jobs and data?

Martini can start an IDMC task, persist the returned job identifier, poll status with bounded backoff, and map the final result to an operations or business system. Large data movement should normally remain within IDMC tasks, Secure Agents, files, cloud storage, or configured database connections rather than passing every row through the platform API.

How does Martini handle IDMC mapping, errors, retries, and duplicate executions?

Martini can transform API, file, and job payloads, validate required fields, preserve correlation identifiers, and route outcomes by error type. Transient failures can use bounded exponential backoff, while authorization, validation, and permanent task errors should not be blindly retried. Durable business keys, job IDs, file markers, and watermarks help prevent duplicate executions.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Coordinate Informatica Intelligent Data Management Cloud integrations with Martini

Use Martini to connect IDMC APIs, asynchronous jobs, files, and enterprise applications through governed workflows, reusable mappings, secure configuration, and operational controls.

EXPLORE MARTINI
BOOK A DEMO