Using Imaging Servers
 

This section describes how to install and use the optional components of Imaging for Windows to access WMS Imaging Server (1.x) or WMS Imaging and Workflow (WMS) servers. For information on how to install Imaging for Windows in a standalone mode, refer to Installing Imaging for Windows.

If you have the necessary client software installed on your PC, Imaging for Windows enables you to access images residing on Imaging 1.x Servers and in WMS Imaging and Workflow environments. Access to the appropriate servers is required.

Contents
Installation
Accessing Imaging Servers
Programming the .OCXs to Access Imaging Servers

Installation

Chapter 2 of the Imaging for Windows Getting Started Guide provides instructions on how to install the 1x components needed for Imaging for Windows to access the WMS Imaging Server (1.x). The Getting Started Guide is on the release media.

In order to access the WMS Imaging and Workflow server, you need to install the WMS Imaging and Workflow Client Components. These components are packaged with the WMS Client software.

Accessing Imaging Servers

Although I can see the volumes on the 1.x server, I can't see the Document Manager databases.
For Imaging for Windows to see the Document Manager databases, there must be Document Manager entries in the oix.vols file, defined with the constant MEDIA_WDOC1. This constant is necessary for Imaging to identify Document Manager databases. Following is a sample oix.vols file.

path is /etc/eiStream/oix
# cat oix.vols
#
# Imaging 1.x server volume configuration file
#
# Each line contains:
# Logical volume name (1..15) characters # Resolution pathname (1..1024) characters
# Media type of volume:
# MD magnetic disk
# MEDIA_WDOC1 eiStream Document Manager Database
# Vol Path/ Media
SYS / MD
images /usr/images MD # images
new_images /opt/oix/images MD # New images
test_db1 /u/eiStream MEDIA_WDOC1
tms_docs /usr/eiStream MEDIA_WDOC1

Programming the ActiveX controls to Access the Imaging Servers

I'm converting a program from the OPEN/image Custom Controls to the Imaging for Windows ActiveX controls, yet I can't find the Document Management control in the ActiveX controls. How do I access the Document Manager and/or files on the Imaging Server?
Imaging Server access is handled by using special syntax in the Image property of the ImgAdmin, ImgEdit, and ImgThumbnail controls. Additionally, many client-server functions are available via the Server Access Object (SAO), a COM object included in the Imaging for Windows package for Imaging Server (1.x) functionality. Following are some examples of the ActiveX syntax:

  • Local files in Windows—
  • ImgEdit1.Image =c:\insurance\claims\claim234.tif"
  • Imaging 1.x Server Document Manager database—
  • ImgEdit1.Image = "Image://DXCESS/ins_db1:/INSURANCE/AUTO/CLAIMS/CLAIM234"
  • Imaging 1.x Server Image File volume—
  • ImgEdit1.Image = "Image://DXCESS\images:\auto\claims.tif"
  • WMS Imaging and Workflow Server
    database—
  • ImgEdit1.Image = "Imagex://claim234"

Although the ActiveX controls do the vast majority of what I need, I can't find corresponding calls for DocManage1.ListAction = OI_PAGE, ImageFile1.FileOption = OI_GET_MEDIA_CAPACITY, and ImageFile1.FileOption = OI_GET_MEDIA_FREE.
The Imaging for Windows ActiveX controls do not have corresponding calls. These calls are not typical in image viewing programs, but are in administration programs that monitor system capacity or perform system backup.

SAO contains methods GetVolumeCapacity and GetVolumeFreeSpace.

GetVolumeCapacity returns the capacity, in kilobytes, of the specified volume. Because the volumes are "logical" constructs, it is possible to define volumes that share physical storage space. In such a case, volume capacity statistics could be misleading, since the shared physical space appears as capacity under each of the logical volumes.

GetVolumeFreeSpace returns the amount of space available, in kilobytes, on the specified volume. Because the volumes are "logical" constructs, it is possible to define volumes that share physical storage space. In such a case, volume free space statistics could be misleading, since the shared available physical space appears as free space under each of the logical volumes.

I am writing a program to access a Document Manager database on the Imaging Server, but I want to test it using a local Document Manager database on my C drive. How do I do that?
You cannot. The Imaging for Windows ActiveX controls can only access Document Manager databases on Imaging Servers. There is no facility for creating a test Document Manager on a local drive.

 
Copyright 2000 - 2006 Global 360, Inc.