Server Package Builds

jdcmwilson

Well Known Member
JDE List,

When we build an update package tied to a parent package do the specs on the
server (under the parent package library) get merged during the build
process or only once the package has been deployed?

The reason I ask is because we were building an update package (client and
server) and the parent package was giving us fits so we built the package
against an "older" parent package. We don't need the parent package any
more but we need the updates in the client.

Does this make sense? Can anyone tell me if I am okay doing it this way
(only a stop-gap measure until we get the server package fixed).

Thanks,

OW B73.3.2 SP10
AS400 V4R4
4 - NT 4.0 App Servers
4 - TSE 4.0 App Servers - 100 users total
500 users total

James Wilson
CNC Consultant

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



All views are expressly my own and in no way reflect those of my employer.
 
Memo from Martin Stutchbury of PricewaterhouseCoopers

-------------------- Start of message text --------------------

Just a thought.

When you build and update package, it does update the specs in the parent
package (i.e. merges them).

What it doesn't do (at least under B73.3.2), is recreate the CAB files. *IF*
the CAB files exist (e.g. from a previous
full package build and compression), the installation will install from the CAB
files which DO NOT contain the new specs.

Two work arounds:
1) Delete the cab files and the install will use the spec files (not
recommended because it will really hit your network hard)
2) From package build history, reset the status of the package compression, and
resubmit the build.

Just a thought. Not sure if it applies to your situation without more info.

Cheers

Martin





jdcmwilson <[email protected]> on 01/01/2001 22:41:14

Please respond to [email protected]
To: [email protected]
cc:


Subject: Server Package Builds ~~0:3272



JDE List,

When we build an update package tied to a parent package do the specs on the
server (under the parent package library) get merged during the build
process or only once the package has been deployed?

The reason I ask is because we were building an update package (client and
server) and the parent package was giving us fits so we built the package
against an "older" parent package. We don't need the parent package any
more but we need the updates in the client.

Does this make sense? Can anyone tell me if I am okay doing it this way
(only a stop-gap measure until we get the server package fixed).

Thanks,

OW B73.3.2 SP10
AS400 V4R4
4 - NT 4.0 App Servers
4 - TSE 4.0 App Servers - 100 users total
500 users total

James Wilson
CNC Consultant

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



All views are expressly my own and in no way reflect those of my employer.
--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=3272
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************



--------------------- End of message text --------------------

The principal place of business of PricewaterhouseCoopers and its associate
partnerships is 1 Embankment Place, London WC2N 6NN where lists of the
partners' names are available for inspection. All partners in the associate
partnerships are authorised to conduct business as agents of, and all
contracts for services to clients are with, PricewaterhouseCoopers. The UK
firm of PricewaterhouseCoopers is authorised by the Institute of Chartered
Accountants in England and Wales to carry on investment business.
PricewaterhouseCoopers is a member of the world-wide
PricewaterhouseCoopers organisation.
----------------------------------------------------------------
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any action
in reliance upon, this information by persons or entities other than the
intended recipient is prohibited. If you received this in error, please
contact the sender and delete the material from any computer.
 
Back
Top