Web Connector Configuration Options
In general, you can use a graphical Web Connector interface to configure your Web Connector settings. All of the settings you specify are also stored in a file called jsconnector.xml, found in your jsconnector/conf directory. Each of the parameters that are saved in the jsconnector.xml configuration file is described here.
Parameters and their descriptions
The following parameters are stored in the jsconnector.xml file and are used for Web Connector interactions. There are two ways to modify these settings:
*
The changes you make on the Administration web page are stored in the jsconnector.xml file on the server where the Web Connector is deployed.
*
Edit the jsconnector.xml file directly using any text editor or XML editor. Be sure that you are comfortable editing XML tags and values before using this method.
*
Any time you edit the jsconnector.xml file manually, you can reload those settings by opening the Web Connector Administration Page (found at http://<host>:<port>/interact/jsp/jsconnector.jsp) and clicking Reload Configuration.
The following table describes the configuration options you can set as they appear in the jsconnector.xml file.
Name of the audienceId field used in the API call to the Interact runtime.
The datatype of the audience ID field [numeric | string] used in the API call to the Interact runtime
Used in the API call to the Interact runtime. In general, this parameter is set to "true".
Used in the API call to the Interact runtime to enable debugging output to the log files.
Default max number of offers to be retrieved from Interact for this interaction point.
Boolean flag (acceptable values: true or false) to turn on special debug mode. If you set this to true, the content returned from the Web Connector includes a JavaScript call to 'alert' informing the client of the particular page mapping that just occurred. The client must have an entry in the authorizedDebugClients file to generate the alert.
A Boolean flag (acceptable values: true or false) to determine whether the Web Connector attaches the raw offer data in JSON format at the tail end of the content.
A Boolean flag (acceptable values: true or false) to determine whether the Web Connector attaches a Digital Analytics for On Premises tag at the end of the content.
Represents an implementation of the APISequence interface, which dictates the sequence of API calls made by the Web Connector when a pageTag is called. By default, the implementation uses a sequence of StartSession, pageLoadEvents, getOffers, and logContact, where the last two are specific to each Interaction Point.
Represents an implementation of the APISequence interface, which dictates the sequence of API calls made by the Web Connector when a clickThru is called. By default, the implementation uses a sequence of StartSession and logAccept.
Represents the HTML and JavaScript template used to integrate a call to the Digital Analytics for On Premises tag. In general, you should not need to change this option.