Publish channels

Edit online

A publish channel is the pipeline for sending data asynchronously from the asset management software to an external system. Events that initiate publish channel processing are object events (insert, update, and delete), application‐initiated calls, and data export.

The content of a publish channel XML message is based on the associated object structure. When you trigger publish channel processing, the integration framework builds the XML message based on the object structure. The system then moves the message through multiple processing layers before it places the message into a queue and releasing the initiator of the transaction. The publish channel can use the following processing layers:
  • Processing rules – The integration framework provides a rules engine where you can filter and transform the XML message. You can implement rules in the Publish Channel application.
  • User exit – Represents a Java™ class that you can use to filter, transform data, and implement business logic. You can use this class as part of an installation‐customization.
  • Data processing class – Represents a Java class that you can use to filter, transform data, and implement business logic. Adapters for Oracle and SAP® provide processing classes to support integration to these products.
  • XSL map – Represents an XSLT stylesheet that you can use to transform data and map the XML message to another format.

After the system places the message into the queue, a polling thread (the system cron task) picks up the message and sends it to an external system through a configured endpoint. The endpoint identifies the protocol that the system uses to send data, such as HTTP or web service. The endpoint also identifies the property values that are specific to that endpoint, such as URL, username, and password.

Operation type

Every enterprise service and publish channel has an operation type that indicates the purpose of the transaction.

In an enterprise service, you can select an operation type from a list of system options. The operations that are available for your selection depend upon the value you specify in Query Only checkbox for the associated object structure.

Maximo® Connector for Oracle Applications uses only the SYNC operation.

Data formats

Maximo Manage and external systems can exchange data transactions by using XML messages, interface tables, and flat files. Maximo Manage accepts XML and interface table transactions for the real‐time exchange of data and flat files for the bulk import and export of non‐system data.
  • Integration XML

    Integration XML is the XML representation that the objects recognize. Maximo Manage writes all outbound XML messages in this format and requires that all inbound non‐system XML messages be converted to this format. If an external system uses another XML format, you must provide Java code or XSL stylesheets to convert the data.

  • Interface tables

    Interface tables are relational database tables that you can use in place of XML messages to transfer data between Maximo Manage and external systems. Each table contains the same data fields as the corresponding integration XML, in a flat, non‐hierarchical format. Maximo Connector for Oracle Applications uses interface tables.

  • Flat files

    A flat file is a non‐hierarchical, non‐relational representation of the data columns in enterprise services, publish channels, or interface tables. You can use flat files to load main data into Maximo Manage, and to import and export non‐system data to and from the asset management software.

You configure the object structure that is associated with the enterprise service or publish channel so that Maximo Manage can assign interface table names. You do so by selecting the Support Flat Structure checkbox on the Object Structure tab of the Object Structures application.