
Applications that access the integration layer of the ECM Infrastructure (ECMI) can use the repositories connected to it to manage unstructured content. You can define the availability of the ECM repositories for an application as follows:
All repositories
Individual repositories (one or more)
No repository
You can define company-specific ECM repository assignments for each application.
Type and Status of Repository Assignments
|
Type of Repository Assignment |
Description |
Status: Active Description |
Status: Overridden Description |
|---|---|---|---|
|
Default |
The repository assignment is defined in the default settings of the application. |
If there is no company-specific repository assignment, the default repository assignment is activated automatically. |
If you add a company-specific repository assignment, the system automatically overrides the default repository assignment. |
|
Company-specific |
The repository assignment is defined by you (the administrator). Note
The company-specific repository assignment takes precedence over the default repository assignment. |
If you assign individual or all repositories, these repository assignments are activated automatically. |
The assignment No Repository overrides all existing repository assignments. |
Open SAP NetWeaver Administrator in the browser.
Choose .
1. Identify Application for Repository Assignment
The table of client applications contains all applications with default repository assignments. If your application is not listed in the table of client applications, proceed as follows:
Choose .
Enter the name that the application will use to log on to the ECM integration layer.
In the table of client applications, select the application whose repository assignment you want to define.
The Details table displays all repository assignments for the selected application.
2. Add a Company-Specific Repository Assignment
In the details for the application, choose .
In the Repository Name selection list, select one of the options described below.
If you add a company-specific repository assignment, the system automatically overrides the default assignment.
|
Repository Assignment |
Description |
|---|---|
|
One of the listed repositories |
The selection list contains all repositories that are connected to the ECM integration layer. You can assign individual repositories to the application. |
|
All repositories |
You can choose this setting in the following cases, for example:
|
|
No repository |
This setting overrides all existing repository assignments. As a result, the application does not have access to any repositories. |
If you want the repository to be called using an alias, enter it in the Repository Alias field.
A repository alias is necessary, for example, for repository access using the WebDAV client.
If the "All Repositories" assignment is active for an application, the system automatically sets the repository name (without namespace) as the alias for repositories that have no other active assignment.
Exception: To avoid conflicts, the system does not set an alias for repositories with identical names; it issues a message.
3. Edit Company-Specific Repository Assignments
Use the options described below.
A default repository assignment cannot be changed or deleted. Applications with a default repository assignment cannot be removed from the table of client applications.
|
Editing Company-Specific Repository Assignments |
Description |
|---|---|
|
Change a repository assignment |
|
|
Delete a repository assignment |
|
|
Reset all repository assignments (only if there is no default repository assignment) |
Note
If you delete an application from the table of client applications, it can no longer access any assigned ECM repositories. If you add the application to the table again, the repository assignment No Repository applies, and you can define the repository assignments again. |