Protegé upload to Viewer on Azure App Service fails to connect

[HBuchner]

Hi John,

i deployed the open source viewer to a Tomcat running on Microsoft Azure App Services and am able to connect to it via Webbrowser. the URL is something like:
<b>https://xxxxxx.azurewebsites.net/essent ... EL=Home</b>
Now i wanted to upload the repository from protege. When entering the URL into the "essential viewer" tab (and username and password, of course), it starts but fails to upload:

Code: Select all

Rendering repository...
Sending repository snapshot...
Checking for access...
Sending XML snapshot...
Failed to send snapshot to the Report Service : 
User name and password required; invalid user name and password supplied

Potential causes:
1) Missing or wrong proxy server configuration
2) Missing SSL connection
3) Wrong port

Do you have somewhere documentation available
1) where and how to configure a proxy server for protegé?
2) enable SSL for upload of the XML file to the viewer for protegé?
3) increase the log level to further investigate, where and how the root cause is?

Even a workaround would be great (if i knew where the XML is stored on a local hosted viewer, i could move it to the Azure viewer's directory and restart the viewer there.

Thanks in advance,

Holger

[jmk]

Hi,
first about the XML on your local hosted viewer:
you should look for the file "reportXML.xml" in your local "webapps" tomcat folder.

Next, about your upload problem:
Accessing tomcat logs would be the best way to find the root cause of your problem (I don't know anything about Azure but I suppose you have access to these logs) : I'd check any ERROR string in here.

Besides your "Potential causes", I'd first check if the tomcat user has permission to write files in the azure "webapps" tomcat folder.

You mentioned username/password : did you set them in tomcat or are you talking about your azure credentials ?

Hope this helps,

Jean-Marie

[HBuchner]

Dear Jean-Marie,

the log-files i could download from Azure look ok (Catalina log):

Code: Select all

10-Jul-2024 15:27:37.845 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name:   Apache Tomcat/9.0.88
10-Jul-2024 15:27:37.846 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Apr 9 2024 13:22:30 UTC
10-Jul-2024 15:27:37.850 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.88.0
10-Jul-2024 15:27:37.852 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Linux
10-Jul-2024 15:27:37.855 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            5.15.153.1-2.cm2
10-Jul-2024 15:27:37.857 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
10-Jul-2024 15:27:37.860 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             /usr/lib/jdk
10-Jul-2024 15:27:37.861 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_412-b08
10-Jul-2024 15:27:37.864 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Temurin
10-Jul-2024 15:27:37.866 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         /usr/local/tomcat
10-Jul-2024 15:27:37.868 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         /usr/local/tomcat
10-Jul-2024 15:27:37.883 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The Apache Tomcat Native library which allows using OpenSSL was not found on the java.library.path: [/usr/lib/jdk/lib/amd64/server:/usr/lib/jdk/lib/amd64:/usr/lib/jdk/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
10-Jul-2024 15:27:38.817 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-80"]
10-Jul-2024 15:27:38.862 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-169.254.130.4-80"]
10-Jul-2024 15:27:38.865 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [2265] milliseconds
10-Jul-2024 15:27:38.930 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
10-Jul-2024 15:27:38.938 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.88]
10-Jul-2024 15:27:38.992 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/usr/local/tomcat/webapps/essential_viewer.war]
10-Jul-2024 15:27:48.191 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/usr/local/tomcat/webapps/essential_viewer.war] has finished in [9,199] ms
10-Jul-2024 15:27:48.208 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-80"]
10-Jul-2024 15:27:48.258 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-169.254.130.4-80"]
10-Jul-2024 15:27:48.270 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [9403] milliseconds

and the log files from the log-stream as well:

Code: Select all

2024-07-10T15:30:39  Welcome, you are now connected to log-streaming service.Starting Log Tail -n 10 of existing logs ----/appsvctmp/volatile/logs/runtime/072659d62e9df91d4c8893b096970327be29146fd04a9be8b7fc6900e53fe68a.log
2024-07-10T15:27:46.920745179Z: [INFO]  Filter: AppServiceFilter filterRegistration: org.apache.catalina.core.ApplicationFilterRegistration@3e8483d9
2024-07-10T15:27:46.921805492Z: [INFO]  Registered filter: AppServiceFilter
2024-07-10T15:27:48.194079185Z: [INFO]  Jul 10, 2024 3:27:48 PM org.apache.catalina.startup.HostConfig deployWAR
2024-07-10T15:27:48.194121486Z: [INFO]  INFO: Deployment of web application archive [/usr/local/tomcat/webapps/essential_viewer.war] has finished in [9,199] ms
2024-07-10T15:27:48.213158417Z: [INFO]  Jul 10, 2024 3:27:48 PM org.apache.coyote.AbstractProtocol start
2024-07-10T15:27:48.213213018Z: [INFO]  INFO: Starting ProtocolHandler ["http-nio-127.0.0.1-80"]
2024-07-10T15:27:48.261163102Z: [INFO]  Jul 10, 2024 3:27:48 PM org.apache.coyote.AbstractProtocol start
2024-07-10T15:27:48.261202102Z: [INFO]  INFO: Starting ProtocolHandler ["http-nio-169.254.130.4-80"]
2024-07-10T15:27:48.273576753Z: [INFO]  Jul 10, 2024 3:27:48 PM org.apache.catalina.startup.Catalina start
2024-07-10T15:27:48.273615954Z: [INFO]  INFO: Server startup in [9403] milliseconds/appsvctmp/volatile/logs/runtime/b6780719ffcda755aabc062a784c4b2d1b384aba65bf612e57d7520aedfffaf2.log
2024-07-10T15:22:51.321503441Z: [INFO]  Filter: AppServiceFilter filterRegistration: org.apache.catalina.core.ApplicationFilterRegistration@3ed930a4
2024-07-10T15:22:51.321526942Z: [INFO]  Registered filter: AppServiceFilter
2024-07-10T15:22:52.783061362Z: [INFO]  Jul 10, 2024 3:22:52 PM org.apache.catalina.startup.HostConfig deployWAR
2024-07-10T15:22:52.783095763Z: [INFO]  INFO: Deployment of web application archive [/usr/local/tomcat/webapps/essential_viewer.war] has finished in [8,000] ms
2024-07-10T15:22:52.804828832Z: [INFO]  Jul 10, 2024 3:22:52 PM org.apache.coyote.AbstractProtocol start
2024-07-10T15:22:52.804863633Z: [INFO]  INFO: Starting ProtocolHandler ["http-nio-127.0.0.1-80"]
2024-07-10T15:22:52.858097149Z: [INFO]  Jul 10, 2024 3:22:52 PM org.apache.coyote.AbstractProtocol start
2024-07-10T15:22:52.858137349Z: [INFO]  INFO: Starting ProtocolHandler ["http-nio-169.254.130.5-80"]
2024-07-10T15:22:52.878876411Z: [INFO]  Jul 10, 2024 3:22:52 PM org.apache.catalina.startup.Catalina start
2024-07-10T15:22:52.878915411Z: [INFO]  INFO: Server startup in [19197] milliseconds/appsvctmp/volatile/logs/runtime/0e42f9f1353284853573debb4722925e1db5972f0d46e076387d6d552c184e8e.log
2024-07-10T15:22:14.003772090Z: [INFO]  INFO: Stopping service [Catalina]
2024-07-10T15:22:14.090045157Z: [INFO]  Jul 10, 2024 3:22:14 PM org.apache.coyote.AbstractProtocol stop
2024-07-10T15:22:14.090084958Z: [INFO]  INFO: Stopping ProtocolHandler ["http-nio-127.0.0.1-80"]
2024-07-10T15:22:14.110138613Z: [INFO]  Jul 10, 2024 3:22:14 PM org.apache.coyote.AbstractProtocol stop
2024-07-10T15:22:14.110176513Z: [INFO]  INFO: Stopping ProtocolHandler ["http-nio-169.254.130.2-80"]
2024-07-10T15:22:14.124358323Z: [INFO]  Jul 10, 2024 3:22:14 PM org.apache.coyote.AbstractProtocol destroy
2024-07-10T15:22:14.124396323Z: [INFO]  INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-80"]
2024-07-10T15:22:14.124402323Z: [INFO]  Jul 10, 2024 3:22:14 PM org.apache.coyote.AbstractProtocol destroy
2024-07-10T15:22:14.124406323Z: [INFO]  INFO: Destroying ProtocolHandler ["http-nio-169.254.130.2-80"]
2024-07-10T15:22:14.494393187Z: [INFO]  Done processing signal SIGTERM. Exiting now!/appsvctmp/volatile/logs/runtime/e041788522f1ea8fa05d74ed194129b4fa66ee81947d7836d62fb1e0e2731c5c.log
2024-07-10T15:27:29.457557276Z: [INFO]  Updated CA certificates/appsvctmp/volatile/logs/runtime/78487d5707d3ef7bca297843d23193b7446d6e01e10f8f40522a1a652e9eb780.log
2024-07-10T15:22:18.863918091Z: [INFO]  Updated CA certificatesEnding Log Tail of existing logs ---Starting Live Log Stream ---

as i am not seeing any access log either, my assumption is, that Protegé isn't able to connect. That leads back to the question about how to configure the proxy settings for protegé accordingly.

[neil.walsh]

Hi,

Publishing via SSL to a remote server has always been a challenge. At the heart of the problem is there are two Java applications which need to talk over SSL and therefore they need to share a certificate to communicate.

This forum post has some further information.
viewtopic.php?f=21&t=2537&p=31115&hilit=ssl#p31115

I quite like your workaround idea of publishing to a local tomcat then copying this file to the remote location.

As Jean Marie mentioned, the file is called reportXML.xml and is located in the root of the essential_viewer folder. You should see the size and timestamp update following a publish. You could then manually copy the file to Azure or perhaps write a little shell script to automate this. Viewer will automatically reload the snapshot into memory if it sees the reportXML.xml file change.

Let me know how you get on.

Neil

[neil.walsh]

Just a quick follow on....
It may be worth downloading the "Essential in a Box" zip which contains Protege, Viewer, Java and Tomcat in a single folder. This doesn't require any installation or configuration. From here you can publish your repository to the included Viewer. From there, you can copy the reportXML.xml to Azure.

See - Essential in a Box - top right of the page.
https://enterprise-architecture.org/pro ... -download/

[HBuchner]

Dear Neil,

thanks fo your reply too! I‘ll try to figure out, how I can map the folder in the Azure App Service configuration.

I‘ll keep you updated on the progress.


Thanks for your patience with me.

Holger

[daniel.victoria]

Hi,
I am trying to create a prod target env in the Import_Utility but the app keeps getting hung?
resarted tomcat multiple times. there is no error on tomcat log.


127.0.0.1 - - [17/Jul/2024:16:42:32 -0400] "HEAD /bian/reportService HTTP/1.1" 302 -
0:0:0:0:0:0:0:1 - - [17/Jul/2024:16:42:32 -0400] "POST /ea_siteone_import_utility/zkau HTTP/1.1" 200 461
0:0:0:0:0:0:0:1 - - [17/Jul/2024:16:42:34 -0400] "POST /ea_siteone_import_utility/zkau HTTP/1.1" 200 35
0:0:0:0:0:0:0:1 - - [17/Jul/2024:16:42:39 -0400] "POST /ea_siteone_import_utility/zkau HTTP/1.1" 200 200
0:0:0:0:0:0:0:1 - - [17/Jul/2024:16:42:39 -0400] "POST /ea_siteone_import_utility/zkcomet?dtid=z_qCptehBx1G98Jyz-XMgGEQ HTTP/1.1" 200 -
0:0:0:0:0:0:0:1 - - [17/Jul/2024:16:42:39 -0400] "POST /ea_siteone_import_utility/zkau HTTP/1.1" 200 553

[daniel.victoria]

Hi ,
Why my Launchpad spreadsheet exporter in essential viewer is grayed out??
i cannot create a excel import spreadsheet.

thanks
Parveen

[JohnM]

It's probably not enabled. Go to EA Support > Essential Viewer > Reports find the Core: Launchpad Spreadsheet Exporter and check 'Enabled on Homepage'

[HBuchner]

Dear Neil, John, Marie,
i was on vacation and couldn't follow up on my initial request. The good news: it is solved.

After setting up a Tomcat server as Azure App-Service, i am deploying the essential_viewer by copying the essential_viewer.war file into the Tomcat webapp root directory and restarting the Tomcat App Service.
It then deploys the "essential_viewer" web-app and is unpacking the .war file.
I tried to change the configuration of the AppService and allow writing into the webapp/essential_viewer directory, but that leads to an error in the deployment of Tomcat.
But it is possible to replace the original reportXML.xml file in the essential_viewer.war file with the reportXML.xml generated on my local Opensource Standalone Essential.

After replacing the vanilla essential_viewer.war with the modified file containing a custom reportXML.xml, it unpacks after starting the Tomcat AppService and displays my custom data.

Enclosed the home screen with the latest version of Essential Viewer (offcourse):

essential_on_Azure_app_service_1.png

As well as some data of the repository:

essential_on_Azure_app_service.png

Many thanks to the team for helping me to solve the topic on how to publish a repository to an Microsoft Azure App-Service hosted Essential Viewer.