4 comments
Various 
Why:
We are using Assyst as our helpdesk tool. If MOM detects a critical error this must be logged as a Assyst call. Now we are doing this manually. I always wondered why there was no MOM product connector for ASSYST. Yesterday I could not wait anymore for it so I have build one my self.
What is it:
The first release will be one build on the MPC SDK example and will be a basic one-way connector and a ASSYST webservice.
How this works:
The new alert is generated in MOM. You evaluate it if this should be logged into ASSYST. You change the resolution state to "Log to Assyst". The MPC will now do a webservice call to the Assyst webservice. This webservice will make a Assyst incident using the ACLI (from Assyst) interface. The ACLI returns the incident number. The MPC receives the incident number and saves this in the MOM alerts "ticked id" field. At last the MPC changes the resolution state to "level 1:…. assigned…".
Status:
Yesterday I complied ,installed and tested the ASSYST MPC. And it works!!! Now I have to put in some error handling.
Download:
In part 2 I will post the setup package. Please let me know if you like this worked out idea.
Michel Kamp
4 comments
Great stuff i’ll think there are to little Helpdesktools with connectors to mom.
We all wait for the service desk but can we dump our current helpdesk tool..
looking forward for part 2.
Robert
Is Part 2 available yet this sounds like something I could really use?
Lynn
Lynn,
I didn’t had the time to program it out yet. And I will not do it. This because we are moving to a different tool (one that is working better : system center helpdesk). Sorry.
What you could do is to make a operator task and use the assyst importer exec tool to make a new incident. I ‘m using this also this way.
Michel
michelk
could you explain how you did do the act with assyst
we have the same problem
lvantoorenburg@hotmail.com