Configuring Admin Center

The adminCenter-1.0 feature enables the Liberty Admin Center, a web-based graphical interface for deploying, monitoring, and managing Liberty servers. After creating a Liberty JVM server, configure the server.xml file.

About this task

The steps below outline how to set up Admin Center.

Procedure

Open an editor on the server.xml file of the Liberty server, and configure the server for Admin Center. Add the adminCenter-1.0 feature to the feature manager.
```
<featureManager>
   <feature>adminCenter-1.0</feature>
   <feature>websocket-1.1</feature>
</featureManager>
```
WebSocket provides a live view of the topology. Without the WebSocket feature, the Admin Center web client periodically and frequently polls for changes.
Add the userid of all users of the Admin Center (SAF userid if registry), or add the RACF group, to the built-in administrator role.
```
<administrator-role>
   <user>username</user>
</administrator-role>
```
For more information about built-in administrator role, see Mapping the administrator role for Liberty on z/OS.
Optional: Give Admin Center access to write to server.xml by adding the following to server.xml:
```
<remoteFileAccess>
        <writeDir>${server.config.dir}</writeDir>
    </remoteFileAccess>
```
In the Admin Center, you can see and edit server.xml and any include files such as the CICS installedApps.xml file.

The design view lists and describes many other attributes of each element, providing a good way to understand the options available.

Note:
Some CICS augmented elements are not understood by a Liberty server and so those must be manually edited in the source view.

Do not remove any of the essential CICS features, such as core-1.0. This disconnects the Liberty instance and the containing JVMSERVER resource.

Results

Admin Center is now set up and ready to use. When you are using Admin Center, you must be aware that it is possible to STOP the server and applications. Any synchronization of resources must be seen as a convenience and not as a primary mechanism of control. The following behavior applies:

A signal is sent to CICS when the Liberty server is stopped. This quiesces all of your JVM server workload with a DISABLE(PHASEOUT) of the JVMSERVER. There is no option in the Admin Center to use FORCE or PURGE commands.
When you stop an application that was installed as a CICS bundle, the parent CICS bundle is notified of the application STOP and moves to the corresponding DISABLED state.