http://scn.sap.com/community/netweaver-as/blog/2013/08/26/upgrade-of-kernel-from-711-to-721-ext-on-a-pi-71-ehp1igsexe.sar and igshelper.sar.DBATOOLS.SARSAPHOSTAGENT. delete the call of the program SAPOSCOL from all the start profilesunregister all standalone CCMS agentsSave the following files and directories:For Java or Dual-Stack systems: the directory jvm or sapjvm* (e.g. sapjvm, sapjvm_4, sapjvm_5, sapjvm_6).the file protect.lst if it existsthe icu libraries (libicu*30. or libicu*34. if they existCheck file permissionsOracle only: check permissions for BR* tools according to Notes 113747 and 1598594.ICM: if using ports < 1024, check Note 421359.For Dual-Stack systems:cd /usr/sap///worksapcpe pf=/usr/sap//SYS/profile/If your system is running with the SAPJVM:sapcpe pf=/usr/sap//SYS/profile/ source: list:/sapjvm_.lstOnly necessary for a dual-stack system: you must set the following parameter in the default system profile DEFAULT.PFL:system/type = DSFor dual-Stack and Java-only systems: in all (Dnn, DVEBMGSnn, Jnn, JCnn etc.) instance profiles, you must set the following parameter:FN_JSTART = jcontrol$(FT_EXE)Copying executable file from NetWeaver RFC SDK 720.The program rfcexec (UNIX and IBM i) is no longer shipped together with SAP kernels 720 and 721 which might break some application scenarios. it is mandatory to move to a new version of these files, contained in the NW RFC SDK 720. Please refer to SAP Notes 1581595 and 1025361 for detailed instructions and further information.Due to the situation described in note 1517379, you have to set the profile parameterrslg/new_layout = 9.deactivate it by setting the following parameters:rdisp/wp_no_restricted = 0rdisp/configurable_wp_no = 0rdisp/dynamic_wp_check = FALSErdisp/wp_max_no = Sum of:( rdisp/wp_no_dia + rdisp/wp_no_vb2 + rdisp/wp_no_btc + rdisp/wp_no_vb + rdisp/wp_no_spo + rdisp/wp_no_enq ).Mind that rdisp/wp_max_no has the default value DEFAULT, which will add two unwanted dynamic processes if not set the number of configured, classical wp types.On all UNIX/Linux platforms with deactivated interactive user logon for user - check Note 1825259. Batch Job Logs (NetWeaver ABAP 7.00/7.01/7.10/7.11/7.20/7.30)Check note 1882691 to prevent errors when displaying job logs.Check if prerequisites for web service authentication in sapstartsrv from note 927637 are met.Java or Dual-Stack systems release 7.00 or 7.01:If the Java instance or even the complete system does not start, check the following points:The minimum support packages and patch levels have been installed as outlined in the note 1716826, the section "Prerequisites" -> "Attention".sapjvm: The directory jvm or sapjvm or the file protect.lst have been saved and restored as described inSection 4.1, "On Unix", steps 3 and 9Section 4.2, "On Windows", step 4DDIC_TYPELENG_INCONSISTENT short dumps (for 7.00/7.01/7.10/7.11 ABAP releases)If you did not handle the DDIC_TYPELENG_INCONSISTENT issue described in the note 1716826, the section "Prerequisites" -> "Attention" while the original kernel was still running, you should now install the note 1610716.SAP NW ABAP releases 7.00 - 7.31: note 1721936 should be implemented to avoid long running locks on the database during the first system start after kernel upgrade.The following points apply only to Dual-Stack or Java systems:Release 7.00 or 7.01: There was an incompatibility regarding jmon (SAP note 1652660). This has been eliminated with the following versions of the SAP Tech S Offline component:Release 7.00: SAP TECH S 7.00 OFFLINE, SP 14, PL 24Release 7.01: SAP TECH S OFFLINE 7.01, SP 3, PL 13This implies that at least support-package stack 14 or 5, respectively, must be installed in your system. Note 1652660 also lists the required patch levels for the higher support packages.Release 7.00 or 7.01: The tool JSPM must have at least SP 24 or 9, respectively.