installing enterprise server on Mapped network drive

pranes

Member
We are running out of disk-space on our server drives for the enterprise
server.

My operations group has asked be to try to reinstall the entire JDE
application on a mapped network drive, rather then on internal drives or
drives in a shelf.

Has anyone seen such a thing? Has it/will it work? If you can do it where
would the application executable run - the real enterprise or the server
that we mapped to?

Please Help!



Xe sp15.1, Oracle 8.1.6.3, NT4sp6a, Citrix

Sue Pranes
[email protected]
Phone: 650-631-5012
Fax: 650-631-3150
Pager: 650-760-1166
 
I wouldn't recommend moving your OneWorld Source Code (it doesn't take up much room on the Enterprise Server anyway). Why not just move your database? After all that is what takes all the space. I am sure a good DBA could move the whole thing in a short time. All you would need to do would be to check your OCM mappings.

During upgrade we had the Source Code on one server and the database on another, no problems.

I am sure there are plenty who could give you more info on this arrangement. It is not recommended for any software to be run off mapped network drives!

OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development
 
Sue :

It's technically possible to install the whole JDE Enterprise directory
on a mapped drive, but its performance won't be very good...
The software will execute locally on the server, but whenever it needs to
read a spec (.ddb & .ddb) it will have to access it via network, some
specs are close to 1 Gb large and thus may turn to be quite slow.
Packages and printqueue will also reside on the mapped drive, so their
performance will also suffer from this penalty.

Sebastian Sajaroff
 
Why not just get some bigger drives (assuming you are running in RAID) and
do a backup and restore. If you run the E-server off a mapped drive the
executable will run on the E-server but it will add an additional load to
the network as it goes back and forth between the machine with the real
drive your code is on and the E-server where it is running. It will work but
now you

1. Add network load
2. Slow processes down as you pull/push things back and forth between the
E-server and the mapped server
3. Add another level of failure - If the mapped server fails no One World.
If the network between the 2 machines fails no One World. Make a change on
the mapped server that affects mapped drives and no One World.
4. Add another level of aggravation when troubleshooting - is it the
E-server or the mapped server

Sounds like it is time to buy some nice big drives. Just talk about downtime
to the ops group and hopefully they will see the light. Good luck either
way.

BTW - we use mapped drives for our /packages and /PrintQueue directories
since we run 3 E-servers but each one has PD7333 installed on its own
drives.

Mark Siebenschuh



Mark Siebenschuh
HP9000/Oracle 8.0.5/JDE XE/Lots of Citrix
 
I agree with Carl. Does not sound like a good idea to move the OW
executable file to a network drive. A disc may break, a network
connection breaks even easier.

Check your package directory on the server. Often there is a lot of old
stuff to be deleted. Maybe you do not need all pathcodes on the ES. See
if you cannot live without pristine and DV pathcodes on the enterprise
server. The log and/or Printqueue directories often have a lot of old
files that may be deleted.

The OW executable portion does not grow to much, usually. It´s your
database that grows. So, as Carl said, work on your database.

I had a client who simply used the NT file system option to compress the
whole disc with OW and Oracle data files on it. The results where
terrible.

Gerd
 
Back
Top