cancel
Showing results for 
Search instead for 
Did you mean: 

New Install of MSCS for an Upgraded Abap System

Former Member
0 Kudos

We are currently on NW04S ECC 6.0 on WAS 700 in a MSCS, Oracle 10g. Our problem is that we are moving to new hardware and our current system uses the old MSCS (which is an upgraded system originally installed at 4.7 640 (perhaps earlier (4.6c)), which to me means that the Central Instance resides in the MSCS in the SAP Group. Our plan is to install a clustered system and do a DB restore or copy over to the new hardware. I have done the install and realize now that the ABAP MSCS install for NW04s ABAP creates the cluster a little differently – in that it looks like the Java (Portal) cluster. Only the SCS and enqueue are in the MSCS and the CI and all Dis are outside of the MSCS. This creates a problem for me in that the SCS is using the 00 system number, that on our old system the CI had, so our gui is now pointing to what would be the wrong system number, as it looks like the gui must point to to the CI system number for connection to the message server. So, I guess this means a reinstall for me and switching the system numbers. I also don’t know exactly how high availability would be created in this new setup unless you put an application switch in front of your CI and Dis, like you would with the Portal, to direct gui requests. With the old MSCS the cluster would know if the CI failed and move it to the other node, but since it resides outside of the cluster, you have to have some type of external director – right?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This system is ABAP only. I have done some research since I posted this and found that there is, in fact, a new architecture for the MSCS as of NW04S wherein the CI is not in the MSCS as it used to be in NW04 and before. Also, the ASCS is now a cluster component. So, really this all looks a lot like a Java (Portal) installation on MSCS. I am not sure why you connect with the gui to the CI instance and not the message server (ASCS (00 in our case)). My problem is now I have to go back to NW04 640 to get the cluster architecture that I need as we don't have time to test the new architecture before this hardware upgrade. I will have to then upgrade Oracle (9 to 10) upgrade R/3 (ECC), Kernel change really and then do a system restore fromt the current system to the new system. Any ideas or thoughts on this ugly (time constrained and mostly my fault) situation?

Thanks.

former_member433984
Active Contributor
0 Kudos

Hello Jack,

even you have upgraded from 6.40 to 7.00 you will need to convert to new HA structure according the note 1011190 to avoid the problems with next upgrade. In 700 the CI and DI are not the SPOF (see also

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b8cd93-f1e9-2910-c186-86bfff3dac63">here</a>) and you can configure logon groups via the message server.

In case of hardware change better to take the system copy guide and install new HA architecture - it will save you manual conversion (SAP note 1011190).

best regards

Answers (1)

Answers (1)

former_member433984
Active Contributor
0 Kudos

do you have Java add-in or you run pure ABAP system?