Installing PI 7.11 SP04 as High Availability on HP-UX using Service Guard.
I am trying to install a PI 7.1 EhP1 SP04 system on HP-UX as a High Availability system using "Service Guard".
I've read lots of SAP Documents on the PI 7.1 EhP1 Installation for HP-UX / Oracle, and the section on HA installation, but I am still not clear on how this should be installed.
I have Node A and Node B, and the primary host for the PPI system is NodeA.
In "sapinst" I selected the option for "High Availability" to install our system and installed the folllowing instances on NodeA:
ASCS00 (Abap Central Instance)
SCS01 (Java Central Instance)
ERS10 (Replication Enqueue for ABAP)
ERS11 (Replication Enqueue for Java)
DVEBMGS02 (Primary Application)
On Node B:
ERS12 (Replication Enqueue for ABAP)
ERS13 (Replication Enqueue for Java)
Our PPI instance starts and stops fine on its native host, NodeA, but when we fail over to Node B, the Oracle Listener and DB starts up but none of the SAP Components start up.
We have two SAP Licenses installed, one for each Node.
When we fail over to Node B, and try to startup SAP using the following command:
/usr/sap/PPI/SCS01/exe/sapcontrol -prot NI_HTTP -nr 01 -function Start
we get the following Error message:
FAIL: HTTP error, HTTP/1.1 401 Unauthorized
startup of Instance failed
Has anybody installled a NW 7.1 system on HP-UX & Service Guard??
If so, is there a document that describes the process in detail???
Was a SAP HA Plug in required for this to work??
What components, if any, needs to be installed on Node B; i.e. Replicaton Enqueue Server(ERS), Primary Application Server??, etc, etc,
If a "Replication Enqueue Server"(ERS) needs to be installed on Node B, then should it be installed on Local directories?? or should it be part of the Virtual Directory??
Once the ERS is installed on Node B should that be always running?? Or only running when the SAP Application fails over??
Any help would be appreciated.