KGS Content Server4Storage
Architecture Description KGS ContentServer4Storage presents itself to SAP as an HTTP server No additional database layer for the administration of content necessary As a JAVA-application it can run on any operating system (Windows, Unix, Linux, etc.) Minimal usage of resources
Configuration Advantages Connection to storage system: talks to storage media using storage system drivers Content administration: no additional database necessary Connection to EMC2 Centera: no simulation of file system, no additional logic layer, since the Centera CLIP-IDs (unique addresses of the content objects in Centera) are stored directly in the SAP link tables
Conventional Archive
Architecture Description: - The storage systems are connected through the archive system and its special modules
- The archive system uses a data base to administer the content and document information
- The archive system itself is not used directly by the user
Configuration Disadvantages - Performance: additional layer with servers, modules, data bases,....
- Implementation cost: licenses for archive, database, implementation,....
- Operational cost: software maintenance, operations personell, know how development,....
SAP Content Server 
Architecture Description The content server presents itself to SAP as an HTTP server The engine has been developed as an MS IIS (Windows) engine or a module of the Apache web server (Unix) The content server stores the data in the SAP data base or in the filesystem The storage drivers hide the specific retrieval mechanisms of the storage media
Configuration Disadvantages Connection to storage system: the content server can not talk to storage systems directly Size restrictions: individual objects can have a maximum size of 2GB Content administration: additional administration information in the KPro layer SAP maintenance mode: SAP has stopped any further development
|
|
|
|
|
