Configure runtimes

Semarchy xDI Analytics connects runtimes to monitor their status, activity and sessions.

Configure a runtime

To configure a runtime:

  1. In the Analytics toolbar, in the user menu, select Administration.

  2. In the Administration editor, select the Runtimes tab.

  3. Click the Add button.

  4. Specify the Name for the runtime

  5. Enter the Host and the Port on which to connect
    The host must include the protocol, such as http://hostname or https://hostname

    Although deprecated, the RMI protocol is still supported for compatibility with legacy Semarchy xDI Runtime versions. Use HTTP instead when possible. However, if you are in a situation where using RMI is necessary, make sure the target Semarchy xDI Runtime supports it and use rmi://hostname or rmis://hostname

  6. Optionally set a User and Password if you have configured authenticated access for this runtime.

  7. Test the connection through the Test button

  8. Select Show in logs selection to have this runtime appear in the profile selector.

  9. Select Hide in navigator to hide this runtime from the Navigator view.

  10. Select Disable log database proxy to prevent xDI Analytics from retrieving session information from this runtime. Use this option if you have separately configured a connection to the runtime’s log database.

  11. Save the editor.

ana parameters runtime

  1. Make sure to configure your network to allow the Analytics server to access the runtime host on its service port (Default: 42200)

  • If you configure Analytics to connect the runtime’s log database directly. Make sure to select Disable log database proxy for the runtime. on each Runtime.

  • If your runtime uses a different log database than the default one, make sure to add the corresponding JDBC drivers in the /jdbc subdirectory of the folder defined in the XDI_ANALYTICS_WEBAPP_HOME variable.

If the Runtime is accessed with HTTPS, ensure that the certificate is accepted by the JVM:

  1. If the HTTPS certificate is delivered by a trusted certificate authority, the JVM should accept it without any additional configuration.

  2. If the HTTPS certificate is a self-signed or JVM-unknown certificate, additional configuration is required in the JVM used by the application server hosting Analytics.

    1. Consult the documentation of your application server to find out how to pass additional Java options. The following Java options must be added and modified according to your configuration:




    2. As an example, with Apache Tomcat, this is known to be done by adding and/or configuring the following line in the setenv file (setenv.bat or depending on the OS):
      set JAVA_OPTS="<keystore_with_selfsigned_certificate_name.jks>" "<Certificate_Password>" "<JKS_or_PKCS12>"