Maximo’s Integration Framework: Interface TablesPresenter: Jeremy Simantel

www.ontracksconsulting.com

August 27, 2009

How to use Maximo Interface Tables

Agenda:• What does the “Integration Framework” do?• Why use Maximo’s Integration Framework?• Integration Framework out-of-the-box• When to Consider Migration Methods• How do Interface Tables Work?• Advantages & Caveats to using Interface Tables• Live Demonstration • Question & Answer Period

What does the “Integration Framework” (formerly Maximo Enterprise Adapter) do?

“The integration framework is a set of applications that help you to integrate the system to your external applications. You also can create business flows between the system and your external applications.”

Maximo 7 Integration Guide

What does that mean?

Why use Maximo’s Integration Framework?

Maximo’s Integration Framework is primarily used for two reasons:

1. Integration Between Systems

2. Ad-Hoc Data Loads / Manipulation

Integration Between Systems

Works Best With:• XML• Web Services

Integration Examples:• Financials• Customer Relationship Management

Ad-Hoc Data Loads

Data Load Examples:• Merging Environments• Historical Data• Data Cleanup

Works Best With:• Interface Table• Flat File

Out-of-the-box, Maximo Integration Framework Supports:1. XML2. Web services3. Flat File4. Interface Table

Integration Framework out-of-the-box

Why not migrate through direct table writes (SQL, ORACLE, DB2, etc.)?

It can be difficult if not harmful migrating data without utilizing Maximo’s Integration Framework

e.g. inserting rows directly into the database

1. Maximo rules are not enforced

2. Referenced data is easily missed

3. Difficult to manage

Why not migrate through the backend?

Why not migrate through the backend?

How do Interface Tables Work?

1. Data Source 2. Pristine Export

3. Staging Table/SQL Data Massaging

4. Interface Framework Processing

5. Maximo Application 6. End User

Advantages of Interface Tables

• Staging & manipulating data strictly through SQL

• Continue using the SQL tools you are familiar with without getting into the mess depicted on Slide 6

• No file transferring necessary

• Pristine & Loaded Data stored in one place

Caveats

Things to consider when using Interface Tables1. Maintain secure environment

a. User will require access to database tables

b. Easy to make widespread changes to the database

2. Manage data volumea. Large data volume typically imply many dependencies

b. Large data volume can substantially decrease application performance

3. Avoid manipulating pristine dataa. Export and copy to “staging” import tables

Demonstration

1. Configure Publish Channel & Interface Table2. Configure Enterprise Services & Interface Table3. Configure Interface Table External System4. Configure External System (add Publish Channel &

Enterprise Services)5. Create Interface Table6. Export7. Manipulate8. Load to mxin_inter_trans9. Import via Cron Task

Questions?