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

ow:Testing SP in other environments

Tricia_Rosas

Active Member
OW B733.2/SP11.1/AS400/WNNT4.0 SP5/SQL Server 7.0 central objects

What would be the procedures on testing a Service Pack in another
environment like CRP. We would like to test these SP before putting them
in production, instead of a problem occurring and then rolling back to
older version. I am not sure if this is possible, because we only have one
deployment server with B7332, with one system folder which is the SP we are
using now SP11.1. My understanding is that when you build a new package in
that environment it will pickup the SP from the system folder not matter
what environment you are in, maybe we need to test the SP in CRP and not
build a full package in prod for at least a week so it will not pickup the
latest SP, kinda scary because one my pass us by and a user could be using
the new SP while everyone else is using the old one.

Then the AS400, we would need to install on the Enterprise Server, and I
believe that all environments will be using the SP immediately. Any
suggestions would be helpful on how you handle these new SP in a testing
environment.

Thanks,

Tricia Rosas
Edwards Cardiovascular Resources
Assoc. Technical Specialist
(Email) tricia_rosas@edwards.com
 

SSAJAROFF

Reputable Poster
RE: Testing SP in other environments

Tricia :

You're right, you can't install SP for just one pathcode.
After installing SP on the Deployment, it alters System, SystemComp and
OneWorldClientInstall folders; these
folders are shared by all the pathcodes.
The same for the Enterprise server.
Nevertheless, you may have an Enterprise running on SP xx.x and another
running on SP yy.y, I don't know how
stable is this.

Correcto, no se puede instalar SP para un sólo pathcode.
Luego de instalar SP en el Deployment, altera los directorios System,
SystemComp y OneWorldClientInstall, éstos están
compartidos por todos los pathcodes.
Lo mismo ocurre en el Enterprise Server.
Sin embargo, puedes tener un Enterprise corriendo con SP xx.x y otro con SP
yy.y; no sé cuán estable puede ser éso.

Sebastian Sajaroff
ssajaroff@grupoassa.com
Application Software SA
Argentina


-----Mensaje original-----
De: Tricia_Rosas [mailto:Tricia_Rosas@edwards.com]
Enviado el: Jueves 14 de Diciembre de 2000 18:39
Para: jdelistml@jdelist.com
Asunto: ow:Testing SP in other environments ~~0:2747


OW B733.2/SP11.1/AS400/WNNT4.0 SP5/SQL Server 7.0 central objects

What would be the procedures on testing a Service Pack in another
environment like CRP. We would like to test these SP before putting them
in production, instead of a problem occurring and then rolling back to
older version. I am not sure if this is possible, because we only have one
deployment server with B7332, with one system folder which is the SP we are
using now SP11.1. My understanding is that when you build a new package in
that environment it will pickup the SP from the system folder not matter
what environment you are in, maybe we need to test the SP in CRP and not
build a full package in prod for at least a week so it will not pickup the
latest SP, kinda scary because one my pass us by and a user could be using
the new SP while everyone else is using the old one.

Then the AS400, we would need to install on the Enterprise Server, and I
believe that all environments will be using the SP immediately. Any
suggestions would be helpful on how you handle these new SP in a testing
environment.

Thanks,

Tricia Rosas
Edwards Cardiovascular Resources
Assoc. Technical Specialist
(Email) tricia_rosas@edwards.com




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
2747
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 
Top