Once the CMS service has been added to the target system, it must then be configured and activated. Configuration is done by means of a group of system properties, 'Application Properties - Content Management Settings', which can be found in the Property Administration section of the System Administration application.
Update the CMIS properties listed below as follows:
Property |
Description |
Default Value |
---|---|---|
curam.cms.enable | Indicates if the Content Management Interoperability Service is enabled. True/false flag. True determines that the storage location for certain files is in a configured CMS. False determines that the storage location is in the Cúram database. | true |
curam.cms.attachment.enable | Indicates if storing attachments to the CMS is enabled. True/false flag. True determines that the storage location for attachments is in a configured CMS. False determines that the storage location is in the Cúram database. | true |
curam.cms.proforma.enable | Indicates if storing pro forma communications to the CMS is enabled. True/false flag. True determines that the storage location for communications is in a configured CMS. False determines that the storage location is in the database. | true |
curam.cms.curam.dir | The absolute path to the root directory for Cúram content within the global CMS repository used by the Cúram application. Must begin with a '/', must not end with a '/', and must not contain any unsupported characters. Refer to the CMS documentation for more specific information on what characters are unsupported. | Set based on the organization implementation, e.g., /Curam |
curam.cms.repository.name | The single repository for the global CMS account used by the Cúram application. | Set based on the organization implementation. |
curam.cms.sso.enable | Indicates if Single Sign On (SSO) is enabled. True/false flag. True determines that SSO support is enabled. False determines that SSO support is disabled and that default authentication will be used. This should only be set to "true" when the organization has implemented the custom code for SSO. Further information can be found in the chapter on customization. | false |