Inverso
Member
Hi Guys,
my company's about to upgrade the servers that OneWorld runs on, but before we go ahead with any changes we'd like to check incase other people have had problems (just so we know what to expect).
We are running a heavily customised version of JDE OneWorld B733 SP20. Our current system consists of an Oracle 8i database sitting on SunOS 5.8 for the production database, and oracle 10g on a windows 2k server for our non live databases (we're using a different version of oracle here so that we could see what oracle 10g was like over a long period of time before risking moving prod). This server is run as a test enterprise server (i.e. used for running UBEs in non live environments as well as the non live databases). We have an additional 4 Application servers and 4 citrix servers which also run win 2k server. Citrix is always kept up to date in terms of version & service packs for both clients & servers. Only our developers and analysts use FAT Clients, all running Windows XP.
Our proposed new system will see all servers changing to win 2k3 server (including the prod database), and will use oracle 10g for both production and test databases. We are keeping the configuration exactly the same in terms of number of servers & their roles. Because of the amount of customisation involved, we're hoping to avoid installing additional service packs. Since there is no oracle 10 DLL, we will be using the JDBOCI90 DLL. Our FAT client machines will also be upgraded to servers running Win 2k3 server (since the new system is located off site). To get around checkout issues we'll be using the OWDEVELOPER=TRUE JDE INI setting on these clients.
To avoid issues the plan is to setup the entire system & ensure that it is running & stable before migrating the business data across & repointing the citrix clients to the new servers.
If anyone can see any huge errors or likely pitfalls, I'd be grateful for your advise.
Kind regards,
JB
my company's about to upgrade the servers that OneWorld runs on, but before we go ahead with any changes we'd like to check incase other people have had problems (just so we know what to expect).
We are running a heavily customised version of JDE OneWorld B733 SP20. Our current system consists of an Oracle 8i database sitting on SunOS 5.8 for the production database, and oracle 10g on a windows 2k server for our non live databases (we're using a different version of oracle here so that we could see what oracle 10g was like over a long period of time before risking moving prod). This server is run as a test enterprise server (i.e. used for running UBEs in non live environments as well as the non live databases). We have an additional 4 Application servers and 4 citrix servers which also run win 2k server. Citrix is always kept up to date in terms of version & service packs for both clients & servers. Only our developers and analysts use FAT Clients, all running Windows XP.
Our proposed new system will see all servers changing to win 2k3 server (including the prod database), and will use oracle 10g for both production and test databases. We are keeping the configuration exactly the same in terms of number of servers & their roles. Because of the amount of customisation involved, we're hoping to avoid installing additional service packs. Since there is no oracle 10 DLL, we will be using the JDBOCI90 DLL. Our FAT client machines will also be upgraded to servers running Win 2k3 server (since the new system is located off site). To get around checkout issues we'll be using the OWDEVELOPER=TRUE JDE INI setting on these clients.
To avoid issues the plan is to setup the entire system & ensure that it is running & stable before migrating the business data across & repointing the citrix clients to the new servers.
If anyone can see any huge errors or likely pitfalls, I'd be grateful for your advise.
Kind regards,
JB