Build and Configure Mainframe Integration Projects
Upload multiple mainframe files
Uploads multiple mainframe files to a specified directory path within the pipeline using batch upload API.
Process Overview:
- Request Validation - Validates path and file list
- Resolution Strategy - Applies specified conflict resolution (REPLACE_ALL, IGNORE_ALL, PARTIAL)
- Batch Upload - Uploads all files in a single operation
- Result Aggregation - Returns success/failure results for all files
Conflict Resolution Strategies:
- REPLACE_ALL - Replace all existing files with conflicting names
- IGNORE_ALL - Skip all files with conflicting names, keep originals
- PARTIAL - Replace only files specified in replaceFiles list, others are ignored
Archive Expansion:
- When uploading a single ZIP file with expandArchive=true, the archive will be extracted
- Individual files will be created from the archive contents
- For multiple files, expandArchive is ignored
Key Features:
- Batch upload support for multiple files
- ZIP archive expansion for single file uploads
- Automatic path handling (uses path as prefix for all files)
- Lists created, conflicted, updated, and ignored files
Path Handling:
- Files are uploaded to the specified directory path
- Directory path (e.g., '/path/to') is used as prefix for all uploaded files
Use Cases:
- Bulk import of configuration files
- Upload multiple scripts at once
- Initial pipeline setup with multiple files
Required Permissions: replication-pipeline::create when permission harmonization is enabled; otherwise, replication-pipeline::manage.
post/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/files/upload
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}/files/upload
- Auth: HTTP bearer
Path parameters
projectIdstring required
Unique identifier of the project
pipelineIdstring required
Unique identifier of the pipeline
Query parameters
conflictResolution'REPLACE_ALL' | 'IGNORE_ALL' | 'PARTIAL'
Conflict resolution strategy to use when name conflicts occur:
- REPLACE_ALL: Replace all existing files with conflicting names
- IGNORE_ALL: Skip all files with conflicting names
- PARTIAL: Replace only files specified in the replaceFiles list; other conflicts are ignored
Response
Upload completed (check response for individual file results)
Changes
No recorded changes to this operation across all 1 revision of this API.