For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.


Configure the endpoint of the application resources (Liberty profile)

For the Liberty profile, configure the endpoint of the application resources through the JNDI environment.


Purpose

Since IBM® Worklight® V6.0, follow this procedure when we must change the URI protocol, host name, and port used by the Application Center client to manage the applications on your device.


Properties

Edit the server.xml file. To be able to define JNDI entries, the <feature> element must be defined correctly in the server.xml file:

<feature>jndi-1.0</feature>

Add an entry for each property in the <server> section of the server.xml file. This entry should have the following syntax:

<jndiEntry jndiName="JNDI_property_name" value="property_value"/>

Where:

JNDI_property_name is the name of the property that you are adding.

property_value is the value of the property that you are adding.

Table 1. Properties in the server.xml file for configuring the endpoint of the application resources
Property Description
ibm.appcenter.services.endpoint The URI of the Application Center REST services. In a scenario with a firewall or a secured reverse proxy, this URI must be the external URI and not the internal URI inside the local LAN.
ibm.appcenter.proxy.protocol The protocol of the application resources URI. This property is optional. It is only needed if the protocol of the external and of the internal URI are different.
ibm.appcenter.proxy.host The host name of the application resources URI.
ibm.appcenter.proxy.port The port of the application resources URI. This property is optional. It is only needed if the protocol of the external and of the internal URI are different.

For a complete list of LAPD properties that we can set, see JNDI properties for Application Center.


Example of setting properties for configuring the endpoint

This example shows the settings of the properties in the server.xml file required for configuring the endpoint of the application resources.

<jndiEntry jndiName="ibm.appcenter.services.endpoint" value=" https://appcntr.net:443/applicationcenter" /> <jndiEntry jndiName="ibm.appcenter.proxy.protocol" value="https" /> <jndiEntry jndiName="ibm.appcenter.proxy.host" value="appcntr.net" /> <jndiEntry jndiName="ibm.appcenter.proxy.port" value=" 443"/>

We can use the asterisk (*) character as wildcard to specify that the Application Center REST services use the same value as the Application Center console. For example: *://*:*/appcenter means use the same protocol, host, and port as the Application Center console, but use appcenter as context root.

Parent topic: Defining the endpoint of the application resources