Troubleshooting

I am unable to see the Application Integrator log in page in the Internet Explorer browser

Turn off the compatibility mode in Internet Explorer Settings (not required for supported Chrome and Firefox browsers).

I cannot log in to Application Integrator designer application

The Application Integrator connects to Control-M/EM Server.

You need to verify Control-M/EM server is running and registered to the local Naming Server.

NOTE: If you have more than 1 Control-M/EM Server (GSR) registered to the same Naming Service, the Application Integrator connects to the default (System) context, or to the first active Control-M/EM Server.

If you want the Application Integrator to work with a specific Control-M/EM Server, you can configure Application Integrator connectivity by setting the ai.cfg file in the following path:

<EM Tomcat home>/AIRepo/_AICFG/ai.cfg

For more information, see Creating a communication configuration file.

I cannot import a WSDL file to the Application Integrator designer

Do one of the following:

• If you are using a proxy server, you need to set the details in the Settings window. For more information, see Configuring proxy server settings.
• Download the WSDL to a file and select Import from file instead of importing from a URL.

When I open the Deploy window, I cannot see any agents in the agent list

Do one of the following:

• Verify that Application Integrator application plug in was installed on the Agent (check the installed-versions.txt file)
• Run the following ctmgetcm command on Control-M Server:

  ctmgetcm –Host <agent name> -ApplType * -Action get

  NOTE: Use the Action Get and ensure Application Integrator is listed.

When I deploy a job type, deployment fails

Do one of the following:

• Verify that Control-M/Server version 8.0.00 fix pack 2 or above is installed.
• Verify communication between Control-M/EM Server and Control-M/Server.

After successful deployment, I cannot see the list of connection profiles or create new one

For Control-M/Server version 8.0.00 fix pack 4 and below, and Control-M/Agent version fix pack 4 and below, ensure you have performed the following post deployment operations:

• ctmgetcm (with action “Get”)
• Agent was restarted

For more information, see Importing the Connection Profile into the CCM.

After successful deployment, I cannot see the new Job Type in Control-M

Do one or more of the following:

• Verify your Control-M client is version 8.0.00 fix pack 7 and above or version 9.0.00 fix pack 1 and above.
• Restart Control-M client.
• Verify that Control-M/EM server short hostname can be accessed/pinged.
• Check that your new job type appears in the following folder:

  <WLA client>\bin\plugins\apps-repo folder

After successful deployment, I cannot open the Connection Profiles Manager from the CCM

Do one or more of the following:

• Verify your Control-M client is version 8.0.00 fix pack 7 and above or version 9.0.00 fix pack 1 and above.
• Verify that Control-M/EM server short hostname can be accessed/pinged.
• Check that your new job type appears in the following folder:

  <WLA client>\bin\plugins\apps-repo folder

My job failed although it should have finished successfully

Check the execution log in your active job synopsis view.