Server Resiliency Improved in Centerprise 7.5

By |2020-04-09T14:58:37+00:00August 29th, 2018|

We are releasing Centerprise Data Integrator 7.5 very soon, and as with every new release, our focus is to improve the product experience for our customers. We have added new features and have made improvements to the existing ones in the upcoming build.

One of the key changes we have made in the 7.5 version is greatly improving the server resilience. This will ensure trouble-free server operations, even when connection issues occur between Astera server and the MSSQL server hosting the repository databases. Enhanced server resilience will not only improve the overall performance of Centerprise, but will also prove to be significantly beneficial in the scenarios where 24/7 operation with high uptime is required, which is the case with most of our enterprise customers.

Key Benefits of Improved Server Resilience

With improved server resilience, users will get the following benefits:

Better and Quick Recovery of the Server

With improved server resilience, Astera server will no longer enter a permanent error state after a database outage event. Instead, it will recover as soon as the connection is restored, allowing the customer to continue with the normal operations without any downtime. The server can now survive most repository database outages without any user action required.

Auto-recovery mode – no manual restarts required

Manually restarting the server will be no longer necessary in case of lost connectivity. The server will recover automatically. If the server starts up when a connection to the repository database is not available, the server will enter a paused state waiting for the connection. When the connectivity is restored, the server will enter its normal operational state without the need for manually restarting it.

Improved Performance

Improved server resilience means improved performance. If the server is running the flows and an outage event occurs, the flows will not be terminated, and instead paused waiting on connection. This means that the server will be able to complete most flows successfully even in the presence of multiple random network and/or database connection issues.

Activity/Error Tracking

Logging in general, and logging of database connection issues in particular, have been greatly improved in the new release. Moreover, the server writes database connection issues in the Windows event log and includes a link to the Error file for easier troubleshooting. An entry is also added to trace the server log when the connection is restored.