Top 5 UNX Roadblocks and How to Overcome Them

I am writing this blog based on my experience using BOC and its connectivity with a Unx.

#1 I am unable to see the “200” confirmation message.


This is a notorious error and it comes up pretty frequently for most new users of BO Cloud. It can be frustrating but it’s actually pretty simple. The “200” message is not as flamboyant as you might think.
 
To resolve this, you need to make sure of the following:
    1) Make sure your tomcat service is running! Hold windows button + R, then type services.msc, locate Apache, then confirm that the service is started


    2) You haven’t deployed the BO Cloud Agent correctly. Go to tomcat folder then webapps folder, and look for the BO agent folder. OR go to http://[localhost]:[port]/manager/html and make sure BO Cloud Agent is running. I like to deploy by simply coping the .war file and pasting it into the webapps folder. It works every time.

    3) Your tomcat-users file is not updated correctly. I will save you the headache. The lines below work so just copy it and you should be up and running. Make sure to open the file with administrative rights in order to edit and save.

    4) Finally, before typing the magical url “[localhost]:[port]/C4A_AGENT/service/api/epm/bw” into your browser, make sure you have fiddler installed! (or any browser extensions). Make sure fiddler is running, then visit the URL, enter your credentials, then the “200” message should show up in fiddler like the image shown here.

#2 I have configured tomcat correctly and received the “200” message; I think my HCC is configured incorrectly and therefore the unx connection is not working.


Assuming you have already opened a ticket with SAP Ops team to open an HCC account, you need to make sure of three things:
    1) Make sure that /C4A_Agent/ is set to path and all sub-paths.

    2) The virtual host and port in HCC matches the one in both the Administration screen and connection screen in BOC.
    3) The username and password in the administration screen in BOC matches the one set in tomcat-users file.

#3 I have configured both HCC and Tomcat correctly, but now I am receiving an Error that says “Make sure BO Cloud Agent is Deployed correctly” and wouldn’t let me create a connection, what should I do?

This issue had taken me a while to figure out but the resolution is easy and silly. Make sure that you are creating the connection in the BOC tenant that your HCC account is designated to. For example, if your BOC runs on tenant 005, and you were assigned an HCC account for that tenant, then you cannot use the same HCC account for tenant, say, 008. So, only 1 HCC account (S-User) can be assigned to only 1 tenant.

#4 I have finally managed to create a connection but now I am receiving an error when I query the Universe.

This is another sticky error that takes some time to figure out, yet the solution is simple – again. You need to be using a BI platform account that has administrative rights in order to avoid receiving errors when querying a UNX. As of now, it is unclear what specific rights are needed to avoid errors, but having administrative rights resolves the issue.

#5 A new version of BO Cloud agent is out. Please update your agent.

I dislike receiving this error because it interrupts my workflow but the message is self-describable. You need to go to support.sap.com, download the new agent .war file, remove/undeploy the old agent, and deploy the new one in tomcat.

BONUS!
 
#6 My BOC cannot locate my BI platform, why?

You need to be using your BO Cloud inside the local network where your BI platform sits. So if your BI platform is hosted in the cloud, then you need to remotely access that virtual machine and do the configuration there. Once the connection is setup, you can acquire data from your BI platform from any internet connection.