8-2 Oracle Fusion Middleware Administrators Guide for Universal Records Management
■
the creation of a nightly log file listing inventory transaction history for a given day. This serves as a confirmation and data synchronization between the two
systems.
To use this functionality, first map default values for different types of storage file formats to districts where the content is stored. Types of file formats include legal
storage, insurance, loans, medical, and other storage types. Default districts are provided and default values for the fields used for storage.
After setting up the mapping, specify the storage parameters on the check-in page for physical content. After the content is checked in, a criteria workflow can be started to
handle the approval of items pending transfer. This workflow must be created and enabled before the Offsite functionality can work. See the Oracle Fusion Middleware
Setup Guide for Universal Records Management for details about setting up this workflow. While not required, it is recommended that this workflow be used.
Iron Mountain is currently the primary offsite provider. After the appropriate configurations are in place, the files are first stored on the computer before being sent
to and from Iron Mountain using File Transfer Protocol FTP. After the files are compiled, they are uploaded to the toplus directory in the software directory
structure.
A confirmation file is sent from Iron Mountain and stored in the fromplus directory in the Iron Mountain directory structure. A nightly history download log is also stored
in the fromplus directory after each night’s district job is processed. Verify beforehand that the chosen FTP location has these directories already created.
Pickup lists are automatically created for items that must be transferred. Manual pickup lists can also be created as needed.
8.1.1 Setting Up Default Customer Information
First set up default customer information about the account to be used by the offsite provider. These defaults identify your company to the provider and are used to
monitor and process offsite requests.
Follow these steps to configure defaults for offsite storage.
1. Click Physical then Settings from the Top menu.
The Configure Physical Content Management Page
is displayed.
2. Click Enable Offsite Storage Functionality then click Submit Update. The
Configure Physical Content Management Page is displayed.
3. Refresh the browser window. Click Physical then Offsite Storage then General
Setup .
The Offsite Storage General Setup Page
is displayed.
4.
Fill in the necessary fields:
■
Customer ID: the customer ID used with this offsite storage facility.
■
Default District: the district to use. Select from a predefined list. If the district has not previously been defined, the definition must be mapped beforehand.
See Mapping New Districts
on page 8-3 for details.
■
FTP Address: enter the address associated with the FTP site.
■
FTP User: enter the user associated with the FTP site.
■
FTP Password: enter the password associated with the FTP site.
Setting Up PCM Offsite Storage 8-3
■
Transfer checkboxes: choose options associated with the transfer:
– Automatically transfer new items: enable automatic transfer of new items.
– Automatically return checked-in items: enable automatic returns of items
that have been checked in.
– Enable workflow: start a workflow for this transfer action. The workflow
must be created before this step. See the Oracle Fusion Middleware Setup Guide for Universal Records Management for details about creating the
workflow.
– Use general requestor for Offsite Requests: choose a user from the list to
use as the requestor. There is a limit of five characters for this value.
■
Box Identifier: choose what identifier will be associated with the box. Options include Name or Title.
5. When done click Submit Update.
A message is displayed indicating the offsite storage data has been configured.
8.1.2 Mapping New Districts
