Dual Stack: JAVA Stack Removal including Multiple Dialog Instances
Scenario: Customer was running SAP ECC as dual-stack system. Dual-stack split was mandatory requirement to perform SAP ECC 6.0 EHP7 upgrade.
Customer migrated business processes running on JAVA stack to SAP Fiori!!
Now JAVA stack was good to be uninstalled!
We had 2 options to perform the Dual-Stack Split.
1.Split Dual Stack into ABAP Stack and JAVA Stack
2.Removal of JAVA Stack
We used the "Remove JAVA Stack option", as customer don't need it anymore.
Below are details of JAVA Stack
JAVA stack contains 1 SCS, 1 Central Instance and 3 JAVA application servers.
Currently running JAVA instances can be checked in SM51.
We used "Keep Database option" in SWPM means we just removed the JAVA instance but we didn't delete the JAVA Schema.
We followed below sequence to delete the JAVA Stack and time it took to complete the activities.
|1||JAVA DB Export||1 Hour|
|2||JAVA Central Instance Export||30 mins|
|3||Removal of JAVA Central Instance||15 mins|
|4||Removal of Dialog Instance 1||15 mins|
|5||Removal of Dialog Instance 2||15 mins|
|6||Removal of Dialog Instance 3||15 mins|
|7||Removal of SCS instance||15 mins|
1.Stop JAVA on all the JAVA nodes using without restart option.
2.Backup the profile directory. (/sapmnt/<SID>/profile/)
1. JAVA DB Export (Optional) : This step was not mandatory in our scenario.
2.Export of Central Instance (Optional) : It was not mandatory in our scenario.
3.Removal of JAVA- Central Instance
- j2ee directory will be removed and can be cross verified at OS level.
4. Removal of JAVA Dialog instances : (To delete multiple JAVA dialog instances,repeat this step on each JAVA dialog node.)
Please follow rest screen shots shown in "Point no 3" for Dialog instance removal.
5.Removal of SCS Instance : Last Step
- All the profile files belonging to SCS instance will be deleted now.
Finally, all the JAVA instances are being removed , can be cross checked from SM51 and now good to start for SAP ECC 6.0 EHP7 Upgrade.
After all steps, please manually cross check parameter j2ee_start = 0 is set in all the profile files.