Connector for dg hyparchive in processes

How to configure a connection to dg hyparchive in Intrexx can be found here.
Information about dg hyparchive in Intrexx applications can be found here.

User switch action

Because interactive user logins to a foreign system are not possible in processes, a login to hyparchive within the process needs to first take place before hyparchive actions are triggered. There are two possible ways to do that, with which an additional user, which was setup in the hyparchive configuration, can be selected for authentication. For a timer-controlled event the user can be directly selected in the timer configuration.

The user switch action, which allows you to switch to hyparchive user within a process, is another possible option.

To do that create a new User switch action and select dg hyparchive on the Action type page. The user, with which the following actions should be carried out, can be selected in the next step.

Synchronize stamp data

In contrast to files, the stamp data of a document, which was saved in hyparchive via Intrexx, is saved in the Intrexx data group fields. If the stamp data of a document is directly edited in hyparchive, then it cannot be automatically and immediately synchronized in Intrexx. Therefore Intrexx updates the fields of a hyparchive stamp automatically, as soon as the data set is opened on a view or entry page. The user needs to click on Save to save the updated data in Intrexx.

This method can be automated by a process, so that the metadata of an Intrexx data group is synchronized with the objects in hyparchive on a regular basis. To do that, create a new process and insert a new Timer event.

In the timer configuration select hyparchive data group and define where appropriate a filter. In the next step you need to define the user, whose static login details were recorded in hyparchive configuration.

Add a new Data group action to the Timer event handler and select Update record. The target data group is the same as the timer's and the two ID fields will be selected as a Simple filter. Field assignment is the next step. Here you can assign fields from the source data group to the target data group, for which hyparchive stamp data should be reread and resaved. Please note with this that the data fields cannot be synchronized, as this would otherwise create a new version in hyparchive.

After closing the dialog, the process can be saved and carried out. When the records from the source data group are read, the data from hyparchive will be reread and then resaved in the assigned data fields in Intrexx.

File transfer between Intrexx and dg hyparchive

Normally files and documents will be only be physically stored on the hyparchive server and loaded by Intrexx during run time when a user accesses a hyparchive file via the portal. In some circumstances it can also make sense to transfer files from hyparchive to Intrexx or to copy existing files to hyparchive from the Intrexx portal. To do that, data fields between Intrexx and hyparchive data groups can be assigned in the Data group action. If information is read from a hyparchive data group and then written in an Intrexx data group, then the files will be copied from hyparchive to the Intrexx Portal Server. Vice versa, files can be copied from Intrexx applications to hyparchive. This is done by reading from an Intrexx data group and then writing to a hyparchive data group. Which data sets – and with that files – should be transferred to each target system can be setup with the filter option on the source data group.

The following example illustrates the transfer of files from Intrexx to hyparchive:

At first the data sets are read from an Intrexx data group via a Timer controlled event. Afterwards, login to hyparchive takes place via a User switch action. Then the files and metadata are transferred from the Intrexx data group fields to hyparchive using a Data group action. The Field assignment looks like the picture below:

Importing and exporting hyparchive configurations

hyparchive configurations are automatically exported, when a portal export is carried out, and re-imported, when a portal import is carried out. Should it be necessary for a single configuration to be exported to another portal, then this is currently only possible using the file system.

The configuration files are found in the portal directory under internal/cfg/dghyparchive. Each configuration consists of an XML file. The file name corresponds to the configuration GUID.

If you need to transfer a configuration to another portal, then you can simply copy the appropriate file and insert it into the subdirectory of the target portal. This configuration will then be available in the Integration module after the portal has been restarted.