The SAP Content Server is a stand-alone component in which a large quantity of electronic documents of any format and with any content can be stored.The SAP applications concerned must support the use of the SAP Content Server. The documents can be saved either in one or more MaxDB instances or in the file system. The SAP Content Server is available for Windows 2000 & 2003 Server as well as for several UNIX variants.
Any number
of content servers can be installed in different locations.As well as
content servers, cache servers can also be used for distributed data retention
to enable quick access to document contents if, for example, you want to
display a document in a Web browser. To do this,
the cache server creates and stores “working copies” of documents
from the content server. For further
information see Knowledge Provider and
Caching.
For
information on how the server works see Architecture of the
Content Server and
Architecture of the
Cache Server.
Below is a list of all the tools relevant for the administration of the SAP Content Server:
·
Content Server
Administration
(transaction CSADMIN) for the
administration of cache and content servers
·
Content Repository
Administration (transaction OAC0)
·
SAP CCMS Monitor for
Optional Components(transaction SCMSMO) for monitoring content and
cache servers
· Database Manager GUI (DBMGUI) or Database Manager CLI for the administration and configuration as well as monitoring and backup of the MaxDB.
·
Customizing for Cache
Servers (transaction SCMSCA)
The SAP Content Server must be installed. You can find information on how to install the SAP Content Server for Windows in the SAP Service Marketplace under the quick link /contentserver ® Media Library ® Literature. For UNIX information, see note 664385 in the SAP Service Marketplace.
For information about availability on various platforms see the SAP Service Marketplace under the quick link /PAM.
The SAP Content Server is not an alternative to optical storage systems and other storage media for long-term document archiving.
The table below lists the most important administration tasks.
Task |
Additional Information |
Start and stop server |
Information about starting and stopping the server under Windows and Unix can
be found in |
Manage repositories |
|
Make security settings |
This contains information about secure URLs, encrypted data transfer, security
against data loss, and protection against unauthorized access to
administration functions.
The corresponding information for the cache server can be found under: |
Save logs |
If necessary, you should perform a By setting the |
Optimize performance of cache server use |
Multi-Layer caching and content server aliases compliment each other. The main aim of multi-layer caching is to minimize access times. Also, URLs received via a content server alias can be handled in such a way that controlled content server accesses from the extranet can be allowed via a firewall. |
Trouble-Shooting |
The following errors occasionally crop up:
|
The following tasks must be done periodically:
Task |
Additional Information |
Create database backup |
The backup strategy depends on the size of the content server database and on the volume of changes per day and week. |
Monitor content server and cache server |
The server is monitored automatically in the |
See also:
·
For more
information about the SAP Content Server see SAP Content
Server and the
Operating Manual for SAP Content
Server.
·
Notes can be
found under Notes on SAP Content
Server Themes.