Each xUML service starts its own instance of a Java Virtual Machine at startup. Thus, the configuration component has a Java Virtual Machine component resident with stereotype <<JavaVirtualMachine>> . It can have one or more <<JavaComponent>> component residents, which are manifested by <<JavaComponentDeployment>> artifacts.

Figure: Component Diagram with a Java Virtual Machine

The <<JavaVirtualMachineDeployment>> artifact shown in the component diagram above configures the JVM used to execute the imported Java code:

Its tagged values are:

• Kill Threads On Shutdown (killThreadsOnShutdown): If threads are still running on shutdown they are killed.
• JVM Options (jvmOptions): Java Virtual Machine options. The option strings has one of the following formats: "-D=...", "-X...", "_...", The system properties java.class.path and java.library.path are set by the model compiler and can not be overridden in the model.
• Parallel Operations (parallelOperations): Number of parallel open JavaVM threads within the runtime. Default: 100. If the limit is reached, the runtime tries for 60 seconds to obtain a free JVM thread. If it does not succeed, an error (JAVAADLM/19) is thrown.

• Shutdown Operations (shutdownOperations): Java operation being called before shutdown.

A component diagram can be drawn with the help of the E2E Component Wizard (for more information refer to the E2E Builder User Guide ). To ensure that the component diagram is correct, E2E recommends the usage of the wizard.

The following pictures show how to create a component diagram that contains a Java Virtual Machine artifact. Having defined the configuration artifact, the SOAP service artifact, and the port type artifact, you need to define the Java Virtual Machine. The Java Virtual Machine is defined as a new service component resident on a configuration. In the underlying example the JVM service resides on the configuration artifact JavaCollectionsExample.

Figure: Creating the Java Virtual Machine at Service Level in the E2E Component Wizard

By clicking the New button in the above dialog the following dialog pops up.

Figure: Selecting the Java Virtual Machine Template

Select the JavaVirtualMachine template and confirm the dialog with OK. In the subsequent dialog you create an artifact on the basis of the JavaVirtualMachine template. In the field jvmOptions you can enter some specific parameters to be passed on to the Java Virtual Machine instance of the composite service.

Figure: Creating an Artifact on the Basis of the Java Virtual Machine Template

The Java Virtual Machine artifact is listed in the right panel as one of the artifacts of the composite service.

Figure: A New Java Virtual Machine Artifact

In the next step all imported Java Components are listed.

Figure: All Imported and predefined Java Components

Take all the items the service needs for its execution from the list on the left hand side to the right hand side. Use the > button.

Figure: Selecting Java Components

Upon completion, the component wizard will draw the component diagram as exemplified by the first figure .

In the deployment diagram, you actually allocate component artifacts defined in the component diagram to their supposed target systems.

Figure: Deployment Diagram with a Java Virtual Machine

A deployment diagram can be drawn with the help of the E2E Deployment Wizard (for more information refer to the E2E Builder User Guide ). To ensure that the deployment diagram is correct, E2E recommends the usage of the wizard.