You are here: Home / Maximo / Configuration / Install multiple instances of Maximo 7 using WebSphere

Install multiple instances of Maximo 7 using WebSphere

March 17, 2009 By 59 Comments

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.

This text is available for purchase but you need to login or register first. Please Login here.
Filed Under: Configuration, Guides, Maximo, Premium, Tips & Tricks, WebSphere Tagged With: , , , , , , ,
About Chon Neth

I am a Senior Software Engineer at InterPro Solutions, LLC located in Wakefield, MA.

← Older Comments
Newer Comments →
  • janhavi

    oracle version is 10.2.0.3

  • zahradnik

    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.

  • Max

    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?

    • http://interprosoft.com Chon

      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.

  • Max

    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.

  • pakino65

    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

    • http://interprosoft.com Chon

      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.

  • ammadnasim

    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

    • http://interprosoft.com Chon

      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?

  • ammadnasim

    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.

  • sakthimeil86

    Hi,

    Instead of copying the SMP folder to create second instance, shall I directly deploy just maximo.ear from another environment by doing the changes as mentioned in this tutorial to create one more instance. I meant changing the web.xml etc. and in websphere- creating server and configuration. Would it work Chon??

    • http://interprosoft.com Chon

      Yeah it may work but the whole point of making another instance is so that it talks to a different database. I mean I guess you could just modify the Maximo.properties file and build ear then deploy, but I think that would defeat the purpose of a second instance.

  • sakthimeil86

    Thnks Chon. Found it really useful.

    I just experimented to setup single websphere instance for many dev. box. Everything successfully deployed. But when I access the url http://localhost:9081/maxtest, I am getting following message in SystemOut.log

    “[3/15/10 15:32:53:411 IST] 00000031 WebContainer E SRVE0255E: A WebGroup/Virtual Host to handle /maxtest has not been defined.” and getting HTTP:404 Page note found error.

    Any suggestions welcomed.

    • sakthimeil86

      Is it mandatory to create virtual host here.

  • Sakthi

    Hooray!!! It’s finally worked. I used default_host, that’s it didn’t work with port 9080 as my appserver port was 9081.

    Thanks,
    Sakthi

← Older Comments
Newer Comments →

Follow Maximo Times

Subscribe to RSS Contact Us Follow Us Linked In Facebook