- How To Use Outbound Processing Rules with Maximo Integration Framework (MIF)
- How to Filter Records with MIF’s Publish Channels for Outbound Data
- How to use XSL Transformations with MIF’s Publish Channels for Outbound Data
- Action properties for Integration Framework (MIF)
- MIF – External Systems
- Setting up JMS buses and queues for multiple instances of Maximo 7
- Maximo 7 Web Services Library
- Creating Additional Continuous Queues and MDBs
- Setup Integration Framework JMS queues and buses in WebSphere
- Maximo 7.1 Integration Framework Configuration Basics
In a recent forum post, I was asked why the data being imported was being overwritten and not replaced by the data specified in the integration table or flat file. In short, the answer is you have to specify an ‘action’ property when importing the data. That property is optional, but you can tell MIF what action to take when it encounters a situation like this one. Here is a list of actions to use when importing data.
- Add – Add records to database in receiving system
- AddChange – Add or update existing records in the database in the receiving system
- Change – Update existing records in the database in the receiving system
- Delete – Delete records from the database in the receiving system
- Replace – Substitute existing records in the database in the receiving system
- null – Add records or replace records in the database in the receiving system depending on whether the primary record exists in the database.
- If the primary record does NOT exist in the database, the system performs an Add action
- If the primary record DOES exist in the database, the system performs a Replace action.
