Hi Thomas,
To answer your second question first.
i. Yes, the proxy settings are used for Presto to connect to other components outside of Presto - could be a resource on the network or on the internet
ii. As mentioned in Presto documentation, did you specify the proxy settings in the adminserver.config configuration file? Once that is complete, Admin Server will be able to work using proxy. Thereafter you can make changes in Admin Console to configure Presto to work with proxy.
Please check the following link for exact steps on configuring Presto to work with proxy
Do let us know how it goes
OK, so changing the adminserver.config file fixed the JSON issue and allowed me to change Global Params. But I'm still wondering if the documentation could be better. That page says, 'if you have a proxy server in your environment', you need to specify it. You have to do that for both the mashup server and the admin server....
1. It's not explained why you need to specify the proxy server. Though I have a proxy server 'in my environment', would I need to specify the proxy server if my data sources are inside my firewall? (I know this one sounds dumb, but again, explaining it is better than assuming they know.) Does the mashup server need it for anything else (downloading other parts on demand, etc.)
2. Why do I need to specify the proxy info for both the admin server and the mashup server separately?
3. Why is one done through the web interface but the other is done through editing the .config file?
I'm still getting the same problem when I try to deploy the sample scripts. All services installs fail. I take it that the mashup server is connecting to www.jackbe.com tyo download them, or is it getting the samples from somewhere else?
Executing unregisterService ----------------Yahoo services --------------
Request (unregisterService ----------------Yahoo services --------------) failed.
Error -> HTTP/1.1 401 Bad credentials
Executing Register service
Request (Register service) failed. Error -> HTTP/1.1 401 Bad credentials
Executing Confirm service registration
Request (Confirm service registration) failed. Error -> HTTP/1.1 401 Bad credentials
Executing Activate service
Request (Activate service) failed. Error -> HTTP/1.1 401 Bad credentials
Executing unregisterService
Request (unregisterService) failed. Error -> HTTP/1.1 401 Bad credentials
Executing Register service
Request (Register service) failed. Error -> HTTP/1.1 401 Bad credentials
Executing Confirm service registration
Request (Confirm service registration) failed. Error -> HTTP/1.1 401 Bad credent
ials
Hi Thomas,
Your feedback regarding documentation will be duly noted. To answer your queries
1. Let us take a typical scenario. If Presto is installed inside a network where a request to a network resource (internet or intranet) needs to be authenticated then we will need to specify proxy settings for Mashup Server. However if Presto would not have to go through any authentication to make requests then one does not need to set up the proxy configuration in Presto. These scenarios are properties of the network wherein the Administrator would have specified if requests for specific resources need to go through the proxy at all.
2. Admin Server is meant to be able to handle multiple mashup servers (a prabable enterprise scenario) and hence is a separate component from mashup server. And that is the reason one needs to specify it at two different places
3. Point duly noted from point of view of consistency. We have kept this in my mind for our future releases.
Coming to the problem you are still facing in Presto Mashup Server, can you try the following:
i. Try to run Presto without providing proxy details (this will ensure that proxy configuration is required)
ii. If the proxy is running on Windows NT Domain then you need to provide additonal details. Refer to the documentation available here
iii. Ensure that you have restarted the mashup server once you have changed the proxy details.
In case things still do not work for you, please attach presto log file(s) (found in <presto installation path>/logs/presto.log in your reply.
Do let us know how it goes.
No luck. I've specified the Proxy values on both the Admin Server and the Mashup Server, I've tried installing both with and without setting the proxy info, I've tried setting it as an NTLM proxy and specified a domain, and I'm getting the same results every time - HTTP 401 error, Bad Credentials. The source files for the samples seem to be in the local TEST directory - what is the server trying to get to an external URL for? An IP address for where it's trying to go might be better for me to try... DNS to IP resolution for external targets doesn't work for us outside of a browser.
Thanks...
Hi Thomas,
To your extant query of why is it trying to connect to an external IP - the information for which services to publish is stored locally indeed. However, to publish these services in Presto, Presto needs to the check the actual URL which is hosted on Yahoo, Xignite etc.,
We are looking into the issue you are facing. Will get back to you on this.
Now I feel stupid, but I don't think I should.... I looked at the sample install script, and the password for the admin user is hardcoded in there. Since I had changed the admin password when I first configured the mashup server, it was failing on the sample service install. It was the mashup server that was complaining about the bad credentials, not the proxy.
Maybe it's time to prompt for the script user/password, or post a warning that if you've changed it you need to update it in the script?
- Tom
OK - I've got two problems that sowed up at different times.
The first is that I can't install the same mashups from the prestocli directory - I get a ton of Java errors. It looks like the proxy is set up wrong, but I can't change the settings (see question #2, below.)
What am I specifying a proxy for? Is it a proxy to get to the Presto server (for some other part of Presto) or is it the proxy that the server will use to get to the outside world?
Errors:
Running test case......test\testcases_public_services.txt
Executing Delete Provider - AmazonWebServices
Request (Delete Provider - AmazonWebServices) failed. Error -> HTTP/1.1 401 Bad credentials
Executing Delete Provider - BBC
Request (Delete Provider - BBC) failed. Error -> HTTP/1.1 401 Bad credentials
Executing Delete Provider - Blogger
Request (Delete Provider - Blogger) failed. Error -> HTTP/1.1 401 Bad credentials
Executing Delete Provider - CNN
Request (Delete Provider - CNN) failed. Error -> HTTP/1.1 401 Bad credentials
Executing Delete Provider - Dapper
Request (Delete Provider - Dapper) failed. Error -> HTTP/1.1 401 Bad credentials
Executing Delete Provider Digg
... Repeat ad nauseum.
The second issue, which is more recent, is that the mashup server appears to start OK, but doesn't show up on the admin console (even though I can log into the local PRest instance with my username/password.) When I try to change global settings, I get this error:
Badly formed JSON string: '{"sid":"","appId":"","oid":"","svcVersion":"","header":{},"error":"{"sid":"","appId":"","oid":"","svcVersion":"","header":{},"error":"Gateway Timeout","errorCode":"504","invId":"","response":"null","version":""}","errorCode":"","invId":"","response":"null","