Deployment

Install

Adeptia Connect can be installed on Microsoft Windows and Linux operating systems. You can download separate installers of the product for Windows and Linux from the Adeptia website.

System Requirement

You need to fulfill prerequisites, including supported operating system, hardware, database, software, and compatible browsers to install and use Adeptia Connect effectively. This page discusses all these prerequisites in detail and help you setup the required environment and seamlessly deploy Adeptia Connect within your production and the non-production environment.

All the information here is distributed in two sub-sections:

• Server Requirements

• Client Requirements

Server Requirements

Operating System

Adeptia Connect can be installed on the following operating systems:

Hardware Requirements

*Actual RAM and hard disk space required for running Adeptia Connect depend on many factors:

• Number of services running on a node,

• The complexity of the services deployed on the node, and

• CPU requirement for running these services.

The expected data flow and system performance also determine the RAM and hard disk requirement. Therefore, these requirements may vary for the production environment and the user is advised to refer to the typical configuration.

Database Requirements

The database requirements for installing Adeptia Connect are:

Database Sizing

*Size of log database can vary (within in the given range in the table above) depending on the number of transactions running in Adeptia Connect and on log retention time.

Client Requirements

Operating System

Software Requirements

Browser Requirements

Deployment Architecture

You can install Adeptia Connect in a clustered and non-clustered environment. In a clustered environment, you need to install Adeptia Connect on all the nodes of a cluster that are in the same network. In a non-clustered environment, you need to install Adeptia Connect only on a single node. 

This section contains the following information:

• Cluster deployment

• Non-cluster deployment

• Multi-zone deployment model

Cluster deployment

This is a multi-node deployment and is recommended for a production environment.

Non-cluster deployment

This is a single node deployment model recommended for a non-production environment. 

Multi-zone deployment model

Adeptia Connect deployment architecture also governs the multi-zone deployment model that defines the components of Adeptia Connect (Connect Portal and Connect Server), shared storage, and redundant databases which ensure optimal operational performance, even at times of high loads. This model also helps you understand one of the disaster recovery mechanisms of the Adeptia Connect system.

The diagram below represents the multi-zone deployment model of Adeptia Connect in different availability zones (data center). All these nodes are accessible to each other.

The multi-zone deployment model mandates the following requirements and configuration:

• Redundant and highly available architecture.

• Minimum 8 servers: 2 for Connect Portal, 4 for Connect Server, and 2 for Database.

• The cluster of Connect Server nodes can be increased to scale with high data and transaction volumes.

Installing on Windows

Download the installer package from the below-mentioned link.

Click here

Configuring SSL

Configuring SSL certificate on Connect Server 

To generate SSL certificate:

1. Open Command Prompt.

2. Go to the directory where JRE is installed (for example,<ConnectServerInstallFolder>/jre/bin).

3. Run the following Keytool command to create a Keystore for Connect Server with a self signed certificate or CA signed certificate. >

4. > For self-signed certificate : keytool.exe -genkey -keyalg RSA -alias selfsigncert -keystore C:/certs.jks -storepass changeit -validity 365 -keysize 2048 -ext san=dns:localhost

5. > For CA signed certificate : keytool.exe -import -trustcacerts -alias server -file <certificate_name>.crt -keystore <domain_name>.jks 

7. Copy this Keystore (certs.jks) at the location (<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel/etc/jetty).

8. From the same folder location, open the jetty.xml file and register the Keystore entry in the file. In the sslContextFactory section, add the path of the Keystore and the Keystore password (password chosen while creating Keystore).

9. Save the file.

10. Restart Connect Kernel and Connect WebRunner.

11. Save the file.

12. Restart Connect Kernel and Connect WebRunner.

Configuring SSL certificate on Connect Portal

To generate SSL certificate:

1. Open Command Prompt.

2. Go to the directory where JRE is installed (for example, <ConnectPortalInstallFolder>/jre/bin).

3. Run the following Keytool command to create a Keystore for Connect Portal with a self signed certificate or CA signed certificate.

   1. Run this command for certificate generation: keytool.exe -genkey -keyalg RSA -alias selfsigncert -keystore C:/certs.jks -storepass changeit -validity 365 -keysize 2048 -ext san=dns:localhost

4. 1. Copy this Keystore (certs.jks) at the location (…/<ConnectPortalInstallFolder>/keystore).

   2. Go to …/<ConnectPortalInstallFolder>/conf and open server.xml in the Text Editor.

   3. Update the Keystore entry in the server.xml file and add the path of KeystoreFile and KeystorePass (password chosen while creating Keystore).

5. Save the file.

6. Restart Connect Portal.