Tuesday, October 30, 2012

Maximo Integration Framework Tutorial (Flat-file export and import)

Maximo Integration Framework Tutorial (Flat-file export and import)

Here we will configure Maximo IF (Integration Framework) to export the data and we will load a flat file (coma delimiter) with our data in Maximo (uploading the data in Maximo).

First we Go To > Integration module > External Systems.

Select EXTSYS1 from the List tab and from Select Action menu select Duplicate External System.
This new External System will be our playgroup we can do any thing with it and if thing gone wrong we can delete it and duplicate another one.







Then in the System text box put EXTSYS0 and Enable it from the check box on the other side.

In the Server where Maximo is installed create a folder where the exported files will go in my case it was a Windows Server 2003 and the path was C:\ibm\MIF.

Back at Maximo Go To > System Configuration module > Platform Configuration > System Properties.
Filter on int.globaldir now change the Global Value to C:\ibm\MIF Save then check the box on the far left of the screen and do a Live Refresh (red arrow), click OK.

It should look like this.


Now Go To > System Configuration module > Platform Configuration > Cron Task Setup.
Filter on flat and select FLATFILECONSUMER from the List tab.




Create a new Cron Task Instance by clicking the New Row command button set the Schedule to Every 30 Second(s) from the select value calender Icon.
Then check the Active box as seen in the snapshot below then Save.








Filter again on jms and select JMSQSEQCONSUMER from the List tab.
Then check the Active box in both instance as seen in the snapshot below then Save.








Now Go To > Integration module > Object Structure.
Create New Object Structure and name it MXJOBPLAN don't forget to select INTEGRATION in the Consumed By text box.
Then click the New Row button and select JOBPLAN as the Object from its select value message box.


Click the New Row button again and select JOBTASK this time as the Object from its select value message box.
Don't forget to select JOBPLAN as the Parent Object and JOBTASK as the Relationship.

Now for our newly created Object Structure be able to export its data as a Flat-file (CSV) we must tell it to Support Flat Structure from the check box marked in the snapshot below and Save.


As you can see there is an Alias Conflict which tell us that some of our Objects have Fields with the same name so to fix that we will select ADD/Modify Alias from the Select Action menu.
Then add a prefix (JP_) to the Fields ALIASNAME that is marked as DUPLICATED and click OK.



Now if should look like this.


Now we have an Object Structure MXJOBPLAN with with no Alias Conflict.

Next we Go To > Integration > Enterprise Services (This is the name the Maximo give to In-pound data configuration) and Create New Enterprise Service and name it MXJOBPLANint then assign it to MXJOBPLAN Object Structure.

Again Go To > Integration > Publish Channel (Out-pound data) Create New and name it MXJOBPLANint then assign it to MXJOBPLAN Object Structure.

Back to the External System where we will add the newly created Publish Channel from New Row then Select Value select MXJOBPLANint .








Don't forget to make the End Point as MXFLATFILE and Enable it from the check box.





Let's try to run a Data Export command button and see what we get.


In our path we created earlier C:\ibm\MIF we will find a new folder named flatfiles and in it we will find our output file.


If you opened it with a simple text editor like Notepad ++ you will see the data in a coma delimiter format (csv) you can now rename it as a .csv and open it with MS Excel edit it save it and re-upload it in Maximo.


As for in-bound integration.
First we enable the integration user in Maximo MXINTADM, from Go To > Security > Users then Filter on mxin select MXINTADM.




Notice that MXINTADM is ACTIVE as a Person but INACTIVE as a user so from the top Toolbar select Change Status set the New Status as Active.
OK and Save.










Now for the Enterprise Services from New Row then Select Value select MXJOBPLANint and Enable it from the check box.





Then click the Data Import button select Flat File and check Import Preview to make it a dry run (test with no actual data uploaded).

If our dry run was a success,


Try it for real.


and yippi.

Your data now is in Maximo congratulation.


10 comments:

  1. why in the folder C: \ ibm \ MIF file does not appear. dat like you? I've followed the steps and ways the written

    ReplyDelete
  2. HI, your blog is extreme good, very helpful

    ReplyDelete
  3. Hi!
    I successfully bound the data import back to maximo with the same message to queue. But when i check the database or in maximo application, it's not there?

    ReplyDelete
  4. Hi Budimulya,

    Please check in the out queues weather the data is successfully published or not.

    ReplyDelete
  5. Hi Alan,

    Thanks for your feedback I am trying to cover more topics on maximo.

    ReplyDelete
  6. Hi Marvin,

    Which application data you are uploading and we have to check for the inbound restrictions for the key value.

    ReplyDelete
  7. This is flat file only. How can when we want data be inserted into external database?

    ReplyDelete
  8. For database to data base integration we can go for the Interface table integration I will upload the detailed article on Interface integration soon.

    ReplyDelete
  9. Manoj. I have created an Object structure in the front end of 7.5 and want to export a flat file that has fields from the Inventory Object and Item description from the Item Object. I was able to create the Object Structure and corrected a couple of Alias conflicts. I successfully exported the data I wanted and when I opened the csv file I noticed that the rows of data appeared duplicated. I expected 860 rows but instead got 1740 row's..
    Can you suggest where I made a mistake on the OS setup?

    ReplyDelete
  10. Hi Manoj How do you remove the header from exported .csv files the header that identifies the external system and publish channel

    ReplyDelete