Administer the Liberty profile using developer tools

We can modify how the workbench interacts with the Liberty profile using the server editor.

1. In the Servers view, right-click the server and select Open.

2. The server editor opens.

Results

The server editor displays the Liberty Profile with general information, publishing, timeouts, and Liberty Profile settings.

The Liberty Profile settings include the following settings:

Stop server on workbench shutdown

Whether a server instance that you started will be stopped when you shut down the developer tools workbench. When creating a server instance, the setting is enabled for that instance by default. We can enable or disable the setting for a particular server instance independent of the other server instances. When we shut down the developer tools workbench, all the server instances started inside the workbench, and that have the Stop server on workbench shutdown setting enabled, will be stopped during shutdown. However, all the server instances started inside the developer tools workbench that have the Stop server on workbench shutdown setting disabled continue to run. Any servers started outside the developer tools workbench also continue to run.

Server connection

Specifies information about the remote Liberty profile server connection settings. This information includes user name, password, and secure port settings for the remote server. These settings are the same as those settings that you enter when we create a new remote server. We can modify the values for these settings and click Verify to test the remote connection. When we click Verify, we establish a JMX connection to the remote host with the values that you specified. If no such server exists, an error message is displayed and the server state is changed to STOPPED. If the connection is successful, a fresh JMX connection is made with the server and the server state is updated according to the state of the remote server.

• The fields for the user name, password, and port number settings cannot be empty. If any of the fields are empty, we cannot do a save. Verify is disabled if any of the fields are empty.

• If we are using a local host, the user name, password, and port number settings are disabled. These settings are enabled only if the server in use is a remote server.

What to do next

We can modify the publishing, timeout, and other settings regarding the interaction between the workbench and the server.

Subtopics

• Edit the Liberty profile configuration using developer tools
  We can modify the behavior of the Liberty profile by editing the configuration. For example, we can configure which HTTP ports to use, what features are enabled, and logging and tracing settings.

• Start and stop a server using developer tools
  We can start and stop a server using the Liberty profile developer tools.

• Defining a utility project as a shared library
  We can define a utility project as a shared library and associate defined shared libraries with an application or web project.

• Explore the runtime environment using developer tools
  We can use the Runtime Explorer view to browse the available servers. This view shows all of the available servers for the runtime environment as opposed to the Servers view, which shows only those servers configured in the workspace. In both the Runtime Explorer and Servers view, we can expand each server to show the configuration for that server.

• Displaying the server configuration in a merged view
  We can use the Merged Configuration view to see a flattened view of the server configuration and any included configuration files.

• View the schema documentation for the server configuration
  We can view the schema documentation for the server configuration (server.xml file) within the workbench. The documentation provides information about the configuration elements available, the default settings, and details for each of the elements.

• Generating a Liberty profile server dump using developer tools
  Using the Liberty profile Utilities menu, we can generate a server dump for support.

• Packaging a Liberty profile server using developer tools
  We can create a compressed file containing a server runtime environment, server configuration, and applications using the packaging wizard.

• Add a data source using developer tools
  We can add a data source to the application using the developer tools.

Parent topic: Administer the Liberty profile

Tasks:

Specify Liberty profile bootstrap properties

Administer the Liberty profile manually

Reference:

Configuration elements in server.xml