Embed Size (px)
Citation preview
Ensuring Data integrity while performing loads into Maximo
Maximo 7.6 – Integration Framework
Why use it
• Leverages the Maximo Integration Framework
– Maximo Business Objects (MBO)
– Not ‘home-grown’ SQL scripts
• Out of the Box Functionality
• Maintains data integrity
– Data Relationships
– Non-Persistent data fields
• Captures erroneous data before it’s loaded
Components
Maximo Integration Framework
Components
• Tables
• MBO
• Object structures
• JMS Queues
• Sources of Data
Communication Modes• Web services (Asynchronous / Synchronous)• HTTP (Asynchronous / Synchronous)• Java Message Services (JMS) (Asynchronous)• Database interface tables (Asynchronous)• XML files and Flat Files (Asynchronous)• Invoke EJB (Asynchronous / Synchronous)
• Asynchronous use the Java Message Service (JMS) queues. Synchronous does not use a queue.
One isn’t necessarily better. It completely depends on the external application compatibility with communication modes. Asynchronous typically means a time based interaction. (Maximo processes the queue at a certain interval)
Maximo Integration Framework (MIF)
• Set of Applications to help integrate to external systems (or flat files)
• Create business flows between the system and external applications
Object Structure
• Common Data layer that the Maximo integration Framework uses for all Inbound and Outbound data processing
• Bottom layer of the integration framework and each integration object can contain one or more business objects
e.g. Locations, Asset, Item, Workorder
Publish Channel
• Used to export (or publish) data to an external application or file location
– Unless specified, the export will be placed in the location set at mxe.int.globaldir
• eg) MXAssetInterface
Enterprise Service
• Used to import data from an external data source or file.
• 60 Out of the Box or create your own.
• E.g. MXAssetInterface
External System
• Collection of associated publish channels and enterprise services
• Associated to a specific end point
End Point
• Location or type of data exchange which the External System is associated with
e.g. flat file, xml file,
interface tables,
webservice
Demonstration
• Loading spreadsheet data via the MIF
• Application Export / Import
• Bulk loading table data via interface tables
Configuration for MIF lmport
Demonstration
Object Structure and Enterprise Service
• Create New Object Structure
– Consumed by Integration
– Source Object – LOCATIONS
• Modify attributes if required – More Actions > Exclude/Include Fields
– Support Flat Structure Enabled (import from csv file)
• Create Enterprise Service
– Processed through JMS
– Object structure (previously created)
– Interface Table Name
– Enable Message Tracking (optional)
End Point and External System
• Choose End Point
– Use standard MXIFACETABLE or MXFLATFILE
• Create External System
– End Point from previous
– Enterprise Services – select the previously defined
– Specify Queues• Add/Modify Queues provides message counts
– Unselect “use continuous queue”
– Create interface tables
Demonstration – Loading Locations
• Configure JMSQSEQCONSUMER Cron Task– Make sure this is active.
• Configuring the IFACETABLECONSUMER Cron Task– New Instance
– Default is not active
• Monitor via – Message Errors via the Re-Processing Application
– Message Tracking (enable at Enterprise Service)
– Also IMPORTMESSAGE in MXIN_INTER_TRAN
Sources of Data
• Using a CSV file (Data import)
– Enterprise System>Enterprise Services>Data Import
• Populating a staging table and the Maximo MXIN_INTER_TRANS table
– Importance of TRANSID (filtering rows)
– Add / AddChange / Delete
Configuration for Application Import
Demonstration
Setting up Application Import
• Create Object Structure
– Duplicate an “out of the box” object for your use
– Ensure Support Flat File is check if you want to use CSV (comma separated values) files.
• Enable Import / Export support for Application within Maximo
– Select Action > Add/Modify Application Export (or Import)
• Grant Import / Export security privileges to Application in Maximo (Security -> Security Groups)
Application vs. MIF
• Application (version 7.5 onwards)– Only requires object structure setup
– Additional security settings required
– Easy for the end user
– Not great for complex or large volumes of data
• MIF– Requires setup of all MIF components (object structure,
Publish Channel, Enterprise Service, External System, End Point
– Requires access to integration global directory
Troubleshooting
Data Loading
Troubleshooting
• Exports / Imports aren’t working
– Is Admin Mode is on?
– Is the JMSQSEQCONSUMER Cron task enabled and running?
– Is the queue and bus setup correctly in the application server? (Websphere or Weblogic)
– Check Log files
Troubleshooting
• When Add/Modifying Application Export/Import setup
Solution:
Go into security and remove the grant to the integration import/export option for that application.
Program Highlights
• Town Hall Discussion (Thursday, October 8 from 4:30 PM – 5:15 PM)– Before noon on Thursday, submit your questions by going to
gomaximo.org - 2015 Conference - Town Hall.
• Prizes, Prizes, Prizes! (Thursday, October 8 during social)– Cash prizes – Must be present to win!
• Attendee Survey– Your feedback on this event is very important to the GOMaximo Board.
• Access gomaximo.org/training to provide feedback on specific training sessions • Go to gomaximo.org/conference to let us know your thoughts on the overall
conference.
– Everyone who completes a survey will be entered into a drawing for cash prizes.
Working with Maximo 7.5 Training3 day Maximo fundamentals workshop
Houston, October 26-28th
