<%@ Page Language="C#" AutoEventWireup="true"%>
<script runat="server">
  public int Sampler()
  {
    Random rand = new Random();
    int nextRandom = rand.Next(1,100);
    int samplepercent = Convert.ToInt32(ConfigurationManager.AppSettings["rate"]);
    if(nextRandom <= samplepercent){
        return 1;
    }
    else{
        return 0; 
    }
  }
</script>
<%
    if (ConfigurationManager.AppSettings["killswitchtype"].Equals("percentagesample")) {
%>
    <%= Sampler() %>
<% } else{ } %>

<?xml version="1.0"?>
<!--
  For more information on how to configure your ASP.NET application, please visit
  http://go.microsoft.com/fwlink/?LinkId=169433
  -->
<configuration>
  <appSettings>
    <add key="killswitchtype" value="percentagesample"/>
    <add key="rate" value="50"/>
  </appSettings>
</configuration>

<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
	pageEncoding="ISO-8859-1"%>
<%@page import="java.util.Properties"%>
<%@page import="java.util.Date" %>
<%@ page import="java.net.*"%>
<%@ page import="java.io.*" errorPage=""%>
<%
	InputStream stream = application
			.getResourceAsStream("/config.properties");
	Properties props = new Properties();
	props.load(stream);
	Boolean DEBUG = false;
	DEBUG = ("true").equals(props.getProperty("debug"));
	String id = request.getParameter("id");
	String randomsample = request.getParameter("randomsample");
	String killSwitchResponse = "";
	String debugstr = "";
	// white list
	if (id != null && !id.isEmpty()) {
		InputStream whitestream = application.getResourceAsStream(props
				.getProperty("WhiteListFile"));
		BufferedReader input = new BufferedReader(
				new InputStreamReader(whitestream));
		String line = "";
		Boolean match = false;
		while ((line = input.readLine()) != null) {
			line = line.trim();
			if (line.equals(id)) {
				killSwitchResponse = "1";
				match = true;
				break;
			}
		}
		input.close();
		if (!match) {			
			killSwitchResponse = "0";
		}
	}
	// If kill switch is by sample rate
	else if (randomsample != null) {
		int rand = (int) (Math.random() * 100);
		int sampleRate = Integer.parseInt(props
				.getProperty("samplerate"));
		if (rand <= sampleRate) {			
			killSwitchResponse = "1";
		} else {			
			killSwitchResponse = "0";
		}
	} else {		
		killSwitchResponse = "0";
	}
	
	out.print(killSwitchResponse);
	//always give the path from root. This way it almost always works.
	String nameOfTextFile = props.getProperty("logfile");
	PrintWriter pw;
	if (DEBUG) {
		try {
			pw = new PrintWriter(new FileOutputStream(nameOfTextFile,
					true));
			Date date = new java.util.Date();
			debugstr = date.toString() + "\t"; 
			if (request.getQueryString() != null) {
				debugstr += request.getQueryString();
			}
			if("0".equals(killSwitchResponse))
				pw.println(debugstr + "\tDisable");
			else
				pw.println(debugstr + "\tEnable");
			//clean up
			pw.close();
		} catch (IOException e) {
			out.println(e.getMessage());
		}
	}
%>

 
WhiteListFile=whitelist.txt
samplerate =50
debug=true
logfile=/killswitchlog.txt

 <?php  
	$ini_array = parse_ini_file("config.ini", true);
	//print_r($ini_array);
	
	// if sample by percent
	if($ini_array['configtype']['killswitchtype'] === 'percentagesample'){
		$sampleRate = intval($ini_array['percentagesample']['rate']);
		killbysamplerate($sampleRate);
	}
	// if sample by whitelist
	else {
		
	}
	
	
	function killbysamplerate($sampleRate){
		$randomnumber = rand(1,100);
		if($randomnumber <= $sampleRate){
			echo '1';
		}
		else {
			echo '0';
		}
	}
	
	function killbywhitelist($whitelistpath){
	
	}
?>

; This is a sample configuration file
; Comments start with ';', as in php.ini

[configtype]
killswitchtype=percentagesample

[percentagesample]
rate = 50

[whitelist]
x
y
z

Configure and verify traffic capture on Passive Capture Application

You must verify that your Tealeaf environment is configured to capture and process the data submitted from the logging frameworks.

Data is submitted from the SDK to the Passive Capture Application (PCA) by using specific content types. The PCA is typically configured to capture these content types by default. You can verify that these content types are enabled for capture through the PCA web console.

Verify PCA capture type configuration

You use the PCA web console to verify that the PCA captures the content types submitted by the SDK. The SDK submits messages by using the text/json application/json content type.

📘

Note:

Depending on the version of the PCA you installed, the required content types may already be configured for capture.

📘

Tip:

Each Tealeaf Logging Framework can use a different content type for submitting events for capture to Tealeaf. Be sure to review and verify the content type for each deployed client framework.

1. Log in to the PCA web console: <PCAServer>:8080, where <PCAServer> is the hostname of the PCA server.
2. Click the Pipeline tab and click Edit Type Lists.
3. In the Capture All POST Types box, verify that the following values are included:
   • text/json
   • text/x-json
   • application/json
   • application/x-json
4. Click Add and Save your changes.

The PCA is now configured to capture the required content types. All subsequent hits of this type are captured.

Configure PCA for screen capture (optional)

You can set up the SDK to do a screen capture during the initial load of each view or screen of your web application.

When the screen capture option is enabled, you must configure the PCA to capture the screens. By default, the PCA captures binary or static content, so you must configure it to capture images submitted as binary POSTs to the target page.

These screen captures are forwarded to the Tealeaf Target Page in PNG and JPG format and used during session display.

PNG files are not compressed, while JPG files are compressed. A PNG file is approximately 20 KB to 35 KB in size; a JPG file is 6 KB to 15 KB.

1. Log in to the PCA web console. <PCAServer>:8080 Where <PCAServer>is the hostname of the PCA server.
2. Click the Pipeline tab and click Edit Type Lists.
3. In the Excluded File Extensions list, verify that png or jpg is listed.
4. In the Included File Extensions list, verify that png or jpg is not listed.

   📘

   Note:

   If a file extension is included in this list, then all instances sent as responses are captured, which significantly expands the volume of data that the PCA captures. Capture in this manner is not required.

5. In the Binary POST Types box, enter the value: image/png and click Add and Save your changes.

The image/png POST type is added and enabled for capture. This setting allows the PNG posts to be captured by the PCA.

Enable automated extraction of compressed POSTs

The SDK automatically compresses POST data. You must configure the PCA to extract them.

1. In the PCA web console, click the Pipeline tab.
2. Select Inflate compressed requests and responses.
3. Save your changes.

The compressed POSTs are now automatically extracted and processed by the PCA.

Monitor captures and processing

You can use different tools for testing your configuration and monitoring captures on an ongoing basis.

• At target page –You can test the basic functionality of the target page by triggering GET and POST actions on the URL where you installed the target page.
• In Windows pipeline –You can monitor the capture and processing of hits in the Windows pipeline in real-time through the Tealeaf Management System.

Configure sessionization

Tealeaf provides multiple mechanisms for identifying and tracking individual visitor sessions. For the Native Mobile SDKs, more configuration can be required.

Enable sessionization

To enable sessionization of hits captured through the Native Mobile SDKs, you must deploy the Sessioning session agent.

1. Log in to the Portal as an administrator.
2. From the Portal menu, select Tealeaf > TMS. The Tealeaf Management System opens.
3. Click the WorldView tab, and for the View, select Servers.
4. Click the Transport Service node.
5. Select Transport Service configuration. Then, click View/Edit.
6. The Pipeline Editor opens.

   📘

   Note:

   Verify that the sessioning session agent was installed. If it was not installed, drag it from the Available SessionAgents window to the pipeline.

7. Select the Sessioning session agent and click Edit.
8. In the Sessioning session agent configuration, modify the PrimarySessField value as follows:PrimarySessField=AppEnv:SessionID,env:HTTP_X_TEALEAF
9. Save the configuration file.
10. Push the change to all servers. A restart is needed for the new sessionization keys to take effect.

Add view name as URL during replay

You can resolve the errors during session replay by using the view name as the URL during replay. When you attempt to replay a session captured by the Native Mobile SDK, an error message can indicate that viewable pages are not there in the session. This error is related to how pages on the devices are mapped.

Instead of displaying the URL during replay, you can configure Tealeaf replay clients to show the view name instead, eliminating this cosmetic error message.

To use the view name as the URL to replay the session, complete the following steps to configure the appropriate replay profile rule.

📘

Note:

You must configure the rule through the replay profile that is stored on the Replay Server.

When this change is applied, the Navigable Pages list in Replay view in Browser-Based Replay and RealiTea Viewer is populated with the view name as the URL, instead of the generic Tealeaf Target page URL.

• Browser-Based Replay or BBRThis web-based replay client is accessible through the Tealeaf Portal and retrieves its sessions through the Replay Server in your Tealeaf environment.
• Tealeaf RealiTea Viewer or RTVThis replay client is a stand-alone Windows application you must install separately on your desktop. Through RealiTea Viewer, you can search for and replay sessions that are stored in your Tealeaf environment.

To change the replay profile, you can use the following options:

• Apply the view name change locally

  Complete the following steps in RealiTea Viewer to make changes locally and test the use of the view name during replay.

  1. Start the RealiTea Viewer application on your local desktop. Note: RealiTea Viewer must be installed locally on your Windows desktop.
  2. Load a session that is captured from the Native Mobile SDK.
  3. From the RealiTea Viewer menu, select Tools > Options.
  4. Click the Profiles tab.
  5. If you did not do so already, enter the name of the Replay Server that controls the replay profile in the Server check box.
  6. Click Check for Updates Now. If a server version of the profile is available, your local version is synchronized to it.
  7. Click Edit Raw Profile. Note: You are editing the raw XML file that is stored on your local desktop.
  8. Locate the RequestMapping section, which should be near the top of the file, and add a Request Mapping URL element entry.
  9. Locate the following header: <RequestEntry name="URL">. Add the following key name as a new entry to the list of entries:`<Key name="HTTP_X_TEALEAF_VIEW_CLASS" enabled="1"/>
  10. Save the file.
  11. After editing the profile as required, click Save Changes > Exit and click OK.
  12. Click Replay in the toolbar to replay the session.
  13. In the Navigable Pages list, the listed URLs reflect the view name for the screen.
  14. If the Navigable Pages list is being populated accurately, you can send your changes back to the Replay Server for deployment to other replay users.

      

      1. From the RTV menu, select Tools > Options.
      2. Click the Profiles tab.
      3. Click Upload Settings to Server.

• Apply the view name change to the Replay Server

  You must apply the change to the Replay Server by accessing the server and editing the appropriate file. This change is then available to all users of the Replay Server's profile, including all Browser-Based Replay users.

  Complete the following steps on the Replay Server so that all Browser-Based Replay users see the view name during replay.

  1. Log in to the server hosting the Replay Server as an administrator.
  2. Edit the following file:<Tealeaf_install_directory>\system\ReplayServerProfile.xml
  3. Locate the RequestMapping section, which should be near the top of the file. Add a Request Mapping, URL element entry.
  4. Locate the following header:<RequestEntry name="URL">
  5. Add the following key name as a new entry to the list of entries:`<Key name="HTTP_X_TEALEAF_VIEW_CLASS" enabled="1"/>
  6. Save the file.