For docuflow ECM the repository ID, albeit mandatory, only requires it to be created with a meaningful description – the details within the repository ID page are irrelevant. No certification needs to be sent as well as additional repository ID CS administration functionality is not relevant (and will fail if you try as this is only utilized by Content Servers). An example is shown below: 

        2. Make sure the changes are saved and captured in a transport so that they can be transported to other environments. 




docuflow ECM

docuflow Content Server

Base SAP ArchiveLink Configuration

docuflow for FileNet

Introduction and Overview

Component and Architecture Overview

Supported Environments

Minimum Requirements for docuflow

Technical Overview

Purpose of Guide

Installation Overview

Customer Resources Required

Overview for SAP Basis

Overview for SAP Security

Overview for FileNet/Content Manager and Middleware Team

Installing the docuflow Enterprise Connector

Installing the docuflow SAP Transports – docuflow ECM Only

Create SAP system account – docuflow ECM Only

Grant Necessary SAP docuflow authorizations

Grant Necessary SAP ArchiveLink authorizations – docuflow ECM or Content Server

Configure SAP RFC destinations – docuflow ECM Only

Configure SAP Gateway – docuflow ECM Only

Base SAP docuflow Configuration – docuflow ECM Only

Base docuflow Enterprise Connector Configuration – docuflow ECM Only

Base docuflow Enterprise Connector Configuration – docuflow Content Server Only

Establishing SAP <-> docuflow Enterprise Connector Connectivity

Configure viewing from SAP – docuflow ECM Only (optional for Content Server)

Follow up Basis Tasks – docuflow ECM Only

Follow up Security Tasks

Follow up Content Manager and Middleware Team Tasks

Follow up FileNet and Middleware Team Tasks

CMIS configuration

Installation and Base Configuration Guide

Solution Guide

Developers Guide

What's New

for ECC and S/4