Importing Patches and Corrections

Use

Since the VM Container provides a runtime environment for Java applications, there are two different types of error corrections (patches): one to import error corrections for the VM Container itself, and the other to import error corrections for Java applications in the VM Container.

Procedure

Importing Error Corrections for the VM Container Itself

The VM Container is part of the kernel of the SAP NetWeaver application server ABAP. Corrections are imported in kernel patches. For more information about importing kernel patches, see SAP note 19466.

Importing Error Corrections for Java Applications in the VM Container

Error corrections of Java applications in the VM Container are provided regularly in the well-known SAP NetWeaver application server ABAP support packages of applications. If it should ever be necessary to correct errors in support packages, import urgent corrections as follows:

...

1. The urgent corrections are available as Software Component Archive (SCA file) in the SAP Service Marketplace (http://service.sap.com/swdc). If the documentation for managing your application is available from the Service Marketplace, download this file onto your PC.

2. Log on to your development and correction system (depending on the system landscape and transport routes) and create a transport request of type Workbench Request in the Transport Organizer (transaction SE09). With this transport request the urgent correction is subsequently transported into your productive system.

3. Execute program RSVMCRT_UPLOAD_SCA_FROM_PC. A selection screen appears. Enter the transport request you just created and the absolute path and file name of the SCA file into the appropriate fields and then choose the Execute pushbutton (F8).

4. The SCA is now read and the program checks if the urgent corrections can be imported into your system. The program checks whether the urgent correction is compatible with the kernel patch level and support package level of the application to be corrected. If this is not the case, the installation of the urgent correction is refused and its incompatibility logged. If the compatibility check is successful, the parts of the application component that have been corrected are indicated in the installation.

5. Once the urgent correction has been imported successfully, it can be transported on to other systems. To do this the relevant tasks and requests must be released in the Transport Organizer (transaction SE09) and imported into the follow-on systems.

Note that no compatibility check takes place in the follow-on systems. Rather, it is assumed that you are not operating a system landscape with different kernel patch levels and different support package levels.