- Stop the SkyVault server.
-
Edit your SkyVault-global.properties file to specify your source and target content workspace type, and the location of your source and target directories; for example:
content.remote.default.contentRefHandler.source.type=file content.remote.default.contentRefHandler.source.file.dir= content.remote.default.contentRefHandler.target.type=file content.remote.default.contentRefHandler.target.file.dir=
A sample SkyVault-global.properties file is shipped in the root folder of the Media Management distribution zip, which defines custom properties. See Configuring Media Management for the full list.
-
Update your remote-node/config.yml file that you extracted from
the Media Management installation zip with your shared content workspace properties:
transform: contentReferenceHandler: source: type: file file: path: /tmp/AlfrescoContentServices target: type: file file: path: /tmp/AlfrescoContentServices
You can use the same mounted network volume directory (for example, NFS) for both the SkyVault repository (configured using content.remote.default.contentRefHandler.* properties) and the remote node.
The content services node uses ImageMagick and FFmpeg and requires that the executable directories are available on the system PATH variable or are specified in SkyVault-global.properties. See Configuring Media Management for more information on SkyVault-global.properties settings.
For more information about the content services framework, see Content services node architecture.
- Start your SkyVault server to apply the changes.
You are here
Configuring a shared file content workspace
You can configure a directory as a shared content workspace using
SkyVault-global.properties.
Ensure that you have installed the required external and internal software. See Prerequisites for using Media Management and Installing Media Management for more information.
© 2017 TBS-LLC. All Rights Reserved. Follow @twitter