for these protocols: 1. Stomp 2. OpenWire 3. AMQP JMS semantics are implemented by a JMS facade layer on the client side. The Apache ActiveMQ Artemis server does not speak JMS and in fact does not know client API directly. You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side. ActiveMQ Artemis Documentation 13 Architecture Apache ActiveMQ Artemis core files A broker instance is the directory containing all the configuration and runtime data, such as logs and data files, associated with a broker process. It is recommended that you do not create the

HornetQ clients). 6. CORE (Artemis CORE protocol) JMS semantics are implemented by a JMS facade layer on the client side. The Apache ActiveMQ Artemis server does not speak JMS and in fact does not know client API directly. You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side. Architecture 13 Apache ActiveMQ Artemis stand-alone server The standard stand-alone Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data files, associated with a broker process. It is recommended that you do not create the

HornetQ clients). 6. CORE (Artemis CORE protocol) JMS semantics are implemented by a JMS facade layer on the client side. Architecture 15 The Apache ActiveMQ Artemis server does not speak JMS and in client API directly. You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side. Apache ActiveMQ Artemis stand-alone server The standard stand-alone messaging Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data files, associated with a broker process. It is recommended that you do not create the

HornetQ clients). 6. CORE (Artemis CORE protocol) JMS semantics are implemented by a JMS facade layer on the client side. Architecture 15 The Apache ActiveMQ Artemis server does not speak JMS and in client API directly. You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side. Apache ActiveMQ Artemis stand-alone server The standard stand-alone messaging Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data files, associated with a broker process. It is recommended that you do not create the

1. Stomp 2. OpenWire 3. AMQP Architecture 16 JMS semantics are implemented by a JMS facade layer on the client side. The Apache ActiveMQ Artemis server does not speak JMS and in fact does not know client API directly. You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side. Apache ActiveMQ Artemis embedded in your own application Apache ActiveMQ Artemis Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data files, associated with a broker process. It is recommended that you do not create the

HornetQ clients). 6. CORE (Artemis CORE protocol) JMS semantics are implemented by a JMS facade layer on the client side. Architecture 15 The Apache ActiveMQ Artemis server does not speak JMS and in client API directly. You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side. Apache ActiveMQ Artemis stand-alone server The standard stand-alone messaging Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data files, associated with a broker process. It is recommended that you do not create the

1. Stomp 2. OpenWire 3. AMQP Architecture 16 JMS semantics are implemented by a JMS facade layer on the client side. The Apache ActiveMQ Artemis server does not speak JMS and in fact does not know client API directly. You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side. Apache ActiveMQ Artemis embedded in your own application Apache ActiveMQ Artemis Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data files, associated with a broker process. It is recommended that you do not create the

1. Stomp 2. OpenWire 3. AMQP Architecture 16 JMS semantics are implemented by a JMS facade layer on the client side. The Apache ActiveMQ Artemis server does not speak JMS and in fact does not know client API directly. You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side. Apache ActiveMQ Artemis embedded in your own application Apache ActiveMQ Artemis Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data files, associated with a broker process. It is recommended that you do not create the

these protocols: 1. Stomp 2. OpenWire 3. AMQP JMS semantics are implemented by a JMS facade layer on the client side. The Apache ActiveMQ Artemis server does not speak JMS and in fact does not know client API directly. You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side. Architecture 12 Apache ActiveMQ Artemis embedded in your own application Apache Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data files, associated with a broker process. It is recommended that you do not create the

1. Stomp 2. OpenWire 3. AMQP Architecture 16 JMS semantics are implemented by a JMS facade layer on the client side. The Apache ActiveMQ Artemis server does not speak JMS and in fact does not know client API directly. You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side. Apache ActiveMQ Artemis embedded in your own application Apache ActiveMQ Artemis Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data files, associated with a broker process. It is recommended that you do not create the