Re: Wonder JavaMonitor problem
Re: Wonder JavaMonitor problem
- Subject: Re: Wonder JavaMonitor problem
- From: Patrick Robinson <email@hidden>
- Date: Fri, 04 May 2012 16:44:55 -0400
Using a reverse proxy is a great idea... thanks!
For you folks who access JavaMonitor directly via its port, how do you *prevent* access via Apache (i.e. via .../JavaMonitor.woa/-56789) ?
On May 4, 2012, at 3:34 PM, Pascal Robert wrote:
>> Yes, I guess I've always used it via Apache -- with a devl URL, i.e.
>> https://hostname/cgi-bin/WebObjects/JavaMonitor.woa/-56789
>> and protected it via Apache config directives. Because I'm accessing w/a devl URL, there's no bizarre "add JavaMonitor with JavaMonitor" weirdness.
>>
>> I'd been looking at this all morning, and learned:
>> (1) It's not unique to Ubuntu; it's not OS-specific at all - it happens w/OSX as well. (Of course!)
>> (2) The wonder build of JavaMonitor doesn't set -WOFrameworksBaseURL the way an ant build of a normal project does.
>
> Exact, probably because everyone says it shouldn't run under Apache :-)
>
>> (3) It dawned on me that there was no corresponding JavaMonitor-WebServerResources.tar.gz. I guess I had manually copied the relevant WebServerResources dirs over to the Apache DocumentRoot at some earlier date, and forgotten about it. *sigh*
>>
>> I take it the usual approach is to open port 56789 to specific hosts that require access? With Apache, I can restrict access to specific hosts AND require user authentication and authorize access only to specific users.
>
> Maybe a reverse proxy (ProxyPassReverse) and blocking port 56789 outside the box would work.
>
>> Live and learn. :-/
>>
>> - Patrick
>>
>>
>> On May 4, 2012, at 2:16 PM, Pascal Robert wrote:
>>
>>> I just did a raw installation on Ubuntu 10.04 Server (only installed Java 1.6 from Oracle and wotaskd/Monitor), and I don't get the problem you have. The path to prototype.js is :
>>>
>>> http://192.168.0.48:56789/cgi-bin/WebObjects/JavaMonitor.woa/wr/wodata=/opt/Local/Library/WebObjects/JavaApplications/JavaMonitor.woa/Contents/Frameworks/Ajax.framework/WebServerResources/prototype.js
>>>
>>> Are you trying to use Monitor under Apache?
>>>
>>>> Oracle jdk-6u31-linux-x64.bin
>>>>
>>>>> Running which JDK?
>>>>>
>>>>>> Ubuntu 10.04 LTS, so .... Yeah. :-)
>>>>>>
>>>>>> On May 2, 2012, at 8:19 PM, Pascal Robert wrote:
>>>>>>
>>>>>>> Is this on Debian?
>>>>>>>
>>>>>>>> Yes, I just downloaded:
>>>>>>>> http://jenkins.wocommunity.org/job/WonderIntegration/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz
>>>>>>>>
>>>>>>>> That has the same behavior (or lack thereof!). :)
>>>>>>>>
>>>>>>>>
>>>>>>>> On May 2, 2012, at 7:48 PM, Pascal Robert wrote:
>>>>>>>>
>>>>>>>>> That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem?
>>>>>>>>>
>>>>>>>>>> I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this:
>>>>>>>>>>
>>>>>>>>>> ant frameworks deployment.tools -Ddeployment.standalone=true
>>>>>>>>>>
>>>>>>>>>> I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the "Site" tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing.
>>>>>>>>>>
>>>>>>>>>> Up in the <head> section, I see:
>>>>>>>>>> <script src="/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js"></script>
>>>>>>>>>> <script src="/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js"></script>
>>>>>>>>>> <script src="/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js"></script>
>>>>>>>>>>
>>>>>>>>>> Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No?
>>>>>>>>>>
>>>>>>>>>> - Patrick
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>>>>> Webobjects-dev mailing list (email@hidden)
>>>>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>>>>>
>>>>>>>>>> This email sent to email@hidden
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>>>> Webobjects-dev mailing list (email@hidden)
>>>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>>>>
>>>>>>>>> This email sent to email@hidden
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden