Configuring Server Settings
Overview
This chapter includes information on the following topics:
“Defining Application Formats” on page 125 “Managing Document Types” on page 131
“Managing Document Class and Subclass” on page 139 “Managing PC Locations” on page 144
“Managing Custom Tables and Subtables” on page 147
See the WorkSite Server Installation Guide for an introduction to using DBAdmin.
Defining Application Formats
Each WorkSite database has a list of applications associated with it that contains information necessary to integrate applications with WorkSite Server. This information includes:
Procedure for associating document types and applications
Information necessary to launch applications from WorkSite Server
Information necessary to open and print documents in integrated applications
When a database is initialized as a WorkSite database, an application list is provided that includes information for most major Windows applications. Normally, the default settings for these applications will not need to be altered, but if necessary this information can be edited using the DBAdmin tool. Additional applications not listed in the table can be added.
NOTES
If you use the default settings for the list of applications for a database, each user should have a DOS path established to the drive and directory of the integrated applications.
App Setup is the default caption for the Application information table in the database. This caption can be customized using the Dialog Editor.
Customizing the App Setup List
You can add, modify or delete records in the list of applications associated with a database. The following sections explain how to edit or add entries to the list of applications.
Adding an Application Setup Entry
To add an application: 1. Start DBAdmin.
From the Windows Start menu, point to All Programs, then Autonomy, and then select
iManage Database Administration.
2. Select the App Setup icon in the tree frame.
The available applications are displayed in the table frame.
3. Click the Add button from the toolbar, or from the Manage menu, select Add. The Add App Setup Entry dialog opens.
Defining Application Formats
Figure 60 Add App Setup Entry dialog box
4. Enter information for each of the fields, as defined in Table 14 . 5. Click OK.
Editing an Existing Application Record
To edit an existing application record:
1. Select the App Setup icon in the tree frame.
The available applications are displayed in the table frame.
2. Select an application to edit. Click the Modify icon in the toolbar. You can also right-click the application in the table frame, and then select Modify.
The Edit App Setup Entry dialog box is displayed. The Add App Setup Entry and Edit App Setup Entry dialog boxes are the same. See Figure 60.
3. Modify the fields displayed in the Edit App Setup Entry dialog box. Table 14 lists the fields and briefly describes them. The Name and Type fields are read-only purposes.
NOTE
These fields cannot be edited once an application record is added. To modify these fields, you must delete the application record and add a new updated recorded.
4. Click OK.
Table 14 Application Setup Properties
Field Identifier Intended Content
Name Enter a descriptive name for the application, so that it will be recognizable to users.
Path Enter the location of the application in this field. You can specify a full pathname. For example, if the application is Microsoft Word and the executable file is WINWORD.EXE, then it would be sufficient to enter WINWORD.EXE in this field.
If the application is a non-primary application (see Primary Application check box in this table), the following command line parameters pass document information to applications launched from WorkSite:
%DOC_DB.Allows you to pass the database name
%DOC_NUM. Allows you to pass the document number
%DOC_VER. Allows you to pass the document version
-NO_OUTPUT Used when the application being launched does not return output to Autonomy.
Example:
You want to pass the database name, document number, and version number to an application via the command line. The specified application will not be returning output to WorkSite. A fax application is an example of an application that might consume this document information but not return output. You call the fax application “sendfax.exe”. Given these parameters, the command line settings for the fax application would be: C:\…\sendfax.exe DB=%DOC_DB NUM=%DOC_NUM VER=%DOC_VER -NO_OUTPUT
Type This field identifies the document type associated with this application. This type indicates the application that is associated with the document.
Primary
Application check box
This check box indicates that the application is the primary application for this document type. If there are multiple applications associated with a document type, one application may be identified as the primary one. If there is only one application associated with a document type, this check box should be selected.
Defining Application Formats
Deleting an Application Record
To delete an application record:
1. Select the App Setup icon in the tree frame.
The available applications are displayed in the table frame.
2. Select the application in the table frame that you want to delete and click the Delete
icon in the toolbar or select Delete from the Manage Menu.
Integration Mode This text-entry field identifies the method for integrating the application with WorkSite:
• COM Integration. Select this option if this application is integrated with WorkSite using macros supplied with the WorkSite DMS.
• ODMA Integration. Select this option if the application is integrated using the ODMA method.
• Non-Integrated. Select this option if the application cannot be integrated using macros or ODMA integration.
For information on application integration, see the WorkSite Desktop Client Customization Guide.
DDE check box Select this check box if he application supports dynamic data exchange (DDE). Complete the fields on the Add or Edit Application dialog box. Most major applications support DDE.
Complete the following sections only if the DDE check box is selected:
DDE Name Enter the DDE application name in this field. The DDE application name is usually the executable filename for the server application (without the .EXE extension).
DDE Topic Enter the DDE Topic for this application in this field. The DDE Topic usually identifies a category of data associated with the server application.
Open Enter the DDE Command Line to open a document in this application. The DDE Command Line varies from application to application.
Open Read Only Enter the DDE Command Line to open a document for read-only viewing in this application. Again, the DDE command line varies from application to application.
Print (Optional) Enter the DDE command line to print a document in this application. The command line should assume that the application is already running.
Print and Exit App (Optional) Enter the DDE command line to print a document in this application, when the application is not already running.
Table 14 Application Setup Properties
3. To delete the record, click OK in the Confirm Delete information window.
Mapping Multiple Document Types to the Same Application
You can create multiple records in the App Setup information table for the same application. These records can list different document types. With this mapping, users can open multiple document types from the same application.
For example, you want users to be able to open ANSI text files and Word documents in Microsoft Word. Confirm that both document types are listed in the Document Type
information table. Next, add a record to the App Setup information table for Microsoft Word. A copy of the entry for Microsoft Word is made, but the ANSI is the document type. Each entry must be designated as the primary application for that data type.
Primary Applications
The primary application is the preferred application for opening a document. If only one application is associated with a document type, the Primary Application check box must be selected in the App Setup list in order for WorkSite to open the document.
If there are multiple applications mapped to the same document type, you can identify one as primary by selecting the Primary Application check box when you create the entry for that application in the App Setup list. Only one application can be identified as the primary application for a document type.
NOTE
To use the Open in WorkSite, the document type must have an application designated as the Primary Application in the App Setup list.
Non-Primary Applications
The Primary application is the preferred application for opening a WorkSite document. Other applications that are mapped to the same document type become non-primary.
All non-primary applications are listed under the Application submenu in the WorkSite client. Users can select documents in the document grid, A user can launch a document in a
Managing Document Types
Managing Document Types
Every document in a WorkSite database is identified by a WorkSite document type. The document type is part of the profile information. WorkSite uses this information to associate documents with their native applications. Each document type is mapped to an application in the App Setup information table, and the mapped application is used to open the document.
Multiple document types can be mapped to the same application by adding additional entries in the App Setup information table. If a document type is not mapped to an entry in the App Setup
information table, then WorkSite Server will not be able to automatically open the document in its native application.
For example, when a document is of type WORD2007, WorkSite Server knows that the
document should be opened in Microsoft Word 2007, because that document type is mapped to that application in the App Setup information table. Document types can be mapped to multiple applications, but WorkSite Server will only open documents of that type in the primary
application for that document type. See “Mapping Multiple Document Types to the Same Application” on page 130.
Default Document Types
Table 15 lists the default document types added to a WorkSite database.
Table 15 Default Document Types
Description Auto Alias DMS Extension AppExtension Word Processing Document Types
Windows ANSI text Y ANSI %V TXT Microsoft Word Y WORD %V DOC Word 2007 Y WORDX %V DOCX Word 2007 Template Y WORDXT %V DOTX Corel WordPerfect Y WPF %V WPD
Spreadsheet Document Types
Microsoft Excel Y EXCEL %V XLS Excel 2007 Y EXCELX %V XLSX Lotus 1-2-3 Y LOTUS %V %V QuattroPro for Windows Y QUATTRO %V QPW
Presentation Document Types
Autodetect Document Types
The document types can be autodetect or nonautodetect. The WorkSite Server examines the structure of the document when it is imported to the database. It determines if the document type is autodetect.
PowerPoint 2007 Y PPTX %V PPTX Presentations Slide Show Y PRSHW %V SHW
Graphics Document Types
Windows Bitmap Y BMP %V BMP Compuserve GIF Y GIF %V GIF PC Paintbrush Y PCX %V PCX Tagged Image File Format (TIFF) Y TIFF %V TIF Windows Metafile Y WMF %V WMF Microsoft Visio 2003 Y VSD %V VSD Joint Photographic Experts Group N JPEG %V JPEG
Portable Document Format
Adobe Acrobat Reader Y ACROBAT %V PDF
Fax
Binary Group 3 Fax Y FAX %V %V
Browser and Communication
HTML N HTML %V HTML
URL N URL %V URL
XML N XML %V XML
MIME Y MIME %V MSG
GroupWise Email N GW %V TXT Notes Email N NOTES %V DXL
Other
Laserform 8 N LFD %V LFD Microsoft Publisher N PUB %V PUB
Table 15 Default Document Types
Managing Document Types
The Auto column in the Type information table cannot be changed. This column indicates whether WorkSite Server will automatically recognize a document type. Document types are marked as non-autodetect if DBAdmin tool does not add them during database initialization. Autodetection is accomplished through file type detection technology, which is built into WorkSite Server. WorkSite Server can detect dozens of different file types. When you create a WorkSite database, a set of default WorkSite document types are installed in the Type
information table.
These document types are mapped to many of the most common file types, such as Microsoft Word, WordPerfect, and PDF.
In addition, you can map a document type to one or more file types. The WorkSite Server can then detect the file type.
For example, you could create a document type for ASCII, Autocad, or HTML, and map those WorkSite document types to corresponding file types. When a document type is mapped to an file type, WorkSite Server assigns the appropriate value to the document type and opens it in the appropriate application. If WorkSite cannot detect the file type of a document, or when the document’s file type is not mapped to a WorkSite document type, then the user must manually select a WorkSite document type. See “File Type Mapping” on page 133
NonAutodetect Document Types
Nonautodetect document types are entries in the Type information table that are not mapped to file types. By default, when WorkSite Server encounters a file extension that is not recognized as a file type, the file extension is discarded and the document is imported with document type ANSI. The document is then automatically opened as a .txt file.
The WorkSite Server can be configured to automatically create new types save the extensions of nonautodetect documents and map them to the appropriate applications. Refer to “Support for Unknown File Types” on page 372 for complete details.
File Type Mapping
Multiple file types can be mapped to a single WorkSite document type. This configuration can be used when working with multiple documents created in earlier versions of an application. It ensures that the latest version of the application is used when opening documents.
Entries in the table of WorkSite Document Types can be mapped to File Types using the Document Type Mapping Management dialog box. This dialog box is available by selecting
Document Type Mapping Management from the Manage menu. See “Mapping WorkSite Document Types to File Types” on page 134.
Mapping WorkSite Document Types to File Types
Then a user adds a document to a WorkSite database, WorkSite clients use file type detection technology. It determines which WorkSite file type is used to label the document. File type detection consists of scanning the file and reading its structure to determine the document’s file type.
In most cases, WorkSite clients can detect the document’s file type.
If the file type is mapped to an entry in the WorkSite Document Type information table, then the WorkSite client labels the document with that WorkSite document type.
If the file type is not mapped to an entry, or if the WorkSite client cannot determine the document’s file type, then the user must select a proper document type for the document from those available in the Document Type information table.
The Document Type Mapping Management dialog allows you to customize WorkSite clients’ automatic document type detection capabilities. With the Document Type Mapping
Management dialog, you can map file types to document types listed in the WorkSite Document Type information table. When a WorkSite Document Type is mapped to one or more file types, it is identified in the Document Type table as an autodetect document type. Entries in the
Document Type information table that are not mapped to any file types are identified as non autodetect. Non autodetect document types can only be applied to documents when WorkSite clients are unable to assign a document type to the document automatically.
The Document Type Mapping Management dialog consists of three columns.
Type. This column lists all document types listed in the Document Type information table.
File Type. This column shows the file type that is mapped to the document type selected in
the Type column.
Available Type. This column shows file types that WorkSite Server can detect
automatically, but which have not been mapped to any WorkSite document types.
Each file type can only be mapped to one WorkSite document type, although multiple file types can be mapped to any one WorkSite document type. Mapping multiple file types to the same WorkSite document type enables you to include documents created in earlier versions of an application. These versions are included within the scope of a single WorkSite document type. The WorkSite Server uses the WorkSite document type to determine which is application used to open the document. For information about mapping document types, see “Defining Application Formats” on page 125.
Managing Document Types
Figure 61 Document Type Mapping Management dialog box
To map a file type to a WorkSite Document Type:
1. Select Document Type Mapping Management from the Manage menu.
2. Click the document type in the Type column. Only those document types already added to the Document Type information table are listed in this column.
3. Double-click the file type listed in the Available File Type column. The selected file type will move to the File Type column.
To dissociate an file type from a WorkSite document type:
1. Click the document type in the Type column to display the list of those file types currently mapped to that document type.
2. Double-click the file type in the File Type column. The file type is displayed in the
Available Type column.
Adding Custom Document Types
You can add document types to a database information table. You can perform this task for applications that are not yet associated with a document type.
Complete the following steps to add custom document types:
1. In DBAdmin, create a document type. See “Adding a Document Type to a Database” on page 136.
2. In DBAdmin or the Client tools (for local applications), create the application setup information for the added document type. See “Adding an Application Setup Entry” on page 126.
3. On the client workstations, modify the NRT.INI file and the registry settings. See “Modify the NRT.INI file” on page 137 and “Registry Settings” on page 137.
Adding a Document Type to a Database
To add a document type to a database: 1. Select the Type icon in the tree frame.
The available document types are displayed in the table frame.
2. Click the Add icon in the toolbar or select Add from the Manage menu. The Add Type dialog opens.
Figure 62 Add Type Dialog
3. Enter the information requested for in the Add Type dialog. Table 16 lists the fields on the Add Type dialog, and their descriptions.