0:00
Using Microclimate locally.
The main use of Microclimate is in production environment such as IBM Cloud Private,
you will see that in a future module.
Although not the primary purpose,
developers can use Microclimate locally to develop code.
In addition to interfacing with a GitHub code repository,
Microclimate has a built-in editor and some monitoring capabilities that
help developers get immediate feedback on the performance impact of their changes.
The objectives of this demonstration are
to introduce the graphical user interface of Microclimate,
to demonstrate editing using the included Theia editor,
to view diagnostic information in the application logs,
to demonstrate the application running,
and to view the application monitor.
Throughout the entire demonstration,
you will see an introduction to the graphical user interface of Microclimate.
The Projects View lists the projects available in Microclimate.
In this case, the only project is the rogue cloud project.
The project's status in the language in which it is implemented are displayed.
The project is not running.
The project has started and its status is now green,
to the right of the project name is Nelips.
Click the "Nelips" to display menu options.
You can edit code,
view the build logs, open the application,
view application logs, monitor the application or delete the application.
In this demonstration "Edit code" is selected.
The "Edit code" button takes you to the details of the rogue cloud project.
The file StartAgentServlet.java is open.
The first thing you must do is defining user name and password for your agent.
The documentation tells you to do this,
but it is a good example of using application logs.
To see the error message informing you that you must create
a username and password, click "App logs".
The next section is viewing diagnostic information in the application logs.
In the "App logs" tab view the logs,
page down until you see the error message.
2:57
and the password is Spring also, save the edits.
Now we move to demonstrating the application running.
To view the opposition running we need to build the URL,
begin by clicking the "Open app" tab.
Look for the application URL.
3:22
Opening browser window and paste the URL into the address field.
Refer to the URL shown below,
in step E) Next steps: watch your agent go and start coding.
Both for the second part of the URL, which is /gameclient/StartAgent.
Copy that portion of the URL so that you can pend it to the address in the browser.
Return to the browser which has the first part of the application of the URL.
Paste the second portion of the URL into the browser address window.
The complete your URL is the local host port and the text that leads to the application,
that is gameclient StartAgent.
This is the rogue cloud application.
Notice that the agent is named Spring.
On the right there's a scorecard the agent is running with
default settings now but can be programmed to behave differently.
Below that display is an Event Log which shows what's happening.
For example in this case Scary Snull attacked Spring and Spring retaliated.
The default strategies are explained in documentation.
You can change your agent's behavior and there are
some strategies suggested in the documentation,
but first, it makes sense to get a feel for the game.
On the lower right there are metrics that can be used to evaluate
the current performance and then any modifications.
To change the agent's behavior you modify the code module named Simple AI class.
The final objective of this demonstration is to view the application monitor.
To view the monitoring capabilities click the "App monitor" on the lower left.
There are two tabs on the monitoring view, Dashboard and Summary.
On the Dashboard for Java App,
the first graph shows CPU usage.
It also shows HTTP incoming requests,
heap size, HTTP throughput and garbage collection time.
This Summary tab shows HTTP requests,
environment information and a summary of resource usage.
In this demonstration, you saw an introduction to
the graphical user interface at Microclimate,
you saw a demonstration of the editing using Theia editor,
you viewed diagnostic information in the application logs,
saw a demonstration of the operation running and view the application monitor.
Karen DurstonSoftware Engineer
Megan IrvineTechnical Enablement Specialist
Steeve Chwojko
