Core Service
The Core Service is a SOAP Web service based on Windows Communication Foundation. It supports WS-I Basic Profile 1.1 and more advanced WS-* protocols.
- Content Manager item identifiers used by Core Service
The Core Service exposes two separate ways of identifying an item in the Content Manager: Content Manager URIs (TCM URIs) or WebDAV URLs (Uniform Resource Locators). - Core Service and the old TOM-based Event System
To fire TOM-based Event System triggers, Core Service requires the Legacy Pack for SDL Web 8.5, which contains the Legacy Event Adapter. - Core Service versioning
To support backward compatibility, new releases of SDL Web (formerly called SDL Tridion) return data that an old client can handle gracefully. For Java, the XmlBeans proxy generator is most reliable to handle compatibility issues. - Core Service mapping
The Core Service is documented in API reference documentation as a server-side C#.NET API exposed through a WSDL in your proxy client. But strong typing and namespaces cause differences between the documented API and the API you use. - Endpoints and bindings
Configure the default IIS-hosted end points in your web.config file. Configure the net.tcp end points in your TcmServiceHost.exe.config file. You can also create custom endpoints and bindings. Anendpointhas a URL andbindingproperties that specify how the data will be transferred. - Core Service clients
Use the built-in .NET client to interact with the Core Service, or create your own proxy client. You can also send raw XML to the Web service. - Synchronizing a content item and its Schema using the Core Service
If a content item and its Schema are not in sync, you can use the Core Service API to synchronize them. A typical use case for this would be a change to an existing Component Schema which has many Components based on it: first query the Schema to get a list of Components that use it, then synchronize the list in one go. - Interacting with the Core Service from client-side .NET
Interact with the Core Serivce from client-side .NET to make your .NET code interact with the Content Manager core. When connecting from an add-on, further add-on-specific configuration on the client and/or server may still be required. Refer to the add-on documentation for details. - Interacting with the Core Service from Java
If you are accessing the Core Service Web service from a Java proxy client, you can see some examples of typical tasks. When connecting from an add-on, further add-on-specific configuration on the client and/or server may still be required. Refer to the add-on documentation for details.