ILM Database Store (New and Changed)

Asynchronous Processing of PUT Requests

The processing of PUT requests has been accelerated. What happens is that the data of the PUT request is first stored in a buffer file. After buffering, the request is returned and final storage of the data takes place in the background. You have the option of defining the amount up to which data is written directly to the database (as it has been up to now) or of buffering the data and then storing it.

Any Number of Connected WebDAV Servers

By changing the processing control, you can use each application server that is connected to the system as a WebDAV server for the ILM Database Store. By doing so, you can set up more systems that each have different users (WebDAV server addresses).

SAP HANA Database as an Additional Store Option

If necessary, you can connect a SAP HANA database to the ILM Database Store as a storage medium.

File System as an Additional Store Option

You can use a file system instead of a database as a store. This can be a fully-fledged replacement of the database or you can store just part of the data. We recommend storing only certain data (such as ISO images and the like) in the file system and moving the other data that is important for your business processes to the database.

Using Shared Files as a Transport Medium in PUT Requests

Currently, all data is transferred from the ADK to the store using an HTTP request in the body of the request. This data transfer is always limited to a size of 2 GB. To bypass the limits on data amounts, you can store the data in a shared file and transfer only the corresponding file names in the request. You can use this procedure for PUTs as well as GETs.

Evaluation Table with Basic Processing Information

You have access to a table that notes some basic data related to a request. You can evaluate this table according to your needs. For example, to determine how many PUT requests were answered in the last two weeks or the average processing time of a GET request up to now.

Infrastructure for Transporting Client-Specific Origin (SRS)

The Origin is the central element in the ILM Database Store with which you separate store scenarios and clients from each other. With this version you have the option of determining the Origin in the respective client system (using a BAdI implementation) and transferring it to the ILM Database Store using SRS. For example, you can send the archive files for the business application log to Origin #1 (which is connected to the file system as a store) while you send the FIN files to Origin #2 (which is connected to the database).

Using Variable User Agents (Optional)

Up to now, all requests to the ILM Database Store have been sent using SRS. This means that the ILM Database Store is only familiar with one user agent. All other requests to the ILM database store are rejected with the message that the user agent is unknown. With this version, you have the option of also using other clients to look at the contents of the ILM Database Store (with a BAdI implementation), for example, the DAV Explorer.

For more information, see http://service.sap.com/ilm. Choose Media Library  Installation and Configuration Guide for the ILM Database Store.