New Enterprise Server

Hello List,

We are expecting the delivery of a new enterprise server and I have been given the task of moving our pre-production and production environments to it.

I have never done this before and as the knowledge jungle is once again being about as much use as a fart in a lift/elevator (depending on which part of the Atlantic you are on) I need your help.

Plan so far, firstly for the pre-production environment:
Add new server through installation plan.
Restore a backup of my database to new ent server.
Copy over the path codes.
Change ODBC and OCM mappings.
Build package and test.

Is this totally rubbish, or does it sound about right? If anyone has any documentation on this, it would be greatly appreciated.

Cheers

Hi CNC KID,

I assume the new server is Windows 2000 and your existing enterprise server is Windows 2000. If this is the case after installing the OS follow these steps:

1. Install Visual C++ 6 and update the Environment variables.
2. Update the hosts file on the new server to reflect the old server. On the old server and the deployment server (and any other OneWorld servers you have in the mix) add a hosts entry for the new server.
3. If you are using local service accounts create these on the new server and make sure the passwords match.
4. Install SQL Server and service packs.
5. Export ODBC's from old server and merge into new.
6. Copy the JdEdwardsOneWorld directory structure making sure to copy the system tree as well as any path codes that will be running on this server. (You do not need to copy logs, temp files, path codes not being used or the contents of printqueue and packages across)
7. Install the jde services on the new server by running jdesnet -i and jdesque -i from ?:\jdedwardsoneworld\ddp\b733?\system\bin32.
8. Update the JDE Services to run under a local or domain account.
9. Modify the JDE.INI on the new server changing the server name where appropiate. Update anything that points to a path code to one that exists on the new server. You will also want to look at the Security server and Lock Manager settings. Make sure the paths and drive letter mappings are correct for the new server don't forget about C++ either. If the system database is staying on the old server do not change anything that points to that. (It is probably easier to modify the old servers JDE.INI file than to start with the fresh INI file that the plan will create.)
10. Transfer the logins and passwords from the old enterprise server to the new. (See MS KB Article 246133)
11. Create and run a plan on the deployment server in JDEPLAN to add the new server. If you create a new Server MAP be sure to create this ODBC on the new enterprise server.
12. Copy or backup/restore the Pre Production and Production databases to the new server. Be sure to leave them off line on the old server so that no one can connect to them by mistake.
13. On the deployment server in Planner and DEP environments update the ODBCs for these environments to point to the new server. Be sure to update the Windows ODBCs when prompted so the the ODBCDatasource.inf file gets updated.
14. Update the windows ODBCs manually on the old and new enterprise server.
15. Start the JDE services on the new enterprise server (If you are using Security server). Run a porttest if it succeeds run some more detailed tests, ie. submitting batch jobs etc.
16. You do not need to run a package build if you copy the path code directories across, but it is worth doing one later to test that it works okay.
17. Manually update the ODBCs on clients or deploy a package to them to update the new mappings for the Pre Production and Production environments. Also for the new enterprise server map datasource if you created one.

This should get you up and running there are a few shortcuts you can take but this should be okay. If I have left anything out then someone else please chip in.

Cheers,

Jack.

OneWorld ERP8 SP 21
iSeries 830 4 Way.

Your plan is sound. However, if you are replacing the enterprise server,
you also may wish to consider another alternative, especially since your
ES is W2K. You can do the following...

- Install OS and SQL on new server, use the same name as the replaced ES
- Install OW on the new ES
- Perform a restore of the SQL DB to new server
- Copy the JDE.INI from old to new ES
- Add all needed ODBC connection to new ES (I generally perform a
registry export on the old and import to the new)
- Turn off and disconnect the old ES
- Turn on and connect the new ES

This method doesn't require any installation plan, no changed
OCM's...basically it's performing a DR process if the ES would ever go
bye-bye. The nice thing about this, is should the new ES have
catastrophic problems, you can turn off and disconnect it and reconnect
the old and be back in business again without needing to change anything
within OW itself.

Of course, none of the above will work if you need or want to have both
servers running concurrently. If that is the case, your process below is
what you'll need to do.

Regards,

Jim
On Wed, 23 Apr 2003 02:37:32 -0700 (PDT) The_CNC_KID

We are expecting the delivery of a new enterprise server

I have never done this before and as

Plan so far, firstly for the pre-production
Add new server through installation plan.
Restore a
Copy over the path
Change ODBC and OCM mappings.
Build package and test.

Is

Cheers

________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!

Hey John,

I've done this exercise 5 or 6 times. It looks like your on the Intel
platform. I've changed out 3 Intel Enterprise servers. I was able to
accomplish the like this.
1. Obviously, back-up everything under the sun.

2. When the new hardware comes in, pull the original Enterprise
server off the network or at least give it a new name. "You want to
give the new server the same name as the old server.

3. Install the new Enterprise server just as if it was a brand
new install.

4. After the install is complete, SQL in the database info from
the old server and also copy in the path codes from the old server,
obviously overwriting the path codes from the fresh install.

5. I think that when I've done this in the past I also had to
change out the Deployment Server at the same time which made the process
easier/cleaner.

6. Pitfalls: It does not look like you'll be changing out the
Deployment server, so you will have to create a new plan to add the new
server if the name of the new server is going to be different than the
old one. I kind think that you only need to run the plan if the new
server is going to have a different name. Also, one time when I copied
in the data from the old SQL2000 DB to the New SQL2000 DB I lost the
indexes for the SYSb7333 data source? It probably was an error on my
part. All I had to do was go in to JDE and rebuild the "Indexes" for
the tables that didn't have them. Outside of this, what you included in
your post is just about all there is.



Brian G. Garity
JDE Sys. Admin/Developer
920-478-2191 ext. 2183
[email protected]



Brian G. Garity
JDE Sys. Admin/Developer
AS/400 Citrix DSI NTApp Server

Thanks Guys,

All your help has been greatly appreciated.
Jack can I ask why do you install C++ onto the enterprise server?

John :

You need C++ on the Enterprise Server to compile server packages.

Regards, Sebastian Sajaroff

-----Mensaje original-----
De: The_CNC_KID [mailto:[email protected]]
Enviado el: Jueves, 24 de Abril de 2003 07:20 a.m.
Para: Sajaroff Sebastián
Asunto: Re: New Enterprise Server


Thanks Guys,

All your help has been greatly appreciated.
Jack can I ask why do you install C++ onto the enterprise server?
Windows 2000 SP2 and SQL 2000 SP2
JDE Xe Sp18 and Update3
--------------------------
To view this thread, go to:
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=53685
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list/forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+
----------------------------------------------------------------------------
Strictly Personal and Confidential.
This email may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.Thanks.
.
Este mensaje es confidencial.
Puede contener informacion amparada por el secreto profesional. Si usted ha
recibido este e-mail por error, por favor comuniquenoslo inmediatamente via
e-mail y tenga la amabilidad de eliminarlo de su sistema; no debera copiar
el mensaje ni divulgar su contenido a ninguna persona. Muchas gracias.
----------------------------------------------------------------------------

You will need C++ on the enterprise server to build server packages on it. You also need some DLLs from C++ to run OneWorld on the enterprise server, I can't remember which ones in particular now.

Cheers.