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 and File Storage 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.

This activity can be performed by adding a record in Repositories page in EDM Basic. You can enter a repository ID, repository type, path and address if applicable and define the status of the repository.

• 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).
In IFS Cloud, a repository address must be defined, as with FTP repositories. The repository address is defined in the Repository Address screen. The address should be on the format //server/share, where server is the IP address or name of the server that has the shared folder, and share is the name of the shared folder. Any additional directory name is added in the Path field in the defined repository that uses the repository address. The Path field there can be left empty, if needed.

• Local Path - If the defined path is a local path, then the path defined should exist within 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 Drive - 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.
• File Storage - 'Repository Address' and 'Path' need not be specified.

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.

You can transfer documents from one repository to another using the Transfer Documents command. Documents can only be transferred from repositories which are in Usable status. This functionality is currently available for transfer between Database and File Storage type repositories only.

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.

Pages

Repositories

Activity Diagrams

BDR for EDM Basic