• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Partial Package

graham_jones

Active Member
Hi,

Our company has a need for a OneWorld client at the end of each one of eight
packing lines. As we don't have terminal servers (everyone is on fat
clients) I am considering a partial client solution as these packing lines
only need the completions workbench applications P3119 and P31114.

Has anyone got any thoughts/experience of partial clients that they would
like to share?

Regards,

Graham Jones
JDE Systems Manager
graham.jones@parkgroup.co.uk

B7332 SP15 / AS400 V4R4 (CO on AS400) / Fat clients NT4


***** DISCLAIMER ***** This communication contains information which is
confidential. It is for the exclusive use of the intended recipient. If you
are not the intended recipient, please note that any distribution, copying
or use of this communication or the information in it is prohibited. If you
have received this communication in error, please notify us by email or by
telephone on 0151 653 1700 and then delete the email and any copies of it.
*****
 

Carl_Fisher

Well Known Member
What are you hoping to gain by this? You can use the partial client package,
but you will find it does not save you much disk space. It might save a
little bit of time on the installation, but will certainly create a lot of
JITIs (Just In Time Installs) when the users start to use it.

With a full package and JITI, you will still get what you want, with less
messing about. You will still get JITIs, a full package only installs the
basics of JDE to get you working.



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

cdawes

VIP Member
I have 220 FAT clients and in 2 months this will hit 250 (I also have 60
Terminal Server Clients).

I would argue that partial packages are the BEST way to go for End-User FAT
clients. My reasoning:

1. End-Users only use 5-10% of the total JDE package so why install 95% of
the package? (Full packages install all objects and specs except for data
dictionary and global tables - when these items are not replicated).

2. Full Packages install 1.3 GB on each workstation. Partial packages
install ~500 MB on each workstation. You do the math.

3. A Full package install pulls 200 MB of cab files plus Foundation across
the network. A Partial package pulls 50 MB of cab files plus Foundation
across the network. Your network - your call.

4. Partial Packages are easier to install and manage. If a mandatory ESU
comes along why build a package? Just reinstall every workstation using NT
scripting - not the JDE package deployment director. This way every machine
gets updated when you want it to - not when users login.

5. JITI's are fun. I think users like to see stuff flying across their
screen. Our average JITI takes a few seconds and since users only use 5% of
the system once it JITI's once it won't JITI again.

6. With Partial Packages you can choose certain objects to install. In this
case P3119 and P31114 look like good candidates.

7. FAT clients (Full or Partial) work well with Microsoft SMS.

8. I can install a partial package in 4 minutes. I can install a Full
package in 14 minutes. I would rather wait 4 minutes than wait 14 minutes.

Colin





Colin Dawes, MSc
City of Guelph
B7332 SP13.1, Oracle 8.1.6, NT 4.0, Fat & WTS
 

Larry_Jones

Legendary Poster
Re: RE: Partial Package

Colin,

a couple of questions.

1. How many of your clients are installed with partial packages as opposed to full?

2. How much time does it take you to build a partial as opposed to a full (I assume you build both).

We discarded partials early on in our B733 implementation due to all the problems OW had then with packages. We haven't re-visited them since, but your post has me thinking.

TIA,

Larry Jones
ljones@wagstaff.com
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials
 

graham_jones

Active Member
Carl,

Thank you for your comments. My intention was to try to simplify some of the
systems administration not to save any disc space.

Graham Jones
JDE Systems Manager
graham.jones@parkgroup.co.uk

B7332 SP15 / AS400 V4R4 (CO on AS400) / Fat clients NT4


***** DISCLAIMER ***** This communication contains information which is
confidential. It is for the exclusive use of the intended recipient. If you
are not the intended recipient, please note that any distribution, copying
or use of this communication or the information in it is prohibited. If you
have received this communication in error, please notify us by email or by
telephone on 0151 653 1700 and then delete the email and any copies of it.
*****
 

gerd_renz3

VIP Member
Graham,
I am a consultant and have seen many different installations on different platforms. Some of my clients are using partial packages. I happen to vistit a client today that has been using partial packages for ALL production users for the last 2(+) years. I just confirmed with the client´s CNC manager that there have been no major issues with partial packages.
There are substantial benefits during package build and package install time. The disk space saved should be about 1Gig on Xe, little less on B7332, considering that the users will use the two applications mentioned only.
If you want to save some JITI, build the two applications´s specs into your partial package.
I think it´s worth a try in this specific case.

Good luck, Gerd


Gerd J. Renz
InfoJBS Consultores Associados
Gerente de Tecnologia
e-mail: gerd_renz@infojbs.com.br
fone: 011 5505-3750



--
ISM - Solucoes na Internet

http://www.ismnet.com.br/
 

cdawes

VIP Member
RE: RE: Partial Package

Larry,

ALL of our 220 live FAT clients run Partial PROD Packages. Our training
machines also run CRP Partial Packages. Development and Admin machines run
CRP and DEV FULL packages. (Of course the Terminal Servers are Full
Packages).

Your times may be different for package builds since we have many custom
objects (Reports & Interfaces)

A Partial package with no objects takes 1 hr 15 minutes.
A Full Client Package takes 3 hr 15 minutes
A Full Client/Server Package takes 5 hr 30 minutes (WOW!!!)

All packages are built on a NT Workstation (PIII - 733mHz 256 MB RAM)

You're right about partial packages. Before B7332 they didn't exactly work.
I think this is why a lot of people have been afraid of them and why
consultants haven't recommended them. Anyone still running a lot of FAT
clients should probably revisit this.

I've never had any problems with Partial Packages from day one. The best
thing about them is that they're so small it's often easier to re-install a
Partial Package on a Workstation then to send out a huge update package.
This was especially usefull before the JD5550 ESU Enhancement that
automatically defined the objects that needed to be included in a package.

Colin




Colin Dawes, MSc
City of Guelph
B7332 SP13.1, Oracle 8.1.6, NT 4.0, Fat & WTS
 

husni

Well Known Member
We used Full Packages when we were on B7331. Since we moved to Xe we use partial packages and we don't find problems with the packages (but obviously with applications....!)
 

graham_jones

Active Member
Many thanks for all the very useful input into this thread. I have now built
a partial package with the required objects and that is now under test.
There were a couple of compression errors i.e. no cab file created but there
is a SAR reporting this issue.

Graham Jones
JDE Systems Manager
graham.jones@parkgroup.co.uk

B7332 SP15 / AS400 V4R4 (CO on AS400) / Fat clients NT4


***** DISCLAIMER ***** This communication contains information which is
confidential. It is for the exclusive use of the intended recipient. If you
are not the intended recipient, please note that any distribution, copying
or use of this communication or the information in it is prohibited. If you
have received this communication in error, please notify us by email or by
telephone on 0151 653 1700 and then delete the email and any copies of it.
*****
 
Top