Here’s a techie from Justin Townsend. We’re working on some interesting ideas and clients (and client bids), where this is relevent.
Using the integrated application (Core Oracle/Siebel modules combined with Analytics & Marketing functionality) relies quiet heavily on the use of web services. These services are invoked in a ‘traditional’ SOAP interface, providing the communication links between the applications.
In a standard installation of the integrated application, web services are used for: pass-through authentication, execution of Marketing jobs and serving up of Analytics and Marketing resources within the integrated environment.
WebCatalogServiceSOAPKPI, as the name may suggest, serves up resources from the Analytics application which are stored in the web catalog file. Using this service you can access: dashboards, requests, iBots, segments, segment trees and list format definitions.
This WebCatalogServiceSOAPKPI is particularly important where the business has many pre-defined reports (visible on dashboards or via requests). In combination with the definition of a symbolic URL, the web service serves up these pages to the user when they access dashboards related screens in the integrated application.
Symbolic URLs are defined in the core Siebel application; when the application’s services are started up, the definitions for these symbolic URLs are stored in the web server cache.
When making changes to symbolic URLs, you need to ensure the cache is cleared to make sure the amended definitions are used by the web service.
Symbolic URLs are defined in:
Administration – Integration > Symbolic URL Administration;
the cache is cleared in:
Administration – Marketing > Servers, Outbound Web Service Port (hyperlink) > Outbound Web Services