Experts,
I have two separate installations of ODI 12c using a WebLogic ODI agent, one per host, which is working fine.
However, I am trying to understand how in our production environment we will be able to have two separate WebLogic tiers, running in active/standby mode (so only one will be up at a time) with the ODI managed server domain pointing to a single shared ODI Master Repository database. The production environment doesn't need the full resilience that Coherence offers, but we do have a hardware clustered database and so would like to have a single XXX_ODI_REPO repository schema that can utilise which ever agent is up when scheduling or executing components - so not needing to startup and catch-up the data inside the standby ODI repository db once it become active.
After updating one of the ODI domains using the wizard to modify the existing repository credentials to use a different pre-existing ODI repository, I am getting errors when the managed server starts as the ODI Master Repository credentials fail to get retrieved - i get a 'cryptographic' error in the log.
Then I tried to create a new domain but pointed the settings at the existing repository database used by another ODI installation. This time the wizard failed as it did not like to share the xxx_OPSS schema.
There are 6 schemas installed in the database as part of the enterprise mode install of ODI. If we have two separate installations of WebLogic do we need to have separate variants of these schemas - such as an xxx_OPSS schema installed in the same repository database used by each of the WebLogic installations? Or can this be shared? Perhaps I need separate xxx_IAU, _IAU_APPEND, _IAU_VIEWER and _STB schemas per WebLogic install but can share the xxx_ODI_REPO schema?
Is there any guidance you can provide that will let me reach the end goal of having:
2 x ODI domain installations on two separate servers running weblogic with the agent on each domain pointing to the same ODI repository database.
allowing me to create two physical agents in the topology navigator which I can point at the current active weblogic server.
and allowing me in the event of a weblogic physical server failure to start up the standby weblogic server and configure the topology to use the new active agent.
cheers,
John