Issues with "Cloud-native on the open Java stack" scenario

[dewan-ahmed]

Module - Cloud Native Intro - Cloud-native on the open Java stack

1. Introduction might be too long. QuickLabs participants would probably not read all of the texts. One paragraph would be ideal.

2. For this step: 
   Edit the source server configuration: /open-cloud-native-intro/src/main/liberty/config/server.xml
   When I add the line: , I get
    on the open Java stack (image on box link)
   When I remove the above parameter and refresh the try the link again for http://localhost:9080/metrics/: (image on box link)

3. For the part of changing greeting from "hello" to "bonjour", the server does not automatically detect the change and restart. When I made that change to line98 of pom.xml, I see the following:
   provided.
   [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.776 s <<< FAILURE! - in my.demo.it.GreetingIT
   [ERROR] testService(my.demo.it.GreetingIT)  Time elapsed: 1.72 s  <<< FAILURE!
   java.lang.AssertionError: Response must contain "Hello"
           at my.demo.it.GreetingIT.testService(GreetingIT.java:57)
   Please make a note to make changes in the test file as well.

4. For Step 4, Build a usr server package, the command cannot be run on the same terminal as the server is running. Please add comment to open a new terminal, change directory to open-cloud-native-intro and then execute the command mvn -P usr-package install

5. Same comment for Docker build step (separate terminal).

6. mvn -P usr-package install finished without creating target/defaultServer.zip hence results in
   (image on box link)

7. Share your success does not show user successfully completed the challenge; rather a link to the challenge (image on box link)

For images referring various issues above, pls refer to https://ibm.box.com/s/swaobbjxf97ypc7vx79qenp7qyqagmui @yasmin-aumeeruddy

[yasmin-aumeeruddy]

1. I do see what you mean and will summarise the introduction.
2. The guide is meant to show that. The user is prompted for a login until the mpMetrics authentication is set to false in the server.xml file :)
3. This has been fixed as the server needs to be stopped in dev mode before editing this.
4. The end of step 3 tells the user to stop the server so it is ready for step 4.
5. See above.
6. We are looking in to this