Installing Maximo Anywhere 7.5 – System Requirements

In this series, I will be documenting my experiences while installing and configuring Maximo Anywhere 7.5, so this NOT a “how-to” guide but more for me to understand what is involved in getting Maximo Anywhere up and running in its simplest form.  I recommend reading this whole series before attempting to install your own.  I will be documenting each step that I will follow from the Maximo Anywhere installation guide and point out some facts that users need to know as to what is required for it to be installed.  As some of you may know, IBM software installations aren’t as easy as they seem.


Maximo Anywhere is a mobile application platform that is built on top of the IBM Worklight platform.  Worklight is the middleware server component that integrates with Maximo Asset Management via OSLC (Open Services for Lifecycle Collaboration) provider capabilities.  OSLC is an add-on to the Maximo Integration Framework and is required to be deployed in Maximo.   To get a high level picture of the architecture, the mobile devices that have the Worklight client installed communicates with the Worklight server and the Worklight server then communicates with Maximo via the Integration Framework with OSLC capabilities.

Understand that Maximo Anywhere isn’t an “add-on” to Maximo like the previous Maximo Everyplace, but a completely separate system altogether that requires an integration layer like any other system would do if you wanted to integration it with Maximo.

System Requirements

Maximo Anywhere requires Maximo Asset Management and above.  Maximo Integration Framework is also required and is included with Maximo Anywhere version 7.5.  The Maximo Integration Framework includes OSLC object structures, which is required to support Maximo Anywhere.

To install Maximo Anywhere, you must install Oracle Java JDK, Android SDK and the JRE which is required to run the Worklight Studio.  IBM Worklight version 5.0.6 is required to deploy Maximo Anywhere in a production environment.

IBM Worklight Server must be deployed to an application server.  Worklight Server does NOT support Oracle WebLogic.  If you use WebLogic, you will have to install another application server that supports Worklight.

In a production environment, Worklight Server requires a production-grade database.

Note: Worklight Server does NOT support Microsoft SQL Server.

Application servers and databases that are supported by Worklight

  • Application Servers
    • IBM WebSphere Application Server Liberty (included)
    • IBM WebSphere Application Server
    • Apache Tomcat
    • Databases
      • Apache Derby (included)
      • IBM DB2
      • Oracle Database
      • MySQL Database

Note: Apache Derby is included for evaluation purposes only and isn’t production-grade ready.

For mobile devices, Maximo Anywhere apps must be installed and deployed to Android devices (more devices coming soon).  Note that you cannot use the default browser to connect to the Worklight Server.

In a development environment, you can install Maximo Anywhere and Worklight Studio on the same machine.

Note: A production environment typically has two servers, one for Maximo Anywhere and another for Worklight Server.

Maximo Anywhere does install in cluster environments.

Series NavigationInstalling Maximo Anywhere 7.5 – Installation Part 1 >

Did You Know...

As Maximo Experts, we have developed several add-on products for Maximo that mobilize the work force, simplifies assignments, provides ad-hoc reporting capabilities and facilitates the seamless integration of Service Requests into Maximo.

Check out our products by clicking on the following links: EZMaxMobile, EZMaxPlanner and EZMaxRequest.

Find Out More

One thought on “Installing Maximo Anywhere 7.5 – System Requirements

  1. Did you ever figure out how to work past the error: “login failed beccause the information that is required for your user could not be downloaded”?

    I am struggling with the same error message after countless redeployments. Perhaps I should have eyed an OOTB database instead of a dev environment. The logs are of very little assistance, but I am seeing a failure in the Maximo systemout.log when I type in a bad user/pw combo and some OSLC info. However, typing in legitimate credentials just shows a nondescript stack trace in the worklight log and Maximo doesn’t log a thing.

Leave a Reply