IBM Cognos Command Center migration to AutoSys

Products

• Autosys Workload Automation

Issue/Introduction

Users evaluating the migration of workloads from IBM Cognos Command Center (CCC) to AutoSys often inquire about native migration tools, plugins, or API integration methods.
This article addresses the availability of these resources and provides best practices for a manual or API-driven migration.

Environment

• AutoSys Workload Automation (All Versions)
• IBM Cognos Command Center

Resolution

Currently, Broadcom does not provide a native migration tool or a dedicated plugin specifically designed to convert IBM Cognos Command Center (CCC) job definitions directly into AutoSys JIL format.

To migrate or integrate these workloads, consider the following approaches:

API Integration

If the IBM CCC environment supports REST or SOAP APIs, trigger and monitor these jobs from AutoSys using standard job types:

• HTTP Job Type: Use for RESTful API calls to trigger processes.
• Web Services Job Type: Use for SOAP-based integrations.

This method allows AutoSys to act as the primary scheduler while leveraging existing logic within IBM CCC during a phased migration.

Manual Migration and Custom Utilities

For environments with a high volume of jobs requiring automated conversion:

1. Use standard AutoSys job types (Command, File Watcher) to recreate the logic within AutoSys.
2. Contact the Broadcom Account Team to discuss options with Professional Services or the partner network. Custom migration utilities may be available through paid services contracts.

Additional Information

To stay updated on integration enhancements, subscribe to this article for future updates. See Subscribe to a Broadcom knowledge article by article or product

For software downloads and release notes, see Download Broadcom products, patches and software