Hi PK,
In a dual stack scenario, everything is in one DB using 2 schemas, one for ABAP and one for Java, after the split, it goes to 2 databases, essentially the split would not touch ABAP side, it exports the contents of the Java instance and installs it into a separate instance. I would suggest to use keep database option. disable the Java on the source, make sure the following are tested and then delete the Java schema on the source.
what you should be testing is connectivity, especially java functions
- Make sure SSO from Java to ABAP is working. Since the stack installs the Java stack as new SID, you will need to reimport all certificates from the Java stack to any connected systems.
- Make sure Java related functions are operational, especially custom codes.
- Fix licensing.
- Check the Jco connections and change them to use the new java instance if any.
Once these are tested, you should be able to safely continue upgrade.
regards
Yogesh