Content Repository Definition

Transaction: OAC0

  • Can be assigned to a transport request.

The Archiving client connects with the archiving service that is using the content repository definition. Once the setup is complete, perform a connection test.

  • Content repository connecting to the SNP Outboard™ Service: D1

Property

Description

Value Example

Content repository

Content repository name.

D1

Description

 

Outboard – <storage type> content repository

Document Area

Communication interface.

<depends on data to be stored>

Storage Type

Repository type.

HTTP content server

Protocol

The protocol is required if a specific application needs to be used to display ArchiveLink document attachments.

n/a

Version no.

ArchiveLink protocol version.

0047

HTTP Server

Hostname of target storage service. The SNP Outboard™ Service runs locally on the same SAP system, therefore it must be the system hostname.

<system host name>

Port Number

HTTP port number of the system.

8000

HTTP Script

Content server path on the web server with the SNP Outboard™ source ID.

dvd_crp_http/E1_D1

SSL

Requirement to use secured communication

Not required – running within an internal network

Basic Path

File path for asynchronous storing of archived data.

<ideally same as the physical path in the logical file path used as staging folder for archiving>

Archive Path

File path for archive file retrieval.

<ideally same as the physical path in the logical file path used as staging folder for archiving>

No signature

Forging communication without signature verification. Also available if the SNP Outboard™ Service is in No signature mode.

<empty>

The Port number and HTTP Script can be found in the Message Server Monitor.

  1. Start transaction SMMS.

  2. Go to Parameters > Display.

  3. Search for the corresponding values in the parameter's table.

  4. HTTP Script ** -> server host (fqn) and Port number ** -> ms/http_port.

 

NOTE If the check of the content repository returns the message Content repository <CREP ID> does not exist, a problem may exist with an authentication set in the HTTP service (transaction SICF). Try to remove SAML Logon from Logon Procedure List of the service.