Re: Windows equivalent of this deployment problem? (Resolved)

Hi Mark,

Thanks for your post.

On 18/05/2004, at 12:18 PM, Mark Ritchie wrote:

> On 14-May-04, at 9:03 AM, Ashley Aitken wrote:
>> The local system admins have been having some problems with local 
>> access to the Internet and may have changed some DNS stuff on the 
>> Windows machines.
>
> Having just helped a client fix a problem with deployment on Linux, I 
> can tell you that WOF deployment is sensitive to DNS.

Yes, I can believe that.

>
> Specifically, here are some things to check:
> Does each machine involved with with the deployment have both a 
> forward (name to number) and a reverse (number to name) entry in DNS?
> Does each machine involved use the well known IP address as it's 
> address?
> Does each machine involved think that it's host name is the name which 
> DNS associates with that IP address?
> (This name should probably be fully qualified.  ie (foo.bar.blat.org 
> and not just foo)
> It's probably also important to make sure that you have correct the 
> correct search domain setup on each machine although this is not so 
> required if you have fully qualified names but it's probably a good 
> idea.
>
> Now, does wotaksd on each machine, and the single instance of Monitor 
> have the same list of host names and IP numbers?  If not then start 
> deleting entries and re-entering with the correct host name.  When the 
> WOF apps are launched, wotaskd won't recognize them unless everyone 
> has the same idea of host name and IP address.

Thanks very much for that list - I will keep it handy in my own 
deployment notes.

> I hope that helps.

Thanks again, but I actually found the problem and posted a resolution 
under a different thread.  The email is appended below (for your 
information, and something else possibly to add to your list).  I had 
changed the application name using ERExtensions and that seemed to 
confuse JavaMonitor.

> P.S.  I wish that I'd actually finished putting together that handbook 
> on WOF deployment which I started to write all those years ago.
> It would be a handy reference at the moment.

I agree ;-)

Cheers,
Ashley.

--

> Howdy All,
>
> Just to report back on the resolution of this problem:
>
> On 05/05/2004, at 11:12 PM, Ashley Aitken wrote:
>> When I start, it fails to start (1 or 2 deaths) and shows up as not 
>> running in JavaMonitor, not through the adaptor or instance or 
>> directly (even after refreshing a couple of times).
>> If I look at the app output (in the app directory) I see it is 
>> running and I can use the URL given (.../-Port) to connect to it.  
>> The apps seems to run fine.
>
> I am using D2W and Project WONDER (ERExtensions, ERDirectToWeb etc.) 
> with WO5.2.3, development on MacOSX and deployment on Windows 2KSP4 
> with Java 1.4.2.
>
> It turns out I had set
>
> ERApplicationName = MyAppName
>
> in my application properties file.
>
> I thought this would mostly be a cosmetic change, e.g. so that 
> exception pages would show the application name I wanted, rather than 
> a development application name.
>
> However, for some (probably good) reason, it seems to do more than 
> that.  It also seems to get JavaMonitor confused so that it could not 
> find running instances of the application.
>
> Perhaps I should have made the application name in JavaMonitor match 
> the above?
>
> Anyway, I changed it back and now all is well again.
>
> Thanks to all those who offered suggestions.
>
> Cheers,
> Ashley.
>

--
Ashley Aitken
Perth, Western Australia
mrhatken at mac dot com