🔗 Source article (Salesforce): Click here
HealthConvEx version 8.5. Installation Requirements overview.
Machine
OS
Database
SSL Configuration
LDAP Configuration
Network Configuration
Old Database Properties (if applicable)
Machine
In order to garantuee the necessary service, provide a machine that has the resources as listed below.
Dedicated (virtual) machine per application of HealthConvEx
Access to a database (see Database)
Min. 2-core, min 8GB ram and 50GB HD per application of HealthConvEx
A valid SSL certificate in case you want to setup HealthConvEx through HTTPS (see SSL Configuration)
Port 443 OR 80 should be open on the firewall for HTTP or HTTPS (see Network Configuration)
Access to the Healthconnect and HealthConvEx central platform (see Network Configuration)
Diabscan 6 database export in a new HealthConvEx schema (if applicable)
OS
Windows server 2012 R2(Extended Security Update Year 3) or higher
OS updates are allowed
All downloads of new HealthConvEx versions must be allowed
Database
In order to store the necessary data, HealthConvEx maintains the data in a MS SQL database with the following requirements:
MS SQL 2016 or higher size on HD minimum 5GB
Can be on a shared instance with shared resources
The HealthConvEx service will need dbowner rights for the database. The type of user may be a sql user or a windows service account
An installation of SQL server management studio 2016
Collation: Latin1_General_CI_AS
Backups on daily basis mandatory
SSL configuration
We strongly advise to setup the HealthConvEx via HTTPS.
In order to configure the SSL connection please provide us the following info:
a valid PFX file (The PFX is a certificate with which we can activate HTTPS to reach the HealthConvex web application) with its required credentials.
LDAP CONFIGURATION
Info here available.
LDAP secure is supported in HealthConvEx
Network configuration
The HealthConvEx application is accessible via the browser.
On the server, make sure port 443 (https) is open (or port 80 when there is no ssl available).
Access to the following endpoints are needed (based on the environment):
ACCEPTANCE
PRODUCTION
Old database properties (if applicable)
During install HealthConnect will migrate the old diabscan 6 into the new database. Therefore we need a connection to A COPY OF your old diabscan database.
Connection info to old diabscan database copy.