MobileFirst Analytics Receiver Server Configuration Guide
improve this page | report issueOverview
Configuration for the MobileFirst Analytics Receiver Server.
Jump to
Properties
For a complete list of configuration properties and how to set them in your application server, see the section Configuration Properties.
Configuration Properties
The MobileFirst Analytics Receiver Server can start successfully with following additional configuration.
The configuration is done through JNDI properties on both the MobileFirst Server and the MobileFirst Analytics Receiver Server. Additionally, the MobileFirst Analytics Receiver Server supports the use of environment variables to control configuration. Environment variables take precedence over JNDI properties.
The Analytics Receiver runtime web application must be restarted for any changes in these properties to take effect. It is not necessary to restart the entire application server.
To set a JNDI property on WebSphere Application Server Liberty, add a tag to the server.xml
file as follows.
<jndiEntry jndiName="{PROPERTY NAME}" value="{PROPERTY VALUE}}" />
To set a JNDI property on Tomcat, add a tag to the context.xml
file as follows.
<Environment name="{PROPERTY NAME}" value="{PROPERTY VALUE}" type="java.lang.String" override="false" />
The JNDI properties on WebSphere Application Server are available as environment variables.
- In the WebSphere Application Server console, select Applications → Application Types → WebSphere Enterprise applications.
- Select the MobileFirst Administration Service application.
- In Web Module Properties, click Environment entries for Web Modules to display the JNDI properties.
MobileFirst Analytics Receiver Server
The following table shows the properties that can be set in the MobileFirst Analytics Receiver Server.
Property | Description | Default Value |
---|---|---|
receiver.analytics.console.url | Set this property to the URL of your MobileFirst Analytics Console. For example, http://hostname:port/analytics/console . Setting this property enables the analytics icon on the MobileFirst Operations Console. |
None |
receiver.analytics.url | Required. The URL that is exposed by the MobileFirst Analytics Server that receives incoming analytics data. For example, http://hostname:port/analytics-service/rest . |
None |
receiver.analytics.username | The user name that is used if the data entry point is protected with basic authentication. | None |
receiver.analytics.password | The password that is used if the data entry point is protected with basic authentication. | None |
receiver.analytics.event.qsize | Size of analytic event queue size. It should be added with caution by providing ample JVM heap size. Default queue size 10000 | None |
MobileFirst Server
The following table shows the properties that can be set in the MobileFirst Server.
Property | Description | Default Value |
---|---|---|
mfp.analytics.receiver.url | Required. The URL that is exposed by the MobileFirst Analytics Receiver Server that receives incoming analytics data and forward them to MobileFirst Analytics Server. For example, http://hostname:port/analytics-receiver/rest . |
None |
mfp.analytics.receiver.username | The user name that is used if the data entry point is protected with basic authentication. | None |
mfp.analytics.receiver.password | The password that is used if the data entry point is protected with basic authentication. | None |
Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.