Managing Content Storage
System administrators use the Content Service page to manage the storage locations available for publishing content to the server. Published content is physically stored in the locations configured in the content service. It typically resides on a separate file server for backup purposes and to provide failover capability and high availability in a My webMethods Server cluster.
My webMethods Server stores the binary content of a file in a content service (either system or network) when you:
Publish a file to the server
Update a file
Check in a new version of a versioned file
The binary content is physically stored in the content service for as long as the file object exists in My webMethods Server. The binary content is marked for deletion when you delete the corresponding file object on My webMethods Server, but the actual file is not deleted until the regularly scheduled purging period. Typically, My webMethods Server purges deleted objects at 2 A.M. server time.
When you set a new default content service, all new content is directed to that service, but content stored in an existing service continues to be accessed from that service.