Skip to main content

Posts

Showing posts with the label CMMS

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...

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...

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 ...

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

Maximo Automation Script Editor

IBM is going to release a new automation script editor for developer(s) which provides  a new and enhanced experience for those who needs editing our automation script in upcoming Maximo feature pack. But we can enable this for our current version of Maximo as well.  Details of installation instruction for this editor has been given in technote . Following are the observation that I have made during the installation as per given documentation- 1. URL to import autoscript.xml will always not be -  http://localhost:7001/maximo/webclient/utility/import.jsp Rather than you should be accessing the port for your Maximo default host. In my case I used -  http://localhost:9080/maximo/webclient/utility/import.jsp 2. After that, once I have uploaded autoscript.xml, I got an error - Import was unsuccessful, please check application server log. In order to fix this issue, you can go to System Properties > Search for the property -  mxe.server.enableCSRFBl...

Power of Maximo Formulas - Build logic w/o Custom Java code or Automation Script

Greetings! Maximo 7.6 has lot of additional capabilities added in Tivoli Automation Engine as compared to older versions of Maximo which aim to allow users to make change in applications for small requirements without actually going to customization route. Automation scripts is one of such tool given for users and technical developers to change the behavior of Maximo in case where functionalities can't be changed only via use of configuration. If we have a requirement to populate some field on basis of other fields , we can easily do that with automation script but in order to do that you still need to have knowledge of Jython or Javascript to write the logic. Maximo formula is one the tool given by IBM which can be used for such business requirements and user can make changes to Maximo logic via configuration without getting into difficulties of coding. Formulas are available from Maximo version 7603. With release of Maximo version 7606, there has been addition of new capabil...

TD Tool Kit - Importing new language in Multilingual Maximo environment

Greetings! +IBM MAXIMO  gives you ability to use multiple languages like Spanish , Portuguese, Chinese , Korean , French etc other than English , if your Maximo environment is global and have users across the globe. Importing a new language in Maximo can be done by TD Tool kit. TD took kit stands for Translation Data Toolkit.  The Translation Data Toolkit is used to translate the Maximo database and handling Multi Language functionality. The TDToolkit is located under the {Maximo_install}\tools\maximo directory.  The process to import new language is a 3 step activity- 1. Take Maximo down by stopping application servers. 2. Export Labels in XLIFF file format 3. Translate the XLIFF file 4. Check for error and import translated XLIFF files. 5. Validate and start Maximo. Export Labels in XLIFF file format -  In Maximo directory , XLIFF files store all the translations for different tags related with a MBO or database table. In order to expor...