Engine configuration 12.2.6 and 12.2.4
(Doc ID 2239971.1)
Last updated on AUGUST 08, 2018
Applies to:Oracle Demantra Demand Management - Version 18.104.22.168 and later
Information in this document applies to any platform.
Customer is on 12.2.4 and is migrating to 12.2.6
They following questions:
Customer current Configuration
In 22.214.171.124, for Non Prod (64-bit Engine on Linux) have a single Engine Manager host and 7 child engine hosts/ blades that are shared across 4 to 5 DEV and TEST instances.
For Production have a separate Engine Manager host but use the same 7 child engine hosts/ blades mentioned above for production as well.
So, in total have
1 engine manager host for all DEV/TEST instances
1 engine manager host for PROD instances
7 child engine hosts/ blades that are shared between DEV/TEST and PROD (mapped in the settings.xml)
1: Sharing one engine for DEV and TEST instances
As customer does not need to run Engine in 2 or more DEV or TEST instances simultaneously so they share the Engine Manager and child blades across instances. Whenever they need to run the engine in a DEV/ TEST instance they just change the DataSource setup on WebLogic side to point the TEST engine to specific instance. Thus by changing the Data Source they re-point the TEST engine from one DEV/TEST instance to another based on need.
2: Sharing same child engine hosts between PROD and DEV/TEST instances
Before Production engine run they ensure that DEV/TEST engine is not running/ scheduled and then Production engine batch run is triggered. They rarely use simulation mode. This way same child hosts are shared during engine run in PROD and DEV/TEST instances but never used simultaneously for 2 different instances thereby avoiding any conflict.
Per the 126.96.36.199 engine deployment guide, if they want to follow the same approaches going forward then before engine run in any instance they need to:
1. Run Setup.sh in each engine host (parent and child) to register/ setup the engine before each run. For production Engine Manager it can be done only once since it is not re-pointed to different instances. But for DEV/TEST Engine manager and child hosts it must be done every time engine is re-point and/ or before engine run to make sure each host is pointing to the correct instance DB
2. Run EngineStarter.sh on each host before running the engine
Please confirm above steps
Can they use the same hosts (parent and child) for setting up 188.8.131.52 engine as well as keep the 184.108.40.206 engine configurations so that they can run both the engines for 220.127.116.11 and 18.104.22.168 instances respectively using same hosts, but not simultaneously, and without creating any conflict between the 2 engine setups?
If that is possible, then what needs to be done differently? Can they create another directory on Linux similar to Engine Root directory they have in 22.214.171.124 and extract the Oracle_Demantra_Linux64_Engine.tar.gz file under the new directory?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document