In the past, the documentation that was created for Maximo clustering with JMS resources typically contained separate buses – one per cluster – to avoid affecting performance while loading data to Maximo, but this is often complicated and has drawbacks when it comes to high availability and scalability as well as ease of configuration. I admit I'm probably responsible for most of that documentation and generally there are always workarounds available to cope with the separate buses when more than one cluster needs access... [More]
IBM Maximo Enterprise Adapter 7.6 for Oracle Applications has several scenarios of trade data that contain a great number of information. If you have questions about what information can be sent by the out of box solution check this document: http://www.ibm.com/support/knowledgecenter/SSLKYL_7.6.0/com.ibm.meaora.doc_7.6.0/pdf_meaora_map.pdf But what if you want to work with some information that is not sent by the Adapter? How to add new fields on the Adapter? On this example I will show you how to add a new field of Maximo and... [More]
Automation Script for Maximo Integration Framework (MIF) is introduced in 7.6 and is a good practice to create and manipulate data. You have the same functionality as the Java Class. But in this case you are not going to lose your class if you upgrade Maximo. Let’s take a look at a simple example. Creating an Automation Script for an inbound Object Structure Go to System Configuration => Platform Configuration => Automation Scripts. Click on Select Action => Create => Script for Integration. You have a couple options... [More]
With the release of Maximo 126.96.36.199 a new JSON API is available. You can find information here: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Maximo%20JSON%20API Moving forward, we will be supporting the JSON API. We will no longer be enhancing the REST or OSLC API's.
Have a need to extend Maximo's Supply Chain capabilities to include Planning and Contract Management. Watch this recording of the integration solution available between IBM Procurement (Emptoris) and Maximo. If you want additional information about the Emptoris-Maximo Connector, feel free to reach out to Paul Nash at email@example.com.
Customers from time to time have noticed that the Maximo system stops responding. When the environment is reviewed, the database has locks on SIB related tables. This is a case where the issue is not primarily because of SIB tables but due to the fact that the SIB tables are the victim of Maximo system freezing and holding locks on the SIB tables. If Maximo integration components are writing to JMS Queues using the database storage, then SIB tables are created and used in the database. Whenever Maximo writes data or reads data from... [More]
Recently I've been doing quite a bit of work with IBM's messaging appliance MessageSight . If you haven't heard of it and want to learn more, please click on the link. In working with this new appliance, I wanted to configure WebSphere MQ to pass my messages to from Message Sight. After configuring this, I started thinking about configuring this same WebSphere MQ environment to work with Maximo instead of using WebSphere's traditional JMS queues. Once I started my configuration the first thing I noticed, is there isn't a lot... [More]
A new youtube video has been released. Maximo Enabling MDB on all members of the MIF cluster This video shows how to enable MDB for the integration cluster You can view the video here - https://youtu.be/raPAg77UUTY
You want to set up crontask parameters for the JMSQSEQCONSUMER or IFACETABLECONSUMER crontask instance so that only messages for certain enterprise services are processed by a particular crontask instance. For example, you may want to process only workorder transactions associated with the MXWOInterface enterprise service. if you set the enterprise service name in your crontask parameters to a value that matches a valid enterprise service name but do not enter the name of an external system which hosts the enterprise service,... [More]
For Maximo 7.6 customers who use the MIF's Message Tracking feature, there is a new archiving utility for Message Tracking data. You can archive the message tracking data and/or the related XML messages. See the details on this utility in the MIF section of the Maximo WIKI: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Integration%20Framework
When using the Maximo Integration Framework (IF) in a clustered environment the following should be considered. For best performance with minimal impact to users, the Maximo Integration Framework (IF) can be configured to run on a single WebLogic application server instance of Maximo while users log in and work with a User Interface (UI) cluster of Maximo instances. In the below example, you will need 4 WebLogic application servers. One application server will serve as the Administration console for the rest of the... [More]
It's been a bit since my last entry in this series, so I thought I'd take some time this morning to finish off this tutorial on configuring a basic horizontal cluster. If you haven't read my previous posts, you can jump over to Part 1: WebSphere Configuration and Part 2: JMS Configuration . In this final portion of the three part series, we will go over the following topics. Creating the Virtual Host Assigning Names to JVM's Building and Deploying ear files Isolating functionality I will note... [More]
Since the 7.1 release when Maximo began integrating with Cognos, I've resolved several PMRs. Many of these were similar issues, but one of the primary concerns was locating relevant error messages and which log files to locate those errors in. For 'Part 1' of this blog, I will cover the common log files that should be reviewed when investigating issues with the Maximo/Cognos integration and submitting PMRs to Support. Cognos Log File Locations : The Cognos log files that will need to be checked when investigating issues with the... [More]
Previously I had posted a blog on creating a horizontal cluster across multiple nodes in WebSphere 8.5.5. If you haven't read that posting, please head on over Clustering with Maximo and WebSphere 8.5.5 - Part 1 - Configuration and take a look. Today we will be continuing forward with JMS configuration. I was going to do this series in 2 parts, but I will separate this out in 3 parts due to the length of the topic. In the original blog posting we configured the following. mxcluster1... [More]