Preparing Systems That Run in High Availability Environment 
If the system is running in a high availability environment you have to consider the following scenarios.
Information about high availability is contained in the various hardware-specific SAP NetWeaver CE installation guides at https://www.sdn.sap.com/irj/sdn/ce (SDN user required).
Make sure that the HA software does not restart the instance automatically during the update.
Except for the case described below, you do not need to make any changes in HA software as it will act transparently.
If the system is running in a high availability envorinment on Windows OS and:
This is a dual-stack system upgraded from SAP NetWeaver 2004
ASCS is not split from the primary application server instance as recommended in SAP note 1011190.
In this case the instance where JSPM will be started will be also under HA control and this could cause problems during offline deployment when AS Java is restarted.
To overcome this, before starting JSPM update, you have to increase the timeout value of the HA software, so deployment can complete without interference from HA software.
Open Cluster Administrator.
In the SAP Group doubleclick on the Cluster Resource SAP <SAPSID> <primary application server instance number> Instance.
Switch to the Parameters Tab.
Remember the current value of Maximum Transition Time.
Set the value of Maximum Transition Time to 6000 (allowed Maximum).
Take the Cluster Resource SAP <SAPSID> <primary application server instance number> Instance offline and online again to activate the change.
Alternatively you can use following command line to change the value:
cluster resource "<complete cluster resource name>" /private AccepableYellowTime=6000
After finishing the JSPM upgdate, reset the parameter to its original value using above described procedure.