Variations

Variant 1: Data Storage on NetWeaver Server Database

The downloading of files that are stored on the database of the NetWeaver system is covered by standard HaloCORE functionality. When using SAP Document Management Services (DMS), it is highly advisable to install and configure some additional logic to better capture significant details from the DMS context (e.g., about the Document Info Record) where the file originates. This logic is included in the software component SECUDEEC (HaloCORE for DMS); integration occurs by implementing BAdIs DOCUMENT_STORAGE01 and DOCUMENT_FILES01 as described in this manual. 

Variant 1

Variant 2: Data Storage on Content Server

When files are stored on external content servers and caches, data exchange at the time of upload and download occurs directly between the front-end and the content server or cache, without the files transiting via the NetWeaver server. To intercept this data, one or more HaloCAD Content Server Proxy (CSP) instances must be deployed. The HaloCAD Content Server Proxy communicates with HaloENGINE, which decides on the action to be performed. Note: The Java component “HaloCAD KPro” is also called “HaloCAD Content Server Proxy” throughout this section.

To minimize data flow, it is recommended to place the HaloCAD CSPs as closely as possible to the content servers and caches.

Variant 2

Prerequisite: Before you begin the installation, ensure you have installed HaloCORE for NetWeaver beforehand as described in the HaloCORE Installation Manual.