(DTERP-2111) Release notes

DT-ERP 2111 Infosession.mp4

New Features

SAP S/4HANA system support

From this release, we are supporting S4HANA systems with all our transports.

Storage service customization simplification

Setup of the source requires creating source definition and mapping to the storage in two separate steps. As the one source can have only one storage assigned to it we merge these two steps into one.

Performance Monitoring

Last release we added functionality to collect archiving statistics and this one front end were built, so you can have better insights into how the incoming HTTP requests are performing. 

Performance results contain the most important indicators of the HTTP request like runtime that is even further broken down to its components like time spent on the storage and so on.

Health check for a content server

Report that verifies whether the actual configuration that is on the system is complete and indicates the possible issues with the configuration. 

Checks that are included in the functionality

• Check the license
• HTTP service check all services that have our HTTP handler
  • whether active
  • user is filled for the service
  • user has assigned our service role
• Check all Sources
  • mapping to SM exist
  • no signature parameter is OFF
  • certificate is received and valid
  • parameters are filled like (Source SID, Client, Cont. rep, RFC destination)
  • storage checks
    • storage is binary
    • hash calculation  is enabled
• Application log excluding rules
  • for which external id it is switched or not
• Statistics check
  • whether are switched ON or OFF
  • size of statistics on DB
• Retention management
  • archiving object customizing check whether both legal entity and retention date field is defined

Insights collector

If you already have Insights and want to monitor the performance of the content server then the new version contains special transport that contains a collector that provides such KPIs. Values are calculated from performance statistics therefore make sure that you have them turned ON before you start the collection of the data.

• Requests
  • Write requests   
  • Read requests
  • Administration requests
  • Failed write requests
  • Failed read requests
  • Failed administration requests
• Runtime
  • Average read request runtime [Size < 1MB]
  • Average read request runtime [1MB >= Size < 10MB]
  • Average read request runtime [10MB >= Size < 50MB]
  • Average read request runtime [Size >= 50MB]
  • Average write request runtime [Size < 1MB]
  • Average write request runtime [1MB >= Size < 10MB]
  • Average write request runtime [10MB >= Size < 50MB]
  • Average write request runtime [Size >= 50MB]
• Size
  • Read request size
• DB size of statistic tables
• HTTP service available
• Write request size

Tool to download stored data files on demand

Simple tool for mass export of stored files based on document IDs to the given location of the application server.

Tool transaction: /DVD/CRP_DL

In three simple steps, you define the selection of the files that you want to download generate the execution portions and execute the portion in background jobs.

Usability improvements

• Analyzer
  • Straggler analysis - Examples - Missing headline of 2 columns
  • Change the order of columns for "Create new analysis run"
• Mass-arch wizard
  • check and customize for phases
    • added checks whether the customizing of the archiving object is correct
  • Integration of selection criteria with Retention Management
  • Archiving object column in the run list
  • Deletion of the variants generated by the mass archiving run
  • Runtime estimates per arch. variant
  • Sort in mass archiving monitor
• Navigation to Archive migration toolset from the cockpit
• Re-branding of the product

Mass archiving - online analysis

Mass archiving analysis requires that at least a quick analysis is done before you want to use it. The new version enables you to skip the analysis execution for some of the archiving objects.

Supported archiving objects

Bug fixes

Registration job over-flood

Retention Management's registration job is scheduled with every store request arriving content server. When storing ADK archive files as well as document attachments. This may over-flood the system the Outboard is deployed on with background jobs waiting for other jobs in the status released.

This could be avoided by scheduling registration jobs periodically with an option to add only new documents that were added to the content repository. This information was updated to the info of expert setting REG_RET_ENABLED of Tool name: CRP_RM.

Create using POST with no multipart ends with internal error due to missing data

Insert of data to storage fails when the "create" command uses method POST and the request does not contain any multipart.
Response is: 500 Internal server error, "Request contains no data to be inserted".

According to the ArchiveLink interface documentation "create" request using the method POST must contain transferred data in multipart. Therefore, if there is no multipart the Outboard will respond with status code 400 (bad request).