Separate production and development servers

Dear Listers:

Are any of you running separate servers for development and production with
each machine having its own System tables and security server?

I'm trying to separate the production and development environments logically
and physically as much as possible without affecting our ability to promote
objects into production.

Regards,
David

Brightpoint NA
Sun/Oracle 8.1.6 / Citrix Xe base Sp15.1 live
Update 4 / SP18.1 sandbox

Hello, David,
I made this separation. Piece of cake, provided you prepared a very accurate
and thorough plan, including a backup
We have two systems. From time to time I refresh my test system with the
production data. Check the KG for documents like 'Changing deployment
server', etc. For table updates you can use my script. It worked fine in
B7332 release. I think it will work in XE as well, but I do not guarantee.
The database name is the same for both systems. If you are going to have
different ones, check other columns of the tables. Should you have two
servers in your system you will have to delete some records. You will have
to update JDE.INI files on both servers, including jde.ini in misc
directory. You will have to update access files on the deployment server as
well.

The script itself:

update sysb733.f00942 set emmkey='HQNTERP2' where EMMKEY='HQNTERP';
update sysb733.f00945 set rmmkey='HQNTERP2' where RMMKEY='HQNTERP';
update sysb733.f00945 set RMJOBN ='HQNTERP2' where RMJOBN ='HQNTERP';
update prodb733.F983051 set vrmkey='HQNTERP2' where vrmkey='HQNTERP';
delete objb733.f9861 where simkey='HQNTERP2';
update objb733.f9861 set simkey='HQNTERP2' where simkey='HQNTERP';

update SVMB733.F986110 set JCEXEHOST='hqoradev' where JCEXEHOST='hqoraprod';
update sysb733.f98611 set omsrvr='hqoradev' where omsrvr='hqoraprod';
update sysb733.f98611 set OMDATP='HQORADEV' where OMDATP='HQORAPROD';
update sysb733.f98611 set OMDATP='HQORADEV - B733 Server Map' where
OMDATP='HQORAPROD - B733 Server Map';
update sysb733.f98611 set OMDATP='HQORADEV - Logic' where OMDATP='HQORAPROD
- Logic';

update svmb733.f98611 set OMSRVR='hqoradev' where OMSRVR='hqoraprod';
update svmb733.f98611 set OMDATP='HQORADEV' where OMDATP='HQORAPROD';
update sysb733.f986101 set OMDATP='HQORADEV1' where OMDATP='HQORADEV';
update sysb733.f986101 set OMDATP='HQORADEV' where OMDATP='HQORAPROD';
update svmb733.f986101 set OMDATP='HQORADEV' where OMDATP='HQORAPROD';
update sysb733.f986101 set OMJOBN='HQNTERP2' where OMJOBN='HQNTERP';
update sysb733.f9650 set MMMKEY='hqoradev' where MMMKEY='hqoraprod';
update sysb733.f9650 set MMMKEY='HQNTERP2' where MMMKEY='HQNTERP';
update sysb733.f9650 set MMDATP='HQORADEV - B733 Server Map' where
MMDATP='HQORAPROD - B733 Server Map';

Good luck.

Regards, Alex Shevchenko

XE SP18 Oracle 8.1.7, Solaris production
XE SP18 Oracle 8.1.7, Solaris test

David,

I have done this a few times. When doing it prior to XE you need to share the Object Librarian tables between Dev and Prod. With XE you also need to share all associated OMW tables. Everything else including the Data Dictionary can be split. Of course this introduces some additional maintenance points such as promoting data dictionary items between your Dev and Prod "Instances".

The choice of which instance to use to host your OL/OMW tables is important. For me the obvious choice is your production instance. That way you know your Production system will always have access to them.

Regards,

Alex-

Thanks for your reply. From the script it appears that you made a copy of
the system tables from the production box to the development box and ran the
script against the development box. A few questions to clarify your setup:

Does each system have its own security server?

Are your CO on the deployment server? (It appears that having them on the
same machine would circumvent any object promotion issues across the Unix
boxes and speed up package builds on the DS)

Where are your Data Dictionary and OL? (Just one DD I suppose - no?)

There are System tables for OMW - did you have to make adjustments to these
at all? With CO on the DS, again, I suppose this would probably not be an
issue.

Finally, if either the development or production boxes bites the dust, how
is your functionality limited on the remaining box?

Regards,
David

Hello, David,
Yes, each system has its own security server. The systems were completely
separated. They don't know each other. They don't even suspect. Each of
the system has its own security/enterprise server, Oracle instance,
deployment server, DD, OL, etc. If one of the systems goes down, it doesn't
affect another one at all. Most users use the production system. The test
system is in use for testing only, i.e. XE upgrade, when it was screwed,
wiped out and restored several times. The real upgrade took several hours
and didn't give me trouble. )


Regards, Alex Shevchenko

XE SP18 Oracle 8.1.7, Solaris production
XE SP18 Oracle 8.1.7, Solaris test

Thanks again, Alex...

How do you promote objects in OMW across the systems? [Product Packaging? No
custom mods?]

For code fixes you can install to each system separately but any custom mods
would have to be done twice. Do you have two full sets of
environments/pathcodes? [Can I have your budget and procurement departments
:=) ?]

Regards,
David

Hi Alex,

You mentioned you have 2 separate systems for JDE, Oracle and Solaris.
Please explain how you addressed the licencing issue.

Regards,

Gopal
XE U1, SP19.1, Oracle 8.1.6.3.0, Solaris 7

Hello, David,
Yes, each system has its own security server. The systems were
completely
separated. They don't know each other. They don't even suspect.
Each of
the system has its own security/enterprise server, Oracle instance,
deployment server, DD, OL, etc. If one of the systems goes down, it
doesn't
affect another one at all. Most users use the production system. The
test
system is in use for testing only, i.e. XE upgrade, when it was
screwed,
wiped out and restored several times. The real upgrade took several
hours
and didn't give me trouble. )
Regards, Alex Shevchenko
XE SP18 Oracle 8.1.7, Solaris production
XE SP18 Oracle 8.1.7, Solaris test
--------------------------

Re: RE: Separate production and development servers

In situations like this you will need to have two separate groups of licenses, one for prod and one for dev. You can work with your engagement manager to get JDE to split your current pool up or you will have to purchase extras for dev.