HP Structured Records Management Solution Tutorial, August 2011

HP Structured Records Management Solution Tutorial 33
Calling the SRMS Loader
Your configuration determines how you need to invoke the SRMS Loader to
ingest your archive files into HP TRIM:
NOTE In most cases, HP Database Archiving resides on a different machine than
HP TRIM. HP Database Archiving can reside on MS Windows or UNIX, whereas
HP TRIM can reside only on MS Windows.
• When HP Database Archiving and HP TRIM are on homogeneous operating
systems with shared file systems and identical path specifications, you can
usually just choose
SRMS > Add SRMS activity to Business Flow and accept
the default settings. If the path specifications are different, you need to change
"DEFAULT_PATH" to a path specification. For example, suppose the path to the
archive files on Windows PC1 is
C:\Program
Files\HPDBArchiving\archivedata\Oracle_OLTP
and the archivedata
folder is shared, but, on Windows PC2, the path to that same location is
mapped to
Z:\Oracle_OLTP. In this case, you would change
"DEFAULT_PATH" to "Z:\\Oracle_OLTP\\" in the sendToSRMS call.
• When HP Database Archiving and HP TRIM reside on homogeneous
operating systems with unshared file systems, you need to include an ftp
command for moving the archive files to a file system accessible by the
SRMS Loader. To achieve this result, you need to insert a Groovy script in the
business flow editor and choose the
SRMS > Call TRIM Loader template.
• When HP Database Archiving and HP TRIM reside on heterogeneous
operating systems with shared file systems, you must provide a path
specification and manually call the SRMS Loader. To achieve this result, you
need to insert a Groovy script in the business flow editor and choose the
SRMS
> Call TRIM Loader (Advanced)
template.