Restoring a Server Package

cnc__guy

cnc__guy

Well Known Member
JDE List,

I have an ES that was created by copying another ES and this "copy" has
never actually had a Server Package deployed to it.

In the next day or two I will be attempting to deploy a Server Package to
this "new" ES and I want to know what to do if the package fails and
corrupts the "package" that is on there already.

This ES is on 2000 Server with Oracle 8i. What do I backup / restore
should I have problems with the package deployment? Is it just the bin32
and spec directories on the ES?

Please advise.

Thanks,
James

James A. Wilson
PricewaterhouseCoopers Consulting
JDE CNC Consultant
 
Yes, to backup your current package in case your server package deployment bombs, grab the bin32 and spec directories under \JDEdwardsOneWorld\ddp\b7333\<path code>.
 
James,
as a test if your new ES is properly installed first submit any UBE and
see if it runs. Make sure the new Logic Datasource (your ES´s name) is
defined in System as well as Planner.
After that, the package should build ok on your new ES.
You may have problems when you try to deploy it. Go to GH9083, Machine
Identification, add your new server´s name under Enterprise Server,
double click on it, go to Form/Environments and type in the environments
you want to run on that ES. That should do it.

Why are you so worried about a backup? In case of any foul up, do another
copy/paste from your original ES as you did in the first place.

Good luck, Gerd
 
Hi Gerd
Good Reply. I followed the same path that you described when I copied environment from one ES to another. The only problem I faced was that when I try to build the update package on the new ES server( If I remember it correctly the problem was not able to find New_ES name.inf file in the Full package name directory). The Old ES name was associated with the old package. Is there any way to connect the the new ES name with the current old packages( May be renaming Old ES.inf file) OR we should do the full package build whenever we move envionments?
 
Vivek,
I´m not so sure exactly when OW let´s you build an update package to an
ES that has been created by copying the whole JDE folder from another ES.
One of the problems I had was that the package assembly worked fine, but
during build the new server´s name (logical datasource) was not found in
the planners data source master (F98611).
I think that the package assembly and build definition do not depend on
any package.inf file at all. Only during the actual build of the update
package, the parent package´s folder must exist on the target machine.

Since this method of building a new ES is a bit "off the book" maybe it´s
a good idea to build a full package first on the new ES anyway.

Thansk, Gerd
 
Back
Top