After a project is approved for deployment, read the ATG Content Administration Programming Guide, which describes how to launch deployment of assets to a target site automatically or manually. It also discusses methods for recovering from deployment failure.

Note: The attachment server and the Knowledge Manager server must be on different hosts or domains to avoid cookie conflict. This can be done using DNS or by modifying the client host file to assign a different machine name to be used for the PublishingWebAgent URL. If the attachment server and Knowledge Manager server share the same domain, the session cookie used when accessing the attachment server will overwrite the Knowledge Manager server session ID, creating a cookie conflict.

Note for JBoss Users: If you are using JBoss 5.0 and using an Knowledge Manager server host name that is the same host name for the external content server, you must configure the following JBoss component:

 -Dorg.apache.catalina.connector.Request.SESSION_ID_CHECK=false