Skip to Content
avatar image
Former Member

VM Container


I have one question about VM Container.

Can VM Container be considered as an alternative solution for the communication between ABAP- and J2EE-Stacks?

What are the possible field of application/advantaqges of VM Container?

Thank you!


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    May 27, 2006 at 06:48 PM

    No, the VMC is just a SAP written implementation of a JVM, following the J2SE specifications, which will be used to speed up the JAVA code, which is used as offload functionality to ABAP. It's not SAP's intend to publish this method for external usage (customers & partners).

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 20, 2007 at 11:47 PM

    Hi Peter,

    Information about VM Container.

    The VM container technology in connection with a Java VM integrated in the ABAP work process provides the following advantages:

    ● Reliability and maintainability as in the ABAP environment

    The integration of the Java VM into the ABAP work process enables strict isolation between active user sessions, which guarantees a large degree of robustness and maintainability.

    One work process can only process one user request at a time, which means that even if one entire Java VM crashes, only the one user active at this time is affected.

    ● Close ABAP/Java communication (in-process)

    Since the ABAP and Java VMs run in the same work process, a quick and efficient communication path can be implemented between the two languages, which means that the security and speed of the communications is significantly increased. For further information, refer to the SAP JCo and Container [external documentation] documentation.

    ● Administration and Sharing of Resources

    While a request is being processed a Java VM works exclusively for one user. There is a pool of VMs dynamically assigned to the work processes. These VMs can access shared data in the shared memory.

    ○ Java shared closures

    Java objects can be moved across process boundaries and shared by processes. This enables an efficient session failover to be implemented. At the same time shared closures offer the option of reducing the memory consumption of the entire system through process-wide caching.

    ○ Shared class pool

    Java classes only have to be loaded into the memory once, the same as for ABAP PXA, and they can be used by all the processes in the system. This reduces the memory consumption and the start time of further processes.

    You can find further information in the following sections:

    Sharing Concepts in the VM Container [page 7]

    Resource Management in the VM Container [page 9]

    Memory Management in the VM Container [page 66]

    ● High Supportability

    Since the JTS uses existing SAP kernel technology, the monitoring functions of the CCMS can be used. For the reason, the familiar SAP statistics can also be used (see Statistics in the VM Container [page 57]).

    ● Debugging

    Each user can dynamically switch to and fro between normal operation and debugging.

    For more information check the below notes.

    <b>Note 854170 - Activating the component "VM Container"</b>



    Add comment
    10|10000 characters needed characters exceeded