Document Finder Customizing
Before you can use the Document Finder, you need to register at least one document area in the Document Finder. A search in the Document Finder always takes place within one document area. In Customizing, you also have the option to group together more than one document area to form an aggregated document area. Using this method, users can indirectly search in more than one document area at the same time.
You can register document areas and create aggregated document areas in Customizing. In the IMG, choose SAP Web Application Server ® Basis Services ® SAP ArchiveLink ® Document Finder Customizing ® Register Document Areas and Create Aggregated Document Areas. For more information, see the online help in the IMG. The following provides some important background information.
To register a document area, you need to enter the following:
A character string of your choice. Note: A document area in the Document Finder is a different entity to a document area in terms of the Knowledge Provider.
Determines the SAP system in which the search takes place. Note: An RFC destination is only useful if you enter a query class that is RFC-compatible (see below).
A character string of your choice. This text should be as informative as possible, because it will be displayed in the document area selection list in the Document Finder.
Class of the SAP class library that determines the layout of the hit list, and the activities that are available in the context menu for each hit.
SAP supplies the standard display class CL_ALINK_HITLIST_TREE. This displays the hit list as a hierarchical tree structure. This is the default setting, and is therefore used if you do not make an entry. If you implement your own display class, this must implement the interfaces IF_ALINK_HITLIST and IF_ALINK_HITLIST_CALLBACK.
A class of the SAP class library that determines the index structure of the documents, and hence which attributes are used for the search.
SAP already delivers some query classes (see below). You can also implement your own query classes. This is recommended if you want to search using content-related attributes as well as technical attributes. For indexing documents, you should consider a solution that uses its own database tables. Every query class must implement the interface IF_ALINK_QUERY. For implementing query classes, you are recommended to use the template class CL_ALINK_QUERY_APP_TMPL as a template.
The query classes supplied by SAP are documented below.
Query classes for searching for ArchiveLink documents using technical attributes
Additional Customizing steps are required for displaying documents and business objects from remote systems. For more information, see
Document areas of these query classes (called technical document areas below) provide a technical view of all documents administrated by ArchiveLink. They possess the attributes that ArchiveLink enters and indexes in the link entry. The search corresponds to the ArchiveLink search that is called using administration. You can create technical document classes for both documents and print lists.
Query class for searching for DMS documents
Additional Customizing steps are required for displaying documents and business objects from remote systems. For more information, see
Document areas of these query classes (called DMS document areas below) include all documents administrated within the Document Management System (DMS), including ArchiveLink print lists.
The documents in a DMS document area have the attributes that have been entered and indexed as document attributes in the DMS. For more information on the DMS, see the SAP Library under Cross-Application Components ®
Document Management.
Query class for searching in external systems
Document areas of these query classes (called external document areas below) include all documents in any external system, for example, a storage system.
The documents in an external document area have the attributes that have been entered and indexed as document attributes in the external system. The query class requests the attributes of the external system at runtime. Check with the storage system supplier whether these functions are supported.