Skip to main contentCarbon Design System

Enterprise service script

Enterprise Services provide the inbound integration backbone of Maximo. They represent the internal implementation for all kinds of services that Maximo Integration Framework (MIF) offers, XML/HTTP, SOAP, Flat Files, Interface tables to name a few. Enterprise services can optionally leverage the queues as it is async.
Enterprise services are also used for Data import from UI as well as cron jobs (File, Interface Tables). If the service is async, the Enterprise service execution starts after the messages get picked up from those queues and get pushed downstream. Like its outbound equivalent (Publish Channel), Enterprise Services are used to transform data from external format to Maximo format, json or xml.
Enterprise Services support the following script points:

Script PointPurpose
External ExitsUsed for data transformation of inbound messages from External format (erData) to internal Maximo format irData
User Exit (Before External Exit)Used for data modification before it reaches the External Exit (erData).
User Exit (After External Exit)Used data transformation from the output of the External Exit to target Maximo format.

The following table lists the available variables:

erDataAn instance of psdi.iface.mic.StructureData used to hold the external document. Available for all three exits.
irDataAn instance of psdi.iface.mic.StructureData used to hold the internal (Maximo format) document. This is set to null (as input) for External Exit and Before User Exit. External exits are expected to set the irData by transforming the erData.
ifaceTypeThe interface type name.
ifaceNameThe channel name.
osNameThe Object Structure name.
messageTypeThe message type which can have values like Sync/Create/Update/Delete.
extSystemThe external system name.
userInfoThe UserInfo object representing the authenticated user that invoked this service.
connThe jdbc Connection object.

The following example is of an after user exit script that sets the wopriority to an inbound WO transaction:

if irData.getCurrentData("vendor")=="A0001" and irData.isCurrentDataNull("wopriority")==True:

The “After User Exit” for Enterprise service would work with the irData (internal Maximo format data) as the inbound External exit would have mapped the external format to an internal format. The following example is of a before user exit. In this example, the script decides to skip the transaction when a certain condition is met.

from org.jdom import Namespace
doc = erData.getData()
extXMLRoot = doc.getRootElement()
orgname = extXMLRoot.getChildText("orgname", Namespace.getNamespace(""))
if orgname=="somevalue":

The Before User Exit has access to only the erData variable that contains the external document. In this case the external document is XML and the API to access that as a JDOM document is erData.getData(). If this was a json document, you would need to use a different API to get the json data. The following script is an example of that:

from import OslcUtils
jsonData = OslcUtils.bytesToJSON(erData.getOriginalByteData())
orgname = jsonData.get("orgname")
if orgname=="somevalue":

The following example is of an External Exit Script that creates a Maximo company by mapping external data to to MXVENDOR Object Structure:

from psdi.iface.mic import EnterpriseServiceCache
from psdi.server import MXServer
from org.jdom import Namespace
doc = erData.getData()
extXMLRoot = doc.getRootElement()
vendor = extXMLRoot.getChildText("vendor", Namespace.getNamespace(""))
organization = extXMLRoot.getChildText("organization", Namespace.getNamespace(""))
srv = EnterpriseServiceCache.getInstance().getEnterpriseServiceInfo("MXVENDORInterface")