How do you troubleshoot when you...?
Make sure that you can log in to https://sc.omniture.com/login/ to ensure that the company, user name, and password are correct.
Make sure that the user is added to the 'Web Services Access' predefined group on the SiteCatalyst side. See the official SiteCatalyst integration documentation for more information here.
Depending on which data center your account is located in, ensure that the endpoint for the 'Data Center URLs' is defined correctly.
Available SiteCatalyst Data Center URLs:
Follow the steps below to use the SiteCatalyst API Explorer to do a test call. This tests if the data center is available/responding and which data center to use.
If you know that your user has "Web Service Access' enabled, but don't know your web service credentials:
Now that you know your credentials you can run a quick test:
Now that you know which Data Center your account is on then:
One possible way to check which Data Center URLs to use - You can try to log in via https://sc.omniture.com/login/ and see where it redirects you to. Such as https://sc2.omniture.com, (Note the 'sc2' here means another data center 2 - 'https://api2.omniture.com/admin/1.3/rest/'). This may not work always (as there are different redirects), so please contact your Sitecatalyst support to get more accurate information on your designated Data Center Url.
If you have followed the step 3 and you still cannot connect to SiteCatalyst from AEM, then you possibly have a network, firewall, or proxy issue. Test the API connection from the server AEM is installed on:
If the API call fails, then communication between the AEM server and the SiteCatalyst API server is blocked. Consult with your Network Administrator to see if you need an HTTP proxy configuration or if the firewall is blocking connections to SiteCatalyst. Some possible network-related issues could be:
If you are using Windows and the API call succeeded, then you likely have a working HTTP proxy configuration in your browser settings. Check the browser's proxy settings and follow the steps in the next section to configure it in AEM.
If your Network Administrator advises you to use an HTTP proxy to connect to SiteCatalyst, then follow these steps to do so:
How do you troubleshoot when you have successfully configured AEM to connect to SiteCatalyst, but you do not see any requests being tracked (in Site Catalyst)?
** If you are using SiteCatalyst 15, then be aware that some data may not show up until 60-90 minutes after the tracking request.
The first step in determining why nothing is showing up in SiteCatalyst is to check if AEM is even including the image/tracking request that sends information to SiteCatalyst.
If the debugger shows that no calls are being made at all, then go on to the next step.
If no tracking calls are being made from your AEM site:
Make sure you:
If tracking calls are made from your Author environment, but not the live site, then make sure you: