Categories
How to enable SSL for OAS?
Hello, does any one know how to implement/enable SSL for OAS on windows platform? we currently use http but need to implement https instead.
Thanks,
Answers
-
@User_27DEY - Please refer the below document for steps and details on how to enabled SSL in OAS.OBIEE 12c/OAS: How To Configure SSL Including Examples (Doc ID 2188982.1)
0 -
Thank you very much! After enable SSO following the note, we are not able to bring up any of the system components. NO log, since it never starts. any idea where to check? this is OAS 12.2.1.4 on windows. might be that is a bug since most people use unix. Appreciate any help! Thanks.
0 -
Hi,
Are you using OBIEE 12.2.1.4 or OAS (what version?) ?
If using OBIEE, what FMW version are you using? 12.2.1.3 or 12.2.1.4?
0 -
Thanks! Both Weblogic and OAS are 12.2.1.4.0, but on windows
0 -
Ok, so you are on OBIEE 12.2.1.4 (it's a quite old version now, OAS came after that and we are now at the 5th edition of OAS: any particular reason for installing OBIEE instead of OAS?).
The support document referenced should still apply. Windows or Linux shouldn't have an impact, also because SSL is enabled at the WebLogic/FMW level, and that one is around for many years (with many Windows users).
Even when not starting, there are logs, because the system tries to start nodemanager and that one has logs already. Once nodemanager is started, it tries to start the weblogic AdminServer etc. All these pieces have logs.
If you did follow all the steps of the support document, you shouldn't have issues. If it doesn't start anymore, it's possible your issue is already at the nodemanager level.
But you should look into those logs (or even just run the start command and see the output you get directly there). Without any log, it just isn't possible to say much.
0 -
Thanks! Yes, we have issues with nodemanager, get the error "javax.net.ssl.SSLHandshakeException"
but we should be able to start up all the services manually one by one without needing nodemanager,
we cannot start with start.cmd command, we started weblogic and managed server using individual commands. and try to start system components using oem console, but not able to. thanks
0 -
If NodeManager doesn't start, you better try to fix that one first, because it means there are issues with your SSL config. Sure you should be able to start things without NodeManager, but you are exposed to even more issues all around.
Did you configure nodemanager.properties correctly? Maybe worth trying both Windows and Linux paths for the keystore, because it could depends on what process read it what kind of path it does understand (I'm trying to remember what I put there inside last time I configures SSL on Windows, but it was a while ago…).
0 -
Thanks. we do not have to enable ssl for nodemanager correct? somehow, one of the lines is missing from nodemanager.properties after ran the ssl enable script, the last line below is gone from the nodemanager.propertoes.
also when try to start the system components . it can not connect to nodemanger . thanks again!
0 -
The only different is, we only did step #1, #2, and #7. also, we use the same for identity keystore and trust keystore.
Do you know if the command : ssl.cmd internalssl true can be re-run??
thanks
0 -
If I understand you correctly you want to enable full SSL, also between internal components?
It's a while I didn't run that, lately I stick to external SSL only, leaving the internal communication between components untouched.
0
