!--a11y-->
HTTP Access for Repositories on SAP Web Application Server 
Use
Knowledge Provider’s Content Management Service can use both the HTTP server and the HTTP client interface of SAP Web Application Server (see also
HTTP Communication with the SAP System as a Client and
HTTP Communication with the SAP System as a Server). 
The test report
The SAP Content Server Interface (see also
SAP Content Server HTTP 4.5 Interface) is implemented in the SAP system as of Release 6.10. This makes the database repository HTTP-compatible. HTTP compatibility contains the functions of the above-mentioned interface.HTTP compatibility comprises the following functions:
For example, SAP ArchiveLink can use the database repository as a HTTP Content Server repository if the corresponding settings are made in transaction
This allows you to use the SAP system as a gateway.

Use the class
This functionality is intended for use in the following situations:

The gateway must be at a different location from the application server.
Prerequisites
SAP Web Application Server Components and
Structure of the ICM.

If an SAP system has more than one application server, HTTP need only be activated on one application server.
Features
HTTP Access to Repositories
It is possible to access repositories via HTTP using SAP Web Application Server (see also
SAP Web Application Server), especially R/3 database repositories. To do this, in your system you need a user for anonymous access, without any permissions (see below). You can create this user in transaction SICF (see below). If you do not create this user, the system outputs a logon screen at the relevant point. 
If you want to use cache servers for HTTP access to repositories via SAP Web Application Server, you need a database repository with version 0046. There are no plans to support cache server functionality with version 0045 database repositories.
Certificate Administration
Full certificate administration is supported (transaction
CSADMIN, tab page Certificates).In transaction
OAC0, set up a repository and choose Environment ® CS Admin to go to transaction CSADMIN. You can then administrate certificates in this transaction. A dialog box appears, in which you have to enter your user and password. The client is entered automatically. From release 6.10, you have the option of specifying the client yourself. Once you make these entries, the authorization object S_TABU_DIS is used to carry out an authorization check. Both read and write authorizations are checked:
Note that these authorizations are only valid for administration commands, not for the service user mentioned above.
You can now make settings on the tab page Certificates in
CSADMIN:
You are working in system A. If you want to make your own database repository accessible to another SAP system (system B), system B must send a certificate to system A. You then have to activate this certificate in your SAP system (system A).
CSADMIN
supports certificate administration only for the R/3 database. It only supports read access for all other functions. A statistics function is not available.Activities
Creating a User for Anonymous Access

This user type corresponds to the former CPIC user.

Do not assign any permissions to this user.
Store User in the SICF
Note that setting under Language here sets the language of the Content Server error messages.
When you create this user, the standard client is also specified.

Note that all services provided by SAP, as well as all newly created services, are initially inactive. Therefore, before you start working with the ICF, you have to activate the services you require. For more information on the Internet Communication Framework (ICF), see the ICF documentation under
Creating an ICF Service.
