Maximo Quest

From IBM Maximo version 7.6.0.2 onwards, IBM has provided a new REST APIs. The new REST APIs for Maximo is a rewrite of the existing REST APIs that were released after Maximo Asset Management version 7.1. These new APIs are also known as REST/JSON APIs or OSLC APIs and provide multiple benefits.  Following post talks about different authentication parameters which we require to login and getting the response from OSLC APIs Please go to URL to check out full details about this blog post - https://medium.com/@sharma.pras06/oslc-nextgenrest-api-authentication-in-ibm-maximo-f15588619120

Greetings! Maximo Integration Framework supports the sharing of data between Maximo Asset Management and external systems based in many different ways. The most common is to replicate data between the systems. However a new feature, Federated Resource, allows the sharing of external system data with Maximo without the need to replicate the data into Maximo. With Federated Resource integration,you can associate Maximo Asset Management objects with data from an external system, and persist the data outside of the Maximo Asset Management database. To do this, the external data must be exposed through a JSON REST API in order for the data to be available as a Maximo MBO. For example - if user need Location related data like temparature, Lat or Long etc in Maximo, we can get this data from different available API. For this example I have used OpenWeatherMap api. You need to have your appid and by this you can fetch location related weather and other information. http://api.openweatherm...

Greetings! If you have noticed recent version of Maximo, couple new application in Integration module has been added which are OSLC Resources and OSLC Provider.These modules gives us ability to integrate with external system in JSON. OSLC is an open community that creates specifications for the integration of products and/or tools.  IBM is a leading contributor to this community and many software products within the IBM Software Group are implementing OSLC in order to enable cross-product integrations. An OSLC integration requires 2 players-  1. OSLC Consumer application 2. OSLC Provider application.   An OSLC provider application makes containers of associated resources(data) available for integration through service providers. Consumer applications then use these service providers to query resources and to create, update, and delete resource data.  The consumer application sends a query to the service provider for resource data. The service p...