Extended API for Implementations of CommandLineClient

CoreMedia introduced several extensions to assist implementing custom implementations of CommandLineClient and related.

(CMS-18408)

Import blob from generic URL in cm serverimport

The command line tool cm serverimport can import blobs with an arbitrary href attribute now. The container URL is retrieved and its content is persisted in the Content Server . This makes it easier to generate files for cm serverimport that reference preexisting blobs.

(CMS-18379)

Third-Party Update: Apache Solr 8.6.3

Apache Solr has been updated to version 8.6.3, which fixes security vulnerability CVE-2020-13957.

For detailed changes of Apache Solr have a look at https://lucene.apache.org/solr/8_6_3/changes/Changes.html .

(CMS-18355)

Third-Party Update: Apache Solr 8.6.2

Apache Solr has been updated to version 8.6.2, which fixes security vulnerability CVE-2020-13941.

For detailed changes of Apache Solr have a look at https://lucene.apache.org/solr/8_6_2/changes/Changes.html .

(CMS-18248)

UUID Support for dump-/restoreusers

The command-line tools dumpusers and restoreusers are now able to store and restore UUIDs of built-in users and groups. For dumpusers you may toggle UUID output via \-\-include-uuids . restoreusers will automatically respect the UUIDs when creating built-in users, unless --skip-uuids is given.

An additional option \-\-force-uuids for restoreusers will force changing UUIDs of already existing built-in users. Use this option with care.

For details and restrictions see Content Server Manual, Section Configuration and Operation /_Server Utility Programs_/_Operation_.

(CMS-17546)

cm serverexport/-import: Supporting Content-UUIDs

To be able to transfer new contents between CMS deployments while keeping their Universally Unique Identifiers (UUIDs) synchronized, you may now optionally export contents via cm serverxexport including their Content-UUIDs. To do so add --include-uuids to your command-line.

cm serverimport will recognize the UUIDs and will apply the Content-UUIDs to newly created contents. You may opt-out from this behavior by running cm serverimport with option --skip-uuids .

For details and limitations see Content-Server-Manual, section “Serverimport/Serverexport” in “Configuration and Operation”.

Upgrade Notes: Unless you opt-in to exporting Content-UUIDs the behaviors of serverexport and serverimport have not changed.

(CMS-17139)

Introducing Content-UUID-Migration Tooling

CoreMedia introduced three command-line tools, which are meant to support customers using multi-environment deployment like development and production, to synchronize UUIDs of documents. While for daily use, serverexport and serverimport have been extended before supporting export and import of content-UUIDs, these tools are meant to assist those, which had servers since before introducing UUIDs for contents.

The new tools will synchronize UUIDs of contents in two environments which share the same path and type.

Usage Example:

dev$ cm content-uuid-export -u <user> ... --output export.csv
prod$ cm generate-content-uuid-map ... --input export.csv --output merge.csv
prod$ cm content-uuid-import ... --input merge.csv

For details see usage information of tools provided with --help or have a look at the documentation of Server Utility Programs (Operation) in Content Server Manual , section Content-UUID-Migration .

(CMS-17000)

Command line tools support REPOSITORY_PASSWORD variable

Instead of providing the password to a command line tool using the -p option, you can alternatively set the environment variable REPOSITORY_PASSWORD now. The command line argument still takes precedence.

This avoids possible leaks of the password through the shell history or the process list. Do not set the password variable globally in an interactive shell, because it might then leak to other processes that are also started in the shell.

(CMS-14445)

Serverexport now also exports timezone id

Until now serverexport did only export the timezone offset (e.g. +0200) and missed to export the timezone id (e.g. Europe/Berlin). As the timezone id is displayed in Studio forms a serverexport and reimport caused that the date was displayed wrong.

In the exported xml a date field looked like this:

<extDisplayedDate format="dd.MM.yyyy HH:mm:ss Z">27.06.2019 00:00:00 -0400</extDisplayedDate>

and has changed to:

<extDisplayedDate format="dd.MM.yyyy HH:mm:ss Z VV">27.06.2019 00:00:00 -0400 America/New_York</extDisplayedDate>

The behavior hasn't changed. Xml content files with dates in old format can still be imported but may cause a wrong displayed date in studio forms.

Affects the fields extDisplayedDate as well as validFrom /{{validTo}} from the default document type model.

(CMS-11665)