Multiple Production Environments

We are using a Co-existence strategy in moving to XE. In World, we have
multiple production environments (some with multi-currency, some not).
These environments have their own data and common libraries but share
objects. Can this be done in OneWorld? We are particularly concerned about
ongoing maintenance.

TIA.....Gerry



World 7.3, Cum 10
Moving to XE, AS/400, Coexistence, HTML

Gerry
Works well.
The real bore is that instead of setting up a LIBL record you have to create OCM
mappings and multiple sets of them - for Thick clients, Citrix clients for both
Servers and Interactive. The cheat way of doing this is to get the mapping right -
manually - and then copy the F986101 records using SQL or CPYF. When you need to
change the name of the environment copy the records out to a work file and change the
environment name. Look at the standard environments to see how to tweak the
environments once copied. For example the Citrix environments map to their Business
Functions to AS400.
Brgards
Robert Fletcher
DHL
AS400 V4R4
OneWorld 7.3.3.2 SP15.1
Citrix and JAS

GMunchel wrote:

Hi Gerry,

yes, you can share object specifications and code between environments but have different data sources. OW is pretty flexible about that.

Regards,

Larry Jones
[email protected]
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials

We do realize multiple production environments can be accomplished, but a
big concern is what happens to the upgrade process. We understand from our
technical consultant doing our first XE install, that major upgrades and
ASUs only recognize the "standard" JDE environments. Is there some
hopefully easy strategy that we can employ now for multi-production (and
also multi-test and multi-prototype environments) that will minimize the
upgrade pain when major updates or ASUs need to be applied?

TIA again...Gerry




World 7.3, Cum 10
Moving to XE, AS/400, Coexistence, HTML

Hi Gerry,

You only apply ESUs and ASUs to pathcodes... not to environments, this will
cut down a lot. If it's a small ESU you apply to one, test it and then
build a project and promote it to the others. If it's large then it's
easier to apply the ESU to each environment once it's been thoroughly
tested.

I hope this is what you're asking, I'm not sure...

Lori
OW Xe SP16 Update 2
AS400 V4R5
NT
Citrix
email: [email protected]