This past weekend we implemented a Microsoft Cluster for High Availability of our ABAPJava Netweaver04 system. Now when we first started this project about a month ago, I would never had thought it would make the subject of a weblog. I figured this process was already well documented and would a walk in the park to implement. After all we were hardly the first people to implement SAP in a Cluster environment. It turns out this was quite true until about half way through the process when we hit the J2EE Add-in installation. From there things got quite a bit more complicated and more than a little fuzzy. Therefore I thought I would pull together our notes to help out anyone else who might be considering this process. Even if you aren’t running your system on the Microsoft platform or you aren’t considering a HA (High Availability) solution, you might want to read only. If nothing else you will get an overview of the many parts and pieces that can be combined in just an ABAPJava Netweaver04 system.
Please note that during our go-live weekend, we had a relatively small downtime window. Because of the rush, we took decent notes, but didn’t get that many screen shots. Therefore my screen shots are combination of ones from the development system (which we also clustered), the actual go-live, and after the fact captures. Therefore don’t be confused by the mixture of host names and virtual names that you might see.
We opted to go with a two node cluster layout. In normal operation, our MS SQL database will run on one physical node. The SAP central instance will run on the other physical node. However the hardware of either node is big enough to run all the software in a fail over situation. Each node was a 3.2 GHz Dual Processor with 5 Gigs of memory. The following shows the physical and virtual services that we will have in the cluster.