Skip to main content

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 Application 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 users to plug and play the applications as per their requirement and architecture. Following are the different workloads and their respective purposes -


Application

Purpose

maximo-ui

User Interface Application

maximo-x

Work Center Application

maximo cron

Maximo Cron Application

maximo api

REST/OSLC API

maximo jms consumer

JMS Consumer for Queue

maximo mea

MEA for Integration Framework

maximo report

Report BROS Configuration

How to run Maximo on WebSphere Liberty (WLP):

To run Maximo on WLP, the following steps need to be followed —

  1. Download WLP from the IBM website.
  2. Install WLP into your local machine or any server as per your requirement. Installation of WLP is really simple in which you need to extract the folder of zip file downloaded in Step#1.

3. Now go to the SMP folder in your admin workstation and access the path C:\IBM\SMP\maximo\deployment where you will be able to see folder was-liberty-default. This folder contains all the files required to build the different applications as per workload requirements.

Image for post

4. Now open Power shell or Command Prompt and access path C:\IBM\SMP\maximo\deployment\was-liberty-default

5. Once done, run file buildmaximoui-war.cmd to build maximo-ui application war. There are other bat files also available for other applications. Generated War files for applications will be available inside C:\IBM\SMP\maximo\deployment\was-liberty-default\deployment folder in respective application subfolders.

Image for post

6. Go to Command Prompt while running it as administrator. Access path <Dir>:\wlp\bin and execute the command to create maximo ui server —

server create maximo-ui-server

Image for post

7. Now go to the WLP folder in your local machine or server and copy the content of C:\IBM\SMP\maximo\deployment\was-liberty-default\deployment\maximo-ui\maximo-ui-server into <Dir>:\wlp\usr\servers\maximo-ui-server folder of local machine.

8. Once the content is copied, run the following command from the command prompt to install maximo-ui application —

installUtility install maximo-ui-server

Image for post

9. Now start the maximo ui server by executing the following command-

server start maximo-ui-server

Image for post

This command will start the Maximo UI application which can be accessed by URL: http://localhost:9080/maximo

To install other applications, similar steps need to be performed step#3 till step#9.

Hope this post helps Maximo Developers and Customers to configure Maximo 7.6 on Websphere Liberty and take advantage of lightweight WSL.

Cheers!

Labels:

Comments

Post a Comment

Popular posts from this blog

Maximo OSLC Integration with External System- Get data in JSON format

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 provider provides a link
Post a Comment
Read more

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
4 comments
Read more

Call publish channel w/o enabling Event Listener in Maximo

Greetings! Generally if we have to send data to external system via MIF, we create Publish Channel and enable Event Listener on publish channel. Once event listener is enabled, Maximo listens for event and send data to end point via publish channel for each Save of related MBO . But t here are many scenarios where we need to send data to external system using publish channel on specific event and not for every save. In order  to send to external system on specific event, for example - sent data to Ariba when PO status in Maximo is changed to APPR, we can use automation script or java code to call publish channel on the go. Below code can be used in automation script - server = MXServer.getMXServer() userInfo = mbo.getUserInfo() whereClause = <CONDITION> server.lookup("MIC").exportData("<Publish Channel Name>", "<External System Name>", whereClause, userInfo, 1000) Via Java class - MXServer server = MXServer.getMXServer();
Post a Comment
Read more