Enter Repository Location

Explanation

Use this activity to create and maintain the location where electronic document files are stored. Locations of type Database, FTP, Shared can be registered. You can enter more than one location for each document class. When specifying a value for the 'Path' the following rules apply.

• Database - 'Repository Address' and 'Path' need not be specified.
• FTP - If 'Path' is not specified the files will be stored in the FTP root (ftp://[ftp_host]:[ftp_port]), else they will be stored at specified path (ftp://[ftp_host]:[ftp_port]/[path]). A path can be a relative path (doc_files/) or an absolute one (/doc_files/).
• Shared - Can be either a local path (C:\Doc\Proj), a path in a mapped drive(S:\Doc\Proj), or a UNC path(\\[host_machine]\Doc\Proj).
• Local Path - If the defined path is a local path, then the path defined should exist with in the same machine which hosts the application server instance. A local path should not be (and cannot be) used if the application servers are configured as a cluster.
• Mapped Path - A shared folder that is mapped as a specific drive of the machine which hosts the application server instance. Application servers that are configured as clusters can work on Shared Path Repositories that are defined as 'Mapped Paths', as long as those mapped paths point to the same shared folder. If the application server instance(s) service is executed as a specific OS user then that user should have read and write access to the shared path.
• UNC Path - Single application server instances as well as application server instances that are defined as clusters can work on Shared Path repositories that are defined as UNC paths. If the application server instance(s) service is executed as a specific OS user then that user should have read and write access to the shared path.

The status for a repository will be either 'Usable' or 'Generating'. Generating is the location where all new document files are stored. A given document class can have only one location in 'Generating' status; all other locations must be set to Usable. 

Note: Do not use the same directory on a disk/FTP address for two or more storage locations that are registered in different databases. This is likely to cause document files to be overwritten.

In the following example, the first and second sites (97-1 and 97-2) are filled. The third site (97-3) is then used when file references are generated.

Prerequisites

• The directory must be set up on the local server.
• Values for the Repository Address field must be selected from registered values.
• The path must be defined. 
• The location must exist.

System Effects

As a result of this activity, the documents will be stored in the Generating location in the path specified for the particular document class.

Window

EDM Basic

Related Window Descriptions

EDM Basic
EDM Basic/Repositories
Select Remote File Location Path

Procedure

1. Open the EDM Basic window and click the Repositories tab.
2. Click New to create a new record.
3. In the Repository ID field, enter the identifier for the location.
4. In the Document Class field, select a document class using the List of Values. The wildcard (*) designates all document classes. A value for the Document Class Description field will be added automatically.
5. In the Repository Type list, select either FTP, Shared (local disk) or Database.
6. In the Repository Address field, use the List of Values to select and enter a registered address.
7. In the Path field, enter a path to your folder.
8. If you selected FTP in the Repository Type field, enter the TCP port number in the Repository Port field.
9. In the Status field, select either Usable or Generating. A document class can have only one Generating location.
10. In the Repository Description field, enter the description of the storage location.
11. Click Save.