MACROMEDIA CONTRIBUTE 3-CONTRIBUTE PUBLISHING SERVER Manual - page 17
Creating a custom publishing service
17
Related topics:
•
“About extending the Simple File Deployment service” on page 20
•
“API data types” on page 22
•
“Web service methods” on page 23
Creating a custom publishing service
The Contribute Publishing Server (CPS) API enables you to write custom services to add more
server-side functionality. For example, with the CPS API you can make the following types of
server-side capabilities possible:
•
Logging changes to a database for auditing
You can write a server-side script to record all site activity against an inventory database.
•
Automated page-checking at the time of publication
You can write a script to check content before it’s published. Checks might include
compliance with standards, such as Section 508, or broken links.
•
Setting file permissions
You can write a script to reset the permissions of newly written files so that all members of a
department can edit them after they are published.
•
Indexing content
You can write a script to index published content for searching. Or, you might want a script to
maintain an index for the title, author, or date of documents.
•
Enhancing the draft review process
You can write a server-side script to create more detailed reports or to trigger more e-mail
notifications, such as one that might alert a reviewer that a draft has been waiting for review for
a specified amount of time.
Note: If you want to create a service to move files from a staging/testing server to a live/production
server, you can extend the Simple File Deployment service. For more information, see
“About
extending the Simple File Deployment service” on page 20
.
CPS sends events to services using the SOAP format over HTTP or HTTPS. A custom service is
implemented as a web service, with a web service method for each method of the CPS API.
To create a custom publishing service:
1.
Write a web service that implements the CPS API.
See
“Write a web service that implements the CPS API” on page 18
.
2.
Install the custom service on an application server that CPS can access.
See
“Installing the custom service on a server” on page 19
.
3.
Configure the CPS Forwarding service to send events for each website to your custom service.
See
“Forwarding website events to a custom service” on page 14
.
4.
Test and troubleshoot you implementation.
See
“Testing and troubleshooting your custom service” on page 19
.