1783285893 by Unknown

Author:Unknown
Language: rus
Format: epub
Published: 2014-05-21T06:31:51+00:00

Chapter 2

You can also perform this configuration through the management console, as we will see in subsequent chapters.

Now that you know the structure of centralized configuration in WildFly more deeply, we can focus on adjusting the settings via the CLI and management console. Yes, you can also make all the settings without them by directly editing the configuration files, but these tools are certainly extremely useful and greatly simplify the administration.

Summary

This chapter showed you details about the main settings and configuration procedures. You learned a lot about deployments and the deployment scanner that uses file marks and how to easily control the deployment and find out about its status.

This chapter has shown us the importance of the logging subsystems and discussed the possibility of segregating logs of applications in different files or just increasing or decreasing the level of detail of the log. It also addressed datasource configuration and how to keep your database password secure from being accessed by a third party.

[ 55 ]

WildFly CLI and

Management Console

In WildFly, as well as in the versions of JBoss 7, all server instances and settings are managed through the Command-line Interface (CLI) and management console instead of editing the XML files. But as we have seen earlier, it is also possible to implement all settings by editing the XML files. Administration through the management interfaces provides an extra validation and advanced features for managing. The main difference between the two methods, manual editing via the Console and CLI, is that the changes made by editing the XML files will be applied only when the server is re-started, whereas some of the changes made through the console are applied even if the server is running.

Connecting to the CLI

The CLI is an administration tool usable by the command line to perform tasks in the WildFly Application server. With the CLI, we can perform diverse administrative actions, such as deploy and undeploy, the stop and change settings, and the system parameters. There is also an interesting option in the CLI that is able to perform actions in the batch mode, which means it can be multitasked like a script. The CLI is able to perform all the administrative operations, whereas the management console can only deal with a part of them.

The CLI is a command-line environment; to use it, you need to run a script that is located in the bin folder of the WildFly installation. The name of the script is jboss

-cli.sh, but soon it will be renamed. Let's access it with WildFly already running.

If it is not running, start WildFly and then run the script as follows:

[root@wfly_book wildfly-8.0.0.CR1]# servicewildfly start

[root@wfly_book wildfly-8.0.0.CR1]# cd /opt/server/wildfly-8.0.0.CR1/bin/

WildFly CLI and Management Console

Now, execute the jboss-cli.sh script as follows:

[root@wfly_book bin]# ./jboss-cli.sh

The output of the preceding command is as follows:

You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.

[disconnected /]

Due to the preceding result of the executed command, type connect to connect to the server using the CLI as

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.