The Connector for dg hyparchive enables you to use the dataglobal
Enterprise Content Management solution dg hyparchive,
hereafter called hyparchive, as the location for
files that are normally saved in Intrexx data groups on the local file system.
In addition to the saving of files, a document's stamp fields can be edited
and maintained. And with that it's irrelevant for the portal user, whether
the file, which is available in the portal, is stored locally or in hyparchive.
The following diagram demonstrates the role of the connector and the related components.
A data field of an Intrexx data group,
which is linked to hyparchive,
corresponds to a document or document folder in hyparchive. One or multiple
documents can be saved per data field. This depends on whether the object in
hyparchive corresponds to a single file or an archive.
Files can not only be saved in hyparchive, but also opened (or actually
downloaded) directly from hyparchive in an Intrexx portal. The access to
hyparchive takes place with a specific
whereby all of the
permissions in hyparchive are taken into consideration. Depending on the
authentication method, Intrexx portal users can either directly log in to
hyparchive or the access takes place with a so-called static user, which is
setup in the file field's configuration.
Intrexx is fundamentally viewed as the leading system in the interaction with
hyparchive. This means that files are uploaded and their stamp information is
created in Intrexx and then transferred to hyparchive. With that, stamp data is
saved in hyparchive and additionally in the Intrexx data fields; files are only
saved in hyparchive though.
A full-text search of the contents of the documents is not
possible using the
because the files
only exist in hyparchive. Searching in hyparchive can be achieved using
Intrexx filters or the research function of the
hyparchive web client.
In the Intrexx Processes module, the same actions
are available to hyparchive, as to the normal Intrexx data groups. This allows
files to be transferred via a process from Intrexx to hyparchive and vice versa.
2. New connection
Selecting dg hyparchive menu / New data source
will open a wizard
where a new connection can be created.
This option is available if the Connector for dg hyparchive is selected under
Consume data on the left-hand side. In each configuration dialog, you can reach the
corresponding Intrexx Help by pressing F1 or by clicking on the "Help" button.
3. Edit connection
Every connection created by you is listed in the right-hand area.
All of the functions available for editing a connection can be reached via the
dg hyparchive menu,
when an existing connection has been selected on the right.
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.
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.
hyparchive requests and responses can be logged in the
Portal log file to help with error analysis.
Tracing is activated with the following method: 1. Open the file
"portal.cfg" from the
portal directory /internal/cfg
with a text editor of your choice.
2. Navigate to the section "environment" and
insert the following lines there:
The certificate from the Certificate Authority, which issued the service
certificate, must be added to the Intrexx Portal Server's certificate store
for SSL connections between the Intrexx Portal Server and a hyparchive web service.
Self-signed certificates, which aren't issued by a known Certificate Authority,
are an exception. To make SSL connections to services with self-signed
certificates, you need to deactivate the checking of the "Certificate Chain"
on the Intrexx Portal Server in this case. This is possible on the service level
with a system property.
To do that open the file "portal.cfg" in the
portal directory internal/cfg
with a text editor and insert a new "<systemProperty>"
to the section "<environment>":
<systemProperty name = "de.uplanet.lucy.server.dghyparchive.connector.sslTrustEveryone" value="true"/>