1. Content Management System Integration Guide
  2. Properties Impacting CMS Integration

Properties Impacting CMS Integration

The following properties control CMS Integration:

  • glog.defaultMimeTypes: These are used by Oracle Transportation and Global Trade Management Cloud documents (as in the document manager). It maps file extensions to a mime type (an application). When using attachments with Oracle Transportation and Global Trade Management Cloud documents, this tells Oracle Transportation and Global Trade Management Cloud what application to use based on the extension of the attached file.
  • glog.document.attachment.maxSize: While configuring a Stylesheet Profile, you can choose to embed a document. Document content is embedded in the notification. The attachment must be the same size or less of the bytes specified by this property. If not, Oracle Transportation and Global Trade Management Cloud Link is used.
  • glog.document.defaultCMS: the default Content Management System. Report storage, document types and ad-hoc uploads will default to this CMS. After installation, it is set to DATABASE, storing document content in the Oracle Transportation and Global Trade Management Cloud schema. If all document content should default to a given external CMS, this property should be modified to reference it.
  • glog.document.external.appendExtension: Many CMS products provide standard URI links for document content. If you click on one of these links, the browser may use the file extension of the file specified by the link to render content. To support this use case, OTM optionally appends the file extension to the uname, based on the content’s MIME type. These properties determine whether OTM appends the file extension to any uname it sends to a CMS.

    A mapping of MIME type to preferred file extension is available in glog.defaultMimeTypes property listed above.

    • glog.document.external.appendExtension.WCC: a flag to determine whether the document file extension should be appended to dDocTitle in WCC. This is necessary for some browsers to match up the document with its proper renderer.
    • glog.document.external.appendExtension.ODC: a flag to determine whether the document file extension should be appended to dDocTitle in ODC. This is necessary for some browsers to match up the document with its proper renderer.
  • glog.document.external.persistRemoveCases: a comma-delimited list of use cases where removal of a document link in Oracle Transportation and Global Trade Management Cloud should delete the corresponding document in the CMS. This property controls the deletion of remote content by OTM. If your CMS does not support document removal, or one to which OTM does not have rights to remove documents, the property should be set to blank to avoid removal errors.

Valid use cases include:

  • preview: Content was created to hold a temporary preview. Once viewed, the content should be removed.
  • overlay: Content was intentionally overlayed by the user by uploading new content into the Document manager.
  • revision: The user opted to remove a Standard Document revision.
  • user: The user opted to delete a Document.
  • owner: OTM removed a document when its owner was removed.

By default, OTM removes external content for preview, overlay, revision and user. This is to avoid the growth of unnecessary content on the remote CMS due to ad-hoc reports and erroneous revisions.

  • glog.document.retrieveURLMimeType: Determines if the URL should be accessed to set the content type on the document. The property defaults to true for backward compatibility.
  • glog.document.cms.msgraph.uploadChunkSize: This property is applicable to SharePoint Online. Defines the upload chunk size (in MB) for uploading a large file (>4 MB) in a single upload request
  • glog.document.cms.msgraph.validateFileUpload: This property is applicable to SharePoint Online. Determines whether to validate the uploaded content in SharePoint Online with the content in the source file.