Hi everyone,

I just got started with webtrends a week ago. I got webtrends.js from tagbuilder.webtrends.com for my dcsid.

I embedded this into my jsp and when my page loads no weblogs are being created if the url has an https header in it.

However if it is http logs are generated.

I have successfully imported a SSL cerificate and configured port 443 in IIS.

I need guidance as to why would http calls get logged and why not https? is there any parameter that we are supposed to configure?

Thanks in advance.
Sunny.

To start, is the pixel request secured? Your page may be secured but if the image request goes through an unsecured path, the pixels will be standard http. Make sure that the pixel call uses https.

"Make sure that the pixel call uses https."

How do i go about doing this?

Thanks.
Sunny.

This should be handled automatically by webtrends.js. No additional configuration required.

To troubleshoot, load the page in browser and enter this in the address bar:
javascript:dcsDebug()

This will create a popup with the protocol used in the pixel request.

I tried dscDebug().. The strings are all correct.

I think that may be the problem is that i have a single deployment of webtrends.. where in SDC and the webserver are on the same box. I think this might not be a supported configuration with webtrends!! any ideas abt this??

Thanks in advance.

You are correct in assuming that it's not a supported configuration. 'Technically' they shouldn't interfere since they're using different ports, but there's a chance you might miss logging data if the server gets too saturated during an analysis.

As for troubleshooting, all should have to do is make sure that the SDC server has a valid certificate, and the tag should autodetect whether or not you're using HTTPS in the page load and send the hit to the SDC with the appropriate protocol.

If you want to test manually, you can always take the string you get back from dcsDebug, and send it manually to the SDC and monitor the result with something like HTTPfox or HTTPwatch (in IE). Those tools generally show you things like cert failures or connection failures.

You can always craft your own hits of the format:

http://sdc.yourdomain.com/your.../dcs.gif?dcsuri=test

and see how it works.