Administration Guide > Installation > New Installation > Installing Utilities (Windows)

Installing Utilities (Windows)

This document guides you through the new installation of the utilitiesUtilities support the execution of administrative tasks in an Automation Engine system (such as reorganizing and archiving the Automation Engine database). (Windows).

Supplied Files

The files for the utilities (Windows) are stored in the directory IMAGE:UTILITY\WINDOWS.

*G.EXE - Java loader for utility
*.EXE - Program for batch request
*.BAT - Batch file for utility

File name

Description

UCYBARBR.EXE

AE Archive Browser (searches the archive files)

UCYBCHNG.EXE

AE DB ChangeUtility for changing transport case exports. (edits exported data)

UCYBDBRR.EXE

AE DB Revision ReportUtility unloading modification reports from the Automation Engine database. Modification reports include detailed information about object modifications and accesses. (creates revision reports)

UCYBDBCC.JAR

AE DB Client CopyUtility for copying and deleting clients (copies and deletes clients)

UCYBDBAR.JAR

AE DB ArchiveThe utility AE DB Archive can be used to remove the increasing amounts of data from the Automation Engine database. (archives the databaseA database is an organized collection of data including relevant data structures.)

UCYBDBLD.JAR

AE DB LoadThe utility DB Load can be used to load data into the Automation Engine database. (loads the database)

UCYBDBRE.JAR

AE DB ReorgData can be reorganized by using the utility DB Reorg. It marks data records with a deletion flag in accordance with the settings that have been specified. (reorganizes the database)

UCYBDBUN.JAR

AE DB UnloadUtility for unloading the Automation Engine database. (unloads the database)

UCYBDBRT.EXE AE DB Reporting ToolThe utility AE DB Reporting Tool can be used to query tasks in your Automation Engine system. (creates objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task queries)

UCYBREPG.EXE (requires 32bit Java),
UCYBREPG.JAR

AE DB Reporting Tool (graphical interface for creating the query files)

UCYBLGMX.EXE

AE.LogMix (combines log and trace files)

UC.MSL

Message library

UC4LAF.JAR

Archive for layout files

*.INI

Initialization files for the utilities

CALLHTMLHELP.DLL, CBLRTSS.DLL, UCCACHE.DLL, UCDBUP.DLL, UCSBEPM.DLL, UCUCLI.DLL, UCUDB32.DLL, UCUOCI.DLL, UCUODBC.DLL, UCYBCLICPY.DLL, UCYDBARCHIVE.DLL, UCYDBREORG.DLL, UCYBDBLD.DLL, UCYBDBUN.DLL, UCZU01.DLL, ZU00132.DLL, ZUXML1.DLL

Libraries of the utilities

COMDLG32.OCX, MSCOMCTL.OCX, RICHTX32.OCX

ActiveX Controls

SETUP.EXE

Installation program

Note that as of Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. version 8.00A, the file names of all utilities have been changed to lowercase letters.

Procedure

1. Installing the Java Runtime Environment (JRE)

This installation step can be ignored if the required version of JRE is already installed.

java -version

Ensure that the order of the indicated directories is correct in the settings of %PATH% or $PATH if several JRE or Java SDK Versions have been installed on the computer. The Java Runtime Environment that is found first in the listing of directories is applied.

2.

Installing the Microsoft Visual C++ 2010 Re-distributable Package

This installation step can be ignored if the packageA Package is an instance (a version, a revision, a tag, …) of your application and defines the content which you want to deploy. Here you decide, if you want to deploy the entire application or just a few specified components. is already available in the required version. Refer to the Control Panel -> Add or Remove Programs to see if the package is installed, and if so, which version.

3.

Installing the utilities

4. Adjusting the INI files and setting up the system environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications.
5. Calling the DLL from a freely selected path (optional)

For example:

cmd="javaw" -Djava.library.path=..\libraries -jar -cp .;.\UC4LAF.jar UCYBDBAr.jar

6. Starting the utilities

See also:

Configuring the Debugger for potential program failures

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH