Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Creating user friendly OBIEE URL and SSL certificates

Received Response
12
Views
4
Comments
User_YMTQZ
User_YMTQZ Rank 1 - Community Starter
edited Aug 13, 2024 5:24PM in Oracle Analytics Cloud and Server

Hi Team,

We have  a bit  complex unreadable  OBIEE url (for example http://s61dc4vl210.USHSSRND4.SAPVIS.NET:19502/analytics )in our environment

and we are planning to move to simpler DNS web url  like  company-obiee-dev:19502/analytics with SSL  certificate .

Please suggest best practice and share related resource/documents to refer

Answers

  • Gianni Ceresa
    Gianni Ceresa Mod

    What will be in charge of making the URL "user friendly" ?

    Are you going to install OBIEE on servers having nicer hostnames instead of more "random" ones? Are you going to have a proxy in front of OBIEE to translate the random one into a nicer one?

    The documentation covers how to setup SSL in OBIEE, the url is generally the hostname where OBIEE is installed by default.

    If you go for the proxy solution OBIEE isn't even going to be aware of anything and therefore you simply need to follow the doc of the proxy you choose.

    Not sure what best practice you imagine, the official documentation cover all the needed aspects. How to generate a nicer domain and the related SSL you have to check with your sys admins as that is your own internal cooking, not something which is standard or OBIEE related.

  • User_YMTQZ
    User_YMTQZ Rank 1 - Community Starter

    Thanks for your response. On, now I got an idea. We have to host dns server/proxy for the server itself where OBIEE is installed.

  • Gianni Ceresa
    Gianni Ceresa Mod

    The proxy can be on the OBIEE server itself.

    For example OAC (at least the "Classic" one) came with a proxy setup on the OBIEE server itself doing the redirect and the SSL offloading: so you connect over SSL till the proxy, and the traffic between the proxy and OBIEE isn't SSL as it's on the same server and therefore it's "local" traffic. This can also make the management of SSL easier as it's maybe easier to setup a SSL in a proxy (OAC used Nginx, Apache HTTP Server can do the same) than OBIEE.

    For example something a client I worked with had was Apache HTTP Server installed on the OBIEE server and allowed to more easily move to a different server and doing upgrades as it was just a change in the proxy to get everybody sent to a different OBIEE. It also made it simpler to setup temporary pages when the service was down for maintenance.

    Taking your original request a proxy could allow you to more easily move your "company-obiee-dev" around. Today your DEV is s61dc4vl210.USHSSRND4.SAPVIS.NET, tomorrow you installed a new OBIEE and after some testing you want to get rid of the old and use the new one instead. You change the proxy to point to something-new-2132131.USHSSRND4.SAPVIS.NET and you already have everybody reaching the new server instead of the old.

    It depends a lot on your own corporate rules for these things and also how you plan to manage upgrades and updates to OBIEE etc.

  • Gianni Ceresa
    Gianni Ceresa Mod

    An added point for the proxy option: you can get rid of the port as well. No need to have it in the URL as you could use the default 443 with SSL.

    And the proxy could also forward / to /analytics by default if you forget it. So your nicer url would only be: https://company-obiee-dev