This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
A lot of companies now use VM's which are just big servers chopped up into
many smaller ones. The real concern is your production system and how robust
it is verses how critical maximo is to the organisation. Production critical
DB servers often have a mirror with automatic fail over.
In truth the standard design of a Maximo cluster isn't that robust and has
single points of failure. To balance that I've been on many sites with this
design and large user bases and have never seen any big problems.
In short what I'm trying to say is make sure production is well designed
distributed and robust and the rest i.e. Dev / Test / UAT does it matter if
one or the other or even all are out for a day ?
Rgds Ian
-------Original Message-------
From: maximal@wanko.com [MAXIMO]
Date: 19/05/2016 14:35:30
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Multiple Production Instances on a Single Server
---In MAXIMO@yahoogroups.com, <mlevinson@ledgesoft.com> wrote :
We are hosting multiple production instances of Maximo for different clients
I am being asked about putting multiple app servers on a single server as
well as multiple databases on a single database server to reduce our overall
footprint.
What's the likelihood of the single server going down? What's the plan if it
does go down?
Same for the databases.
My personal preference is three environments: dev, test, production. Test is
identical to production except for data. Each environment is designed for
best uptime probability: OS selection, hardware, clustering all factor into
this. If something catastrophic does happen to production, data can be moved
to test and DNS can be updated to point there, and your users will never
know.
Real story: a system I designed in 2003 had a production failure. It was a
combination of AIX and Windows, and the Windows piece failed (what a shock).
I was offered stupid consultant money to fix it. I told them to just import
the prod data to test, as they were identically configured. Then go fix
production if you like. This is why I'm a terrible consultant (but a
terrific employee). They saved lots of dollars by using what they already
had.
If you have VM environments, it's even better because if you take snapshots
or backups regularly, you are basically immune to hardware failures. What
you lose in speed you gain in persistence.
Having said all that, multiple app servers on the same machine might not be
wise. I'm thinking that Websphere, for example, has the concept of cells and
nodes for a reason. I would suspect a good Websphere architect could help
you host many Maximo clients on a single Websphere installation using
multiple cells. I mean, who wants to log into n-consoles to manage things
when you can log into one?
That's my thinking.
-C
Thank you all for your input it is much appreciated.
I find databases are very disk intensive. So, if you plan on putting multiple databases on a single server, make sure it is configured correctly. SSD is preferred, but if you're using mechanical drives, you'll have to use separate disks for redo log files, rollback segments, and temporary space. This is also why I don't like putting database servers on VMs unless they are guaranteed some SLA with cpu and disk.