Professional Documents
Culture Documents
EL100100-GGD-EN-1
Open Text® Enterprise Library Services
Configuration and Scenario Guide
EL100100-GGD-EN-1
Rev.: 2009-Jan-26
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
E-mail: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit http://www.opentext.com
1 Introduction ............................................................................... 9
1.1 Related documentation ............................................................................ 9
1.2 Conventions ........................................................................................... 11
1.3 Abbreviations and terms ........................................................................ 13
1.4 Contact information ................................................................................ 13
This part contains general information regarding the contents and structure of this
manual and the architecture of Open Text Enterprise Library Services.
Product The following documentation is available for Open Text Enterprise Library Services
documentation in the Open Text Knowledge Center (https://knowledge.opentext.com/docs):
• Open Text Enterprise Library Services - Installation and Upgrade Guide (EL-IGD)
This manual describes the installation of the Enterprise Library Services
components using the Open Text Installation master setup. Additionally, an
overview of the configuration of Enterprise Library Services is given.
• Open Text Administration Help - Content Services (EL-H-AGD)
This online help gives information on the administration of Enterprise Library
Services using Administration Client.
Most of the tasks presented within this Configuration and Scenario Guide make
use of Administration Client. It is assumed that you know how to administer
Enterprise Library Services. Please consult the Administration Online Help in
any case of doubt.
Programming Besides the detailed description of the Enterprise Library Services API, you can find
reference information on the underlying architecture of Enterprise Library Services in the
Open Text Developer Network (http://otdn.opentext.com/)
Release Notes The Release Notes describe the following aspects in detail:
• The software supported by the product
• Requirements
• Restrictions
• Important dependencies
• Last-minute changes regarding the documentation
• Identification codes of the current documentation
The Release Notes are continually updated. The latest version of the Enterprise
Library Services Release Notes is available in the Open Text Knowledge Center
(https://knowledge.opentext.com/knowledge).
Components The following documentation is available for the respective Enterprise Library
documentation Services component:
1.2 Conventions
Read the following conventions before you use this documentation.
Typography In general, this documentation uses the following typographical conventions:
• New terms
This format is used to introduce new terms, emphasize particular terms,
concepts, long product names, and to refer to other documentation.
• User interface
This format is used for elements of the graphical user interface (GUI), such as
buttons, names of icons, menu items, names of dialog boxes, and fields.
Important
If this important information is ignored, major problems may be
encountered.
Caution
Cautions contain very important information that, if ignored, may cause
irreversible problems. Read this information carefully and follow all
instructions!
Environment The percent signs %...% are used to denote a Microsoft Windows environment
variables variable. You should use the value that is set on your system.
To find the value of all environment variables set on your Windows computer, enter
in a command prompt the command set
To find the value of a particular environment variable set on your Windows
computer, enter in a command prompt the command echo %variable name% (e.g.
echo %TEMP%).
Related topic Wherever applicable, links to related topics are collected in a list at the end of a topic
links rather than placing the links within the text. If the same topic occurs in both
scenarios, only the first scenario is referenced.
Abbreviation Term
EL Enterprise Library (short for Enterprise Library Services)
ESC Expert Service Center
KC Open Text Knowledge Center
MMC Microsoft Management Console
RDBMS Relational Database Management System
RSI Record Series Identifier
Naming The following names are used for the different installation scenarios within the
convention documentation. Depending on the existing environment and the scaling
requirements, combinations of the mentioned “servers” on distinct computers are
possible.
Background:
• “Scenarios overview” on page 27
The services provide an API to use the functionality of Enterprise Library Services
by custom applications. You find a detailed description of the services in the Open
Text Developer Network (http://otdn.opentext.com).
2.3 Applications
All applications that deal with records or content that have evidence for an
enterprise and are subject to legal regulations can greatly benefit from Enterprise
Library Services. These records cannot be managed as single files on a file server, as
they belong to business processes and often have relations to other records. Access
to those records need to be recorded on a fine granular level (per application) and
their consistency and integrity have to be guaranteed throughout the lifecycle.
Before a business application is able to use Enterprise Library Services, it needs to
register as Enterprise Library application. Therefore, an Enterprise Library
application must be created with the application client or via the application's
administration environment. An Enterprise Library application is characterized by a
unique identifier, a password, and a set of audit interests. The password is used by
the application for authentication. Each Enterprise Library application has a distinct
application space. The application space can be shared with other applications or
can be protected (for example, only the designated application can create new
content).
Audit interests
Applications might have different needs in regards to auditing access requests.
Auditing requirements might span from monitoring almost nothing to nearly
everything. In Enterprise Library Services, there is a list of standard audit events
available, but applications can also define additional events writing their own audit
entries.
Procedure:
• “Creating the application” on page 43
• “Creating the application” on page 89
1. Creation
The item (document, record) is created by a user or application. It hence has
metadata and classification information and, maybe, content in variants.
Additionally, Enterprise Library Services may create renditions of the item, for
example to archive it in a more reliable format or to extract information
(metadata) from image files via OCR.
2. Lifetime
During the item's (document's, record's) persistence in the system, it may be
subject to a search. Its metadata or status can change.
3. Optional: Hold
If the item (document, record) has to be kept in the system longer than its
retention period affords, it can be put under a hold. This is also possible to
prevent changes maybe otherwise allowed.
4. Deletion
After – and only after – the item's (document's, record's) retention period has
expired, both content and metadata can be deleted.
When installing and configuring Enterprise Library Services, you have to maintain
all of the mentioned aspects.
Background:
• “Abbreviations and terms” on page 13
• “Enterprise Library Services objects and their lifecycle” on page 17
Related Topics:
• “Scenario I – Fixed Retention” on page 29
Related Topics:
• “Scenario II – Variable Retention” on page 77
Procedure:
• “Creating rendition targets and rules” on page 55
2.7.1 Overview
Enterprise Library Services is based on a flexible and powerful document model,
which supports the needs of many applications and lays the foundation for
managing the whole lifecycle of business records. Those records are tagged with
custom metadata using a type system, and the lifecycle is controlled via Records
Management and Retention Series Identifiers (RSI) assigned to the classification and
records, respectively. Access to Enterprise Library Services objects is controlled via
Access Control Lists (ACLs). An ACL entry comprises a list of users and/or groups
as well as permissions.
Metadata Applications are mapping their metadata to the ones managed within Enterprise
Library Services using a document model. Typically, a subset of the metadata
maintained in the original application is replicated to and managed in ELS.
Essentially, everything needed to manage a record until the end of its lifecycle has to
be kept in ELS. Normally, records managed via Enterprise Library Services are not
seen as “dead content” and therefore, metadata is needed for locating and making
them available to applications later on. In many cases, record content gets full-text
indexed providing even richer search and discovery capabilities.
Records Records can be very simple-structured like SAP Outgoing Invoices (just a set of
metadata and a content blob; no versions, no renditions, no language-specifics).
They also can be complex like an instruction manual, which exists in many different
versions and languages, has its own internal structure and has to be stored in more
than one file format.
Built-in types Item and folder types that are matched to already defined items in Enterprise Server
are marked as Built-in. You do not need to specify these types. Built-in types
represent the common Enterprise Server items (“standard Livelink” objects).
The namespace of built-in types is “dm”. Table 2-1 shows the built-in types in detail.
Type Description
Item types
dm.Document Standard Livelink Document
dm.Object Standard Livelink Object
Folder types
dm.Folder Standard Livelink Folder
dm.RootFolder Standard Livelink Root Folder
2.7.3 Folders
A folder can contain items or additional folders. A folder is assigned to a folder
type, which specifies a set of metadata.
2.7.4 Items
An item is assigned to an item type, which specifies a set of metadata (properties).
An item can contain one or more variants with or without content.
Variants
The structure and relation of records is represented by variants. Variants can have
different layout along the three dimensions: version, language, rendition. Any
number and combination of those dimensions can be used (in any order) and an
application might choose to use the one which most closely resembles its model. In
addition, user defined properties can also be added (see “Property types and
property group types” on page 24).
A variant is any combination of Version, Language, Rendition.
Possible V, VR, VL, VRL, VLRL, LR, LV, LRV, LVRR, RL, RV, RLV, RVL
combinations
Version
Versions are structured as <major>.<minor>.<micro>. A micro version is created
when only the metadata of a variant changes. Therefore, all micro versions of a
particular item with same <major> and <minor> numbers share the same content.
Note: It is up to the application to enforce proper usage of
major/minor/micro settings. Enterprise Library Services only provides
some built-in rules to increase version numbers automatically if no
numbers are specified during the creation of a record. However, ELS cannot
decide on its own if, e.g., a new minor or a new major version should be
created. In some cases, the decision is based on a user's choice and the
application has to get it and pass the result to ELS.
Language
If the variant layout contains the dimension “Language”, a language fallback list
can be configured. This list is used when client applications that do not
understand the “Language” dimension accessing ELS (not specifying which
language to fetch). For those clients, the language fallback list defines preferred
languages to be returned.
Rendition
If the variant layout contains the dimension “Rendition”, a rendition fallback list
can be configured. This list is used when client applications that do not
understand the “Rendition” dimension accessing ELS (not specifying which
rendition to fetch). For those clients, the rendition fallback list defines preferred
renditions to be returned.
Level
The level defines where the property is assigned to.
• Item Level – The variants cannot have their own property value. The
property value is valid for the item with all its variants.
• Variant Level – There is a property value for every variant.
Required
Is set, if the entry is mandatory.
Searchable
The entry of this property type should be included when searching for an entity
of this item type or folder type. This setting is only relevant if the type has an
indexing mode value“Metadata and content” or “Metadata only”.
Multi value
Is used if the property type may have more than one entry of the defined data
type. If “boolean” is selected as data type, “multi value” cannot be set.
Procedure:
• “Configuring Content Move” on page 103
Background:
• “Fixed and variable Retention Management” on page 18
Procedure:
• “Configuring and running a disposition search” on page 71
• “Configuring the RSI” on page 51
This scenario describes the necessary steps to set up Enterprise Library Services with
a fixed retention period. As an example, invoices are chosen. All other scenarios for
objects that require being safely stored for a known period of time are also covered,
of course.
Background:
• “Document model” on page 19
11. Declare which and when items are to be deleted; see “Configuring and running
a disposition search” on page 71.
12. Finally, after running the disposition search, delete the found items; see
“Deleting items” on page 75.
Code tables
Cross Reference
Lets you link two objects.
You have to set up a special cross-reference for Open Text Rendition Services.
This is necessary to connect the original object with its rendition and vice versa.
The cross-reference code for the original object must be els.orig; for the
rendered object it must be els.rend.
Essential Record
Lets you specify options for setting the importance of an object.
In this example, set to YES.
Hold Type
Lets you specify options for hold types (optional).
In this example, set to keep.
Holds for SAP ILM:
If you want Enterprise Library Services to support SAP ILM hold cases, you
have to create the hold type ILM.HOLD. See also Section 4.9 "Configuring
WebDAV Services" in Open Text Enterprise Library Services - Installation and
Upgrade Guide (EL-IGD).
RSI Retention
Lets you specify options for retentions.
In this example, set to INVOICES.
RSI Retention Stage
Lets you specify options for stages that objects can complete.
In this example, set to f01. The Stage Order is set to 1 (of one).
RSI Rule
Lets you specify options for rules.
In this example, set to outInv.
RSI Status
Lets you specify options for an RSI status.
In this example, set to ACT.
Status
Lets you specify options for a status.
In this example, set to ACT.
Storage Medium
Lets you specify options for naming the type of storage media available.
In this example, set to HD
Creating codes Follow the procedure below to create all of the mentioned codes consecutively.
To create a code:
1. From the Livelink administration page, from the Enterprise menu, choose
Records Management.
2. On the Records Management page, click the Records Management
Administration link.
3. On the Records Management Administration page, click the Table Maintenance
link.
4. On the Records Management Table Maintenance page, click the link for the
table you want to add a code to.
5. Click a code type on the Add Item menu.
6. Type a code in the Code field.
7. Specify any of the remaining settings.
8. Click the Submit button.
Background:
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Accessing the Livelink Administration Page” on page 119
Background:
• “Document model” on page 19
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Working with Administration Client” on page 117
• “Related documentation” on page 9
Procedure:
• “Creating the classification” on page 52
Click Next.
6. Select Set default classification and click Browse.
Locate and select I-01 (Outgoing Invoices) from the classification tree and click
OK.
7. Click Finish.
Background:
• “Folders” on page 22
Click Next.
6. Select Set default classification and click Browse.
Locate and select I-01 (Outgoing Invoices) from the classification tree and click
OK.
Click Next.
7. On the Variant Layout page, select Rendition and then click Add.
Click Next.
8. On the Rendition Fallback List page, select the MIME types for PDF
(application/pdf), and text (text/plain), and then click Add.
Click Next.
9. On the Summary page, check the settings and click Finish.
Now, you can specify the property types for the item type.
Click Finish.
Background:
• “Items” on page 22
• “Property types and property group types” on page 24
Click Next.
6. On the Audit interests page, specify the events to trigger auditing.
Note: Entries starting with “AL” are only relevant for ArchiveLink.
Click Finish.
Background:
• “Applications” on page 16
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Working with Administration Client” on page 117
• “Related documentation” on page 9
Background:
• “Related documentation” on page 9
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Working with Administration Client” on page 117
Volume name
Unique name of the volume.
Mount path
Mount path of the volume in the file system. The mount path is a drive
under Windows and a volume directory under UNIX. Enter a backslash in
front of the root directory if you are using volume letters (e.g. e:\vol2).
Volume class
Select Hard Disk.
6. Click Finish.
Related Topics:
• “Creating status codes” on page 35
Background:
• “Related documentation” on page 9
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Working with Administration Client” on page 117
Important
Enterprise Library Services supports Enterprise Archive only.
Click Next.
6. From the Logical Archive box, select the logical archive to use with the new
provider (I1).
As we did not configure a Storage Tier, you cannot select any.
To allow the deletion of Archive and Storage Services content when deleting an
invoice, select Delete Documents from Archive.
As Content Move jobs are not needed, keep Allow Content Move Operation
cleared.
Click Next.
7. Click Finish.
Click Next.
4. From the Value box, select ERP_inv.
Note: If you have selected another rule, this page may look different.
Click Next.
5. Click Finish.
Background:
• “Related documentation” on page 9
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Accessing the Livelink Administration Page” on page 119
4. Click Add.
Background:
• “Related documentation” on page 9
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Working with Administration Client” on page 117
• “Creating renditions” on page 19
Create cross- Before you can create the rendition target, you have to set up a special cross-
reference reference for Rendition Services. This is necessary to connect the original object with
its rendition and vice versa.
The cross-reference code for the original object must be els.orig; for the rendered
object the code must be els.rend.
3. Expand Enterprise Library Services and select the Rendition Targets node.
4. In the action pane, click New Rendition Target.
5. On the General page, specify the following:
Target name
Enter a unique name for the new target, e.g. ToPdf
Description
Optional: Enter a description for the target.
Rendition key
The rendition key specifies the target format of the rendition. Rendition keys
must be supported by Rendition Services and they must be defined as MIME
type in Enterprise Library Services to ensure that the rendered content can
be stored.
The rendition key contains at least a MIME type, which defines the target
format of the rendered document. Optionally, there is additional information
(content type) after the MIME type, separated by semicolon. This allows the
creation of several rendition keys of the same MIME type. The rendition is
stored as a new variant of the object with the same version and language and
with the whole specified rendition key.
Notes:
• Syntax of MIME types
The syntax of a MIME type has to be
<type>/<subtype>;<key1>=<value1>;<key2>=<value2>
for example image/tiff or
application/pdf;confidential=true.
Please note that the default value contains all the technically
supported rendition MIME types. Changes to the configuration
value are only useful to exclude a specific type from being offered as
a target MIME type.
You can define rendition keys that can be stored in Runtime and
Core Services > Configuration > Elib Service >
elservice.mimeTypes.mimeType<n> properties.
For details on the Runtime and Core Services configuration, see
Open Text Runtime and Core Services - Administration Guide (ELCS-
AGD).
Select the MIME type of the rendition to be created, e.g. application/pdf.
Modifying To modify a rendition target, select it in the result pane and click Properties in the
rendition targets action pane. Proceed in the same way as when creating a rendition target.
Deleting To delete a rendition target, select it in the result pane and click Delete in the action
rendition targets pane. Confirm with OK.
Related Topics:
• “Creating status codes” on page 35
Click Finish.
Modifying To modify a rendition rule, select it in the bottom area of the result pane and click
rendition rules Properties in the action pane. Select the General or Targets tab. Proceed in the same
way as when creating a rendition rule.
Disable/Enable Rendition rules are automatically enabled after creation. To disable a rendition rule,
rendition rules select it in the bottom area of the result pane and click Disable in the action pane. A
disabled rule is ignored. Click Enable if you want to activate a disabled rule.
Changing the The conditions of the rules are checked in the same order as the rules are listed in
order of rendition the result pane. The first rule with matching conditions is performed, the following
rules
rules are ignored. To change the order number of a rendition rule, select it in the
bottom area of the result pane and use the arrow buttons in the action pane to move
the rule up or down.
Deleting To delete a rendition rule, select it in the bottom area of the result pane and click
rendition rules Delete in the action pane. Confirm with OK.
Procedure:
• “Creating the application” on page 43
To create a hold:
1. On the Livelink administration page, from the Enterprise menu, choose Records
Management.
2. On the Records Management page, click the Hold Maintenance link.
3. On the Hold Maintenance page, from the Add Item menu, select Hold.
4. On the Add: Hold page, enter the following:
Hold Name: Enter a name for the hold.
Date Applied: Specify the start date of the hold.
Hold Type: Select keep.
Date to Suspend: Specify the end date of the hold (optional).
Related Topics:
• “Creating status codes” on page 35
Background:
• “Related documentation” on page 9
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Accessing the Livelink Administration Page” on page 119
Background:
• “Related documentation” on page 9
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Accessing the Livelink Administration Page” on page 119
Important
• The port number and the consecutive port numbers must not be
used by third-party applications, another data sources on your
system, or other Open Text applications running on the same
system.
• The port numbers must be available on all selected hosts.
Important
Open Text strongly recommends that you choose a directory on a
local drive of the Livelink Admin server host running the Document
Conversion process.
4. To start the data flow processes as soon as they are created, select the Start
Processes in Data Flow check box.
5. Click Create Processes.
6. Restart Enterprise Library Services and Tomcat.
7. If you deployed Enterprise Library Services as a WAR file, redeploy the WAR
file.
8. On the Data Flow Creation Status page, click Continue.
Create slice from You create a search slice from a query when you want to apply queries to the set of
query data defined by the search criteria in the slice.
7. Click Edit to modify the categories and attributes associated with this item.
8. Click Browse Livelink, browse to the Livelink System Folder, and click the
Select link in the Actions column of the Slice Folder.
9. Click Add.
Displaying The properties of Enterprise Library Services objects can be viewed in Livelink.
properties
Displaying When a variant is created in Enterprise Library Services, but no content is attached,
information on the entries in the function menu's General tab show “Not available”. This happens
variants
because the information in these fields is derived from the content. To display the
corresponding information for the variant, do the following:
3. In the File name column, open the function menu for the variant you are
interested in.
4. Select Properties > General.
Background:
• “Related documentation” on page 9
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Accessing the Livelink Administration Page” on page 119
Start disposition Now you can start the disposition search. However, this only makes sense after the
search creation of objects within Enterprise Library Services.
Important
Running a disposition search does not perform any action on the found
objects.
(Exception: Auto Process Search Results is selected.)
Stop disposition The disposition search does not terminate by default. Instead, you have to stop it
search manually.
Background:
• “Related documentation” on page 9
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Accessing the Livelink Administration Page” on page 119
Related Topics:
• “Configuring and running a disposition search” on page 111
Background:
• “Defining the document model of the fixed retention scenario” on page 31
• “Steps within this scenario” on page 32
• “Accessing the Livelink Administration Page” on page 119
• “Deleting items” on page 25
This scenario depicts the necessary steps to set up Enterprise Library Services with a
variable retention period. As an example, bank accounts are chosen. All other
scenarios for objects that require being safely stored for an unknown period of time
are also covered, of course.
• A folder type, named gen.folder. The folder type has the subentry
customerName as individual property type.
• Type, the account type being either “giro” or “depot”. These two kinds of
Type can be represented by a Boolean property type.
• To transfer closed items from the first to the second storage tier, we have to set
up Content Move.
Additionally, the underlying architecture has to be provided. In the context of this
guide, it means: We have to configure the logical archive (e.g. accounts), two
storage tiers (OnlineData, OfflineData), and the storage provider.
Background:
• “Document model” on page 19
5. Set up rules where to put documents; see “Configuring storage providers and
rules” on page 95.
6. Prepare the RSI stages and the classification settings; see “Configuring the RSIs
and the classification” on page 99.
7. Define the Content Move jobs to transfer closed accounts to another storage tier;
see “Configuring Content Move” on page 103.
8. Optionally, put holds on specific items to prevent them from being deleted; see
“Setting a hold” on page 105.
9. Search for certain items; see “Searching for items” on page 107.
10. Provide read-only access from the Enterprise Server GUI; see “Read-only access
from Enterprise Server” on page 109.
11. Declare which and when items are to be deleted; see “Configuring and running
a disposition search” on page 111.
12. Finally, after running the disposition search, delete the found items; see
“Deleting items” on page 113.
Code tables
RSI Retention
In this example, set to ACCOUNTS
RSI Retention Stage
In this example, we need two codes: v01, with the Stage Order set to 1;
f02, with the Stage Order set to 2
RSI Rule
In this example, set to AccountsOpen
RSI Status
In this example, set to ACT
Status
In this example, we need two codes: OPN (open) and CLO (closed).
Creating codes Follow the procedure “To create a code:” on page 36 to create all of the mentioned
codes consecutively.
Background:
• “Related documentation” on page 9
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
• “Accessing the Livelink Administration Page” on page 119
Background:
• “Document model” on page 19
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
• “Working with Administration Client” on page 117
• “Related documentation” on page 9
Procedure:
• “Creating the classification” on page 101
Background:
• “Folders” on page 22
Now, you can specify the property types for the item type.
Background:
• “Items” on page 22
• “Property types and property group types” on page 24
Background:
• “Applications” on page 16
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
• “Working with Administration Client” on page 117
• “Related documentation” on page 9
Background:
• “Related documentation” on page 9
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
• “Working with Administration Client” on page 117
In our example scenario, only one kind of pool is presented – the HDSK (write-
through) pool.
Note: HDSK pools are not intended for use in productive archive systems, but
for test purposes and special requirements.
Background:
• “Related documentation” on page 9
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
• “Working with Administration Client” on page 117
6. From the Logical Archive box, select the logical archive to use with the new
provider (accounts).
As the Storage Tier, select OnlineData.
To allow the deletion of Archive and Storage Services content when deleting an
account, select Delete Documents from Archive.
As Content Move jobs are needed, select Allow Content Move Operation.
Click Next.
7. Click Finish.
8. Repeat the steps 4 to 7, but this time use the following settings:
Name: accountsClosed
Status: OPN
Under Disposition Control: Keep cleared.
14. On the RSI Schedule – Date to Use page, from the Date To Use drop-down list,
select Status Date.
15. In the Years field, type 2.
16. Click Continue.
17. On the RSI Schedule – Event Conditions page, from the Property drop-down
list, select Status.
18. In the Status field, select CLO.
19. Click Continue.
20. On the RSI Schedule – Action To Perform page, from Default Process, click the
Destroy radio button.
From the New Status drop-down list, select CLO.
21. Click Add Item.
4. Click Add.
Testing job If you want to test the created Content Move job before actually executing it,
proceed as follows.
3. In the Status and Statistics section, check the results of the simulation.
Start job In addition to the schedule of a job, you can also start it manually.
Background:
• “Related documentation” on page 9
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
• “Accessing the Livelink Administration Page” on page 119
• “Migrating with Livelink ECM – Content Archiving for Enterprise Server”
on page 25
Background:
• “Related documentation” on page 9
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
• “Accessing the Livelink Administration Page” on page 119
Background:
• “Related documentation” on page 9
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
See also the notes on displaying properties in “Read-only access from Enterprise
Server” on page 69.
Background:
• “Related documentation” on page 9
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
• “Accessing the Livelink Administration Page” on page 119
9. In the Search Criteria section, in the RSI field, type the name of the RSI to use
(ACCOUNTS).
Alternatively, click Select RSI... > Search RSI's and select the RSI in the
displayed window.
10. From Default Process, select Destroy.
11. Keep the other settings and click Update.
12. Repeat the steps 3 to 11, but this time use the following settings:
Name: search_f02
Stage: f01
Default Process: Update Storage Provider > New Status: CLO
Start disposition Now you can start the disposition searches. However, this only makes sense after
searches the creation of objects within Enterprise Library Services.
Important
Running a disposition search does not perform any action on the found
objects.
(Exception: Auto Process Search Results is selected.)
Stop disposition The disposition searches do not terminate by default. Instead, you have to stop them
searches manually.
Background:
• “Related documentation” on page 9
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
• “Accessing the Livelink Administration Page” on page 119
Related Topics:
• “Configuring and running a disposition search” on page 111
Background:
• “Related documentation” on page 9
• “Defining the document model of the variable retention scenario” on
page 79
• “Steps within this scenario” on page 80
Console tree The Administration Client window is vertically divided into three major parts. The
left-hand part – the console tree – shows the available configuration objects (also
called nodes), like Archiving and Storage and Libraries.
Result pane The middle part – the result pane – is horizontally divided into a top and a bottom
area. Depending on the selected object in the console tree, the corresponding results
and information are displayed. Clicking an entry in the top area leads to the display
of corresponding details in the bottom area.
Note: Some fields allow multiline entries (e.g. descriptions). If these entries are
displayed in single-line list views, the character is used to indicate the end of
a line (carriage return). Final carriage returns at the end of descriptions are not
displayed.
Action pane The right-hand part – the action pane – contains all available actions that can be
performed on the selected object or result. Actions to be performed on objects are
shown in the upper, actions to be performed on results in the lower half.
Right mouse If you right-click an object or result in the result pane, a context menu opens. The
button menu provides the same actions as shown in the action pane. Thus, you get a fast
access to according functions.
Refresh If settings are changed or jobs are run, a refresh of all parts of the administration can
be enforced manually. This ensures that the current status of the system is
displayed. To enforce a refresh, click Refresh in the action pane.
Getting help As you can extensively customize Administration Client, only the default look is
described. To get further information on Administration Client or a selected object,
open the online help at any time by pressing F1.
Note: For general help on Microsoft Management Console (MMC), press F1
and select Microsoft Management Console in the contents tab to open the
corresponding online help.
where <protocol> is either http or https, <server> is the name of the Web host,
<port> is the port on which your Web server listens, and <URL_prefix> is the
URL prefix mapped to the <Livelink home>/cgi folder of the new version of
Livelink.
Tip: If you are working on a Windows host, you can also access this page
by doing the following: Click Start, point to Programs, point to the
program folder name that was entered for Livelink (default is Livelink),
and then click Livelink Administration.
2. On the Livelink Administrator log-in page, type the Livelink administrator
password in the Password field, and then click the Log-in button.
Tips:
• At the bottom of most administration pages is the Admin Home link, which
returns you to the main Livelink administration page.
• Click Show As Tabs in the upper right side of the page to show the entries
per group only.
For further information, consult the Enterprise Server and module documentation.
ArchiveLink
See: SAP ArchiveLink
Disposition Management
Objects that are subject to Disposition Management can be deleted at any time,
especially using a “disposition run”.
See also: Retention Management.
Document
A (Enterprise Library Services) document is any object that is archived via SAP
ArchiveLink. Documents are no subject to Retention Management.
See also: Item, Record, ArchiveLink.
Item
An (Enterprise Library Services) item is any object that is under Retention
Management.
See also: Document, Record.
Livelink Classifications
Livelink Classifications places Livelink items, such as documents, e-mails, or
HTML pages, into a hierarchical structure of classification trees. Classification
trees provide an alternative way to organize, manage, and browse Livelink
items.
MIME type
A file identification based on the MIME encoding system; de facto standard for
identifying Web content. The MIME Content Type consists of a type and subtype
separated by a slash; for example, text/plain and image/gif.
Object
Most general term for everything that Enterprise Library Services can deal with.
An (Enterprise Library Services) object is either a Document, an Item, or a record.
OCR
See: Optical Character Recognition (OCR)
Record
An (Enterprise Library Services) record is any object that is under Records
Management. Records are a special kind of items.
Rendition Services
See: Open Text Rendition Services
Retention Management
Items, i.e. objects that are subject to Retention Management, cannot be modified
or deleted before the retention period is over. The retention period can be fixed
(hardware protection) or variable (software protection).
See also: Document, Object, Record, Disposition Management.
RSI
See: Record Series Identifier (RSI)
SAP ArchiveLink
Additionally to Web Services, Enterprise Library Services have a SAP
ArchiveLink interface built in. ArchiveLink is the standard interface for
document archiving from SAP software and is defined by SAP as a HTTP based
protocol interface. For a more detailed description of ArchiveLink, refer to
http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCSRVARL/BCS
RVARL.pdf.
Variant
Enterprise Library Services objects consist of the metadata describing (aspects of)
the content and the content itself. Depending on the variant layout, different
representations of the content are possible – versions, renditions, or languages.
For example, the English and the German version of a text can be two variants of
the same object.
See also: Variant layout.
Variant layout
The variant layout defines a virtual hierarchy of version, language, and rendition
(MIME type) representations. Each Enterprise Library Services object can have
up to three levels. Each Enterprise Library Services object must have at least one
variant layout.
J P
Job ticket templates 57 Pools 47, 92
Jobs HDSK 47, 92
Content Archiving 25 Programming reference 10
Content Move 103 Property types 38, 86
L R
Lifecycle 17 Read-only access 69, 109
Items 17 Record 122
Objects 17 Record Series Identifier 51, 99