Audience Manager custom binding
If you want to connect to the Core Service using an endpoint other than the default NetTcpBinding or wsHttpBinding bindings, you can create a custom binding. This topic provides an overview only. For more detailed information, refer to the Core Service documentation itself.
- Core Service
-
The Core Service is an API that interacts with the Content Manager through a web service that uses the Windows Communication Foundation (WCF) standard. Audience Manager connects to the Content Manager through the Core Service. The following diagram shows a standard installation where an Audience Manager WCF client is installed on the same server as the Content Manager Server:
- The Content Manager Server runs as a web application in Internet Information Services (IIS).
- The Core Service runs in a virtual directory if you connect to it using HTTP (if you connect using NET.TCP, the Core Service runs as a Windows service).
- Audience Manager also runs in a virtual directory within the Content Manager server web application.
- Audience Manager default connectivity to the Core Service
-
Audience Manager connects to the Core Service via an endpoint. Audience Manager provides out-of-the-box endpoints for connecting to the Core Service using the
NetTcpBindingorwsHttpBindingbindings which use respectively thenet.tcpandhttpprotocols to communicate with the Core Service. - Creating a custom binding for Audience Manager
-
If you want to connect to the Core Service using an endpoint other than the default
NetTcpBindingorwsHttpBindingbindings, or if you want to specify your ownbindingproperties for these protocols, you need to develop custom bindings and endpoints.