Control-M for Web Services Job Type Conversion

The Control-M for Web Services Job Type Conversion tool enables you convert one or more Control-M for Web Services jobs to Control-M Web Services REST jobs or Control-M Web Services SOAP jobs on Windows or UNIX. This eliminates the need to manually redefine job definitions when you want to upgrade to one of the newer, Application-Integrator-created plug-ins.

You can convert a Control-M for Web Services Job with one of the following procedures:

Converting a Control-M for Web Services Job to a Control-M Web Services REST or Control-M Web Services SOAP Job on UNIX

This procedure describes how to convert a Control-M for Web Services job to a Control-M Web Services REST or Control-M Web Services SOAP job on UNIX, based on the user-defined host or host group in the Control-M for Web Services job definitions.

You must create a new connection profile for the relevant jobs, since this utility only converts jobs—it does not convert connection profiles.

Before You Begin

Begin

  1. Do one of the following to export the Control-M for Web Services jobs to a JSON file:

    • From Control-M Web, export the Workspace to a JSON file, as described in Exporting a Workspace.

      Note

      Only Control-M for Web Services jobs are migrated. All other jobs and folders remain unchanged.

    • Export the relevant Control-M Web Services jobs via Control-M Automation API, as described in deploy jobs::get.  

  2. Copy the exported JSON file to the Agent where the original Control-M for Web Services jobs execute.

    Note

    If you copy the exported JSON file to a different Agent, the migration cannot run since the job definitions refer to the local resources of the original Agent, such as the local connection profile, WSDL files, and header.

  3. Log in to the Agent account that executes the Control-M for Web Services jobs.
  4. From the Control-M for Web Services, Java, and Messaging plug-in directory, run the following command:
    wsconvert -input <Original_WS_Job_Definitions_Pathname> -output <Converted_WS_Job_Definitions_Pathname> -agent <Agent_Name>
    For a more information, see Migration Utility Parameters.
  5. Do one of the following to import the converted Web Services job definitions:
    • From Control-M Web, open the required Workspace and import the converted Web Services job definitions, as described in Importing a Workspace.
    • Import the converted Web Services job definitions via Control-M Automation API, as described in deploy.  
  6. Create one of the following connection profiles, depending on the converted job type.

Converting a Control-M for Web Services Job to a Control-M Web Services REST or Control-M Web Services SOAP Job on Windows

This procedure describes how to convert a Control-M for Web Services job to a Control-M Web Services REST or Control-M Web Services SOAP job on Windows, based on the user-defined host or host group in the Control-M for Web Services job definitions.

You must create a new connection profile for the relevant job type, since this utility only converts the job type.

Before You Begin

Begin

  1. Do one of the following to export the Control-M for Web Services jobs to a JSON file:

    • From Control-M Web, export the Workspace to a JSON file, as described in Exporting a Workspace.

      Note

      Only Control-M for Web Services jobs are migrated. All other jobs and folders remain unchanged.

    • Export the relevant Control-M Web Services jobs via Control-M Automation API, as described in deploy jobs::get.  

  2. Copy the exported JSON file to the Agent where the original Control-M for Web Services jobs execute.

    Note

    If you copy the exported JSON file to a different Agent, the migration cannot run since the job definitions refer to the local resources of the original Agent, such as the local connection profile, WSDL files, and header.

  3. Log in to the Agent account that executes the Control-M for Web Services jobs.
  4. From the Control-M for Web Services, Java, and Messaging plug-in directory, run the following command:
    wsconvert -input <Original_WS_Job_Definitions_Pathname> -output <Converted_WS_Job_Definitions_Pathname> -agent <Agent_Name>
    For a more information, see Migration Utility Parameters.
  5. Do one of the following to import the converted Web Services job definitions:
    • From Control-M Web, open the required Workspace and import the converted Web Services job definitions, as described in Importing a Workspace.
    • Import the converted Web Services job definitions via Control-M Automation API, as described in deploy.  
  6. Create one of the following connection profiles, depending on the converted job type.

Migration Utility Parameters

The following table describes the Control-M for Web Services Job to Control-M Web Services REST or Control-M Web Services SOAP Job migration utility parameters.

Parameter

Description

-input

Defines the pathname where the exported Control-M for Web Services job definitions JSON file is located.

-output

Defines a pathname where the migrated Control-M Web Services REST or Control-M Web Services SOAP job definitions are exported.

-agent

Defines the Agent names or host group names that the Control-M Web Services REST or Control-M Web Services SOAP jobs runs on. Use a , (comma) to separate multiple Agent or host group names. 

The conversion utility cannot convert jobs whose host or host group job attribute does not match the -agent parameter.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*