Managing Content Storage
The Content Service page allows system administrators to manage the storage locations available for content published to the server, which 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 a failover capability for high availability in a My webMethods Server cluster.
The default system content service stores files in the My webMethods Server database. You cannot modify the system content service but it is visible on the Content Service page.
If users of My webMethods Server store large files (1 MB or larger) or a large number of files, the system content service may not be adequate for your file storage needs. In such cases, you should provide a network content service to provide higher capacity. My webMethods Server supports network file storage by the use of a file system.
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 physical binary content is stored in the content service 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, such as the system content service, continues to be accessed from that service.
To configure a new Content Service for the server repository
1. As system administrator: Administration Dashboard > Content > Content Service > Create New Content Service.
2. In the Service Name field, type a name for your new content service.
The user ID can be 1 through 255 characters and can contain only alphanumeric ASCII characters with no spaces.
3. From the Type list, select File System and click Next.
4. Type a physical storage location for your content service.
On Windows, use a valid UNC path. The format of a UNC path is:
\\server\volume\directory\
and is not case-sensitive. For example:
\\my_sys\C$\temp
On UNIX, use the path the mounted location of the network storage:
\mounted_location\folder
Note: | There are many ways to configure an external content repository for My webMethods Server. This example assumes your network administrator has provided the proper security settings to allow all servers in a cluster to have read/write access to the network file system. If My webMethods Server runs as a Windows service, make sure the user account used to run the service has the right access privileges for the network file system. |
5. Click Apply.
6. To make the new content service the default content service, click 
Tools for the new service and then click Set As Default. The new Content Service becomes the default location for storing new content that is published to the server.
