Update & Parent packages

[boaterdan]

I swear, just when I think I'm understanding something...

To make a long story short, after I finally got update 2 in to the PY environment, it had created an UPDATE package with PY7333FA as the parent. That package is building right now.

This JDE tech support guy has been in contact with me on this project, and he just called. I told him that the update package was building right now, but I don't really intend to deploy it, so I'm going to recompress the full parent package and install that.

There was a silence like he didn't know what I was talking about when I said "recompress the parent package". After discussing that he essentially said I should always build full packages with all the spec and build function checkboxes marked.

Now, either page 217 of the Deploying Mods book, my teacher for that class, and my understanding of the whole concept of parent packages are all wrong, or this guy was.

I'm trying to maintain my sanity here, and all the conflicting information from JDE isn't helping. Ok, I'm done ranting, anyone want to comment?

---------------------------------
OneWorld Xe SP15
Clustered Windows 2000 + SQL 2000

 

[JamieMarino]

I would definately build a full server and workstation package after
applying update 2.

 

[Guest]

Yes, you have to wonder sometimes about whether the helpdesk actually works
for JDE!

Our procedures are to build update packages and recompress the parents once
or twice a week. It all depends on whether I need the full package to install
a new client and how many updates I have. But, no, you do not have to always
build full packages!

You still have your sanity!
Mechele
Xe, SP15.1, Unix, Oracle

-- Original Message --

and
now,
full




Visit iWon.com - the Internet's largest guaranteed cash giveaway! Click
here now for your "Thank You" gift:
http://www.iwon.com/giftcenter/0,2612,,00.html?t_id=20157

 

[brother_of_karamazov]

I think he must have been wondering if you added all
of the objects in Update 2 by hand... :=0

The rule of thumb usually is that if there are more
objects than you care to enter individually, you build
a full package.

I know you are thinking, "But the ESU process creates
an update package for me, how neat." The kinks are
still not worked out on the ESU-created packages and
until they are I do not trust them. There are issues
with dependencies that may or may not cause false or
real errors in the build logs.


--- boaterdan <[email protected]> wrote:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=17758


__________________________________________________

 

[Sanjeev_Harrish]

Hi there,

This issue confused me for a long time but I've got something which may help you. My understanding is that:

If you build a full package X (with no options selected to compress any part), then any changes in further update packages which are created (with the package X as the parent package) get written to the full package X.

If the full package X was compressed (any part of it), then the updates aren't written to the full package. Therefore, the need arises to 'recompress' parent packages.

Hope this helps!

Regards,

Sanjeev Harrish
Technical Consultant

 

[swhitmire]

Just wanted to clarify this in case anyone is confused (and of course, this
is just
my understanding; if I've missed something, please let me know.) The updates
are always written to the
full package; it's how the full package is updated/deployed when compression
is used
that causes the need for recompression. If you look in the directory for
your full package on your
deployment server, you'll see both a set of directories with the components
of the package
in them (bin32, spec, etc) and a set of .CAB files with the same names. The
CAB files are
just compressed versions of the directories. When you build an update with
the full
package as a parent, the changes are merged in with the files in the
directories, but
the CAB files are not automatically recreated. Client installations use the
CAB files,
and this is why you'll need to recompress (i.e. create new CAB files from
the directories)
before the changes from the update will be reflected in an installation of
the full package.

--Scotti Whitmire
DeRoyal Industries
Xe SP15, AIX4.3.3, Oracle 8.1.6

 

[tompm]

The instructions for U2 included a specal note to build a full package. Not
to use the update.

 

[Carl_Fisher]

I agree - that is my understanding too.

I think the real issue is with Update 1 and Update 2.

These are such large ESU's that JDE advise doing a full package build.

Having seen how many objects are involved I cannot see any real time saving
in doing an Update Package and a Parent Compress, so I think I would take
the SAFE option and follow advice, do a full package build, you can always
create a new Parent Package. This does ensure that EVERYTHING is in your
package, avoids all those funny messages you get from a BUSBUILD where not
all the objects are in the Package and lots more heartache.

I have in fact created a full package even with ESU's where a large number
of Objects are concerned, it just seems safer. If you have a well specified
Deployment Server it should take about a day. It can take as long to do an
Upgrade package.



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