Service package 1
Übersicht Leistungspakete
Automic V24 Upgrade
V24 is a new major release of Automation Engine. With the discontinuation of the widely used V21 in September 2025, the topic of updating to the new major release is becoming more pressing for many users.
Many have experienced it themselves: a major release update of the Automic environment involves many uncertainties. There is a lot of experience to be gained during an update, some obstacles that cause delays, and some new features and configurations that need to be learned.
Automic Automation V24 in particular is characterized by extensive adjustments to the Automic software components in order to meet customer requirements, including the use of established standards in the areas of security, flexibility, scalability, and data storage. From V24 onwards, 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 the Automic database to be converted to the UTF-8 character set.
The effort and complexity involved should not be underestimated and may be a reason 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 want to help you carry out the necessary migration securely, stress-free, and quickly, and with predictable costs!
- EXPERIENCED
Our 18 permanent Senior Automic Consultants have more than 100 years of consulting experience between them. We have successfully supported many updates. Take advantage of this experience to eliminate potential obstacles in advance.
- COMPETENT
Deep technological knowledge helps us evaluate critical situations or recommend a course of action for your update. So you can focus on your important tasks.
- SAFE
The standard procedure we provide in this service module has proven itself. With it, you are on the safe side.
- TRANSPARENT
Every step in our process is transparent. We show you what is important and what steps need to be taken.
- KNOWLEDGE TRANSFER
We share our knowledge with you.
Secure an appointment for your upgrade today!
Our service package
1. PREPARING FOR 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 review of the environment using migration scripts. The result of this analysis is a list of objects that need to be changed. In the next phase of the project, these objects must be examined in more detail and incompatible objects must be adapted.
3. IMPLEMENTATION OF THE MIGRATION
The first step involves migrating the test system and its database according to a predefined procedure. The experience gained from migrating the test system forms the basis for optimizing the procedure for migrating the production system. After the migration has been completed, the new system environment is monitored. If a system runs stably over a longer period of time, the agents can be migrated successively for the test and production systems.
4. ENVIRONMENT TEST
Extensive testing is carried out after migration. We at best-blu initially supervise the tests; more in-depth testing is then usually carried out by the customer.
5. QUOTA FOR RETOUCHING
Following migration, questions or adjustments may arise. best-blu will provide support and assistance as needed.
Secure an appointment for your upgrade today!
Our service package
1. PREPARING FOR 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 review of the environment using migration scripts. The result of this analysis is a list of objects that need to be changed. In the next phase of the project, these objects must be examined in more detail and incompatible objects must be adapted.
3. IMPLEMENTATION OF THE MIGRATION
The first step involves migrating the test system and its database according to a predefined procedure. The experience gained from migrating the test system forms the basis for optimizing the procedure for migrating the production system. After the migration has been completed, the new system environment is monitored. If a system runs stably over a longer period of time, the agents can be migrated successively for the test and production systems.
4. ENVIRONMENT TEST
Extensive testing is carried out after migration. We at best-blu initially supervise the tests; more in-depth testing is then usually carried out by the customer.
5. QUOTA FOR RETOUCHING
Following migration, questions or adjustments may arise. best-blu will provide support and assistance as needed.
Secure an appointment for your upgrade today!
And after the migration? Optimization!
Optimize your Automic environment. To this end, we offer to check one to two months after the migrated environment has been in operation whether the selected configuration of the production system meets the requirements for performance, maintenance/reorganization, and operation in general, or whether further optimization is possible.
A health check is recommended for this purpose, whereby the values for the relevant system parameters are collected and analyzed.
This analysis can be used to derive concrete suggestions for further optimization of the system. By performing regular health checks, 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 effort is 3-5 days.
Calculable expenses!
For an initial configuration as follows:
- An Automation Engine system landscape with one Automation Engine Server in the Standard Edition under Windows or Linux for testing and production.
- A Microsoft SQL Server, Oracle, or PostgreSQL database.
- One AWI instance on each Automation Engine Server.
- The version of the active Automation Engine corresponds to the previous major release.
Total of 10 service days*
for test and production migration
* Services are provided on a time and material basis. If less is required, less will be billed, and vice versa
Any additional components that may be connected are not included in the cost (Analytics, Request Manager, etc.), nor is the setup of Zero Downtime Upgrade (ZDU), migration to a Kubernetes edition (AAKE), or the adaptation of objects or updating of agents.
