Automatic commit: Move 'cp-enterprisemessaging-javaclient-app' from QA to Production

thecodester · thecodester · commit 3a2b86183ebe · 2021-03-29T11:41:00.000+03:00
diff --git a/tutorials/cp-enterprisemessaging-javaclient-app/cp-enterprisemessaging-javaclient-app.md b/tutorials/cp-enterprisemessaging-javaclient-app/cp-enterprisemessaging-javaclient-app.md
@@ -1,31 +1,28 @@
 ---
-title: Create an Application for Sending and Receiving Messages using Java based client
-description: Develop and deploy a basic Java based messaging application for sending and receiving messages to a queue.
+title: Create App for Sending and Receiving Messages Using a Java-Based Client
+description: Develop and deploy a basic Java-based messaging application for sending and receiving messages to a queue.
 time: 45
 auto_validation: true
 tags: [ tutorial>intermediate, topic>java, products>sap-business-technology-platform, tutorial>license]
 primary_tag: products>sap-event-mesh
 ---
 
 ## Prerequisites
-- Installed Java 8 -> [Java download](https://www.java.com/en/download/)
-- Installed Maven 3.x -> [Maven download](https://maven.apache.org/download.cgi)
-- Installed Git -> [Git download](https://git-scm.com/downloads)
-- Follow [Create Instance of SAP Event Mesh Service](cp-enterprisemessaging-instance-create) and follow [Create Queues and Queue Subscriptions for Event Mesh](cp-enterprisemessaging-queue-queuesubscription) to create a queue in an instance of Event Mesh.
+- Installed Java 8: [Java download](https://www.java.com/en/download/)
+- Installed Maven 3.x: [Maven download](https://maven.apache.org/download.cgi)
+- Installed Git: [Git download](https://git-scm.com/downloads)
+- Follow [Create Instance of SAP Event Mesh Service](cp-enterprisemessaging-instance-create) and [Create Queues and Queue Subscriptions for Event Mesh](cp-enterprisemessaging-queue-queuesubscription) to create a queue in an instance of Event Mesh.
 - Follow [Install the Cloud Foundry Command Line Interface(CLI)](cp-cf-download-cli) to download and work with CLI.
-
-## Recommended
-- Installed IDE of choice (e.g. [Visual Studio](https://code.visualstudio.com/) with installed [Java language support](https://marketplace.visualstudio.com/items?itemName=redhat.java) plug in)
+- Installed IDE of choice (e.g. [Visual Studio](https://code.visualstudio.com/) with installed [Java language support](https://marketplace.visualstudio.com/items?itemName=redhat.java) plugin)
 
 ## Details
 ### You will learn
-  - How to create a basic messaging client application with Java, using combinations of vanilla Java, Spring, and JMS for sending messages to a queue
+  - How to create a basic messaging client application with Java
   - How to deploy this application to the SAP Event Mesh and test it
 
-
 ---
 
-[ACCORDION-BEGIN [Step 1: ](Setup the environment)]
+[ACCORDION-BEGIN [Step 1: ](Set up environment)]
 
 
 |       Application                    |              Scenario Description                                 
@@ -50,11 +47,11 @@ primary_tag: products>sap-event-mesh
 |                                      |  The REST endpoints are provided via the
 |                                      |  `MessagingServiceRestController`.
 
-To download and install the samples, just clone the repository via:
-   [git clone](https://github.com/SAP/enterprise-messaging-client-java-samples)
+To download and install the samples, just clone the repository via: [git clone](https://github.com/SAP/enterprise-messaging-client-java-samples)
 
 This downloads both the scenarios to your local IDE and the structure is as follows:
-  ![Project Structure](ProjectStructure.JPG)
+
+!![Project Structure](ProjectStructure.JPG)
 
 The downloaded project has all the dependencies and required client files for both scenarios mentioned above.
 The Event Mesh service descriptor is `/config/em-config-default.json`. Detailed information on different parameters of the
@@ -98,52 +95,55 @@ To be able to build, deploy and run the Java message client, ensure the followin
 
 [ACCORDION-BEGIN [Step 3: ](Code Snippets - common for both examples)]
 
-Open the manifest.yml file for the projects and make changes to the following parameters:
-  - applications:
-     `-` name: *<<Customized name of choice. Should be unique for a space of SCP>>*
-  - services:
-     `-` *<<name of the SAP Event Mesh instance>>*
+1. Open the `manifest.yml` file for the projects and make changes to the following parameters:
 
+    - applications:
 
-- Get the `MessagingService`
+        `-` name: *<<Customized name of choice. Should be unique for a space of SCP>>*
 
-```
-ServiceConnectorConfig config = null; // currently there are no configurations for the MessagingServiceFactory supported
-Cloud cloud = new CloudFactory().getCloud();
-// get a messaging service factory via the service connector
-MessagingService messagingService = cloud.getSingletonServiceConnector(MessagingService.class, config);
+    - services:
 
-```
+        `-` *<<name of the SAP Event Mesh instance>>*
 
-- Create a `MessagingServiceFactory` object with the help of `MessagingServiceFactoryCreator` and get a `MessagingServiceJmsConnectionFactory`.
-The Connection Factory can be configured with the `MessagingServiceJmsSettings`. In case the reconnection feature is not needed and an individual
-connection mechanism (for example, through a connection cache) is used these settings can be skipped. The connection factory can be built with `messagingServiceFactory.createConnectionFactory(MessagingServiceJmsConnectionFactory.class,settings)`.
 
-```
-MessagingServiceJmsSettings settings = new MessagingServiceJmsSettings(); // settings are preset with default values (see JavaDoc)
-settings.setMaxReconnectAttempts(5); // use -1 for unlimited attempts
-settings.setInitialReconnectDelay(3000);
-settings.setReconnectDelay(3000);
-MessagingServiceFactory messagingServiceFactory = MessagingServiceFactoryCreator.createFactory(messagingService);
-MessagingServiceJmsConnectionFactory connectionFactory = messagingServiceFactory.createConnectionFactory(MessagingServiceJmsConnectionFactory.class, settings)
+2. Get the `MessagingService`
 
-```
-- Create a connection and a session
+    ```
+    ServiceConnectorConfig config = null; // currently there are no configurations for the MessagingServiceFactory supported
+    Cloud cloud = new CloudFactory().getCloud();
+    // get a messaging service factory via the service connector
+    MessagingService messagingService = cloud.getSingletonServiceConnector(MessagingService.class, config);
+    ```
 
-```
-Connection connection = connectionFactory.createConnection();
-Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE));
-```
+3. Create a `MessagingServiceFactory` object with the help of `MessagingServiceFactoryCreator` and get a `MessagingServiceJmsConnectionFactory`.
+
+    The Connection Factory can be configured with the `MessagingServiceJmsSettings`. In case the reconnection feature is not needed and an individual connection mechanism (for example, through a connection cache) is used these settings can be skipped. The connection factory can be built with `messagingServiceFactory.createConnectionFactory(MessagingServiceJmsConnectionFactory.class,settings)`.
+
+    ```
+    MessagingServiceJmsSettings settings = new MessagingServiceJmsSettings(); // settings are preset with default values (see JavaDoc)
+    settings.setMaxReconnectAttempts(5); // use -1 for unlimited attempts
+    settings.setInitialReconnectDelay(3000);
+    settings.setReconnectDelay(3000);
+    MessagingServiceFactory messagingServiceFactory = MessagingServiceFactoryCreator.createFactory(messagingService);
+    MessagingServiceJmsConnectionFactory connectionFactory = messagingServiceFactory.createConnectionFactory(MessagingServiceJmsConnectionFactory.class, settings)
+    ```
+
+4. Create a connection and a session
+
+    ```
+    Connection connection = connectionFactory.createConnection();
+    Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE));
+    ```
 
 [DONE]
 [ACCORDION-END]
 
 [ACCORDION-BEGIN [Step 4: ](Code Snippets - Point to Point communication)]
-### Sending
+#### Sending
 
 Open the `MessagingServiceRestController.java` source code. Change the value of `QUEUE_PATH` based on the values of the instance you created.
 
-  `private static final String QUEUE_PATH = "queue/{queueName}";`
+`private static final String QUEUE_PATH = "queue/{queueName}";`
 
 For sending messages a Connection and a Session are required first. Note that those resources must be closed if they are not needed anymore. As those objects
 are implementing the `autoclosable` interface they will be closed automatically after the try-catch-block. Now a `BytesMessage` can be created. In the next
@@ -164,10 +164,13 @@ try (
 	LOG.error("Could not send message={}.", message, e);
 }
 ```
-### Receiving
-In this example a consumer is listening to a queue. Again a Connection and a Session are required. Note that those resources must be closed if they are not
-needed anymore. First a queue with the mandatory prefix "queue:" is bound to a consumer. Since the messages are sent as a `ByteMassage`, the message needs to be
+
+#### Receiving
+
+In this example, a consumer is listening to a queue. Again a Connection and a Session are required. Note that those resources must be closed if they are not
+needed anymore. First, a queue with the mandatory prefix "queue:" is bound to a consumer. Since the messages are sent as a `ByteMassage`, the message needs to be
 converted to say a String.
+
 ```
 try (Connection connection = connectionFactory.createConnection();Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE)) {
 	connection.start();
@@ -179,23 +182,24 @@ try (Connection connection = connectionFactory.createConnection();Session sessio
 } catch (JMSException e) {
 	LOG.error("Could not receive message.", e);
 }
-
 ```
 
 [DONE]
 [ACCORDION-END]
 
-[ACCORDION-BEGIN [Step 5: ](Code Snippets - Publish & Subscribe)]
+[ACCORDION-BEGIN [Step 5: ](Code Snippets - Publish and Subscribe)]
+
+Open the `MessageingServiceRestController.java` source code. Change the value of `TOPIC_PATH` and `QUEUE_PATH` based on the values of the instance you created.
 
-Open the `MessageingServiceRestController.java` source code. Change the value of `TOPIC_PATH` & `QUEUE_PATH` based on the values of the instance you created.
+`private static final String TOPIC_PATH = "topic/{topicName}";
+private static final String QUEUE_PATH = "queue/{queueName}";`
 
-  `private static final String TOPIC_PATH = "topic/{topicName}";
-  private static final String QUEUE_PATH = "queue/{queueName}";`
+#### Sending
 
-### Sending
 For sending messages a Connection and a Session are required first. Note that those resources must be closed if they are not needed anymore. As those objects are
 implementing the `autoclosable` interface they will be closed automatically after the try-catch-block. Now a `BytesMessage` can be created. In the next steps,
 a topic is bound (not created) to a producer. Note, that the prefix "topic:" is mandatory. Finally, the message can be sent to the topic.
+
 ```
 try (
   Connection connection = connectionFactory.createConnection();
@@ -210,7 +214,9 @@ try (
 	LOG.error("Could not send message={}.", message, e);
 }
 ```
-### Receiving
+
+#### Receiving
+
 Currently, direct topic subscription is *not supported for the default plan*. In this example, a consumer is subscribed to a specific topic. Again a Connection
 and a Session are needed. Note that those resources must be closed if they are not needed anymore. First a topic (not created) with the mandatory prefix "topic:"
 is bound to consumer. Since the messages are sent as a `ByteMessage` the message needs to be converted to say a String
@@ -234,10 +240,12 @@ try (
 [DONE]
 [ACCORDION-END]
 
-[ACCORDION-BEGIN [Step 6: ](Build & Deploy)]
-- Build the project with maven (`maven clean install`)
-- Push it to Cloud Foundry via `cf push` using CLI from the folder where the executable is available.
-- After successful deployment, follow [Send and Receive Test Event Mesh](cp-enterprisemessaging-test-queue-sendreceive) to test sending and receiving of message using the Java client.
+[ACCORDION-BEGIN [Step 6: ](Build and deploy)]
+1. Build the project with maven (`maven clean install`).
+
+2. Push it to Cloud Foundry via `cf push` using CLI from the folder where the executable is available.
+
+3. After successful deployment, follow [Send and Receive Test Event Mesh](cp-enterprisemessaging-test-queue-sendreceive) to test sending and receiving of message using the Java client.
 
 [VALIDATE_2]
 [ACCORDION-END]
