Date Posted:
Product: TIBCO Spotfire®
Product: TIBCO Spotfire®
Problem:
How to check the Public Address URL configured on TIBCO Spotfire Server using a Troubleshooting bundle
Solution:
The public address is the base URL that is used by Spotfire when generating absolute URLs. A public address must be configured if the Spotfire Server is accessed through a load balancer or reverse proxy. This article demonstrates 3 ways to determine what public address is configured on the TIBCO Spotfire Server based on a Troubleshooting Bundle.
Below are three possible ways to check which Public Address URL that the TIBCO Spotfire Server is using:
1) Open the Configuration.xml from the Troubleshooting bundle and check if the below '<public-address>' section is enabled:
<public-address> <enabled>true</enabled> <url>https://tss78.nc.com/</url> </public-address>
2) Open the Sites.txt and check here:
site id;site name;public address 5c2c7b84-e1f4-4187-9799-85a2a48f0ebc;Default;https://tss78.nc.com/ (c)
3) Open the server.log from within a "tss-" Spotfire Server folder (note: this requires the logging level is set to DEBUG) and search for "Frontend server manifest" and Backend server manifest" to see which public address endpoint it is pointing to:
DEBUG 2018-10-16T14:56:35,862+0000 [] server.manifest.ManifestServlet: Frontend server manifest: <?xml version="1.0" encoding="UTF-8"?> <manifest> <client-login> <show-login-dialog>standard</show-login-dialog> <always-online>false</always-online> <allow-save-information>true</allow-save-information> <allow-user-provided-credentials>true</allow-user-provided-credentials> <offline-days-permitted>infinite</offline-days-permitted> <technical-min-version> <cloud>10.12</cloud> <standard>10.12</standard> </technical-min-version> <min-version>4.5.0</min-version> </client-login> <server-info> <version>47.0.8014.637</version> <release>standard</release> <login-initiation-endpoint>/spotfire/auth/web/initiate</login-initiation-endpoint> <login-success-endpoint>/spotfire/auth/web/success</login-success-endpoint> <oauth2-authorization-endpoint>/spotfire/oauth2/auth</oauth2-authorization-endpoint> <oauth2-token-endpoint>/spotfire/oauth2/token</oauth2-token-endpoint> <authentication-modes> <sf-oauth2 /> <sf-web /> </authentication-modes> <session> <timeout>23</timeout> </session> </server-info> <logging-categories /> <monitoring-commit-period>300</monitoring-commit-period> <public-endpoints> <public-endpoint>https://tss78.nc.com/</public-endpoint> </public-endpoints> </manifest> DEBUG 2018-10-16T14:56:35,862+0000 [] server.manifest.ManifestServlet: Backend server manifest: <?xml version="1.0" encoding="UTF-8"?> <manifest> <client-login> <show-login-dialog>standard</show-login-dialog> <always-online>false</always-online> <allow-save-information>true</allow-save-information> <allow-user-provided-credentials>true</allow-user-provided-credentials> <offline-days-permitted>infinite</offline-days-permitted> <technical-min-version> <cloud>10.12</cloud> <standard>10.12</standard> </technical-min-version> <min-version>4.5.0</min-version> </client-login> <server-info> <version>47.0.8014.637</version> <release>standard</release> <authentication-modes> <sf-backend-trust /> <username-and-password /> </authentication-modes> <session> <timeout>23</timeout> </session> </server-info> <logging-categories /> <monitoring-commit-period>300</monitoring-commit-period> <public-endpoints> <public-endpoint>https://tss78.nc.com/</public-endpoint> </public-endpoints> </manifest>
Doc: Create a Troubleshooting bundle Doc:set-public-address
Comments
0 comments
Article is closed for comments.