Administration Guide > Installation > Upgrade Installation > Upgrading from Version 11.1

Upgrading an AE System from Version 11.1

Guidelines for upgrading to a new Automation Engine version.

Below you find the necessary steps for upgrading your system to the latest version.
To help you follow the individual steps of an upgrade process of your AE system meticulously, this topic is divided into several steps.

Our consultants are experts in upgrading AE systems. Contact Automic, our experts will be pleased to assist you whenever it is necessary.

In order to print the whole contents of the collapsed pages below, use the button Expand all/Collapse all in the menu bar above.

Preliminary Information

ClosedNotes

To ensure that your upgrading process is successful Automic recommends that you strictly follow the steps that are described in this guide.

Never upgrade a productive AE system without having it tested extensively in a separate environment.

For details about installing hotfixes, see the related topic hotfix installation.

ClosedGeneral Information

It is very important that you follow a structured procedure when you upgrade an AE system, because it guarantees that processing can be continued as soon as possible.
The following guidelines explain the required steps in detail and especially address areas that need special attention. Follow the recommended steps for a smooth conversion process and you will soon be able to use all the new functions of your new Automation Engine version.

When changing the version of the Automation Engine, the utility AE DB Load processes and monitors all the required steps for changing the databaseA database is an organized collection of data including relevant data structures.. This is necessary, because it also modifies data that cannot be changed with SQL. All steps that the utility processes during the upgrading process are logged in the file uc_upd.txt. The file chngdb.sql also informs about the database-relevant statements that were set. These statements must be processed by the utility. Refer to the Release Notes of the relevant Automation Engine version for changing the database and preparing the necessary steps.

The upgrading process comprises of several stages:

  1. Installation and comprehensive testing in a test environment.
  2. Planning the conversion time and creating a plan for a possible re-conversion.
    Never change to a new Automation Engine version without having planned a re-conversion scenario.
  3. Make a backup of the AE database and all the components' directories.
  4. Upgrade your system step by step WITHOUT using the new functions.
  5. Only use the new functions when every component has been converted to the new version and after a particular system-monitoring period.

Each stage consists of many small steps. Your AE system is not upgraded all at once but step by step. The old components are not overwritten and the new files are installed in separate directories. Only the AE database is directly upgraded with the utility AE DB Load. This method has two main advantages:

  1. You can quickly re-convert to the old AE-component version if problems occur in your system environment. Therefore, there is almost no risk for your processing.
  2. Depending on the size of your AE system, the complete upgrading process can take some time. The advantage of upgrading step by step is that you can do so in individual and shorter periods of time which makes it easier to coordinate the upgrading process with other departments and processes. And it is also easier to locate errors that might occur.

First upgrade your test system. Possible problems can so be recognized and solved before they occur in your production system. Test the individual upgrading steps, thereby setting up a plan for upgrading your production system.

The AE system is not available while the database is upgraded.

After each step of the upgrade installation, it is essential to monitor the new components for some time. Only continue the upgrading procedure when they have proven to run stably.

Note that the upgrading process Automic recommends enables production to be continued in the old Automation Engine version at any time. The only requirements are a parallel installation of the components and the provision of a second database instance.

Use the message-comparing program if you require a list of all changed messages.

Our consultants are experts in upgrading AE systems. Contact Automic, our experts will be pleased to assist you whenever it is necessary.

ClosedRequirements

Done

Condition

Carefully read the Release Notes of the relevant Automation Engine version. They include information that must be taken into account during the upgrading process.

The most important requirement is a test system. Comprehensive tests in a separate system are necessary before the new Automation Engine version is used in your production system. The test system helps you to get used to the necessary steps for upgrading your production system and even to optimize them.

Has your database been maintained on a regular basis? Automic recommends starting a reorganization run with AE utilities and database means before you upgrade the database. The smaller the database, the quicker the upgrading process. Note that it will still take some time to upgrade the AE database and that you will need sufficient disk space for having tables duplicated.

Authorizations for the affected computers, databases, ERP systems etc. are required during the various upgrade phases. Ensure that the responsible administrators are available during the particular work steps.

You can request assistance from consultants, developers or even 24x7 support when you upgrade your system. Our experts are trained in providing excellent support when action is taken in critical and sensitive areas of your AE system. Contact your Account Manager or the Technical Support TeamTechnical Support Team as soon as you know when you are going to start the upgrading process.

Ensure that you have the phone number and e-mail address of Technical Support and your login data for the Download Center.

The Installation Steps

Closed1. Check Incompatibilities between Version 11.1 and 11.2

The table below lists new features that might lead to compatibility issues or should be taken care of when upgrading - it does not list all new features of this AE version.
New features are described in full in the release notes.

Description of the table columns:

  • Topic - Name of the general topic or new feature
  • Changed behavior - What has been changed
  • Possible incompatibilities - Impact the change may have
  • Actions/Countermeasures - What can be done to identify and/or remove possible incompatibilities

Topic

Changed behavior

Possible incompatibilities

Actions/Countermeasures

General DB change

Information and the checking instructions apply to all versions, between your existing installation and the latest you want to upgrade to, respectively.

The DB scheme/structure has been changed.

Custom SQL queries on AE DB do not work anymore.
  • Check chngdb.sql for general changes
  • Check and adapt relevant SQL/SQLI/SQLJOBS objects accordingly
  • Check and adapt relevant DB queries used in external tools/programs

Release Packaging

The Release Packaging (zip files, folder structure and its content) have been changed.

The following files and folders have been removed:

  • Folder ./11/ (the content, e.g. UserInterface, AutomationEngine) are now directly in the base directory and no longer in the sub folder.
  • The uc4setup files and the CD image files have been removed.
  • There is a new installer available for single box installation in the product bundles.

Possibly automated installation routines using release images will not work.

If there are scripts relying on the old package structure, you have to adapt the paths.

CP/WP routing 

FORMS request routing to RA agents has been changed.

When you edit RA connection objects, a corresponding RA agent has to be active in the same client to retrieve data.

Assign an RA agent for relevant clients.

Third party monitoring via External Monitoring Interface

The new state-of-the-art JMX interface EMI (External Monitoring Interface) has been introduced.

The existing SNMP interface is still available, but the third party integration with BMC Patrol, HP OpenView, and Tivoli has been de-supported.

There is no incompatibility, but the integration with BMC Patrol, HP OpenView, and Tivoli is not available anymore.

Integrate third party monitoring systems via the new EMI instead.

Doubled MQ tables

MQ tables have been doubled and renamed.

MQ tables might not be considered when you use DB Reorg and existing scripts might fail due to changed table names.

Adapt DB Reorg scripts.

Proxy INI file extensions

Parameters and the format of some parameter values have been changed in the INI file due to functionality improvements.

You will not be able to reuse INI files of Proxy versions prior to v2 without adaptions.

Adapt INI file parameters according to the Proxy user documentation.

Closed2. Prepare for Upgrade

Done

System
available:

Work steps

ClosedRead Release Notes

  • Start off by reading the Release Notes of the Automation Engine version to which you intend to upgrade. They are available in the "Release Notes" chapter of the Automation Engine documentation.
  •  The section "Check Incompatibilities between Version X and Y" is very important. It contains information about incompatibilities and points out additional work steps that can be required during or even before the installation. Automic recommends preparing your AE system and your system environment accordingly.

ClosedDeny New Job Starts

  •  Processing must not be changed during the whole upgrading procedure. If a problem occurs in your system environment during a particular step, you can either restore the AE database or directly use the original one if you made a copy. In doing so, there is almost no risk for your processing.
    Note that statistical data, reports, and modifications made to Variable object and Sync object contents are lost.
  • Inform all affected persons about the upgrading process and make sure that processing is not changed.
  • Create a user group that explicitly denies everything and assign all users to this group.
    If the Revision Report is activated in your AE system, the assignment to the user group must be made in the User object because the tab is locked in the user group object in this case.

ClosedPrepare the Upgrading Process of Core Components

  • Determine a point in time for upgrading the core components. Note that the Automation Engine must temporarily be stopped which interrupts processing. For this reason Automic recommends determining a time during which only a few activities take place. The duration of the upgrading process depends on the size of your AE system. Your experiences when upgrading the test system will help you estimate the required time to upgrade your productive system.
  • Ensure that you have the phone number and e-mail address of Automic Support and your login data for the Automic Automation Support zone ready. Carefully think about requesting temporary 24x7 support, if sensitive systems should be upgraded or if the upgrade is not made during the regular business hours of our support team.
  • Our experts are trained in providing excellent on-site support in upgrading your AE system. Contact your Account Manager or the Automic Support Team. Your request will be forwarded to the relevant expert in order to make an appointment.
  • During the upgrade process, you require access to the AE database and to all computers with AE core components (such as the Automation Engine, utilities etc.). Access to all affected computers is required, if you work in a distributed Server environment. Ensure that the responsible administrators are available and that the login data (such as passwords) is correct.
  • The UserInterfaces may already be upgraded. If you upgrade them together with the core components, access to the relevant computers is required.

ClosedUpgrade UserInterfaces

  • In order to upgrade, start the program SETUP.EXE in the IMAGE:USERINTERFACE\WINDOWS directory.
    All files required for UserInterface operation are copied into the specified directory. The default directory is C:\AUTOMIC\USERINTERFACE\BIN.
  • On UNIX follow the steps as described in the new installation of the UserInterface (UNIX).

Notes:

  • When you execute the setup.exe, the installation will find and keep existing configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. files from the previous installation.
  • Automic recommends using UserInterfaces in a preceding AE system only for a few days when converting to a later version. As of version 9.00A, UserInterfaces can also be used in the particular preceding version. The only requirement is that your AE system has the latest hotfix version. Be informed that the UserInterface is not completely downwards compatible. Some functions are not fully available.
  •  Changes made in the UserInterface's interface only become visible when the core components have been upgraded to the new version.
  •  Older UserInterfaces cannot be used with AE systems of a newer version. They must be upgraded at least when the core components are upgraded.
  •  This does NOT apply to agents which function the other way round. Later agent versions CANNOT be used in former AE systems. But former agent versions can also be used in the succeeding Automation Engine version (this means that an 9.00A agent can also be used in a 10.x AE system). This requires the most current hotfix version to be installed on your AE system.

ClosedUpgrade the Enterprise Control Center

Upgrading from ECC 2.1 or 11.1 to 11.2

Upgrading an existing ECC installation to a new release upgrades the ECC framework and all its plug‑ins at the same time. Use the same steps to install hot fix packages between releases.

Overview

To upgrade from Enterprise Control Center 2.1.x or 11.0 to 11.2 .x.x involves the following steps:

No data migration is needed.

Closed1. Stopping the Apache Tomcat Service

Closed2. Backing Up Current Configurations

Closed3. Upgrading Apache Tomcat

Upgrade the Apache Tomcat web applicationA web application is an application that is accessible over a network (Internet or intranet) and is typically coded in a programming language like Java or JavaScript, combined with a markup language like HTML. Web applications are provided on web servers and web browsers are used as GUI on client computers. server where you have ECC currently installed to the latest version that complies with the new release.

  1. Check the System Requirements in our online database, the Automic Compatibility Checker to see which version of Tomcat you need.
  2. Go to the Tomcat home page and then download and install the required version. You will find the installation instructions and other relevant information on their home page.

    http://tomcat.apache.org/index.html

    For Windows: Download the package called "32-bit/64-bit Windows Service Installer." This will install Tomcat and a Windows service for it.

  3. Increase the memory that Tomcat can allocate to ECC to the amount described in the table that follows..

    Reason: By default Tomcat allocates a low amount of memory to an application. This is not sufficient for ECC, which keeps a lot of UI state data in memory.

    Memory ParameterAmount to Allocate
    PermGen Space256m
    Heap size

    As much as possible (at the very least 2GB)

    On Windows: 

    1. Go to the "bin" folder in your Tomcat installation (...Apache Software Foundation\Tomcat 7.0\bin).
    2. Right-click the file tomcat7w.exe and from the context menu select Run as administrator.
    3. On the Java tab make the following changes:
      • In the Java Options, set the PermGenSpace by adding the parameter
        "-XX:MaxPermSize=256m". (Attention: Case sensitive parameter!)
      • Set the heap size by setting the Maximum memory pool to the maximum possible on your system, for example 8192MB, as shown below.

    On Linux: In the CATALINA_OPTS environment variable, set the permGen size to 256MB and the heap space to the maximum possible on your system. In this example, the heap space is set to 8192MB: 

    -XX:MaxPermSize=256m -Xmx8192m

Closed4. Restarting the Apache Tomcat Service

Closed5. Deploying the New ECC WAR File

Closed6. Configuring the New ECC Version

Closed7. Starting the New ECC

ClosedMaintain the AE database

  • Automic generally recommends that you maintain your AE database with our utilities and database-specific tools on a regular basis. However, reorganize your database before you upgrade it. The smaller the database, the faster the upgrading process to the new Automation Engine version will be.
  • Carefully read the AE Scripts that refer to the AE database and prepare adjustments (e.g., tablespaces). In doing so, you see the actions that will take place and respond to them in the database and on the computer on which the database has been installed (e.g., by providing disk space).

These scripts are provided in the directories IMAGE:DB\GENERAL\<version> and IMAGE:DB\<database type>\<version>. The files uc_upd.txt and chngdb.sql are especially important.

ClosedDuplicate the AE database

  • For company-critical processing in the AE system Automic recommends duplicating and backing up your database.
    In doing so, you may leave one of the databases unchanged and easily re-access your old database, if any problems occur in your system environment.
  • The database can be duplicated in several ways:
    • For smaller databases: Dduplicate the database in offline mode. This can be done during the upgrading process of the core components. During this time, the AE system is not available anyway.
    • For larger/complex databases: Upgrade in online mode before the core components are upgraded.
      Inform your database-administration group because the current log files must be stored in the duplicated database.

Closed3. Upgrade the core components

Done

System
available:

Work steps

ClosedUpgrade Utilities

  • Always use a separate directory in order to avoid mixing files of the different Automation Engine versions. Depending on the computer, you will either install one or several components. First create a folder whose name represents the Automation Engine version. Then create an individual sub-folder for each component. An example is shown in the chapter about new installations.
  •  Do not remove or overwrite the installation directories of your utilities. Back up the corresponding folders in order to make sure that you can quickly return to your old version if any problems occur.
  • Install the utilities (UNIX or Windows).
  • Copy the folder "DB" from the CD to the directory of the utilities. It includes the files for loading the AE database. The DB folder must be a parallel folder of the utilities' BIN directory.

    Example for Windows:

    Utility in C:\AUTOMIC\UTILITY\BIN

    Database files in C:\AUTOMIC\UTILITY\DB

ClosedUpgrade AE and ServiceManager

  •  Do not remove or overwrite the installation directories of your Automation Engine and the ServiceManager. Back up the corresponding folder in order to make sure that you can quickly return to your old version.
  • Install the Automation Engine (UNIX or Windows) to a new directory.
  • Install the new ServiceManager version. Use a new name for the ServiceManager environment (phrase).

ClosedUpgrade Framework Integration (optional)

  • Alternately, you can carry out this step after the core components have been upgraded. The function Framework Integration is not available until it has been installed.
  •  Do not remove or overwrite the installation directories of your utilities. Back up the corresponding folders in order to make sure that you can quickly return to your old version if any problems occur.
  • If you use a Framework Integration such as "AE Smart Plug-In for HP OpenView", Automic recommends installing it in the new Automation Engine version.  

ClosedUpgrade UserInterfaces (if they have not yet been upgraded)

If you didn't upgrade during the preparation process, do so now.
Details you find above under "Prepare for Upgrade > Upgrade UserInterfaces".

ClosedUpgrade the Enterprise Control Center (if it has not yet been upgraded)

If you didn't upgrade during the preparation process, do so now.
Details you find above under "Prepare for Upgrade > Upgrade the Enterprise Control Center".

ClosedStop all clients

  •  Starting with this step, your AE system is no longer available until the database has successfully been upgraded.
  • Stop all clients when the upgrading time is ripe. This is easily done in the system control of client 0000.

ClosedStop the Automation Engine

  •  Stop all server processes. If you work in a distributed Server environment, note that all server processes on all participating computers are deactivated.
  •  Pay attention to programs such as Watchdogs, cluster monitoring etc. before ending the server processes. They might raise an alarm or restart the Automation Engine.  

ClosedBack up the AE database

  •  Back up your AE database.
  • As already described in the section on preparations, creating a database copy provides many advantages. Duplicate it now if you have opted for this step but have not yet executed it. If a database duplicate was already made at an earlier point in time, check if this duplicate must be upgraded.

ClosedUpgrade the AE database

  • Automic strongly recommends reading the notes concerning database modifications below before starting the upgrading process.
  • Upgrade your AE database using the utility AE DB Load. The individual steps you find below.
  • If you have created a duplicate, Automic recommends upgrading it now in order to make sure that the original instance remains operable. Keep in mind to enter the correct database connection in the INI files of the utilities.
ClosedNotes on Upgrading the AE Database

 

Important Notes:

 
Automic recommends that a database administrator execute the following steps.

 Direct modifications that are made in database contents without using AE programs will result in an inconsistent database.

Always make a database backup before you process any work steps.

This process can take a while depending on the database size and upgrading complexity.

Ensure there is sufficient disk space for the \AUTOMIC\DB directory and that the database's LOG section can store all this data.

 Schemes that provide access to the database should be removed after the updating process in order to avoid unintended database modifications.

DB2: After updating the AE database, check the size of the tablespaces and if required, run the following SQL statement:

alter tablespace <UC4 tablespace name> reduce max;

ClosedDatabase Upgrade with AE DB Load Utility


Notes:

  • The DB directory of the installation CD can include several versions of SQL scripts and database files. They are required if you upgrade several versions. Be sure to use the correct version if <vers> is indicated in the document.
  • Automic strongly recommends you also read the notes for upgrading the AE database above.
  • Modifications that should be made are available in the special_rt.sql file. Also execute the new_mq.sql file. Search the UC_UPD.TXT file for the lines shown below and remove the comment "message" at the beginning.
  • Extract of the adjusted UC_UPD.TXT file:
    • process_sql_file new_mq.sql
    process_sql_file special_rt.sql
  • The special_rt.sql file converts the stored reports in the database. Depending on the number of report data records that are affected by the conversion it is important to ensure that there is sufficient memory and a transaction log of the appropriate size. Because the table is copied, it exists twice for a while which also prolongs the conversion process. Automic recommends reorganizing the reports before you execute the UC_UPD.TXT file in order to minimize the number of report data records.

Procedure:

1. Changing the database scheme and loading new initial data to the database

  • Server computer
    All server processes must be stopped. Pay special attention if server processes run on several computers. The following steps must only be processed when all server processes have been stopped.
  • Admin computer
    The directory containing the database files must be stored at the location that has been specified in the INI-file parameter INPUT of the utility AE DB Load. The folder that includes the BIN directory of the utilities is the default folder. 

    Windows example:

  • Utility in C:\AUTOMIC\UTILITY\BIN
  • Database files in C:\AUTOMIC\UTILITY\DB
  • Utilities - Windows:
    The files for the AE database are provided in IMAGE:DB. Copy the complete DB folder to the above directory
  • Utilities - UNIX:
    The database files are included in the archive db.tar.gz which is provided in the folder IMAGE:DB. To unpack the archive, use the following commands:
    gzip -d db.tar.gz bzw. gunzip db.tar.gz
    tar xvfo db.tar
    (Linux: tar -zxvf db.tar.gz)
    Copy the unpacked files to the defined directory.

  • Start the program AE DB Load to upgrade the database.Select the file <DB directory>\GENERAL\<vers>\UC_UPD.TXT
  • The current database version is identified and the database upgraded. As this happens, the database structure and data are changed. Objects of client 0000 are automatically replaced or amended.

2. Selecting the authentication method

  • Admin computer
    The utility AE.DB Load displays a mask in which you must select an authentication method.

    This mask is only displayed if the database is upgraded to a new Automation Engine version.

3. Installing partitioning with ILM (optional)

  • Admin computer
    A mask opens in which you can select the settings for partitioning with ILM. This step is optional.

     You cannot undo an AE database partitioning process.

ClosedConfigure and start the Java Work Process (JWP)

  • As of version 11.2 of the Automation Engine the function Export with references and the full text search in the ECC require a JWP.

General

The JWP is a component of the Automation Engine which is required for the following functions:

  • Single Sign-on (via KDC)
  • Adaptive ERT calculation
  • Function Export with references
  • Application Release Automation Integration
  • ECC Global Search

Files Provided

The JWP is provided in the same directory as all the other Automation Engine files.

File / Directory Description
ucsrvjp.jar File for starting the JWP.
/lib/ Directory with OSGI implementation and JDBC driver.
/plugins/com.automic.database.jar File for database access.
/plugins/com.automic.ara.jar Opens the ARA WebService.
/plugins/com.automic.ert.jar (Adaptive) ERT calculation.
/plugins/com.automic.kernel.jar JWP kernel.
/plugins/com.automic.network.jar TCP/IP connections.
/plugins/com.automic.sso.jar Single Sign-on.
/plugins/com.automic.util.logging.jar Logging / Trace.
/plugins/org.apache*
/plugins/org.eclipse*		 Additional OSGI bundles for console and services.

The directory /configuration/ is created automatically when the JWP is first started and contains the OSGI bundle's cache.

Installation

Unpack the files

In Windows, the JWP files are automatically copied from the SETUP.EXE program to the BIN directory. In UNIX, the files are located in the respective TAR archive.

Copy the provided "plugin" and "lib" directories into the BIN directory of the Automation Engine.

The subsequent installation steps depend on the database type used.

MS SQL Server

1)

Install JDBC driver

Download Microsoft JDBC Driver 4.0 for SQL servers.

After downloading, copy the file "sqljdbc4.jar" into the lib directory of the Automation Engine.

 

2)

Activate TCP/IP in the MS SQL server

Now check whether the MS SQL server instance used allows access via TCP/IP.

Open the SQL Server Configuration Manager and select Protocols for MSSQLSERVER under SQL Server Network Configuration. The item "TCP/IP" must be set to "Enabled" in the right-hand section.

 

3)

Determine the MS SQL server port

The default port of the MS SQL server port is 1433.

If you are not sure of the port of your MS SQL server instance, you can find this out from its log file. The message "Server is listening on [ 'any'<ipv4> port number]" should be found in the current log file, which contains the port.

 

4)

Modify the Automation Engine configuration file

The JWP uses the same configuration file (ucsrv.ini) as the other work processes of the Automation Engine system.

The database connection must be modified in the configuration file for the JWP. There are 2 different options for this:

1) DSN-less ODBC Connection

Please note that with this option, the same database connection string that is also used by all the other WPs in the Automation Engine system must be changed in the configuration file. When installing a JWP for an existing system, all WPs must be subsequently restarted.

A connection string is required in the [ODBC] section of the configuration file, the syntax of which does not require DSN. The server and database name must be specified directly in this case.

SQLDRIVERCONNECT=ODBCVAR=SNNNNNRN,Driver={SQL Server Native Client VERSION};Server=tcp:SRVNAME,PORT;Database=DBNAME;Uid=DBUSER;Pwd=DBPWD

  • VERSION- Version of SQL Server Native Client. Is displayed in the SQL Server Configuration Manager.
  • SRVNAME - Name of the database computer.
  • PORT - port of the MS SQL server instance.
  • DBNAME - Database name.
  • DBUSER - Database user.
  • DBPWD - Database password.

Example:

[ODBC]
SQLDRIVERCONNECT=ODBCVAR=SNNNNNRN,Driver={SQL Server Native Client 11.0};Server=tcp:dbsrv01,1433;Database=AEV10;Uid=user;Pwd=password

The entry should be on one line (no break).

 

2) Separate connection string for the JWP

With this option, a separate database connection string for the JWP is defined in the [JDBC] section.

Example:

[JDBC]
SQLDRIVERCONNECT=jdbc:sqlserver://dbsrv01;databaseName=AEV10

The name and password of the database user are used by the [ODBC] item.

The advantage of this method is that the connection string of the other WPs ([ODBC] section) does not need to be changed or restarted.

Oracle

1)

Install JDBC driver

Copy the JDBC driver "ojdbc6.jar" from the Oracle database client installation to the "lib" folder of the JWP.
The file is located here: ORACLE_HOME/jdbc/lib/ojdbc6.jar

 

2)

Configuring the database connection

There are 2 options:

1) Connection via OCI

Modification of the INI file "ucsrv.ini" is not necessary in this option. However, the JWP requires access to the Oracle database libraries in the same way as a WP. In UNIX, the environment variables LD_LIBRARY_PATH or SHLIB_PATH must therefore be selected accordingly, depending on the platform.

More information on installing the JDBC driver can be found in the JDBC installation instructions from Oracle.

 

2) Direct connection to the database

You can connect directly to the database using the Oracle JDBC Thin driver.

The [JDBC] section in the ucsrv.ini file must be configured accordingly. Example:

[JDBC]
SQLDRIVERCONNECT=jdbc:oracle:thin:@dbserver:1521/service_name

The name and password of the database user can be found in the [ODBC] item.

DB2

1)

Install JDBC driver

Copy the file "db2jcc4.jar" (JDBC driver) into the "lib" directory of the JWP.

This file is part of the DB2 client and is located in the sub-directory "SQLLIB/java".

2)

Configuring the database connection

Modification of the ucsrv.ini file is not necessary.

However, if required, the database connect string can be defined in the [JDBC] section of the INI file.

Example:

[JDBC]
SQLDRIVERCONNECT=jdbc:db2://server:<port>/database

The user name and password for database access can be found in the [ODBC] item.

Add certificates for SSL

In order to use SSL, the certificate(s) of the LDAP server must be available to the Java Work Process.
The JWP uses the default keystore file "cacerts" in the lib/security directory of the JRE.

Two options are available to add the certificates:

1 Add certificates with the keytool
  • Go to the jre\lib\security folder of the Java installation and import the certificate with the keytool command:

    keytool -keystore cacerts -importcert -alias ldapServer -file certficate.cer

  • When prompted to trust this certificate respond by typing "Y".

 

2 Add certificates via download

Another option to install the certificate is the command line parameter -installcert of the Java Work Process.

java -jar ucsrvjp.jar -installcert <host>:<sslport>

  • This assumes that the Java Work Process has write access to the cacerts file of the Java installation.
  • This command detects the path of cacerts, connects to the specified host and port and tries to create an SSL connection.

If a certificate is missing, the message "unable to find valid certification path to requested target" is printed and the missing certificate is downloaded and stored in the cacerts file.

Start the JWP

Use this kind of command to start the JWP via the command line:

java -Xmx512M -jar ucsrvjp.jar -IC:\temp\ucsrv.ini

The file "ucsrvjp.jar" is provided in the same directory as the other Automation Engine files. It is used exclusively to start the JWP.

The JWP can also be started via ServiceManager. 

java -Xmx512M -jar ucsrvjp.jar -svc%port% -IC:\temp\ucsrv.ini

The -svc parameter should be omitted when starting directly via the command line.

The parameter -I to specify the INI file is optional. If the parameter is missing, the JWP attempts to find the file "ucsrv.ini" in the current working directory (= directory in which the file "ucsrvjp.jar" is located).

ClosedStart the Automation Engine and clients

  • Cold-start the server processes when all installation and configuration step have successfully been completed. Do so in the INI file of the server processes by setting the parameter StartMode= to COLD. Now the processes can start.
  • All clients can be started from the System Overview of client 0000.

ClosedMonitor the AE system

  • Do not yet replace the agents. Older agent versions run smoothly with newer Automation Engine versions.
    In order to take advantage of new features to the full make sure to upgrade agents as well.
  •  Do not change anything in your processing and carefully monitor your AE system over an extended period of time. A few hours or days are not enough. It can take a while before problems occur, especially if they are the result of a particular constellation in your processing.

Closed4. Upgrade all other components

Done

System
available:

Work steps

ClosedInstall the Agents

  •  Do not remove or overwrite the installation directories of your agents. Back up the corresponding folder in order to make sure that you can quickly return to your old version.
  • The new agents must also be installed in a separate directory. An adequate monitoring period is essential. Automic recommends not replacing all agents by the new version. Replace one platform after the other, for example. First replace UNIX and only replace the next one when the agents have proven to run stably for some time.
  • As of version 9, the UNIX agent files will be supplied in lowercase letters. To ensure that jobs call the new Job Messenger, follow the steps below:
    1) Automic recommends: Correct the file name of the Job Messenger in the INI file when you upgrade the agent (variable UC_EX_JOB_MD).
    2) Important: When you install the new agent in the same directory as the old one, you must delete the old Job Messenger after the installation process.
    3) Instead of adjusting the INI file during the upgrading process, you can also create a link (with the old messenger names in uppercase letters) that points to the new messenger
    Example for Linux: ln -s ucxjli3m UCXJLI3M

ClosedInstall the remaining components

  •  Do not remove or overwrite the installation directories of the remaining components. Back up the corresponding folder in order to make sure that you can quickly return to your old version.
  • Now you can replace components such as the CallAPIs. Keep in mind to monitor the newly installed version for some time.

ClosedUse the new functions

  •  Monitor your upgraded AE system for a time. The upgrading process is complete if no problems occur.
  • Now you can upgrade your production system. Repeat the steps made when upgrading your test system. Upgrading a test system optimally prepared you for upgrading your production system.
  • Again read the Release Notes of the new Automation Engine version after having upgraded your productive system. They list all new functions. Use them and extend your processing. Automic Support will be pleased to help you with any problem that may occur.
  • Enjoy using your new Automation Engine version.