Automic V24 Update

made easy!

With V24, a new major release of the Automation Engine is available. With the discontinuation of the currently widely used V21 in September 2025, the topic of updating to the new major release is coming closer for many.

Many people have experienced it themselves: a major release update of the Automic environment is associated with many uncertainties. Many experiences that have to be made during an update, some obstacles that cause postponements and some new features and configurations that have to be learned.

Automic Automation V24 in particular is characterized by far-reaching adjustments to Automic software components in order to implement customer requirements, including the use of established standards in the areas of security, flexibility, scalability and data storage. As of V24, this includes, for example, the conversion of the database to UTF-8, the Automic Automation Kubernetes Edition (AAKE) and the conversion of the Windows and Linux agents to Java.

The conversion to Unicode requires a conversion of the Automic database to the UTF-8 character set.

The effort and complexity are not to be underestimated and can be taken as an opportunity to switch to the open source database PostgreSQL.

We have therefore put together our V24 service package based on our experience. With this package, we would like to help you to carry out the necessary migration safely, stress-free and quickly, and at a calculable cost!

Book an appointment for your upgrade today!

Please fill out the contact form.
Contact

Experienced

Our 18 permanently employed senior Automic consultants can draw on well over 100 years of consulting experience. We have successfully supported many updates. Use this experience to eliminate potential obstacles from the outset.

competent

In-depth technological knowledge helps us to assess critical situations or recommend a course of action for your update. So that you can concentrate on your important tasks.

Safe

Our standard procedure, which we provide in this service module, has proven itself. So you are on the safe side.

Transparent

Every step in our process is transparent. We show you what is important and which steps need to be taken.

knowledge transfer

We share our knowledge with you.

Our service package

1. Preparation of the migration

As part of the preparation, the migration process is worked out with the customer. This includes planning the conversion of the Automic database to the UTF-8 character set or the switch to a PostgreSQL database.

2. Migration-analysis

The migration analysis includes at least a check of the environment using migration scripts. The result of this analysis is a list of objects that need to be changed. In the further course of this project phase, these objects must be examined more closely and incompatible objects adapted.

3. Implementation of migration

The first step is to migrate the test system and its database according to a pre-agreed procedure.

The experience gained from the migration of the test system forms the basis for optimizing the procedure for migrating the production system.

Once the migration is complete, the new system environment is monitored. If a system runs stably over a longer period of time, the migration of the agents can be carried out successively for the test and production system.

4. Testing the environment

Extensive tests are carried out once the migration is complete. We at best-blu initially accompany the tests; more in-depth tests are then usually carried out by the customer.

5. Contingent for rework

Questions or adjustments may arise after the migration. This is where best-blu will provide support and be available.

Book an appointment for your upgrade today!

Please fill out the contact form.
Contact

Migration example

Our service package

And after the migration?
The optimization!

Optimize your Automic environment. To this end, we offer to check one to two months after operation of the migrated environment whether the selected configuration of the production system meets the requirements for performance, maintenance/reorganization and operation in general, or whether there is room for further optimization.

A health check can be used for this purpose, whereby the values for the relevant system parameters are collected and analyzed. Concrete suggestions for further optimization of the system can be derived from this analysis. By carrying out a health check regularly, e.g. once a year, future bottlenecks can be identified in good time and thus proactively prevented. Depending on the size of the production system and the scope of services, the expected time required is 3-5 days.

Back

Calculable effort!

For an initial constellation, as follows:

  • An Automation Engine system landscape with one Automation Engine server each in the standard edition under Windows or Linux for testing and production.
  • One Microsoft SQL Server, Oracle or PostgreSQL as database.
  • One AWI instance on the Automation Engine server.
  • The version of the active Automation Engine corresponds to the previous major release.

total 10 service days*

for the migration of test and production

* Services are provided on a time and material basis. If less is required, less is billed and vice versa

Any other connected components are not included in the effort (Analytics, Request Manager, etc.), nor is the setup of Zero Downtime Upgrade (ZDU), or the migration to a Kubernetes edition (AAKE) or the adaptation of objects or the update of agents.