A–C
D–H
I–Z
Developer services
Project centers
Community resources
- Adobe Cookbooks (share code)
- CSS Advisor (browser bug fixes)
- Exchanges (share components)
- Adobe Labs
- Adobe Open Source
- Forums
- RSS feeds
- Bug base
- User groups
- Adobe Community Experts (ACE)
- Developer events
Integration
Product documentation
Downloads
Samples
Training and books
- Online training
- Classroom training
- Certification
- Adobe Developer Library
- Adobe Press
- Safari Books Online
Newsletters
Blogs
Archives
ADC program
Additional resources
Table of Contents
Creating a Custom Contribute Publishing Service
Architectural Overview
The Contribute Publishing Services are components of a server application that runs on a server somewhere in your organization. When you enable a website to use Contribute Publishing Services (CPS), you specify the address of this server. This instructs all of the Contribute clients that interact with that website to send a stream of event data to the CPS server over a secure connection. These events (editing, publishing, sending for review, and so on) represent the major actions a user undertakes transmitted as SOAP web service invocations.
Most of the publishing services are built on these events. For example, the Logging service logs the event data to a file on the server, and the E-mail Notification service e-mails users about pages sent for review. Custom publishing services are supported through the Forwarding service, which passes along the event data through additional web service invocations.
The following diagram illustrates how a publish event is posted to the CPS server and forwarded to a custom service implemented in ColdFusion.
Figure 1. How a publish event is posted to the CPS server and forwarded to a custom service implemented in ColdFusion
The User Directory service uses a separate web service API for extending how Contribute selects, authenticates, and retrieves connections for users. This article focuses on the event API.
