2 of 2 people found this helpful
There are a lot of schools of thought behind that, here's some info to help you make the best choice!
For what it is worth, we use one EM.
Using a Single Enterprise Manager
* Simplifies promotion between environments
* Simplifies end user administration
* Provides for a way to view "all environments" in a single pain of glass
Using Two or More Enterprise Managers
* Provides a way to wall off certain environments, may be appropriate in some cases.
* Promotion will need to utilize CLI tools (or API) to bridge between the two EM's
* Let's you more easily test upgrades/etc by being able to do it on one stack before the other.
That's just a few considerations, I'm sure others will chime in with more.
Thank you Robert! Robert if I may ask how is your company set up? 2 or 1 EM?
1 of 1 people found this helpful
We have separate EM for TEST and PROD, it is better to have separate EM for TEST and PROD as it allows you to test and analyze that impact before implementing anything to PROD related to EM like EM parameters, patches, fix pack etc.
Also it helps you to identify the challenges in case of EM upgrade to new version.
I agree with Ilyas, We have separate EM for each environments, This will protect production environment, Though having one EM will allow us to promote from Test to PROD using WCM, I would prefer separate environment, This will allow tester to perform various test cases without impacting Production environment, also you can test Fix pack\patch releases before promoting to PROD
We (CTM admins) have the luxery of having a Sandbox environment with 1 EM, 1 CTM and few agents where we can test upgrades and such.
All the other CTM's (Prod, QA,Test, Dev.and the mainframes) are connected to one Prod EM, which gives you one view, and all the possibilities of migrating jobs, global conditions, easier admin/use, remote force job, etc.
How do you migrate your job from TEST to PROD with two Enterprise Managers? Is it complicated?
Thank you for your reply, what is WCM?
You can use export/import utility, CLI or API, but I think easiest is in the GUI to export your workspace, and import it in the other EM.
Workload Change Manager
Export to xml from TEST & import to Prod. Make environment changes as required.
Yes, I always had a single EM but was then obliged to go to 3 (Dev, UA & Prod). It complicates life somewhat, getting conditions to jump between systems is not easy. The upside is that you can roll out system upgrades in Dev without causing wider issues.