Difference between revisions of "Venice connector/Requirements"
From 1Archive help
Dino.dewaen (talk | contribs) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
==System requirements== | ==System requirements== | ||
| + | * At least Windows 8/Windows Server 2012 with TLS 1.2 enabled | ||
* Microsoft .Net framework version 4 or higher | * Microsoft .Net framework version 4 or higher | ||
* 100 MB RAM | * 100 MB RAM | ||
* 10MB disk space for the installation of the service | * 10MB disk space for the installation of the service | ||
* System logging can take up several GB per month. Cleanup of these files is not foreseen | * System logging can take up several GB per month. Cleanup of these files is not foreseen | ||
| − | * The service needs to run with a user that has sufficient privileges to access the venice folders and the connector folders. | + | * The service needs to run with a windows user that has sufficient privileges to access the venice folders and the connector folders. |
==Venice requirements== | ==Venice requirements== | ||
| Line 13: | Line 14: | ||
==Firewall settings== | ==Firewall settings== | ||
| − | The Venice monitor communicates to the onea archive (typically http://vis.onea.be/Onea) via https. You will need to allow this traffic in order for the Venice monitor to work. | + | * The Venice monitor communicates to the onea archive (typically http://vis.onea.be/Onea) via https. You will need to allow this traffic in order for the Venice monitor to work. |
| + | * In order to download and install new versions of the software, access to Amazon S3 downloads will be required (i.e. https://s3.eu-west-1.amazonaws.com/onea.downloads/veniceConnector/) | ||
==Requirements in SQL Server== | ==Requirements in SQL Server== | ||
| − | * We need an sql server instance running and a user with read and write rights to the database defined below. SQL express | + | * We need an sql server instance running and a user with read and write rights to the database defined below. SQL express 2016 or higher is perfect. |
* Database VENICE_MONITOR with 3 tables: | * Database VENICE_MONITOR with 3 tables: | ||
Latest revision as of 08:21, 22 September 2021
 |
You need to have an SQL Server running. If that is not the case, follow the SQL Server installation instructions. |
Contents
1 System requirements
- At least Windows 8/Windows Server 2012 with TLS 1.2 enabled
- Microsoft .Net framework version 4 or higher
- 100 MB RAM
- 10MB disk space for the installation of the service
- System logging can take up several GB per month. Cleanup of these files is not foreseen
- The service needs to run with a windows user that has sufficient privileges to access the venice folders and the connector folders.
2 Venice requirements
- The Venice monitor connects to the Venice SDK using a Venice user. So you will need to provide a user license for this.
- For further installation specifics you can check out the Venice connector installation
3 Firewall settings
- The Venice monitor communicates to the onea archive (typically http://vis.onea.be/Onea) via https. You will need to allow this traffic in order for the Venice monitor to work.
- In order to download and install new versions of the software, access to Amazon S3 downloads will be required (i.e. https://s3.eu-west-1.amazonaws.com/onea.downloads/veniceConnector/)
4 Requirements in SQL Server
- We need an sql server instance running and a user with read and write rights to the database defined below. SQL express 2016 or higher is perfect.
- Database VENICE_MONITOR with 3 tables:
- SVC_CABINET
- SVC_DOSSIER
- SVC_SYNCACTION
 |
The scripts to create these tables are provided by Onea, please contact us if you haven't received them. |
SVC_CABINET
This table is used to:
- store the locations of the cabinets to synchronize.
- store the URL and login info needed to upload/download data from VIS.
Following columns are available:
- code: contains the path to the cabinet. For example: "C:/Venice/Cabinets/cabinet.
- isActive: indicates if the sync of the cabinet should be active or not. Possible values are:
- 0: not active
- 1: active
- instanceCode: the name of the instance to which the cabinets belong.
- serviceAddress: the address of the webservice. Default value: https://vis.onea.be/Onea/WS
- serviceName: the name of the webservice. Default value: ERPSync
- username: the username of the user that will be used for synchronization. This should be provided by Onea.
- password: the password of the user that will be used for synchronization. This should be provided by Onea.
- scanProImageLink: the prefix-URL of the direct link to a document. Default value: https://vis.onea.be/Onea/site/d/
- hasPriority: if set to 1, this cabinet is synchronized first.
- prioritySorting: influences the order in which the cabinets are synchronized.
- processing: indicates that a cabinet is being processed at the moment.
- scanProPublicImageLink: the prefix-URL of the public link to a document image. Default value: https://vis.onea.be/Onea/p/d/
- scanProPublicDocumentLink: the prefix-URL of the public link to a document. Default value: https://vis.onea.be/Onea/p/doc/
SVC_DOSSIER
This table is used to define which dossier(s) of which cabinets need to be synchronized with VIS.
Following columns are available:
- dossier: indicates which dossier of the cabinet needs to be synchronized. This is the name of the dossier folder. It is also possible to use a wildcard (*) to indicate that all dossiers of the cabinet should be synchronized.
- isActive: indicates if the sync of the dossier should be active or not.
- cabinet_id: the id of the entry in the SVC_CABINET table.
- processing: indicates that a dossier is being processed at the moment.
- hasPriority: if set to 1, the dossier is synchronized first.
- prioritySorting: influences the order in which the dossiers are synchronized.
SVC_SYNCACTION
This table is used to store all different elements synchronized. There is no need to create rows here, these will be automatically added by 1Archive.
