gregglarkin
Legendary Poster
Cody,
You wrote to me off-line:"I read in one of your post that you use a test server to deploy your new packages to and then copy the libraries to the production servers. What are the specs on the "test" server? Are you running Win2k adv svr?
Do you run more than one pathcode on a TSE?
"We generally build and deploy a new PY and PD package on our production system three times a month, each."
Cody Bell"
______________________________
Our test terminal server is very similar to our production terminal servers. It is a Win2K, Citrix XP terminal server. It has all of the same service packs and Citrix Feature releases as our production boxes. We have five pathcodes installed; Dev (DV7333), ESU (ESU7333), Pristine (JD7333), Production (PD7333) and Prototype (PY7333). The ESU pathcode is JDE pristine with any and all ESUs and Updates that we have chosen to install. We install ESUs on an as needed basis. We then periodically migrate to major Updates. Currently we are upgrading to Update 6 from Update 2. Praxair does a great deal of custom coding and has made some modifications to JDE code to add functionality that we require or to fix JDE's broken code. Our PY environment is split seven ways, providing separate playgrounds for country or project specific testing and a separate environment for training users.
In addition to our production servers, we maintain a "Global Kernel" set of servers. That set of servers and terminal servers is where we develop custom code that will be used by Praxair globally. Praxair is running Oneworld in North America, South America, Europe, and Asia. We use product packaging to distribute that code to our other IT teams across the globe. We also use the Global Kernel system to test JDE's latest and greatest. Service packs and updates are applied and tested on the Global Kernel enterprise server first, then migrated out to the production and regional "sandbox" servers.
Gregg Larkin
Global CNC, Praxair Inc.
Win 2K, SQL 2K, XE, SP 19.1, Update 6, Citrix XP, XPI 4.5, Cognos E-apps
You wrote to me off-line:"I read in one of your post that you use a test server to deploy your new packages to and then copy the libraries to the production servers. What are the specs on the "test" server? Are you running Win2k adv svr?
Do you run more than one pathcode on a TSE?
"We generally build and deploy a new PY and PD package on our production system three times a month, each."
Cody Bell"
______________________________
Our test terminal server is very similar to our production terminal servers. It is a Win2K, Citrix XP terminal server. It has all of the same service packs and Citrix Feature releases as our production boxes. We have five pathcodes installed; Dev (DV7333), ESU (ESU7333), Pristine (JD7333), Production (PD7333) and Prototype (PY7333). The ESU pathcode is JDE pristine with any and all ESUs and Updates that we have chosen to install. We install ESUs on an as needed basis. We then periodically migrate to major Updates. Currently we are upgrading to Update 6 from Update 2. Praxair does a great deal of custom coding and has made some modifications to JDE code to add functionality that we require or to fix JDE's broken code. Our PY environment is split seven ways, providing separate playgrounds for country or project specific testing and a separate environment for training users.
In addition to our production servers, we maintain a "Global Kernel" set of servers. That set of servers and terminal servers is where we develop custom code that will be used by Praxair globally. Praxair is running Oneworld in North America, South America, Europe, and Asia. We use product packaging to distribute that code to our other IT teams across the globe. We also use the Global Kernel system to test JDE's latest and greatest. Service packs and updates are applied and tested on the Global Kernel enterprise server first, then migrated out to the production and regional "sandbox" servers.
Gregg Larkin
Global CNC, Praxair Inc.
Win 2K, SQL 2K, XE, SP 19.1, Update 6, Citrix XP, XPI 4.5, Cognos E-apps
