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.