Article

mbluteau's picture
article
Reads:

4197

Score:
5
5
1
 
Comments:

0

Practical example - Web Services integration: Frontrange Heat

(View Disclaimer)

Implementing a reusable interface between Identity Manager and a 3rd party application provides for an effective and easy way to deliver extended integration. In this example, we use Frontrange Heat, a popular ticketing system, and we describe the few simple steps that are required.

For information on how to configure Heat for Web Services, see my other appnote: Heat and Remedy Integration Using Web Services

The first step is to obtain the WSDL file by pointing at the Heat url, e.g. http://MyHeatServerIP:8080/HEAT_WS.asmx

Then you can create a provisioning request in Designer, using the template with No Approval.

Click to view.

Figure 1: Drag the Integration Activity in the workflow.

Click to view.

Figure 2: After importing the WSDL into the Integration Activity, you should see this pop-up for the setCall function.

Click to view.

Figure 3: You need to edit the Request Form and add the fields that will feed the setCall input values.

Click to view.

Figure 4: Then you need to map all the form fields into flowdata values.

Click to view.

Figure 5: You must map the flowdata values to the input values for setCall.

Click to view.

Figure 6: You must configure the server parameters, if they were not included in the WSDL.

Click to view.

Figure 7: If you have configured authentication for the web service, you must provide the credentials.

Click to view.

Figure 8: After importing the WSDL, you will see one function call for setCallSoapIn. You must copy this call and modify the copy to act on setCallSoapIn/setCall, to properly format the XML document sent to Heat.

Click to view.

Figure 9: Resulting Integration Service with a copy of the step.

Click to view.

Figure 10: Once you have the provisioning request working, you can invoke it from Policy Builder for any driver.

Click to view.

Figure 11: Properties for the Start Workflow Policy Builder action.

Click to view.

Figure 12: It is also possible to invoke the provisioning request from another provisioning request, which together with the Start Workflow action in Policy Builder, provides easy reusability once you have a working provisioning request configured for setCall.


Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.




User Comments

© 2013 Novell