IXOS Connector Volume Table: ixos_volume - IXOS Connector Volume Table: ixos_volume - Saperion ECM - Saperion IXOS Connector - Current/Saperion-IXOS-Connector/hbi1763030646485 - Current - Current

Saperion IXOS Connector

Platform
Saperion ECM
Product
Saperion IXOS Connector
Release
Current
License
ft:lastPublication
2026-04-06T13:28:41.785926
ft:locale
en-US

In the OT archive, ISO files can be found on either a Centera or a on a NetApp. This information can be offloaded in a separate table and is linked with the component table by means of VOLID[1-3].

Process via OT:

Which medium must be accessed is determined using the VOLID[1-3] entries. There are varying media, for example: disk buffer, cache, ISO image, etc. To access legacy data, only ISO images are relevant. The OT server is called with the appropriate volume name and determines which NetApp or Centera the read call should be sent to, based on accessibility, workload and performance. The volid and volname are contained in the ds_volid OT table. The OT server knows all the “volnames” and thus also the Clip ID or path of the original and backup NetApp.

Process via IXOS Connector:

In the „ixos_comp“ component table, there are three columns which contain a reference to the actual storage location of the ISO image: vol[1-3]. The exact value of one of these columns can be resolved via the ix-os_volume table. Thus the entries in volid[1-3] are independent from the Centera or NetApp archive storage system. The way Centera and NetApp handle this differs only in whether the ixos_volume table contains the Clip ID or the NetApp path.

The content of the ixos_volume table is supplied by means of the TOC files from the original and backup virtual jukebox. The pathnames of the ISO images are inherited from the TOC files of the virtual original and backup jukeboxes. The column “volumename” is populated by means of the “isoutil size –I $iso” IXOS tool. The IXOS connector sequentially reads the values of volid1, volid2 and volid3, and searches the volid column in the ixos_volume table for the corresponding ISO image. If the entry exists, SAPERION tries to load the ISO from the original or backup storage location.

The table for the volume information is thus comprised of the following columns:

Field Name Type Description
VOLID number(9) Reference column
VOLUMENAME VARCHAR2(32) Volume name
VOLUMETYPE VARCHAR2(1) 1:Centera Clip, 2:NetApp File name
ORIGPATH VARCHAR2(256) Access information (ClipID, path)
BACKUPPATH VARCHAR2(256) Access information for backup data (ClipID, path)
Warning: The VOLID1-3 field in the ixos_comp table must contain enough information to uniquely identify either a Centera Clip ID or a NetApp path

It is the customer’s responsibility to migrate the IXOS data into the connector volume table, since without this information, no documents can be extracted from the Siemens archive. The number of columns in the archive table can be expanded as needed to accommodate future growth.