Accessing multiple enviornment (TEST, DEV ) using single installation of ODI Studio
(Doc ID 2143033.1)
Last updated on OCTOBER 22, 2018
Applies to:Business Intelligence Applications Consumer - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
OBIA 220.127.116.11.0 version, DataWarehouse
Customer is having multiple environments ( DEV and TEST ) and they wanted to access both the envrionment using single installation of ODI Studio.
We have a wallet.sso and jsp-config.xml for EACH of the environment (meaning 2 wallets and 2 jsp-configs). When we want to make a connection to DEV we have to switch the wallet and jsp-config.xml and to TEST vice versa so that it will authenticate.
Is there a way to combine these wallets and jsp configs so that we do not have to switch them back and forth?
We have also been told to use different instances of ODI STUDIO for different environments. Meaning have 1 ODI Studio for dev, 1 ODI Studio for test, etc... this does not seem reasonable, since ODI Studio supports the ability to connect to different master/work repostiory, but the wallet.sso is not allowing it (unless it is swapped).
how can we connect to multiple instances without moving wallet.sso all the time?
In our situation if we do use 2 instances of ODI Stuido, what is the best method of making sure the BIN folders are separated? I have seen in the past the use of 2 instances of ODI Studio and they actually installed them on different drives, because both instances where still trying to use the same BIN path to get wallet.sso. Is there any documentation of the cloning process you mentioned?
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