CNC :: Server Migration Project

Hi Guys,

We're upgrading several of our JDE Servers, but I cannot find much documentation on what needs to be changed in JDE in order to do this . . .

The servers to be upgraded include our database servers for all non-production databases, some UBE servers, our Enterprise and Deployment servers and our Security server.

Does anyone know of a generic plan / document showing what changes need to be made where?

Our system is EnterpriseOne B733 SP20 running on Windows 2000 Servers.

Any help would be much appreciated.

Thanks in advance,

JB

My suggestion would be to add each new server on a one-to-one basis. Swap out a batch server with it's new counterpart. Add each new server to the enterprise and that way you can bring it up and test it, then just switch over OCM's pointing to the one it will replace and you're good to go. The trickiest one will be the DB server(s), but again, if you add them to the existing enterprise, you should then be able to migrate DB's over one at a time (or in small groups or by path code), until you're on the new server(s).

By using this method, you always have the ability to cut back over to the existing server, as you are essentially just manipulating OCM's...could you have a burp and need to bring the system down...sure, but the impact would be minimal.

Or you can do it the way some would try, start on a Friday night and replace all the machines at once during the weekend, then spend a week trying to fix things...have management and all end-users hating you...become addicted to no-dose and coffee...decide it's just not worth it...quit your job and become an Alpaca farmer...and never worry about E1 again!

[ QUOTE ]
Our system is EnterpriseOne B733 SP20 running on Windows 2000 Servers.

[/ QUOTE ]

What are you upgrading your servers TOO? Keep in mind that SP20 is not supported on 2003 servers and you will likely have to upgrade the Service Pack to even get it to work if you change the OS.

[ QUOTE ]
[ QUOTE ]
Our system is EnterpriseOne B733 SP20 running on Windows 2000 Servers.

[/ QUOTE ]

What are you upgrading your servers TOO? Keep in mind that SP20 is not supported on 2003 servers and you will likely have to upgrade the Service Pack to even get it to work if you change the OS.

[/ QUOTE ]

I agree with Shawn's sentiment but will correct him on the technicality. SP20 will run on Windows 2003. I just set up a server with an even earlier service pack release on Windows 2003. But as soon as I had the server working and stable, I bumped it up to Service pack 23.

Gregg Larkin
JDE System Administrator (CNC) / North America
Praxair, Inc.

No worries Greg. I haven't personally tried running SP20 on 2003 so I can't say for sure if you would or would not eventually run into issues of some sort in regards to the SP / OS level. Technically it is not supported. Although, if the post is correct and they are really on B733??? then they are not supported anyway!

B733 AND W2K...neither is supported. And you two Alpaca feeding wannabe's should know the mantra by now..."Just because it isn't supported doesn't mean it won't, or can't be made to work"...what did they use to call it back in the good old days of B731 and B732...cowboyin'...yippee cay yay...

The Alpaca's have spoken and they have given me the following Sage advise:

See the following attachment on Changing out a Deployment Server

Some caveats:
You do not need to install everything when reinstalling the dep server. Just the Foundation will do. You do not need to restore from tape. Just copy over from the old server. If you are changing the name, be sure to update all the tables.

If changing out the Enterprise Server (assuming no DB) all you really need to do is enter a record in the P9654a for Enterprise Servers, add the environments (from the environments exit) that need access to that server and add Logic Data Sources for System and Server Map. You will also need to install the actual host code on that system.

If your enterprise server contains the DB, you will also have to update your DB Data Sources (assuming that the name of the server has changed).

This is basically the quick and dirty of what you are looking to do. If you want some additional detail, ask me and I will try to get the Alpaca's to share more of their wisdom...

On and Intel Platform that should not be too difficult.

If by upgrading you are referring to replacing the servers with now ones this is not a difficult process. The only one that will require some more detailed attention will be your SQL server, because you will have to migrate your master and MSDB databases over. If you are replacing the old servers with new ones I will recommend that you maintain the same server names.

I recently did this for a number of our servers and did not have any issues at all.

If you are going to be upgrading the existing servers then I would recommend that you get clean complete backups of your JDE folders and databases and rebuilt the servers rather then upgrading, it is much cleaner and will take less time in my opinion because there will be less troubleshooting.

I have some documents that I have created when I upgraded my servers you can contact me for more details, I cannot post them because they have all my system specs embedded - sorry.

Hi Guys,

thanks for all the feedback - the Changing Out a Deployment server document was particularly useful . . .

The upgrade is mainly a hardware upgrade, though after talking to our server ops team, I've found out that we are also upgrading OS to 2003. Unfortuntaly, the powers that be decided that our new servers should conform to the company's naming standards (the old ones are from many years ago before various mergers and take overs, so are completely different), so our DR plan & much of the advice on Oracle's site is not too helpful. My background is as a support specialist/developer on VB, C, Prolog & Web applications, but I recently moved into JDE as a developer (6 months ago), and was asked to take over the CNC role as the former CNC guy recently left & my background included working with servers & problem solving; however I've only had a couple of days CNC training (since 99% of what I do is the routine new user accounts, password resets, killing jobs & deleting citrix profiles).

I have a good overall idea of what needs to be done, but only a very rough idea of the finer details.

We are upgrading the following servers, all of which are changing their names (I've just numbered them here to keep things simple):

S1 :: Security/UBE Server
S2 :: UBE Server (nothing special)
S3 :: UBE Server (Running Create!Form)
S4 :: UBE Server (Containing dev & crp databases)
S5 :: Enterprise/UBE Server (containing test database)
S6 :: Deployment Server

The only JDE server which is not changing is our production database server, which is running UNIX/Oracle 9i. (Citrix servers are also remaining the same).

New Servers

S1 -> SEC (Security & UBE)
S2 -> UBE1 (UBE)
S3 -> UBE2 (UBE with Create!Form)
S4 + S5 -> ENT (Enterprise, NonProd DBs)
S6 -> DEP (Deployment Server)

S4 & S5 are combining so that all of our non-prod databases can be managed on the same machine.

I'd also like to make one of these servers a backup security server; I assume DEP would be best for this since it has the least to do?

Idealy I'd like a step by step document saying "go to menu G98XX, click Work With Servers, etc" if anyone's got anything that detailed? However, I doubt that such a document currently exists (I'll post one once I've learnt what to do though), so any information along those lines would be appreciated.

Thanks again for all your feedback.

Cheers,

JB

Hi,

If you're speaking about JDE Security, your Deployment
can't run as a Security Server, it has to be some of
your Enterprise/UBE servers.
If you're speaking about Windows security (AD), then yes,
your Deployment could be promoted as a Domain Controller,
though Denver strongly recommends not to use JDE servers
for other purposes than the ERP itself.

I will tell you right now that what you are going to do is going to be difficult to pull off if you don't know what you are doing. Changing servers and server names is a pain even for those with a lot of experience. There are a lot of tables that hold the various server names including the Versions Tables (They hold the Deployment Server name), the Object Librarian (F9861 also holds the Deployment Server Name), you need to change your DB Data Sources and Logic Sources, you also need to update the jde.ini files on all servers except the database server as your security server is going to change names.

My suggestion is to really seek some outside consulting (and I truly am not suggesting this as a way to get business as anyone who is experienced can help you) because you could really screw up your system big time.

If that won't cut it, then make sure you backup EVERYTHING. Because there is a good chance that something will get missed. Changing out one server is a hastle. Changing them ALL out is a PROJECT.

[ QUOTE ]
My suggestion is to really seek some outside consulting (and I truly am not suggesting this as a way to get business as anyone who is experienced can help you) because you could really screw up your system big time.

[/ QUOTE ]

As a non-consultant, in the firm "not for hire" category, I agree with Shawn 110% Right now my main project is building a new set of test servers which are a clone, with different names, of my production boxes. It's a whole lot of work, with a lot of behind the scene direct modifications to tables. I have five years of CNC, my boss has six, and there are still bits and pieces that we miss. If you have that little experience in the CNC world, then you will need a whole lot more training, experience and or consulting time to tackle this project. On the plus side, when done, you'll have a pretty in depth knowledge and could eventually join Shawn's ranks as a conslutant.

Gregg Larkin
JDE System Administrator (CNC) / North America
Praxair, Inc.

Though it pains me to have to agree with the two above and haven't been called "firm" in years...absolutely get help. I thought in your initial post you were going to replace old machines with new but keep everything the same. You are doing a OS upgrade, which may or may not cause you to have to put in a new service pack, but you are physically changing machine names, which as the above have told you, isn't a walk in the park in E1. In addition to the advice already given, I would still suggest a one machine at a time approach. Your UBE processing machines would be my first target, followed by a phased DB roll over, and lastly the DS change.

Hi all,

I am taking this opportunity ask the same question: "Does anybody have documentation for changing out the Enterprise Server (AS400)?" Currently, our DV, PY, and PD are all in the same subsystem. We are moving to a new machine, with a new name, and will be putting DV/PY in one LPAR, and PD in another LPAR. Any advice or can someone provide a high level schematic as how this should be done?

thanks for any input.

Recently we have upgraded our OW servers from Win2000 to Win2003. We followed the attached method to upgrade the Deployment server. It was very easy and less time consuming.