Enterprise Server as Fat Client?

alexanac

Member
Hello All,

Interesting problem and I am under the gun to deliver something today. Here is my situation...

System: OneWorld 733.2 (SP 15.1)
ENT: WinNT 4.0 SP6a / Oracle 8.1.5
DEP: WinNT 4.0 SP6a
TS: WinNT TSE

All of the above servers exist in San Francisco. Our development fat client exists in Cincinnati. The connection between the two is so slow that to deploy a full package out to the fat client takes 5+ hours. Checking out large objects can take a long time as well. A developer needs some sort of fast development access ASAP. Is it possible to install the workstation on the Enterprise Server (and hit through PC Anywhere)? OW workstation would be in a different directory, but would that be enough? How would it be registered in Machine ID? I need to put something together... Also, is it at all possible to do development on the Deployment Server? This is a demo environment with only CRP active so if we need to alter the Central Objects directly, that's okay!

Any help is appreciated!

- Tony Alexander
[email protected]
 
- Tony Alexander,
We have set remove developers up on a spare Citrix Terminal Server. This
will work ONLY if 1 user/developer is working on the WTS at a time. (You
don't want people stomping all over each other and ruining your specs
now do you??)
Not the best but is "a" solution if you happen to have a spare server
sitting around.
Have the developer connect via a Citrix Internet Connection to the
server (you probably already have then setup via VPN).

Lisa G. Stinebuck
Senior Service Delivery Technician
Logical eBoc
US Logical
311 Elm Street, Suite 150
Cincinnati, OH 45202
(513) 412-3400 Office
(513)378-2832 Cell
[email protected]
www.us.logical.com <http://www.us.logical.com/>
 
I don't think you would be able to do any JDNET stuff as both Clients and
Enterprise would be fighting over the port 6008

Simon
 
We are using PC Anywhere for our development. It is working fine for us.
Someday access is bad (mostly around 12:00 - 3 pm).

System: OneWorld 733.1 (SP 7.1)
ENT: WinNT 4.0 SP6a / SQL server 7.0

Hope this helps,
 
Checking out objects will be slow too, so even if you installed OW on the
fat client in OH it would be unacceptable.

I would suggest installing OW on a development workstation in CA and then
accessing that machine using PC anywhere. You could even install new client
updates remotely once you had it all setup.

Hope this helps!

James Wilson
CNC Consultant

OW Xe B73.3.3 SP16 AIX
IBM RS/6000 AIX 4.3.3 Enterprise Server (Central Objects)
Oracle DB 8.1.6.3
NT 4.0 Deployment Server
"fat" Win95/Win98 and TSE/Citrix "thin" clients
ZenWorks - using to deploy initial OneWorld clients








All views are expressly my own and in no way reflect those of my employer.
 
Alex :

I've never tried to install fat client on an NT Enterprise Server.
If you need a fast developer tool, find a cheap clone PC in
San Francisco, install OneWorld and a remote administration software,
then you'll be able to access from Cincinatti without endless delays.
Finally, it's not possible to develop on the Deployment because how
would OneWorld distinguish a checkout object from its master location?
Master location is DEPLOYMENT, and you can't check it out to DEPLOYMENT!

Sebastian
 
1. Develop on E.S. box ... NO!
2. Develop on D.S. box ... NO!

Best bet is to setup a Terminal Server (separate box!) with one user/client allowed - which would be your Concinnati developer.

Search the forum archives for key words "Remote Development" and "Terminal Server" for related options.


Larry Jones
[email protected]
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials
 
Thanks for all the help. I should have put this in the original post, but we have done PC Anywhere development extensively as well. The only issue with this is that we host at a third party datacenter that would take at least a week to get a new box set up on the floor. My client needed something immediately and was willing to go for just about anything. I wanted to stay away from using the TS since we have had issues in the past (even with just one developer on at a time). I see several of your points about the problems of using either the DEP or ENT and have set them up to use the TS for now, with a workstation on the way.

Thanks for the help!

- Tony
 
I agree with the majority of the responses you have received. It is not advisable to install a OneWorld Client onto your Enterprise Server due to registry and port conflicts between the two. You would also not want to use your Deployment Server for much the same reason.

However, I must take issue with the posts regarding Remote Development on TSE using OneWorld Xe. I've heard it can be done and is being done by more than one J.D. Edwards Client. Caveat - It is not yet supported by Denver Development or GSS. It is a field supported solution.

Just my $.02 worth.
 
Back
Top