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 - 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.
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.

Repository ID	Document Class	Document Class Description	Repository Type	Repository Address	Path	Repository Port	Status
97-1	*		FTP	191.10.92.1	/pub/	19	Usable
97-2	*		FTP	191.10.95.2	/pub/	19	Usable
97-3	*		FTP	191.10.97.6	/pub/	19	Generating
97-4	200	General	Shared	//myserver/myshare			Generating
97-4	100	Drawing	Shared	//myserver/myshare	drawings		Generating
97-5	500	Specification	Database				Generating
97-6	900	Part List	File Storage				Generating

For more information, go to Topics in IFS Cloud / Create and Maintain Document / Document File Repositories.

Prerequisites

Any paths used in FTP and Shared repositories must exist in the storage locations before the repositories can be used.

System Effects

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

Enter Repository Location

Explanation

Prerequisites

System Effects

Pages

Activity Diagrams