Pressing Next button on the subsequent dialog will bring $(/J2EE/StandardSystem/SAPSystemName) system in Downtime. Make sure that you have created all required backups and the system is ready for downtime:

• Back up your database as described in your database manual.
• Back up the $(/ProcedureName) directory $(/JUMP/DIR/MAIN).
• If your system has dialog instances, make sure that they are uninstalled. For more information please check upgrade guide section Upgrading or Installing Dialog Instances. ]]>
• Make sure that SAP MMC is not running. ]]>
• Make sure that SDM GUI is not running.
• Make sure that jcmon and other standalone monitoring tools are not running. ]]>
• If your system is installed in a High Availability switch-over environment, make sure that the failover capabilities of the cluster switch-over software are disabled during the downtime. This is to prevent unwanted failover actions during stopp actions of the $(/ProcedureName) procedure. Also you must stop the primary application server instance and then the remote SCS instance manually. If the SCS is on Windows,disable the SCS instance service. ]]>
• Automatic update of native binaries is not supported when SCS is on remote host. Update them manually before to continue. See SAP note 1122058 for details. Make sure that the system is running after update of the kernel. ]]>

If any of the above processes are running, you must stop them now at the latest. Failure to do so will result in errors during the $(/ProcedureName). ]]> #Continue Cance#l /OkCancel com.sap.sdt.j2ee.tools.dialog.elim.BatchModeDialogEliminator