I did this in Java for an integration because it was easier; it would be easy for you to do that with an automation script.
- My requirements were like this Maximo needs to construct a SOAP API message to Opentext Content Server, called livelink, in older terminology
- Maximo has built-in SOAP Clients almost no code needs to be written.
- In my case, each SOAPCall needed to be prefixed with an authentication header this too to a certain extent, you do not need to write code.
- In my experience or rather inexperience I found it easier to extend the JAXWS handler and add about 1 or 2 lines of java code so my approach was I would issue a rest call to the OTDS(OpenText Directory Server), retrieve a token and then once I get this I would send the standard SOAP message.
If you are a starter, just try to do some simple examples involving REST using automation scripts, and you will probably get through this in no time.
My flow is like this
- Publish Channel has my custom Java Handler
- When an MBO is changed, the Publish Channel sends me a message to the External System configured. Note that an External System is not a middleware; it is just an entity in Maximo that effectively ties your code asynchronously.
- The External System can be triggered by a JMS queue, so when a change happens in Maximo, depending on your JMSQ setting, the message would reach your destination system.
Coming from other technologies, I found Maximo to be a very mature system, albeit much of the starter code is not readily available or broken IBM links
I looked at Viet Tran Blogs, Bruno Portaluri as well as a whole lot of big brains in the maximo space to deliver my solution.
Edit: I do not know if this happens in your case, but in my case, the XML that Maximo generates has to be changed to what OT expects so XMLTransformation needs to be done so that was again the reason I had to resort to java as the transformation got way too complicated :)