The Acoustic™ Experience Analytics (Tealeaf) CX Passive Capture Application can be configured through a web-based console or through the configuration files that are stored on the PCA server.
Configuring PCA by using the Web Console
The PCA Web Console provides a convenient graphical interface for monitoring and configuring the CX PCA and its connections.
For most activities, the Web Console is the primary location for configuring the CX PCA. You can edit the configuration files when a parameter needs to be changed and is not available through the Web Console.
Configuring CX PCA by using configuration files
You can modify the CX PCA settings through the vi editor to update the configuration files.
Configuration settings that apply to how the PCA interacts with the operating system are specified in two files. These files are located in the /usr/local/ctccap/etc/ directory:
ctc-conf.xml: This configuration file contains passive capture configuration settings.
runtime.conf: This configuration file contains custom settings and values for operating system-level configuration. This file can be used to override any of the default setting values that are listed in the
tealeaf.conf: This configuration file contains the default settings and values for operating system-level configuration.Note:
tealeaf.confmust be assigned read-only permissions for all users. It must never be edited.
runtime.conffile supersedes the default
tealeaf.conffile can be used to revert changes to the default settings if necessary, and it must be configured to be read-only.
To change a runtime setting:
- Copy the entry from
- Paste it into
runtime.confand edit the setting value.
runtime.confand restart the PCA.
Setting up SSL decryption
If SSL decryption of your web data is required, load it by using the web interface or through the command line.
- To set up by using the Web Console:
- Go to
https://<machineIP>:8443/and click SSL Keys.
- Click Loaded at the top of the page to view the loaded SSL keys and add new SSL keys.
- Click Save when done.
When you make changes by using the Web Console, services are automatically restarted to apply the changes.
- Go to
- To set up by using the command line interface:
- Edit the file
- Edit the XML node CaptureKeys.
- Modify any remaining options by using either the web UI or by editing the
- After you edit the
ctc-conf.xmlfile, restart the capture services manually by using the following commands:
tealeaf stop capture tealeaf start capture
- Edit the file
If you are not using the Experience Analytics Cookie Injector for sessionization, sessionization parameters must be configured in the TLSessioning session agent in the
TealeafCaptureSocket.cfg file on the Experience Analytics CX Server.
Changing the language in your current session
During initial configuration, your language is set to the language in your locale. If you want to change to a different language in a session, you can change the language for the session to one of the supported languages. Setting the language in a session affects only the current session. The next time that you log in, the language will be the language for the locale of your main server.
- In your current session, enter the command locale -a to see a list of supported locales.
- Enter the command LANG=, where <lang locale> is the language locale that you want to use in your session.
Enabling asynchronous posts to the target page
Improve performance and reduce the risk of data loss by configuring the PCA to use the W3C Beacon API to post capture data asynchronously to the Acoustic Experience Analytics (Tealeaf) target page.
Sending capture data to the Experience Analytics target page synchronously when a user closes a page can result in poor page performance. However, sending the payload asynchronously can result in loss of data. Support for the Beacon API addresses this problem by prioritizing transmission of the capture data and does not require the system to wait for an acknowledgment before sending the package.
Support for the Beacon API, also referred to as “sendBeacon”, is not enabled in Experience Analytics by default in the UI Capture SDK, nor is it supported by all versions of Experience Analytics or the PCA. To take advantage of the Beacon API, you must do the following:
- In the UI Capture SDK, set the useBeacon configuration to True. For details, see the UI Capture reference.
- Upgrade Experience Analytics to Version 10.0.
- Upgrade the PCA to the latest version.
Configuring PCA Web Console
By default, the PCA Web Console is accessible in HTTP mode over port 8080 or in HTTPS mode over port 8443. You can configure the PCA to toggle HTTP/HTTPS access.
By default, the PCA Web Console listens to the ports 8443 for HTTPS and 8080 for HTTP. You can change the listening ports by adding the following lines to the
runtime.conf file is used to override the default settings that are stored in the
tealeaf.confmust be configured to be read-only and must never be edited.
- To toggle HTTP/HTTPS access, in the /usr/local/ctccap/etc/runtime.conf file, add or edit the following lines:
- To change the listening ports,
- Edit the /usr/local/ctccap/etc/runtime.conf file.
- For HTTP (unencrypted), add the following lines:
- For HTTPS (encrypted), add the following lines:
Xis the port number to which the Web Console must listen for traffic.
The following commands can be used for either SLES and RHEL distributions, which have different filenames.
Make sure to save the updated files and restart the PCA.