In this post, I will talk about the coexisting OIA and OIA side by side and some of the options that I tried and it's eventual outcome.
Option 1
Deploy OIA on the same OIM managed server. Does not work.
Deploy OIA on the same OIM managed server. Does not work.
Option 2
Create a separate managed server and deploy OIA. That did not work either
Create a separate managed server and deploy OIA. That did not work either
Option 3
Create a new domain within the same middleware home and deploy OIA in a server there. Unfortunately that also did not work.
Create a new domain within the same middleware home and deploy OIA in a server there. Unfortunately that also did not work.
Option 4
Deploy OIA on a fresh weblogic middleware home. Finally it worked.
Deploy OIA on a fresh weblogic middleware home. Finally it worked.
All along it kept complaining about a context loader and some other issues which are difficult to debug.
To conclude OIA and OIM in the same domain or same middleware home does not work.
There were issues that arise during integration, firstly with option 4 you will have to establish domain level trust between the 2 domains to fix the authentication issues.
Other fix is to set prefer-web-inf-classes to true in weblogic.xml in WEB-INF folder. Well this is not an integration per se but a general fix to load application libraries first and then the app server libraries. More to do with the class loading issue.
There were issues that arise during integration, firstly with option 4 you will have to establish domain level trust between the 2 domains to fix the authentication issues.
Other fix is to set prefer-web-inf-classes to true in weblogic.xml in WEB-INF folder. Well this is not an integration per se but a general fix to load application libraries first and then the app server libraries. More to do with the class loading issue.
