MEA (Maximo Enterprise Adaptor) or MIF (Maximo Integration Framework) export files not generated, no errors, why?
Everything was working before, why not generated anymore, and there is no error. End up it was the messages which got stuck in the queue. Here are the steps to delete the stuck messages from the queue.
From the Maximo’s Go To menu, select Integration\External Systems
Select the external system to which data is to be sent (EXTSYS1)
Select action Add/Modify Queues
Maximo Integration framework supports asynchronous
processing using JMS queues. Queues are tied to External systems configuration
such that each external system can potentially have their own set of outbound
and inbound queues to communicate with Maximo. Outbound queues are meant to facilitate asynchronous
messaging from Maximo to External system. For example when a Mbo gets
created/updated/deleted, the MIF Publish Channel traps the event and sends an
XML message [based on the Object Structure defined] to the Queue. All outbound
Do you prefer to not to include custom Java code in your integration implementation? Don’t have available personnel with the appropriate Java skills? There are capabilities in the integration framework to implement processing functionality by using integration processing rules and control where Java code is not needed. Processing rules can be configured on any Publish Channel or Enterprise Service in order to filter transactions or set field values. Integration Controls can be used as part of a processing rule to allow for configurability of... [More]
Integration framework uses XML messages
to publish and consume data from and to Maximo. However there are a
range of characters that are considered invalid for an XML document.
The Maximo Mbo framework would allow such characters to be entered
and saved into Maximo. Problem starts however when one tries to
export that data through the Integration Framework. Compounding the problem - most XML
parsers would not validate for invalid XML characters in XML
node/element values while creating an XML document – but do so when
parsing an XML... [More]
To help you understand OSLC better, the 22.214.171.124 release of Maximo Asset Management features significant changes to the OSLC documentation in the information center. The existing 126.96.36.199 content that describes OSLC consumers has been enhanced, while a whole new section on OSLC providers has been added. The enhanced OSLC consumer section includes an example of designing an OSLC query interaction. Meanwhile, the OSLC provider content includes information on configuring Maximo Asset Management data as an OSLC resource to support creating, querying,... [More]
For those of you looking for additional content regarding the Integration Framework (MIF), check out the refreshed Wiki Page for Integration Framework content. New and existing content has been consolidated into one location for easier access. A sampling of the content includes discussion around various integration components, use of processing rules on a service or channel and the use of an alternate key in inbound message processing. There are also links to other content such as the Info Center and Support tech notes.... [More]
With the release of Maximo 7.5 we introduced a feature in the Integration Framework to propagate events on a child object to the parent and generate an outbound transactions as described in this wiki page.
The goal of this feature was to allow customers to generate outbound transactions when a change is made to a child object on an object structure when it is changed in the parent objects application.
Over the recent weeks in Support we've seen customers attempting... [More]
Transaction processing associated with Maximo integration scenarios involving a high number of external systems, might not necessarily be the optimum when working with a SINGLE continuous queue. Application server’s queue configuration values will be driven by the largest common denominator that addresses the transactional needs of ALL external systems. Are you aware that is possible to specify to each external system in your integration scenario a dedicated continuous queue? By configuring Maximo’s integration framework continuous queue... [More]
When importing linear asset features using the MIF, the following error may be encountered: "BMXAA6177E - Reference Point and End Measure must be between the linear asset's Start Measure 0.00 and End Measure 681,700.00." While this error is sometimes appropriate, the error should not be seen when the sum of the start and end measures and the respective start and end offsets on an asset feature are within defined Start and End measures of the linear asset. In addition to insuring that the latest cumulative hot fix has been applied,... [More]
This article aims at demonstrating the required steps to delete
non-processed messages from a queue of IBM Maximo Asset Management 7.5, IBM
WebSphere 188.8.131.52 and Oracle Weblogic 10.3.3.0
You can use Maximo Integration Framework (MIF) for integrating an external
system to the Maximo Asset Management 7.5 system. With MIF you can exchange
data through importing and exporting operations. XML and .dat files are
examples of ways to do the operations. This article comprises the steps
required for deleting... [More]
Functional improvements in Maximo Integration Framework (MIF) Data Import functionality enable the selection of two different ways to address error correction: GUI-based and File-based . The data import functionality provided through the External System application gives the option of identifying the error management mechanism of your preference. "File-based" error management is supported by Maximo's Message Reprocessing application thru an enhanced GUI where re-processable files (files including all errors identified from their... [More]
Customers often have the need and/or desire to work with data in a spreadsheet format because of the usability of applications such as Excel. With release 7.5 of Maximo, users can now have their applications enabled to support the export and import of data into a delimited file format (.csv) that lets them view and manage that data in Excel. A Maximo user whose job it is to manage a company’s asset master data can have a feature where they are in the asset application and can export asset information, such as assets and their... [More]
Maximo Asset Configuration Manager (ACM) allows the construction, use and management of complex assets. These assets are generated based on structures known as Models. These models are built based on sub components known as build items (cm items). The ACM 184.108.40.206 patch introduced the ability to use the Maximo Integration Framework (MIF) to perform many ACM functions and load data into associated tables. One of the most common and time consuming functions used within (ACM) is the addition and configuration of complex Models. These operations... [More]
Maximo Asset Configuration Manager (ACM) allows a complete history of the components which make up a complex a
Asset to be maintained and easily viewed for any given point in time. The ACM 220.127.116.11 patch introduced the ability to use the Maximo Integration Framework (MIF) to perform many ACM functions and load data into associated tables.
One of the most common functions used within (ACM) is the and removal and installation of sub-assembly Assets. These operations are now achievable via the MIF and three separate transactions are... [More]