Filename encoding on content server

[Former Member]

Hi experts,

In DMS we are using file system repository from the SAP Content Content installed on HP-UX. When we save files with the russian filename all symbols in the saved file are encoded with % + hexadecimal representation. So we can save files only with the short names. When we try to save file with the long filename its encoded name exceed 256 symbols limit and system give us an error.

I appreciate any suggestion or any workaround.

Best Regards

Pavel

[christoph_hopf]

Hi Pavel,

if possible I would recommend you to upgrade your content server patch level to the latest available. For further information please see SAP note 514500.

Best regards,

Christoph

[Former Member]

Hi Christoph,

Thank you for your suggestion. We are already on the latest version.

Seems this limitation is impossible to overcome and the only way is to switch to DB based repository.

Best Regards

Pavel

[Former Member]

The official answer from SAP:

Content Server operates on Non unicode mode which means it cannot store
the files or documents with special characters(russian here ),Hence KPROLayer before it sends the document for Storage to the Content Server it
converts the russian file name to binary format.
During the Conversion each special(russian) is mapped to particular
format, hence after conversion the file name would be large,Since it is
a File System Repository,the operating system wont allow to create the
files larger than 255 characters.
Hence this is a limitation from Operating system, the files exceed 255
characters, it is not supported.
Even if the Content Server is based on MaxDB, the length of the
converted result is same and MaxDB also has the maximum filename
restriction of 254 characters.
If the ECC system is unicode,the length of the converted result will be
short than now (this is the behaviour in our internal system which is
unicode).This should resolve the issue, but we are not completely sure
of this.
However if you use R3 System Database, there will be no issue as
conversion does not happen there.

But with MaxDB it works.