Instructions for installing your license(s) are available under
'our Management System''License' '"Add, Assign or Un-assign Licenses' in
the "Intercept Studio User Manual"
for more information.
The uX Collector is deployed for the same web sites where
monitored application is installed. The uX Management Console is
used to configure the relative uX Collector path for the
application. The URL to send client side events and statistical
information to the Collector is set to
/CsmCollector/CsmCollectorService.asmx. Therefore the user
should decide what applications he/she wants to monitor and deploy
the uX Collector in corresponding web sites via the uX Collector
Configuration utility
Please see 'Configuration' 'Intercept uX Management Console
'General Properties'
'Collector Settings' in
this manual for more information.
The list of valid applications that are enabled for monitoring
through the Intercept Management console will populate the list of
available applications. If the list is long, enter any part of the
name of the element to search for in the 'Search for Applications'
field (search results will be highlighted on the fly as you
type). Select the application to monitor.
Click OK
A pop-up message will appear that notifies you that the
application has been added for monitoring, and that the Application
Code Scan utility will be launched. Please read the
Application Code Scan utility section of this manual for more
information.
To set the Collector service connection, it is important to know
that the address is visible from the outside clients. When the
Collector is installed on the same server as the monitored
applications, typically the DNS name for the server is well known
and accessible from the outside. When the Collector is on a
separate machine however, the only way to ensure that the address
is visible outside of the internal network is to test it from a
device outside of the internal network, such as a cell phone with
web access or Remoting into an external machine.
On the uX Collector server, go to
Start
Programs
AVIcode Intercept Studio
Intercept Configuration
Intercept uX Management Console
Right-click the 'Web Applications' node
Choose 'Properties' from the menu
Go to the General tab
Set the Collector Service URL. By default this is
set to the relative path "/CsmCollector/CsmCollectorService.asmx".
Note that this URL may be modified to use a non-default port number
or https, but it must always point to the semlogws.asmx web service
with an address that is formatted as:
FOR TESTING WITH CLIENTS WITHIN THE INTERNAL NETWORK: Click
Test Connectivity . Try correcting
the Collector Service address if the connection fails.
FOR PRODUCTION SERVERS AND CLIENTS OUTSIDE OF THE INTERNAL
NETWORK: Copy the Collector Service URL, and copy it into a browser
on a machine outside of the internal network. If the web service
schema and method list (e.g. 'Echo') does not appear, try
correcting the Collector Service address. Click on the 'Echo'
method, enter a test string, and click Invoke . If the string is not returned by the
service, try correcting the Collector Service address.
If an existing firewall will change the client IP address in
messages to the Collector, the IP Client properties can be set to
ensure that the correct IP address is reported in the event
statistics.
On the uX Collector server, go to
Start
Programs
AVIcode Intercept Studio
Intercept Configuration
Intercept uX Management Console
Right-click the 'Web Applications' node
Choose 'Properties' from the menu
Go to the Client IP
tab
Select an existing firewall setting or create a new one if the
information is available.
If the application is not on a load balanced server, then IIS
may be restarted after configuring the Intercept Agent and the
Collector. If this is a load balanced server, then:
Remove the Application Web Server from the Balancing
Rotation
Restart IIS
Return the Application Web Server into the Balancing
Rotation
'License' 
Please read the
Application Code Scan utility section of this manual for more
information.
If the application is not on a load balanced server, then IIS
may be restarted after configuring the Intercept Agent and the
Collector. If this is a load balanced server, then: