Administration of shadow instance

In SAPehpi a shadow instance is created that runs in parrallel to live instance while you implement the modification adjustment (SPDD) and then start the activation.The last activity of shadow instance is the removal of activation error.

There are situation in which you need to intervene the installation routine like starting,stopping,locking and unlocking of shadow instance.

Starting the shadow instance
-----------------------------------
Go to installtion directory /EHPI/ABAP/BIN. Use the command ./SAPehpi startshd start the shadow instance.

Stopping the shadow instance
-----------------------------------
Go to installtion directory /EHPI/ABAP/BIN. Use the command ./SAPehpi stopshd stop the shadow instance.Note that shadow instance only runs between the phases STARTSHDI_FIRST and STOPSHDI_LAST.Logging on to the shadow instance is only for modification adjustment and removing activation error.

Unlocking the shadow instance
--------------------------------------
A manual unlocking of the shadow insttance is required for removing the activation error.
cd /EHPI/abap/bin
./SAPehpi unlockshd <SAPSID>

Locking the shadow instance
-----------------------------------
Manual locking of shadow instance is imperative after the manual unlocking before you continue the installation routine.
cd /EHPI/abap/bin
./SAPehpi lockshd <SAPSID>

Unlocking the system and the development environment
--------------------------------------------------------------------
In exceptional cases( for example support cases) you must unlock the instnce and undo a transport lock, if refquired . To do this call the following commands

tp unlocksys <SAPSID> pf=<path to transport profile >/tpprofile
tp unlock_eu <SAPSID> pf=<path to transport profile >/tpprofile

Use this command only if the support team explicitily request you do so.
The unauthorised import of transport after an official lockins of the development env by EHPI means that you can bring your system to an incostitent state, you may lose your support claim.

Locking the system and the development environment
-----------------------------------------------------------------
Always lock your system again before you continue the installation routine using the command

tp locksys <SAPSID> pf=<path to transport profile >/tpprofile
tp lock_eu <SAPSID> pf=<path to transport profile >/tpprofile