Read more about Data Workbench’s End-of-life announcement.
Detailed instructions for installing and configuring Sensor for WebSphere 5.x running on AIX 5.1 or later.
The program files for Sensor are packaged in an installation file that you obtain from the Adobe download site. If you do not already have the Sensor installation file for your particular web server, download it (or obtain it from your Adobe representative) before you begin the following procedures.
The Sensor for WebSphere servers does not support controlled experimentation. For information about controlled experimentation, see the Data Workbench Controlled Experiments Guide.
Procedure to extract and install the program files for Sensorto the server machine.
Log on as the root user or as a user with root authority.
Decompress and unpack the installation file using the following command:
gunzip installationFilename.tar.gz tar -xf installationFilename.tar
Copy the unpacked program files to the directories identified in the following table:
|libvisual_sciences.so||The collector load module||/usr/local/visual_sciences|
|J2EECollector.jar||The collector load module libraries||WebSphere /lib directory|
|txlogd||The transmitter program||
|txlogd.conf||The Sensor configuration file||/etc|
|trust_ca_cert.pem||The certificate used to validate the digital certificate that Insight Server presents during the connection process||/usr/local/visual_sciences|
The installation package contains a spreadsheet file called TestExperiment.xls. This spreadsheet is a tool that architects use to configure a controlled experiment. Sensor itself does not use this file, so it is not necessary to install the file on the machine where Sensor is running (although you may choose to do so). You might want to, instead, copy the file to a location where your architects can access it or simply extract the file from the installation package as needed. For more information about controlled experimentation, see the Insight Controlled Experiments Guide.
Permissions on the Program Files
Incorrect permissions on the program files cause the majority of problems encountered when installing Sensor.
Please make sure that you set the permissions exactly as stated in this section.
By default, the program files in the tar file have the following permissions. Depending on how your system is configured, these settings might be altered (unmasked) when you extract the files.
To reset the permissions to the recommended default settings, use the chmod commands below.
Check that the directories into which you have installed the files permit at least this level of access.
|File||Default Permissions||chmod command|
|libvisual_sciences.so||rwx --x --x||chmod 711|
|J2EECollector.jar||rw- rw- r–||chmod 664|
|txlogd||rwx --x --x||chmod 711|
|txlogd.conf||rw- rw- r–||chmod 664|
|trust_ca_cert.pem||rw- rw- r–||chmod 664|
If you want to use permissions other than the recommended defaults, review the information in Sensor UNIX File Permissions, to be sure you understand how these files are used.
The txlogd.conf file contains the configuration parameters for Sensor.
You must edit the file to specify, among other things, the size of the disk queue, the address of the Insight Server, and the ID that will be attached to the data produced by this sensor.
The configuration file contains required parameters and optional parameters.
To edit the configuration file
Procedure to create the disk queue, after you configure the txlogd.conf file.
If the directory in which the disk queue resides does not already exist, create it. Make sure that the directory provides both the collector module and the transmitter program with read/write access to the file.
On the computer where Sensor is installed, execute the following command to start the transmitter:
/usr/local/bin/txlogd -ic -f /etc/txlogd.conf
Verify that the transmitter has created the disk queue in the location specified in the QueueFile parameter and of the size specified in the QueueSize parameter.
If the queue has not been created correctly, type Ctrl+C to terminate the transmitter, then do the following:
For WebSphere servers, the collector operates as a filter in the servlet container.
To add the collector to the web application, add the filter to the web application’s web.xml deployment descriptor and restart the web application.
Using a text editor, open the web.xml file for the web server whose events Sensor captures.
Add the following
<filter-mapping> elements to the descriptor file. If you did not install txlogd.conf in the /etc directory, you need to enter the correct path to this file in the
<filter> <filter-name>VSCollectorFilter</filter-name> <description></description> <filter-class> com.visualsciences.collector.VSCollectorFilter </filter-class> <init-param> <param-name>configPath</param-name> <param-value>C:/VisualSensor/txlogd.conf</param-value> <description></description> </init-param> </filter> <filter-mapping> <filter-name>VSCollectorFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
These lines are case sensitive. Type them exactly as they appear above.
Restart the web application. The collector is loaded with the application and will begin collecting event data and writing it to the disk queue.
Procedure to edit the Websphere startup script to declare the location of the J2EECollector.jar and libvisual_sciences.so files.
Open the setupCmdLine.sh file in the Websphere /bin directory.
After the line that defines the $WAS_CLASSPATH variable, add the following line:
After the case block that defines the $WAS_LIBPATH variable, add the following line:
Save the setupCmdLine.sh file.
Procedure to start the transmitter and verify that it can successfully connect to the Insight Server and transmit event data to it.
To verify that the transmitter can successfully send event data to the Insight Server, make sure that the target Insight Server is installed and running before you begin the following test.
If the transmitter is not already running, restart it using the following command:
/usr/local/bin/txlogd -i -f /etc/txlogd.conf
Open a browser (on any machine) and request a page from the web server on which Sensor is running (be sure to select a page that Sensor is monitoring).
After you issue the request, check the transmitter’s console for messages indicating that it is sending event data to the target Insight Server.
If Sensor is not transmitting data successfully, verify that:
Information to ensure that the transmitter loads automatically when the web server machine is restarted.
Add the following command (which launches the transmitter) to your system startup script.
/usr/local/bin/txlogd -f /etc/txlogd.conf
This command starts the transmitter as a daemon. Operating and error messages that the transmitter generates are written to syslog.
Sensors for all platforms can collect any of the data available in the HTTP request and response headers.
The Sensors for the J2EE Platform provide a mechanism for collecting data that is not available on other platforms. The collector for the J2EE platform (J2EE collector) sits on the application layer, which enables it to collect sensitive data that is available only to the application and should not be exposed through page tagging or in the headers.
While page tags and header modification can hide the data, it is still available to those who examine the source code of a page or look at the headers using browser plug-in tools.
For example, the J2EE collector can be used to capture cost per click (CPC) data for links displayed on a page, sensitive partner information on a page, and many other data points. The J2EE environment makes it easy for you to modify your WEBAPP to capture this custom data using our collector class.
When a Sensor for the J2EE Platform receives a request, it invokes a collector class that imports the appendToLog function. The appendToLog function appends to the initial request the query string parameters specified in the appendToLog function. This results in the URI of the initial request containing additional query string name-value pairs that correspond to the names and values of the data that is being captured. For example, CPC=20 would be appended to the initial request when the value of a particular ad placement or click-through link is 20 cents. Insight Server processes these values into the dataset for analysis. One additional benefit to this collection methodology is that it allows the collection of additional data without creating extra log entries, as might be created using page tagging methodologies.
For more information about processing, see the Dataset Configuration Guide.
Add the following code to the top of the .jsp page from which you want to capture data:
<%@ page import="com.visualsciences.collector.VSCollector" %>
Use the appendToLog() method of the collector object to append the desired name-value pairs to the requested .jsp page’s query string. The following example appends “A=1” and “B=2” to the requested .jsp page’s query string for the /index.jsp page:
<html> <body> <h1>Hello World</h1> <% VSCollector collector = new VSCollector(request, response); collector.appendToLog("A", "1"); collector.appendToLog("B", "2"); %> </body> </html>
The resulting request URI is /index.jsp?A=1&B=2.
Repeat this procedure for each .jsp page from which you want to capture additional data.