Essential Viewer ReportService could not be found at this UR

Post Reply
kdprybil
Posts: 3
Joined: 11 Jun 2013, 16:06

I just recently went through the installation Essential Architecture Manager in standalone mode.

I have gone through all prereqs and am using local Tomcat 6.x.

I can hit http://localhost:8080/essential_viewer through browser. However, when I try to publish repository, I get error message 'Failed to send snapshot to the Report Service: Essential View ReportService could not be found at this URL.'
The url I am trying to use is:
http://localhost:8080/essential_viewer/reportService

This url in a browser takes me to Essential Viewer Error Report page with unrecognizable URL requested.

I will attach images of errors.

Thanks,

Kirk
You do not have the required permissions to view the files attached to this post.
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

Hi Kirk,

I'm going to start with things that you've probably already thought of. ;-)

The Essential Viewer environment needs to be running for the Architecture Reporting Tab to be able to send the repository snapshot to it.
Make sure that Viewer is running on your local machine (as you're using localhost as the hostname) before you try to publish.

The Viewer and the service to receive the repository snapshot from Protege run on different URLs, hence the http://localhost:8080/essential_viewer/reportService does not succeed when you navigate there using your browser.

Incidentally, the next version of the reporting tab for Protege will unify the URLs (from a user perspective) between the browser and the reporting tab, so you can use the same URL for your selected Viewer environment in both.

You get a response from http://localhost:8080/essential_viewer/reportService - which is the Unrecognised URL requested page that aims to inform you that you've got the URL (for accessing Essential Viewer) incorrect and providing a link to where you should be going.

As long as your Protege environment is running on the same host (localhost) as your Tomcat Essential Viewer environment, and Tomcat is running, you should be able to use the URL that you show to publish to Viewer.

If, however, your Protege is running on a different host to where the Viewer is, then you need to replace the 'localhost' in the Report Service URL with the host of the server that is hosting Viewer.

Jonathan
Essential Project Team
kdprybil
Posts: 3
Joined: 11 Jun 2013, 16:06

I checked all that you have listed. And everything looks right. I am able to hit viewer on localhost via browser. However, I am still getting the same error on publish.

I switched to using the ip of the machine. This fails in a different way. It actually hangs on Sending Repository snapshot. The error in the backing terminal window is a java.lang.OutOfMemoryError: GC overhead limit... This the same error I get when trying to publish to central Tomcat instance as well.

I am running Windows 7 with McAfee.

Other ideas or trouble shooting tasks?

Thanks,

Kirk
kdprybil
Posts: 3
Joined: 11 Jun 2013, 16:06

Ok. I have update. I am able to see published changes in viewer if I use IP address. However, from a status perspective in Protege, it still is spinning in Sending..

Does that it need a talk back that might be blocked? The data looks like it made it over.
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

There is no talk-back required. The tab only waits for an HTTP success message from the server.

The Out of memory error is likely to be causing the problem.
If you're seeing it in the Protege console window, this is in your Protege client.

To resolve this, see this documentation from the Protege Wiki.

Set the heap size max to something like 1500MB or 2000MB and restart Protege.

Jonathan
Essential Project Team
Post Reply