Technical Blog Post
Installing Maximo 7.6 to Oracle WebLogic 12c: Introduction
Welcome to another of my multi-parters! This one will be somewhat complex. Not Maximo installation, but, of course, the order of installation.
There are five parts:
Part 1. WebLogic installation done. Part 1.5 Install Maximo Asset Management 7.6.0 done.
Part 2. Configure WebLogic
Part 3. Create JMS and email listener queues
Part 4. Configure Maximo Asset Management 7.6.0
Part 5. Deploy the Maximo ear files to WebLogic
Parts 1 and 1.5 are below, nice and short. Since IBM includes WebSphere 184.108.40.206 with Maximo 7.6, the Configuration Tool configures it for Maximo, and you can also create WebSphere clusters with the Configuration Tool. The Configuration Tool does not handle WebLogic.
Therefore, the focus of these blog posts will be configuring WebLogic and deploying Maximo 7.6. I'm made a couple of assumptions before preparing the process:
- You will be creating a Maximo domain.
- You will install Maximo to the Administration Server in that domain.
If you already have a WebLogic environment, you will likely not follow those steps. For example, you wouldn't install Maximo to your Admin server, but instead create a managed server or cluster. The key parts for you will be creating JMS queues and configuring Maximo.
Part 1. Install Oracle WebLogic 12c
Before configuring WebLogic for Maximo, install WebLogic 12c using the latest version of Oracle JDK 1.7 (1.7.0_80). Do not install JDK 1.8, which is not supported for use with Maximo Asset Management as of version 220.127.116.11.
Part 1.5. Install Maximo Asset Management 7.6.0
Using the Launchpad and IBM Installation Manager, install Maximo 7.6. Do not install WebSphere Application Server. When complete, do not launch the Configuration Tool.
Part 2 starts tomorrow. Stay tuned!