Question
Things to be taken care of when OS changes from 2003 to 2008 R2
Currently, I have a number of business streams (applications) sitting on pega 6.1 platform. Sitting on Windows 2003 server (Web (IIS), app and archive). Servers are getting upgraded from 2003 to 2008 R2. Planning to use Mixed federated Node feature of IBM WAS to replicate the configurations details from old servers to new server, inorder to reduce the down time. WAS version will remain the same. No code change. No functional change in any of the applications. Also, user domain and service accounts domain remain the same. Please advise what is the testing scope for this considering unit, System, System Integration and UAT, Performance and volume testing. There are around 35+ upstream applications interationg with Pega applications built on Pega 6.1.
What are the areas to be focused durng testing?
What is the optimum recommended way of tetsing the migration?
Thanks,
KG.
H Kevin,
Thanks a lot for your comments.
WAS is supported. Version 7.0.1 is on the current system. It will remain the same.
On point 4 - DB is on a separate server. No change in DB server. This has already been migrated to windows 2008 few months back.
Inorder to do reduce the production downtime due to server upgrade, implementation approach is planned to use mixed federated node feature of IBM WAS.
As per this, within the same cell, nodes running on different OS can sit. Then configurations will be replicated from the old server to new server.
There will be the following 3 phases:
Phase 1:System runs on Old servers
Phase 2: add new server anlong side old server, keep on adding new servers.
Changes will be done in DMGR. Configurations will be replicated automatically. Minimum configurations will have to be done manually.
Phase 3: keep on removing old servers..Final stage is only new servers.
If you have any idea on what needs to be tested for mixed federated node configurations, please provide that details.
Thanks a lot.
KG.
KG,
I will add some of my thoughts as more people can weigh in.
1. I have checked pega platform guide, windows 2008 is supported for pega 6.1, so no worries there.
2. Make sure your version of WAS is supported by IBM for windows 2008. I assume you have already checked on this.
3. In theory, your applications should just work. Your integration with other systems should not even care about the underlying OS change.
4. Without knowing your normal testing scope, I would run some critical business scenario tests for each application and focus on the performance testing (I assume you already have something setup and you can simply kick off the run once the systems have been upgraded to new OS).
5. Curious, is your database affected by this upgrade? or it is on a separate server?