Separate install of OW for testing etc

Hi everyone,

We currently have a standard out of the box installation of OneWorld but we have reached a point whereby we require a completely separate installation for testing SP's, security changes, Updates etc etc. My questions to those of you out there who have done this how did you approach it with regard to sizing it etc? Did you have a separate deployment server? What environments / pathcodes did you configure.
Any help would be appreciated.

Thanks in advance,

Maria

Hello, Maria.

You can create an environment SU7333 (with own path code, own data dictionary and control tables) as advise JDE. You can use SU7333 for testing USE, ASU, but not SP.
Secondly you may create second installation (deployment and enterprise servers) for testing only. But you nedd divide licenses between two deployment servers (1-2 licenses for test deployment, other for main installation). You may use not very perfomance hardware for test installation.

https://knowledge.jdedwards.com/sea...ult.asp&SPageName=SimpleSearch&Num=13&Max=200

https://knowledge.jdedwards.com/jde...initial_packages_custom_path_codes_peplau.doc

Hi Maria,

The installation that I help manage took a two-pronged approach. We created an ESU pathcode as a compliment to the Pristine pathcode. Our ESU pathcode is Pristine plus any ESU, ASU, or Update that we are interested in applying. That pathcode contains no custom code.

Our other prong is a completely separate set of servers. That set has it's own Enterprise, Deployment, Terminal, and Web server.

Our process for evaluating any new code from JDE is this:

1) The code is applied to our ESU pathcode on the test servers.
2) If it doesn't break anything, we apply it to the Dev pathcode on that server. We test that against our custom code changes and if it passes, we continue the migration up through PY and PD.
3) If the code from JDE passes all of our testing our test servers, we will then follow the same process on our enterprise system.

One challenge for us, we have modified some core JDE objects to better suit our business. In that scenario:
1) we apply the downloaded objects to our test server in the ESU pathcode.
2) Migrate the object to Dev and make modifications (or take out our modifications).
3) After appropriate testing, we build a product package (essentially our own custom ESU) and apply that object to our enterprise system. We also make that custom ESU available to our other JDE installations in other regions of the globe.

A note on licensing, we have an enterprise license for JDE and a huge number of client licenses.

Test system: XE, Update 6, SP21F, Windows 2000, SQL 2000, Citrix XP, Websphere 4.0

Production System: XE, Update 6, SP21F, Windows 2000, SQL 2000, Clustered Enterprise server, 2 Logic servers, 18 Citrix XP terminal servers, Websphere 4.0, XPIE

JDE installations in: North America, South America, Western Europe, Asia and China

Gregg Larkin
North American CNC