---
title: "Configure mainframe pipeline components"
method: POST
path: "/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/configuration"
tags: ["Build and Configure Mainframe Integration Projects"]
---

# Configure mainframe pipeline components

`POST /v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/configuration`

## Request

- Base URL: `https://integration-adapter.connect.cloud.precisely.com`
- URL: `https://integration-adapter.connect.cloud.precisely.com/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/configuration`
- Auth: HTTP bearer

Configures source assets selection, target assets selection, and field mappings (transformation) for a mainframe pipeline.

**Process Overview:**
1. **Resource Validation** - Validates project and pipeline existence
2. **Parallel Component Processing** - Processes each component configuration independently
3. **Component Types Supported**:
   - **Sources**: Source asset selection (e.g., topics)
   - **Targets**: Target schema and table definitions
   - **Transformation**: Field mapping and transformation criteria
4. **Isolation & Fault Tolerance** - Component failures don't affect others
5. **Consolidated Response** - Returns unified status after all processing

**Key Features:**
- All component configurations are optional
- Parallel processing for optimal performance
- Independent component execution (failure isolation)
- Metrics per component for better observability
- Component specific thread pool resource allocation
- Comprehensive error reporting per component

**Required Permissions:** Either `replication-pipeline::create` or `replication-pipeline::update` when permission harmonization is enabled; otherwise, `replication-pipeline::manage`.

## Path parameters

- `projectId` string, required
- `pipelineId` string, required

## Request body

- MainframePipelineConfigurationRequest: Request model for configuring a mainframe pipeline, including source assets, target assets, and field mapping criteria.
  - `sources` string[]: List of source topic identifiers.
  - `targets` SchemaTables[]: List of target schema and table definitions.
    - `schema` string, required: Selected schema.
    - `tables` string[], required: List of selected tables in the schema.
  - `transformation` CDCFieldMappings: CDC field mapping configuration
    - `sourceMessageProducerFormat` 'custom' | 'precisely_replication' | 'debezium', required: Source message producer format
    - `fieldMappings` FieldMapping[], required: Field mappings for CDC
      - `sourceField` string: Source field name
      - `targetField` string, required: Target field name
      - `valueMappings` object: Value mappings for the field

## Response `201`

Pipeline components configured successfully

- MainframePipelineConfigurationResponse: Consolidated response containing results from mainframe pipeline component configuration operations
  - `requestId` string: Unique identifier for this configuration request
  - `overallStatus` 'SUCCESS' | 'PARTIAL' | 'FAILED': Overall status of the configuration operation
  - `executionTimeInMs` integer: Total execution time for all component configurations in milliseconds
  - `sources` SourceSelectionResult: Result of source asset selection/configuration.
    - `selectedResources` string[]: List of selected source asset identifiers.
    - `status` 'SUCCESS' | 'PARTIAL' | 'FAILED': Status for this endpoint configuration
    - `response` string: Response / status message from the configuration process
  - `targets` TargetSelectionResult: Result of target asset selection/configuration.
    - `selectedResources` SchemaTables[]: List of selected target schema and table definitions.
      - `schema` string, required: Selected schema.
      - `tables` string[], required: List of selected tables in the schema.
    - `status` 'SUCCESS' | 'PARTIAL' | 'FAILED': Status for this endpoint configuration
    - `response` string: Response / status message from the configuration process
  - `transformation` Transformation: Result of transformation (field mapping) configuration.
    - `status` 'SUCCESS' | 'PARTIAL' | 'FAILED': Configuration status for transformation component
    - `response` string: Response message from the configuration process

## Other responses

- `400`: Bad Request - Invalid configuration request due to one of the following reasons: - Invalid project ID - Invalid pipeline ID - Invalid component configuration parameters - Missing required configuration fields
- `401`: Unauthorized - Authentication required, valid credentials not provided
- `403`: Forbidden - User lacks 'replication-pipeline::create' or 'replication-pipeline::update' when permission harmonization is enabled, or legacy 'replication-pipeline::manage' otherwise
- `404`: Not Found - Project or pipeline does not exist
- `422`: Unprocessable Entity - Configuration conflicts or business rule violations: - Component configuration conflicts with existing pipeline settings - Invalid combination of component configurations - Resource capacity constraints exceeded - Invalid data connection types for specified components - Authentication failures with provided credentials
- `500`: Internal Server Error - Component processing failures: - Source Selection configuration failures - Transformation(field mapping) configuration failures - Target Selection configuration setup failures - Thread pool execution errors - Internal processing errors

---

[API](https://skmtc.dev/precisely/apis/precisely-integration-adapter-service.md) · [All operations](https://skmtc.dev/precisely/apis/precisely-integration-adapter-service/llms.txt) · [OpenAPI document](https://skmtc.dev/precisely/apis/precisely-integration-adapter-service/revisions/2d2629f4987d?raw)