About this task
The REST connector is enabled through the Liberty feature restConnector-1.0. Remote access through the REST connector is protected by a single administrator role. In addition, SSL is required to keep the communication confidential. The restConnector-1.0 feature already includes the ssl-1.0 feature.
Note: An application deployed on Liberty has unrestricted access to its MBeanServer directory.
The following section describes how to configure and access the REST connector on Liberty.
- Enable the REST connector by using the following code in the server.xml
file.
<featureManager>
<feature>restConnector-2.0</feature>
</featureManager>
- Configure SSL certificates in the
server.xml file.
Ensure that the CN value of the certificate's subjectDN is the host name of the machine where the
server is running, and that the truststore contains the certificate of the server in the jConsole
connection.
- Configure a user or group to the administrator role in the server.xml
file.
- Access the REST connector.
You can access a Liberty REST connector
from a Java client or directly through an HTTPS call. A Java client uses the client-side of the
connector, which is in wlp/clients/restConnector.jar and implements the
javax.management.MBeanServerConnection interface. HTTPS calls use the server-side
of the connector. As to HTTPS calls on the server-side, any programming language that can make HTTPS
calls, such as C++, JavaScript, curl, Ruby, and Perl, can use the REST APIs. The REST APIs contain
endpoints for management (JMX), file transfer, collective routing, and collective deployment.
Note: You can specify some JMX REST connection options as system properties. See the Liberty API -
WebSphere JMX REST Connector API.