Skip to main content
Version: Deploy 24.1

Configure application by enabling logging subsystem on JBoss Server using Deploy

This topic describes how to configure and deploy the application by logging subsystem enabled on JBoss server using Deploy.

It assumes you have the JBoss Domain plugin installed.

Step 1 - Connect to your infrastructure​

Connect Deploy to the host on which JBoss is running. Follow the instructions for the host's operating system and the connection protocol that you want Deploy to use. For more information, see :

Step 2 - Add a stand-alone JBoss server​

To add a stand-alone JBoss server:

  1. Hover over the host that you created, click Menu button, and select New > jbossdm > StandaloneServer.
  2. In the Name field, enter a name for the server.
  3. In the Home field, enter the JBoss home directory. For example, /opt/jbossdm7/.
  4. In the Administrative PORT enter the port number to login to JBoss Native Administration.
  5. In the Administrative username and Administrative password fields, enter the user name and password used to log in to JBoss Native Administration.
  6. Click Save or Save and Close button.

Step 3 - Create an environment​

An environment is a grouping of infrastructure and middleware items such as hosts, servers, clusters, etc. An environment is used as the target of a deployment, enabling you to map deployable to members of the environment.

To create an environment where you can deploy a sample application, follow the procedure described in Create an environment in Deploy .

To deploy to a Standalone JBoss Server, you must add a jbossdm.StandaloneServer to the environment.

Step 4 - Configure the LoggingSpec sample application​

Sample application

Configure the properties in LoggingSpec:​

  1. Name: The name of the Configuration item.
  2. Choose file: Logging application file.

Sample application

Step 5 - Deploy the sample application​

To deploy the sample application, follow the steps described in Deploy an application.

Once the deployment succeeds, the status of the deployment must show EXECUTED

Sample application

Verify the deployment​

To verify the deployment from jboss CLI use the following commands
EAP_HOME/bin/jboss-cli.sh --connect
deployment info

Output should include the name of the deployed application:

Sample application

Check the genereted log-files using following command

/subsystem=logging/:list-log-files

The output must include the list of the log files with application name.

{
    "outcome" => "success",
    "result" => [
        {
            "file-name" => "logging-app.debug.log",
            "file-size" => 0L,
            "last-modified-date" => "2021-10-01T09:59:17.684+0200"
        },
        {
            "file-name" => "logging-app.error.log",
            "file-size" => 0L,
            "last-modified-date" => "2021-10-01T09:59:17.685+0200"
        },
        {
            "file-name" => "logging-app.fatal.log",
            "file-size" => 0L,
            "last-modified-date" => "2021-10-01T09:59:17.685+0200"
        },
        {
            "file-name" => "logging-app.info.log",
            "file-size" => 0L,
            "last-modified-date" => "2021-10-01T09:59:17.684+0200"
        },
        {
            "file-name" => "logging-app.trace.log",
            "file-size" => 0L,
            "last-modified-date" => "2021-10-01T09:59:17.684+0200"
        },
        {
            "file-name" => "logging-app.warn.log",
            "file-size" => 0L,
            "last-modified-date" => "2021-10-01T09:59:17.684+0200"
        },
        {
            "file-name" => "server.log",
            "file-size" => 177011L,
            "last-modified-date" => "2021-10-01T09:59:18.676+0200"
        },
        .
        .
	      .