RES: Enterprise Server as Fat Client?

I have followed this thread with interest. Although it kind of died by now,
please allow me one more comment.
My first reaction the orginial post was: of course one canNOT install a OW
client onto the Enterprise server. Most answers seemed to confirm that.
Now I have some doubts: can one not create combo-boxes, that is Deployment
Server and EnterpriseServer(NT) on one physical box? If so, why can one not
install a client together with an ES? After all, a DS is pretty much a
OW-client with a special configuration. At least what JDENET and registry
entries are concerned, a DS is not different from a OW client. As far as I
know NT Enterpriser Servers do not use the registry, although there might be
entries. And why would JDENET be problem? JDENET passes any read or write
requestes on to the TCP layer, and that can handle such tasks. Any machine
can ping itself. On a UNIX box you can telnet to the proper machine itself.
One can have Oracle clients on the same machine as the database.
Anyway, it is more an academic thought (meaning: not of much use). And to
get me right: I DO NOT recommend installing a OW client and ES on the same
box (but I am curios to find out if it would work).

Thanks, Gerd

Hi Gerd,

I have tried this when trying to build a fully self-contained development system on a laptop with both client and server.

What I found was that the client could not bind to the control port (6009 in XE) if the server was running first and the server could not bind to the JDENet control port if the client was started first.

I agree with your general statements about TCP/IP and ports. For whatever reason the client and server don't play well together on the same box.

Regards,



Justin Miller
[email protected]

working with B7332 and XE on AS/400, NT, Solaris and AIX