«artifact» orders.jar
«component» OrderServiceApplication JVMSelect a device, runtime, artifact or solid line. Inspect nesting, deployment targets and communication paths.
The file icon marks an artifact. Drawing it inside a node places it on that target, as with the program artifacts inside the application JVM.
A solid line declares a communication path between devices. Labels describe the modeled traffic in this fictional example.
The lab checks the required target for each artifact and the declared direct paths between devices. Capacity, live connectivity, protocol behavior and availability require separate verification.
OMG · UML 2.5.1 §§19.2–19.5 ↗The runtimes are on separate gateway, application and database hosts. This case requires direct client–gateway, gateway–application and application–database paths.
Switching loads the selected topology’s preset. Undo restores your previous edits.
The lab checks the required target for each artifact and the declared direct paths between devices. Capacity, live connectivity, protocol behavior and availability require separate verification.
The runtimes are on separate gateway, application and database hosts. This case requires direct client–gateway, gateway–application and application–database paths.
Switching loads the selected topology’s preset. Undo restores your previous edits.
Check the deployment to find the artifact or path that needs repair.
The lab checks the required target for each artifact and the declared direct paths between devices. Capacity, live connectivity, protocol behavior and availability require separate verification.
A «manifest» relationship links the artifact to the logical component. Deployment allocates the artifact to a node.
«artifact» orders.jar«component» OrderServiceApplication JVM«artifact» payment-adapter.jar«component» CardPaymentAdapterApplication JVMA server hosts a JVM, and reports.jar is deployed in that JVM. The diagram needs to identify the runtime.