Integrating Remedy with Control-M Workload Change Manager

This procedure describes how to integrate Remedy with Control-M Workload Change Manager through a REST Service. This procedure contains example code which can be modified to fit your specific criteria.

Before you begin:

• Ensure that you have the following installed:
  • Java JDK 1.8
  • Apache MAEVEN build utility

To integrate Remedy with Control-M Workload Change Manager:

1. Navigate to the following directory:
   • Windows:<em_InstallFolder>\WCMRemedyIntegration\src\main\webapp\WEB-INF\classes
   • UNIX: <em_InstallFolder>/WCMRemedyIntegration/src/main/webapp/WEB-INF/classes
2. Open the RemedyIntegration.properties file to configure the settings of your Remedy properties, as described in Remedy integration file properties.
3. In the same directory, open the NewTicketFields.properties file to configure the field ID values that are used to create a Change Ticket ID. You can modify the values to reflect your Remedy environment values.

   Note: The values of the fields can contain values for the REST Service request such as: Control-M Request ${name} by ${endUser} performed by ${scheduler}.

4. Open a command line and navigate to:

   <em_InstallFolder>/WCMRemedyIntegration

5. Enter the following commands to create a WAR package:
   • Windows:
     1. SET JAVA_HOME=
     2. SET M2_HOME=
     3. SET PATH=%JAVA_HOME%\bin;%M2_HOME%\bin;%PATH%
     4. mvn package
   • UNIX:
     1. setenv JAVA_HOME
     2. setenv M2_HOME
     3. set path = ($JAVA_HOME/bin $M2_HOME/bin $PATH)
     4. mvn package

   The MAEVEN build utility creates a WAR and JAR file in the target directory.

6. Deploy the WAR file to a Web Server. You can use a Control-M/EM Web Server by copying the WAR file into the following directory:
   • Windows:<em_InstallFolder>\emweb\tomcat\webapps
   • UNIX: <em_InstallFolder>/etc/emweb/tomcat/webapps