Hello all,

Has anyone worked on a Maximo outbound integration where a Data Warehousing tool reads from Maximo DB?
How do we send out non-persistent attributes in such a scenario?


Thanks,



------------------------------
KKunnuthara
------------------------------

#Maximo
#AssetandFacilitiesManagement

There isn't much detail to go on, so I'll be making a few assumptions in my answer, but I hope this helps.

To get access to non-persistent fields, you'll need to go through the business object layer.  In each object structure, you have the ability to expose non-persistent fields.  At that point, you can use any number of methods to extract the data.  Which one you pick will largely be influenced to how easily accessible the server is.

If you are polling as opposed to pushing, and have access to some kind of middleware, you might consider using REST or WebServices.  If you are looking for updates to be triggered whenever records are updated, you could use Publish Channels if you have a well defined endpoint that can accept the outbound XML.  CSV or IFACE tables are also an option if you can get the object structure to a place where you can mark it as flat and have appropriate access to fetch them.

------------------------------
Daniel Brame
Senior Technical Consultant
Intelligent Technology Solutions
dbrame@webuildits.com
www.webuildits.com
@dbrame/@webuildits
------------------------------

Original Message:
Sent: Thu March 03, 2022 12:08 AM
From: KKunnuthara
Subject: Maximo outbound integration via a Data Warehouse

Hello all,

Has anyone worked on a Maximo outbound integration where a Data Warehousing tool reads from Maximo DB?
How do we send out non-persistent attributes in such a scenario?


Thanks,



------------------------------
KKunnuthara
------------------------------

#Maximo
#AssetandFacilitiesManagement

Thanks very much for that response @Daniel Brame

In this instance, we are not using MIF at all, so Webservices and Publish Channels are not available.

The architecture being proposed here is a pure data fetch (by the Dataware housing tool) directly from Maximo DB.
Given that the non-persistent attributes are calculated at run time by the MBO layer, there might not be a way to include them in this type of integration.

------------------------------
KKunnuthara
------------------------------

Original Message:
Sent: Thu March 03, 2022 08:53 AM
From: Daniel Brame
Subject: Maximo outbound integration via a Data Warehouse

There isn't much detail to go on, so I'll be making a few assumptions in my answer, but I hope this helps.

To get access to non-persistent fields, you'll need to go through the business object layer.  In each object structure, you have the ability to expose non-persistent fields.  At that point, you can use any number of methods to extract the data.  Which one you pick will largely be influenced to how easily accessible the server is.

If you are polling as opposed to pushing, and have access to some kind of middleware, you might consider using REST or WebServices.  If you are looking for updates to be triggered whenever records are updated, you could use Publish Channels if you have a well defined endpoint that can accept the outbound XML.  CSV or IFACE tables are also an option if you can get the object structure to a place where you can mark it as flat and have appropriate access to fetch them.

------------------------------
Daniel Brame
Senior Technical Consultant
Intelligent Technology Solutions
dbrame@webuildits.com
www.webuildits.com
@dbrame/@webuildits

Original Message:
Sent: Thu March 03, 2022 12:08 AM
From: KKunnuthara
Subject: Maximo outbound integration via a Data Warehouse

Hello all,

Has anyone worked on a Maximo outbound integration where a Data Warehousing tool reads from Maximo DB?
How do we send out non-persistent attributes in such a scenario?


Thanks,



------------------------------
KKunnuthara
------------------------------

#AssetandFacilitiesManagement
#Maximo

Hi, you can make a publish channel and use Maximo DB as endpoint. In this case you could include all non persistent attributes you need in the object structure, all data is in DB and can be picked up from datawarehouse tool.
The result will even better for the warehaus, than they get only those information they need and can control better what is already taken/not taken.

 

Regards

Renata

------------------------------
Renata Nowicka-Pyda
------------------------------

Original Message:
Sent: Thu March 03, 2022 05:41 PM
From: KKunnuthara
Subject: Maximo outbound integration via a Data Warehouse

Thanks very much for that response @Daniel Brame

In this instance, we are not using MIF at all, so Webservices and Publish Channels are not available.

The architecture being proposed here is a pure data fetch (by the Dataware housing tool) directly from Maximo DB.
Given that the non-persistent attributes are calculated at run time by the MBO layer, there might not be a way to include them in this type of integration.

------------------------------
KKunnuthara

Original Message:
Sent: Thu March 03, 2022 08:53 AM
From: Daniel Brame
Subject: Maximo outbound integration via a Data Warehouse

There isn't much detail to go on, so I'll be making a few assumptions in my answer, but I hope this helps.

To get access to non-persistent fields, you'll need to go through the business object layer.  In each object structure, you have the ability to expose non-persistent fields.  At that point, you can use any number of methods to extract the data.  Which one you pick will largely be influenced to how easily accessible the server is.

If you are polling as opposed to pushing, and have access to some kind of middleware, you might consider using REST or WebServices.  If you are looking for updates to be triggered whenever records are updated, you could use Publish Channels if you have a well defined endpoint that can accept the outbound XML.  CSV or IFACE tables are also an option if you can get the object structure to a place where you can mark it as flat and have appropriate access to fetch them.

------------------------------
Daniel Brame
Senior Technical Consultant
Intelligent Technology Solutions
dbrame@webuildits.com
www.webuildits.com
@dbrame/@webuildits

Original Message:
Sent: Thu March 03, 2022 12:08 AM
From: KKunnuthara
Subject: Maximo outbound integration via a Data Warehouse

Hello all,

Has anyone worked on a Maximo outbound integration where a Data Warehousing tool reads from Maximo DB?
How do we send out non-persistent attributes in such a scenario?


Thanks,



------------------------------
KKunnuthara
------------------------------

#AssetandFacilitiesManagement
#Maximo

"Given that the non-persistent attributes are calculated at run time by the MBO layer, there might not be a way to include them in this type of integration."

You are right. There is not a way to include Maximo "calculated fields" when the part that does the calculation is not part of the integration.

Instead, you would have to use your platform's tools to define methods for calculating those values. For example, on Oracle, you could write a function that takes a siteid and wonum and returns the total cost for the WO hierarchy and use that in place of the WOGRANDTOTAL.ACT.

------------------------------
Blessings,
Jason Uppenborn
Sr. Technical Maximo Consultant
Cohesive Ontracks
------------------------------

Original Message:
Sent: Thu March 03, 2022 05:41 PM
From: KKunnuthara
Subject: Maximo outbound integration via a Data Warehouse

Thanks very much for that response @Daniel Brame

In this instance, we are not using MIF at all, so Webservices and Publish Channels are not available.

The architecture being proposed here is a pure data fetch (by the Dataware housing tool) directly from Maximo DB.
Given that the non-persistent attributes are calculated at run time by the MBO layer, there might not be a way to include them in this type of integration.

------------------------------
KKunnuthara

Original Message:
Sent: Thu March 03, 2022 08:53 AM
From: Daniel Brame
Subject: Maximo outbound integration via a Data Warehouse

There isn't much detail to go on, so I'll be making a few assumptions in my answer, but I hope this helps.

To get access to non-persistent fields, you'll need to go through the business object layer.  In each object structure, you have the ability to expose non-persistent fields.  At that point, you can use any number of methods to extract the data.  Which one you pick will largely be influenced to how easily accessible the server is.

If you are polling as opposed to pushing, and have access to some kind of middleware, you might consider using REST or WebServices.  If you are looking for updates to be triggered whenever records are updated, you could use Publish Channels if you have a well defined endpoint that can accept the outbound XML.  CSV or IFACE tables are also an option if you can get the object structure to a place where you can mark it as flat and have appropriate access to fetch them.

------------------------------
Daniel Brame
Senior Technical Consultant
Intelligent Technology Solutions
dbrame@webuildits.com
www.webuildits.com
@dbrame/@webuildits

Original Message:
Sent: Thu March 03, 2022 12:08 AM
From: KKunnuthara
Subject: Maximo outbound integration via a Data Warehouse

Hello all,

Has anyone worked on a Maximo outbound integration where a Data Warehousing tool reads from Maximo DB?
How do we send out non-persistent attributes in such a scenario?


Thanks,



------------------------------
KKunnuthara
------------------------------

#AssetandFacilitiesManagement
#Maximo

Thanks @Jason Uppenborn.

Yes, that might be technically feasible,
but currently there is no appetite to 'extract' the logic from Java classes and then move that to an Oracle DB function​.

------------------------------
KKunnuthara
------------------------------

Original Message:
Sent: Fri March 04, 2022 10:48 AM
From: Jason Uppenborn
Subject: Maximo outbound integration via a Data Warehouse

"Given that the non-persistent attributes are calculated at run time by the MBO layer, there might not be a way to include them in this type of integration."

You are right. There is not a way to include Maximo "calculated fields" when the part that does the calculation is not part of the integration.

Instead, you would have to use your platform's tools to define methods for calculating those values. For example, on Oracle, you could write a function that takes a siteid and wonum and returns the total cost for the WO hierarchy and use that in place of the WOGRANDTOTAL.ACT.

------------------------------
Blessings,
Jason Uppenborn
Sr. Technical Maximo Consultant
Cohesive Ontracks

Original Message:
Sent: Thu March 03, 2022 05:41 PM
From: KKunnuthara
Subject: Maximo outbound integration via a Data Warehouse

Thanks very much for that response @Daniel Brame

In this instance, we are not using MIF at all, so Webservices and Publish Channels are not available.

The architecture being proposed here is a pure data fetch (by the Dataware housing tool) directly from Maximo DB.
Given that the non-persistent attributes are calculated at run time by the MBO layer, there might not be a way to include them in this type of integration.

------------------------------
KKunnuthara

Original Message:
Sent: Thu March 03, 2022 08:53 AM
From: Daniel Brame
Subject: Maximo outbound integration via a Data Warehouse

There isn't much detail to go on, so I'll be making a few assumptions in my answer, but I hope this helps.

To get access to non-persistent fields, you'll need to go through the business object layer.  In each object structure, you have the ability to expose non-persistent fields.  At that point, you can use any number of methods to extract the data.  Which one you pick will largely be influenced to how easily accessible the server is.

If you are polling as opposed to pushing, and have access to some kind of middleware, you might consider using REST or WebServices.  If you are looking for updates to be triggered whenever records are updated, you could use Publish Channels if you have a well defined endpoint that can accept the outbound XML.  CSV or IFACE tables are also an option if you can get the object structure to a place where you can mark it as flat and have appropriate access to fetch them.

------------------------------
Daniel Brame
Senior Technical Consultant
Intelligent Technology Solutions
dbrame@webuildits.com
www.webuildits.com
@dbrame/@webuildits

Original Message:
Sent: Thu March 03, 2022 12:08 AM
From: KKunnuthara
Subject: Maximo outbound integration via a Data Warehouse

Hello all,

Has anyone worked on a Maximo outbound integration where a Data Warehousing tool reads from Maximo DB?
How do we send out non-persistent attributes in such a scenario?


Thanks,



------------------------------
KKunnuthara
------------------------------

#AssetandFacilitiesManagement
#Maximo