Skip to main content

Posts

Calling External Python File/Libraries with "mxe.pylib.path" in IBM Maximo

Greetings, Automation Scripting is a powerful tool in Maximo that can be used to customize the Out Of Box (OOB) behavior of Maximo without the need to deploy any class file which requires downtime of the system. While automation script provides the ability to write code into multiple different languages and their versions like Python, Jython, JavaScript, and Nashhorn, etc. Python/Jython remains the most popular language they use. One of the most powerful features of Python is the availability of reusable libraries available to achieve many tasks. Many times a requirement need an external library to be called Automation Scripting which can be done much more easily with Maximo 7.6.1.2 onwards. In this use case, we have written an action script that will be called when the user presses the Test button on the Work Order application. This automation script contains the logic to call another external file with the name externalPy.py. We create a folder in the application server and place thi
Recent posts

Handle SQL Condition on Workflow Action’s in Maximo via OSLC API

  Maximo’s NextGenREST OSLC API(s) are very powerful but they don’t provide the capability to handle SQL Conditions associated with Actions or Nodes. For example- A manual Input node in the workflow can have multiple actions available and they are to be shown on the basis of SQL Expressions then OSLC API returns all options when making API call w/o evaluating the SQL expression. To handle this, another feature to ca l l automation script using OSLC API can be used to return the response with a flag having true or false information. In the script below, let us assume we have a workflow on the PR object and we need to evaluate SQL conditions associated with a manual input node. From Postman make a GET call for each action: GET <servername:port>/maximo/oslc/script/<scriptname>?ownerid<x>&actionid=<y>&wfactionid=<z> & response of this script shall return true or false based on SQL condition evalauted. load("nashorn:mozilla_compat.js"); im

Playing with Time Zone in Maximo - Time Zone Rules

  IBM Maximo 7.6.0.8 onwards provides a new application – “Time Zone Rules”. This application can be accessed from Administration > Time Zone Rules. In the Time Zone Rules application, users can create rules on different processes on which time zone shall be applied from the process rule. Records will show the local date and time of the user who is accessing the record even if the record was created in a different time zone. Time zone rules can be associated with a process at the system, organization, or site level. Let us see how time zone rules work in Maximo with the example of PM Work Order generation. Following are the steps to be followed in this example- 1.First create a rule for PM Work Order Generation where Time Zone will be picked from the Asset record on the PM. 2.The current user that I am using has Time Zone set to Asia/Kolkata as shown below- 3.Maximo Application Servers are in EST time zones in the US. Now, let’s select an asset and associate Time Zone to America/Los

Maximo API Key - REST/OSLC API Authentication with IdP via SAML

Maximo 7.6.0.9 provides capability to integrate Maximo with Identity Providers (IdP) like Azure AD, Open Connect etc., using SAML. Security Assertion Markup Language (SAML) is an open standard that allows identity providers (IdP) to pass authorization credentials to service providers (SP). As this integration worked properly on Maximo UI application, Browser less connection for Maximo REST, OSLC APIs was not supported and needed direct local active directory connection. Maximo has added this feature of API Key from Maximo 7.6.0.9 which can be used to overcome the unseen limitation. In the earlier versions of Maximo, creation of API for specific user and management of the key was not user friendly and it needed MAXAUTH to be passed to generate the API Key from REST/OSLC API call. With Maximo 7.6.1.2, API Key feature has been improved and now administrators can generate the API keys for users from Maximo UI and revoke them on the go. Once users have integrated Maximo with SAML authentica

Maximo 7.6 with IBM WebSphere Liberty

WebSphere  Liberty (WLP) is a new age Java Enterprise Edition (Java EE) application server that provides support for Microservices, Containers, and Cloud while providing the ability to speed up the development as it has a very low boot-up time. One of the biggest issues with the traditional WebSphere Appl i cation Server is that it takes too much time to start any application. For Maximo, this results in extended downtime during deployment in Production Instance and increased development time for Java Customization. Developers tend to go for a hot deployment approach while developing any customization which sometimes results in problems like changes not loading properly or other caching issues. Maximo 7.6 running on IBM WebSphere Liberty profile helps to overcome these issues. This also gives the ability to run local Maximo instance for developers on their computer. For WebSphere liberty, the Maximo workload is broken into multiple different applications which provides the ability for

Docker Commands for Maximo Consultants

Containers are becoming popular day by day and provide great flexibility of running the instance locally and play around for developers. For Maximo developers, it is even more relevant as there is no need to coordinate with others while enabling admin mode, or restarting the server, etc for any developmental need. Docker for Maximo can be used by Developers to run their isolated local instance. A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime system tools, system libraries, and settings. While working with docker, the following are some of the frequently used commands which every Maximo consultant should know. Happy Dockerizing! Commands Purpose docker --version Version of Docker installed on your machine docker info Details of Docker installed on your machine docker images List of images on your machine docker images -a List of images with creation time, size and all other details

OSLC (NextGenRest) API Authentication in IBM Maximo

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