Creating HyperDoc database

Launch SQL Server Enterprise Manager utility. Create empty database 30 MB in size with Create for load option set. Load the HyperDoc database backup into it. Now you can create users in this database. If any of such users already exist, you must delete them and then create them again. Each user must have this database set as its default database. See section HyperDoc databases in SQL Server for important details on setting user permissions.

ODBC source configuration

To create ODBC source for HyperDoc perform the following steps:

From the Control Panel, double-click the ODBC application; Choose the Add button; From the Installed ODBC Drivers select SQL Server and click the OK button; In the ODBC SQL Server Setup dialog fill-in the following fields: Data Source Name - give unique name to the data source Server - name of the appropriate SQL Server Network Library - see comments below Click on the Options button and enter HyperDoc database name in the Database Name field and make sure that the Create Stored Procedure for Prepared Statement option is off. In default ODBC configuration client connects to SQL Server using named pipes protocol. Named pipes connection requires validation by NT server. To connect to SQL Server without NT validation, the client workstation must use either TCP/IP protocol or SPX protocol. To set up requested network communication protocol fill Network Library field in the ODBC source definition with one of the following values: DBMSSOCN for TCP/IP DBMSSPXN for SPX To use TCP/IP protocol the DBMSSOCN.DLL library must be in directory pointed to by the PATH environment variable. The same applies to DBMSSPXN.DLL library for SPX protocol. These libraries are usually placed in \MSSQL\BINN directory by SQL Server client setup.

Preparing hdoc.ini file

In order to make HyperDoc use SQL Server database you must make the following modifications to the hdoc.ini file: Set DBType=ODBC in the Database Settings section. WARNING! This setting is case sensitive. Set MainDatabase=DataSourceName in the ODBC Settings section, where DataSourceName is the name of the ODBC data source created in the previous topic.

HyperDoc needs a properly configured database in order to work. HyperDoc database configuration consists of the following steps:

Creating database. Creating system tables. Preparing object hierarchy. Preparing document types. Defining HyperDoc Login account. Defining HyperDoc database users and administrators. Configuring logical devices. Preparing user interface profiles. Defining graphical representation of business objects.

HyperDoc Options dialog consists of six tabs, each for separate set of options, and common dialog elements. Tabs are:

This tab contains options of Hyperdoc’s general behaviour:

Print selected element - controls state of selection of vector objects on printout. If enabled, selected elements are printed with selection attributes. Possible values are 0 or 1.

Use image colors when printing - enables color printing.

HyperDoc option

Parameter name

Container

Print selected element

PrintSelectedElementHDocParams table

Use image colors when printing

Use image colors when printingINI file, [TSLPPL Library Settings] section

HyperDoc option

Parameter name

Container

Ask for save vectors in new version

AskForSaveVectorsInNewVersionHDocParams table

Autoload geographical transformation

AutoLoadINI file, [Geographical Mappings] section

Autosave interval for vector drawings

SaveOnDemandIntervalHDocParams table

Cache expiration period

CacheExpirationPeriodHDocParams table

Disable versioning (remove old versions after adding new one)

DisableVersioningHDocParams table

Display FI2002 page

FI2002StandardINI file, [Floor Plan Settings] section

‘Documents For Spots’ list mode shows connected documents too

InfoScopeDocListExtendedModeHDocParams table

Expand hierarchy tree after marking multiple objects

ExpandHierarchyAfterMarkingObjectsHDocParams table

Fill/clear overlapping viewports common parts

DefaultVportsOverlapModeINI file, [TSLRVC library settings] section

Flush log

FlushLogINI file, [TSL Diagnostics] section

List documents when multiple

ListDocsWhenMultipleHDocParams table

Log basic

LogBasicINI file, [TSL Diagnostics] section

Log file name (without the path)

LogNameINI file, [TSL Diagnostics] section

Max number of auto windows

MaxAutoWindowsHDocParams table

Max number of shown windows

MaxShowWindowsHDocParams table

Max number of tiled windows

MaxTiledWindowsHDocParams table

Object infoscope title

ObjectInfoScopeTitleHDocParams table

Preview associated Security Class names in hierarchy

SecurityClassHierarchyPreviewHDocParams table

Skip config verification

SkipConfigVerificationHDocParams table

Skip restoring document

SkipRestoringDocHDocParams table

Trace errors

TraceErrorsINI file, [TSL Diagnostics] section

Work with CADRaster

CADRasterINI file, [General] section

Work with SuperEdit

SuperEditINI file, [General] section

Work with SuperView

SuperViewINI file, [General] section

Zoom factor used to expand/shrink area with spot to display it

ZoomAroundSpotFactorHDocParams table

Follow this steps:

Domain user logged into windows that is a member of added to domain group will now be able to log into HyperDoc without authentication and he will be granted rights according to the group he belongs to.

loading table of contents...