Hotfixes are released with each sub-releaseReleases combine a set of activities and a set of packages as well as other release artifacts under a timeline (a plan including milestones and phases), which can be planned, baselined and tracked.. They serve to remove possible malfunctions and defects. Please note that the most current hotfix always includes the modifications of previous hotfixes. It is therefore not necessary to install all previous hotfixes in order to have all modifications included in your AE system.
Use the guidelines for upgrading an AE system if you intend to upgrade to a new version of AE.
Messages and message numbers can also change within hotfixes. Adjust them if they have a control functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… in your AE system. The message-comparing program UCCMPMSL.EXE lists all messages that have changed.
![]() |
1. |
Downloading a Hotfix |
---|
A listShows entities in a grid view of applicable downloads will be listed at the bottom of the screen.
![]() |
2. |
Installing a Hotfix |
---|
The installation procedure depends on the componentA component is a single deployable application artifact. As an example, this can be yourfile.war to be deployed into a Tomcat container. Each component has different properties which determine where to get it from, how to configure it, etc. You will need one component per application artifact: e.g., one for the application tier and one for the database backend. that is to be updated.
The DB directory must be a parallel directory of the utilities' BIN directory.
Set the parameter StartMode =COLD in the INI-file UCSRV.INI of the server processThe core of the component Automation Engine. Different types are available: communication, work and dialog processes, as well as nonstop processes. that starts first (in other words, the one that will be the primary work processIt is responsible for the execution of Automation Engine-internal tasks and work processes.). Restart this server process and then restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts. all other server processes.
If you intend to update the server as well, a coldstart is only required after the server hotfix installation.
Automic recommends installing one common hotfix version for initial data, server processes and UserInterfaces.
When updating the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."] to a new hotfix version, make sure that you use the current Online Documentation. If your version is not up to date it can happen that an incorrect document opens when you open the help in the UserInterface via the F1 key. This can also happen if you install the Online Documentation with a hotfix but use an older version of the UserInterface.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |