• 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!

'Normal' ESU procedures

boaterdan

Active Member
\'Normal\' ESU procedures

I've had system admin and package deployment classes. Being essentially the one-man IT department at my company, I've now been thrust into responsibilities for managing all things CNC. We've got a financials apps consultant modelling away, and finding problems (we were on the original installation SP13).

I've worked my way through a couple of ESU's, but I need help in understanding what the normal process would be (per JDE) for deploying them.

When they are installed (to DV) they create two package assembly definitions (DV and PD) and one package build definition (DV) which are meant, I presume, to help you deploy the contents of the ESU to those environments. However, I notice...

1) The build definition is a client-only package. Don't ESU's generally need to be deployed to the enterprise server(s) as well, particularly those with Business function type changes? I'm guessing I'm supposed to modify the package assembly and build accordingly. Yes, no, maybe so?

2) The PD definition doesn't include any objects. What's the point here?

<tongue-in-cheek>I know I have to be missing something because surely software at this level has to be distributed in the best way possible. </tongue-in-cheek>.

Can anyone help?
 

ssolberg

VIP Member
Re: \'Normal\' ESU procedures

I am in much of the same boat and just went through a similar question with JDE. In my case, I had been doing some ESU's and many times I would get to the point of wanting to deploy them and would just get an error report that says "Internal Error". Wow, that helps! As it turns out, we are deploying to PY and I also had noticed the "extra" pkg built for PD but just ignored it. As it turns out, the solution to my problem was to just delete the PD pkg and deploy to PY again. Voila! it worked. Got no explanation as to why this would happen (corrupt records, blah, blah...) but I guess I can work "around" it in the future.

Programmer/Developer/Anything-They-Give-Me
World A7.3 11 (quite stable and usually happy)
Attempting CO with Xe, AS/400, V4R5 (not happy)
 

MagarG

VIP Member
Re: \'Normal\' ESU procedures

Here's the answer to number 1:

See Breaking News document OTM-01-0047 dated 06/29/2001. You need to modify the definition to include the server as you figured out. gman.

As400 V4R5 Xe SP15


I've had system admin and package deployment classes.
Being essentially the
one-man IT department at my company, I've now been
thrust into responsibilities
for managing all things CNC. We've got a financials
apps consultant modelling
away, and finding problems (we were on the original
installation SP13).

I've worked my way through a couple of ESU's, but I need
help in understanding
what the normal process would be (per JDE) for deploying
them.

When they are installed (to DV) they create two package
assembly definitions (DV
and PD) and one package build definition (DV) which are
meant, I presume, to
help you deploy the contents of the ESU to those
environments. However, I
notice...

1) The build definition is a client-only package. Don't
ESU's generally need to
be deployed to the enterprise server(s) as well,
particularly those with
Business function type changes? I'm guessing I'm
supposed to modify the package
assembly and build accordingly. Yes, no, maybe so?

2) The PD definition doesn't include any objects.
What's the point here?

<tongue-in-cheek>I know I have to be missing
something because surely
software at this level has to be distributed in the best
way possible.
</tongue-in-cheek>.

Can anyone help?




--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Ca
t=&Board=OW&Number=15744


----- End forwarded message -----


AS400 V4R5 CO-NT Xe SP15 Oneoffs 002/007/010 JD9533 ESU
Websphere 3.5.3 on AS400 JAS SP15
 
Top