vConnect Components

The vConnect module has the following components:

Connectors

In the vConnect module, the connector is one of the main components. It helps you configure third-party APIs, database services, etc. The vConnect module incorporates a UI-enabled configurator that helps you configure multiple APIs and databases.

Post successful configuration, the Vahana platform incorporated APIs and applications can connect with third-party APIs, applications, and databases.

The vConnect connector can be used for the following purposes:

• Connect RESTful APIs to databases
• Connects help execute drivers such as functions and procedures in the database
• UI-enabled configuration of parameters can be either passed in or returned from the function
• Helps convert Python, Java class or function, or java script files into API.

Core Functionality

In the vConnect module, the core functionality includes multiple features that are briefly described as below:

API Orchestration

This feature allows you to club multiple API based functions into a single web API call. This single API can be also referred to as wrapper API. After the wrapper API receives the client request, the clubbed APIs execute sequentially or parallel to return the response to the client environment. The API orchestration can be achieved in the following ways:

Orchestration Type	Description
Parallel Orchestration	Parallel orchestration is also referred to as enumeration. In the parallel orchestration, an incoming client request is broken into multiple outgoing sub-requests. Each sub-request executes through different service end-point simultaneously and captures a response. Thus, the responses to all sub-requests are combined into a single response and then returned to the client.
Sequential Orchestration	In the sequential orchestration, you can access multiple end points by automating a number of sequential calls. After the single API point (wrapper API) receives the client request, it sequentially invokes multiple service points to fulfill or authorize the client request.

Monitoring and Tracing API Performance

The vConnect portal allows you to constantly monitor the performance of the API. The UI based dedicated dashboard, log stash viewer, allows you to monitor and check the following performance parameters of an API:

• API execution time
• Timeout
• Average response time, etc.

This feature also stores the response of the API in the server machine and checks API tracing rule to reprocess the request if the request processing fails as a result of disconnection. It also allows you to configure alerts, API execution timeout.

API Management and Other Features

This feature allows you to manage multiple versions of an API. These multiple versions of an API can work in parallel manner in different environments. It also allows you to cache the API response for a specific time period. It also performs the API processing asynchronously that stores the response of the API in the back-end repository if the client application is not requesting the response.

UI Enabled Dynamic Environment Management

This feature creates “n” number of environments if the machines are available. To configure an environment, it only requires the IP address and the port number. It also manages the migration of the API across multiple environments. Based on environment-specific requirements, you can configure the variable.

Security Features

The vConnect portal offers the following security based features.

Feature	Description
Time-Synchronization Check	It checks the time difference between the device and server times.
Authentication Levels	It manages different levels of authentication.
IMEI (International Mobile Equipment Identity)/SIM Authentication	It enables IMEI number or SIM card type authentication.
Session Management	It maintains two types of sessions: Device Session and User Session. The device session is created after the app is installed on the device. The user session is created after the user logs in to the app. The scope of server side APIs is defined as a device session or a user session. If the scope of an API is defined as a user session and the API is invoked with the device session token, it cannot use the respective API. This feature configures the session timeout for the device session and user session.   The inactive session timeout can also be configured. For instance: – If a user does not perform any activity for the last x minutes, the user session will automatically log out of the application.
Strong Encryption Algorithm	It offers different types of encryption mechanisms such as RSA, AES, RSA+AES, etc.
Different Level of Keys Management	It provides user key management and device key management.
Encrypted Request and Response Over Format	It encrypts all requests and responses that are transmitted between the front-end application and middleware system by using a RSA+AES key algorithm.
User Key Management and Rotation	Every user has different RSA and AES keys to encrypt the data. The rotation of the user-specific key is configured in vConnect. Each end-user request is authenticated by using a JWT (JSON Web Token). For a user or app, the keys can be rotated dynamically.
Data Masking	In the vConnect portal, this feature allows you to mask the information for security purposes.
PI Data Encryption	This feature allows you to encrypt the personal data by using a AES key. We can configure the JSON key’s name for encryption.
Digital Signing of Request/Response	This security feature digitally signs data that is transmitted between the application and middleware. During the data transmission, if any single byte of data is spoofed, the middleware system does not accept the data.
Unique Request ID	Every request that is posted to the middleware should have a unique request Id. If someone attempts to copy and paste the existing request, middleware will not validate the request. As a result of validation failure, it will return the error message.
Application Access Control	It remotely blocks the access to an application by configuring the application access on the vConnect portal.
IP Whitelisting/Filtering	If any application needs to work only on a specific IP address or a range of IP addresses, you can configure the IP address filtering/whitelisting property in the middleware.
Device and Login ID Binding	You can use this feature to configure a IMEI (Internation Mobile Equipment Identity) number.