Show TOC

Providing ECM Repositories as Copies of the SAP TemplateLocate this document in the navigation structure

Prerequisites

You are familiar with the functions and use of the JCA.

Context

The SAP shipment of the ECM integration layer includes a connector for the SAP ECM back-end system, and an ECM repository (as a logical instance of the connector). The connector is defined in the Java Connector Architecture (JCA). The repository is represented by the technical object JCA Connection Factory .

Procedure

  1. Open SAP NetWeaver Administrator in the browser.
  2. Choose Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.
  3. In the list of application resources, display the JCA Connection Factories with ecm in their name.
    Note

    The JCA Connection Factory ecm/default represents the repository provided by SAP, where default is the repository name . It is not necessary to change the configuration, but you can adapt individual parameters.

  4. Optional: If you need additional repositories, create them as copies of the repository shipped by SAP. Follow the procedure below:

    1. In the list of application resources, select the entry ecm/default .

    2. In the resource details, choose Start of the navigation path Antecedent Resources End of the navigation path.

    3. Select the SAPContentStoreJava entry and choose Start of the navigation path Antecedent Resource Details End of the navigation path.

    4. Under Dependent JCA Connection Factories , select the entry ecm/default and choose Start of the navigation path Copy & Add JCA Connection Factory End of the navigation path.

    5. Follow the procedure below:

      • Under JNDI Name , enter the name of the new JCA Connection Factory , adhering to the following syntax (with or without the optional namespace):

        ecm/{ <namespace> } <repository name>

        ecm/ <repository name>

      • Optional: Add an Alias for the repository.

        Note

        The alias is necessary for accessing the repository using the WebDAV client. If you do not define an alias, the system automatically sets the repository name (without namespace) as the alias if necessary (for example, if the repository is manually assigned to an application).

        More information:

        Defining ECM Repository Assignment of an Application

  5. If necessary, adapt the following parameters of the relevant JCA Connection Factory for each repository:

    Parameter

    Description

    ContentStorePath

    The path in the file system of Java Enterprise Edition under which the system saves the content of the objects. The system automatically creates a subfolder under this path for each repository.

    Note

    It is not necessary to change this setting.

    SuperUserRole

    ID of the superuser with all change rights for the repository. The superuser can be a single user, a group, or a role.

    Note

    This setting defines which users have initial access to a repository, and can assign access rights, for example.

    More information: Setting Up WebDAV Access to an ECM Repository