SP12+ and MSCS installation

Question

Has anyone succeeded in applying SP11/12/13 to a MSCS clustered portal installation? If so how?
We have successfully installed an MSCS/MSSQL out of the box SAP Web AS 6.40 + EP6 + KMC Nw04 SR1 (==SP9) according to the documented procedure.
However when I try to install SP12 (initially for WebAS/J2EE) SAPINST determines that the installation it is installing in to is non standard (correct!) and falls over failing to access the secure file store (which is not on teh central instance in a clustered instalklm but on the central services instance).
What is not clear (from SAP documntation) is, is there a product_ha.catalog equivalent for sapinst call, or can we use the out of the box SP9 product_ha.catalog parameter file for the SAPINST call whilest installing SP12.
I would practice this --- but unfortunately I am running this up against a production system and dont really want to cause more damage (work) than necessary.
Thank you

Answer 1

Hello,
apparently this is due to a fault in the control.xml file checking the wrong location for the secure file store during sapinst.
A fix from SAP helps in our situation of WebAS SP9 --> SP12 on MSCS clustered WebAS.
1. start sapinst on CI host , and run the user dialogs unitil it breaks.2. stop sapinst
3. go to .\program Files\sapinst_instdir\... and open the
control.xml file
4. search for "dCheckParameters" string
inside of the java script you have to update just the 2 lines
starting with :
context.set("secFilePath... and context.set("secLibPath...
So the correct lines should be:
context.set("secFilePath", "
<SCSVirthostName>
sapmnt
<SID>
sys
global
security
data");
context.set("secLibPath", "
<SCSVirthostName>
sapmnt
<SID>
sys
global
security
lib
tools");
replace <SCSVirthostName> with SCS virtual host name and <SID> with
your SAP System ID.
This will set the correct values for "secFilePath" and "secLibPath"