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 is irrelevant for the portal user, whether the file, which is available in the portal, is stored locally or in hyparchive. The following chart shows the role of the connector and the involved 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 cannot 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 hyparchive user, 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 Intrexx search 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 "Processes" module, the same actions are available for dg hyparchive as for normal Intrexx data groups. This allows files to be transferred via a process from Intrexx to hyparchive and vice versa.
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.
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.
The name of the connection is shown here.
The description of the connection is shown here
"Data groups" column
The number of data groups, which are integrated into applications as external data groups, is shown here.
dg hyparchive configurations are automatically exported when the portal is exported, and then imported with the portal. 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. After restarting the portal server, the configuration will be available in the Integration module.
dg hyparchive requests and responses can be logged in the Portal log file to help with error analysis. Tracing is activated as follows:
Open the "portal.cfg" file from the portal directory \internal\cfg\ in a text editor.
Navigate to the section "environment" and insert the following lines there:
<systemProperty name="com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.dump" value="true"/>
Example of a request/response tracing entry:
---[HTTP request - https://10.10.101.213:8001/HypService]--- Accept: application/soap+xml, multipart/related Content-Type: application/soap+xml; charset=utf-8;action="HypWcfApi.HypService/IHypService/MDocGetInfo" User-Agent: JAX-WS RI 2.2.9-b130926.1035 svn-revision#5f6196f2b90e9460065a4c2f4e30e065b245e51e <?xml version='1.0' encoding='UTF-8'?><S:Envelope ... </S:Envelope>[HTTP response - https://10.10.101.213:8001/HypService - 200]--- null: HTTP/1.1 200 OK Content-Length: 2614 Content-Type: application/soap+xml; charset=utf-8 Date: Mon, 27 Apr 2015 13:20:30 GMT Server: Microsoft-HTTPAPI/2.0 <s:Envelope xmlns:s="https://www.w3.org/2003/05/soap-envelope" xmlns:a="https://www.w3.org/2005/08/addressing"><s:Header><a:Action s:mustUnderstand="1">HypWcfApi.HypService/IHypService/MDocGetInfoResponse</a:Action><a:RelatesTo>uuid:65af1684-0548-47d2-8346-fff60f4c85f1</a:RelatesTo></s:Header><s:Body><MDocGetInfoResponse xmlns="HypWcfApi.HypService"><MDocGetInfoResult…></s:Envelope>
For SSL connections between the Intrexx portal server and an OData service, the Certificate Authority that provided the service certificate must be added to the certificate store of the Intrexx portal server. Self-signed certificates are an exception to this, which are not provided by a recognized Certificate Authority. In order to enable SSL connections to services with self-signed certificates, the check on the certificate chain must be deactivated. This is possible at the service level via a system property. To do so, open the "portal.cfg" file in the portal directory /internal/cfg/ with a text editor and add a new <systemProperty> entry to the <environment> section:.
<systemProperty name = "de.uplanet.lucy.server.dgdg hyparchive.connector.sslTrustEveryone" value="true"/>
After saving the "portal.cfg" file, the Intrexx portal service must be restarted so that the changes take effect.