Maximo Tips & Tricks
Babson College - Utilizes EZDash
Babson College, one of the leading business colleges in the world, has chosen InterPro Solutions’ EZDash module for a real-time and easy visualization of their maintenance productivity and energy consumption data. This customizable dashboard runs 24 hours a day on a 46” wide screen monitor in the main office, so ...
EZMaxMobile - Maximo Mobile Integration
Real Time Maximo Mobile Connectivity InterPro Solutions’ has developed a mobile integration framework that provides real time connectivity to Maximo via WiFi or 3G connectivity. Devices such as BlackBerry, iPhone, Android, MC 50/70s, etc. are now capable of logging into and communicating with Maximo on a real time basis. No longer ...
WebAssign - Workorder Assignment & Scheduling
This web-based add-on to IBM Maximo application provides supervisors and managers with the ability to assign work orders to specific staff as well as track the status of those work orders. Work orders can be assigned on an individual basis or by groups - it as easy as a "point ...
EZDash - Custom Maximo Dashboard
A web based dashboard that seamlessly interacts with your Maximo maintenance management system. EZDash provides real time interactive graphs and charts for use by staff to monitor and manage work processes, inventory, labor hours, PM schedules, etc. EZDash is easily configured to display a wide range of key performance metrics ...
WebMaint - Customer Service Request Module
This web-based add-on to IBM’s Maximo application system provides customers with a simple way to enter service requests and view their previously entered service tickets. Customers can enter requests without having to be a registered Maximo user, therefore eliminating the need for a user to register or be registered in ...Install multiple instances of Maximo 7 using WebSphere
The previous versions of Maximo all came with an installation guide that helped you install a Maximo application server for production purposes and also for testing or development purposes. In most cases, this is how most of our applications are setup. Unfortunately, Maximo 7 does not come with any demo data or even an installation guide for installing a MaxTest instance. The Maximo install guide does show you how to install one instance on one server, but some of you may want to install a MaxTest application server as well as your MaxProd application server. This guide will show you just how to add a MaxTest Maximo application using WebSphere. It also assumes that you have successfully completed the installation for your Maximo 7 production application.
Step 1:
Create a backup copy of your Maximo production database. I will assume most of you know how to do that, but if you don’t, you can find a guide for backing up a SQL Server database here or an Oracle database here. After you have created a backup, restore the database and name it MaxTest.
...
For more, Please login or register for FREE!
Tags: Maximo, Maximo 7, WebSphere, Multiple Instance
oracle version is 10.2.0.3
Create clean instance with the same name. After instance is created you run maximo\tools\maximo\en\createmaximoes.sql script which creates maximo user. Then you have to run maxinst to populate your DB maximo schema with new maximo data. Then you will be able to connect again to Maximo appl. Restart of application is of course necessary.
I have followed the instructions, synchronized the nodes and generated and propogated the webserver plugins. Both MXtest and Maxtest are running. When I go to the browser and type the url I get the HTTP 500 internal error. Maximo login page does not display. Is there anything that I am missing? Do I need to define a webserver2?
What does your log files say for MXTest? It might be started in WebSphere, but the log have some info on why it didn’t actually start successfully.
Thanks Chon,
Tried looking at the log files but it is difficult to figure out what is actually going on.
I will try a clean install and see what happens.
hi at all,
i have a question about this procedure. We need to know if implementing this solution could be appear performances problmes. this because we’ll build twoo aplication server on the same Phisical Server, and actually this is a Production system. About this, someone could indicate us, if this configuration can be installed on twoo different server, in order to prevent perfomance problems.
Many tks Pasquale
This is not recommended on a production server. Only one instance should be installed on a physical production server. This is more for development and test environments.
CHON,
I am struggling to move maximo 7.1 from one environment to another one I have copied the application folder from source to target modified props file, database restored sucessfully, ear built sucessfull its just i cant get the steps and list of files i need to change after migrating in MAM 7.
i am getting following error when deploying
the ear files in weblogic orginally at source running on websphere.
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(mboejb.jar) Unable to deploy EJB: JMSContQueueProcessor-2 from mboejb.jar: [EJB:011113]Error: The Message Driven Bean ‘JMSContQueueProcessor-2(Application: maxuat, EJBComponent: mboejb.jar)’, does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
Substituted for missing class [EJB - 11113]Error: The Message Driven Bean ‘JMSContQueueProcessor-2(Application: maxuat, EJBComponent: mboejb.jar)’, does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
kinldy reply
Thanks
Amad
I think there are too many variables when changing from WebSphere to WebLogic. I have not done it myself and not really sure what you can do. When I migrate from one system to another, I usually deploy ears on the same web application and I only move the database. Does anyone else have any suggestions?
well Finally i resolved myself steps are following
Manual Migration Process for Maximo 7.1
Step 1
Close the database, application server and any other related application or files from the target system.( If possible)
Step 2
Copy the the folder named maximo ( folder containing the whole maximo Application) from the source system to the target system.
Step 3
Restore the database from the backup taken earlier from the source system and restore it by either making a new database or replace an exististing maximo database.
Step 4
Test the integrity of the database.
Step 5
copy or replace the maximo source folder into the traget drive.
Step 6
Make appropriate changes to maximo .props file like localhost name, database name, instance, id and password.
Additional files to look on for appropriate changes
Web.xml
Doclinks. properties
other custom props file
Ejb-jar.xml
Step 7
Build the ear file and redoply the solution in weblogic or Websphere.