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.

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 file.
• tealeaf.conf: This configuration file contains the default settings and values for operating system-level configuration.
  Note: tealeaf.conf must be assigned read-only permissions for all users. It must never be edited.

To change a runtime setting:

1. Copy the entry from tealeaf.conf.
2. Paste it into runtime.conf and edit the setting value.
3. Save runtime.conf and restart the PCA.

• To set up by using the Web Console:
  1. Go to https://<machineIP>:8443/ and click SSL Keys.
  2. Click Loaded at the top of the page to view the loaded SSL keys and add new SSL keys.
  3. Click Save when done.

  When you make changes by using the Web Console, services are automatically restarted to apply the changes.

• To set up by using the command line interface:
  1. Edit the file /usr/local/ctccap/etc/ctc-conf.xml.
  2. Edit the XML node CaptureKeys.
  3. Modify any remaining options by using either the web UI or by editing the /usr/local/ctccap/etc/ctc-conf.xml file.
  4. After you edit the ctc-conf.xml file, restart the capture services manually by using the following commands:

     
     tealeaf stop capture
     tealeaf start capture
     

If you are not using the Tealeaf Cookie Injector for sessionization, sessionization parameters must be configured in the TLSessioning session agent in the TealeafCaptureSocket.cfg file on the Tealeaf CX Server.

1. In your current session, enter the command locale -a to see a list of supported locales.
2. Enter the command LANG=, where <lang locale> is the language locale that you want to use in your session.

Sending capture data to the Tealeaf 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 Tealeaf by default in the UI Capture SDK, nor is it supported by all versions of Tealeaf or the PCA. To take advantage of the Beacon API, you must do the following:

1. In the UI Capture SDK, set the useBeacon configuration to True. For details, see the UI Capture reference.
2. Upgrade Tealeaf to Version 10.0.
3. Upgrade the PCA to the latest version.

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.

The runtime.conf file is used to override the default settings that are stored in the tealeaf.conf file.

• To toggle HTTP/HTTPS access, in the /usr/local/ctccap/etc/runtime.conf file, add or edit the following lines:

  
  httpd_port_enable="NO"
  httpd_portssl_enable="YES"
  

• To change the listening ports,
  1. Edit the /usr/local/ctccap/etc/runtime.conf file.
  2. For HTTP (unencrypted), add the following lines:

     
     httpd_listen="X"
     httpd_port="X"
     

  3. For HTTPS (encrypted), add the following lines:

     
     httpd_listenssl="X"
     httpd_portssl="X"
     

  where X is 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.

cat /etc/*-release 

System
release info                 : LSB_VERSION="1.3"
Red Hat Enterprise Linux ES release 3 (Taroon Update 5)

uname-a

kernel info                   : Linux venus.tealeaf.com 2.4.21-32.EL #1 Fri \
> Apr 15 21:29:19 EDT 2005 i686 i686 i386 GNU/Linux

cat /proc/cpuinfo

processor                     : 0
vendor_id                    : GenuineIntel
cpu family                    : 6
model                            : 8
model name               : Pentium III (Coppermine)
stepping   : 3
cpu MHz                       : 664.526
cache size                    : 256 KB
fdiv_bug  : no
hlt_bug                         : no
f00f_bug  : no
coma_bug                   : no
fpu                                  : yes
fpu_exception           : yes
cpuid level                   : 2
wp                                  : yes
flags                               : fpu vme de pse tsc msr pae mce cx8 sep \
> mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips                     : 1327.10

cat /proc/meminfo

total:    used:    free:  shared: buffers:  cached:
Mem:  258945024 250028032  8916992        0 110923776 90759168
Swap: 534601728  5242880 529358848
MemTotal:       252876 kB
MemFree:          8708 kB
MemShared:           0 kB
Buffers:        108324 kB
Cached:          85572 kB
SwapCached:       3060 kB
Active:         183328 kB
ActiveAnon:      37496 kB
ActiveCache:    145832 kB
Inact_dirty:     35704 kB
Inact_laundry:    7588 kB
Inact_clean:      3436 kB
Inact_target:    46008 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       252876 kB
LowFree:          8708 kB
SwapTotal:      522072 kB
SwapFree:       516952 kB
CommitLimit:    648508 kB
Committed_AS:   285972 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     4096 kB

dmesg

dmesg
device eth2 entered promiscuous mode
device eth0 left promiscuous mode
device eth4 left promiscuous mode
device eth1 left promiscuous mode
device eth2 left promiscuous mode
device eth0 entered promiscuous mode
eth4: Promiscuous mode enabled.
device eth4 entered promiscuous mode
device eth1 entered promiscuous mode
eth2: Setting promiscuous mode.
device eth2 entered promiscuous mode

Make sure to save the updated files and restart the PCA.