32-Bit Workload Automation 5 for Windows on 64-Bit Windows Systems

Transcription

1 32-Bit Workload Automation 5 for Windows on 64-Bit Windows Systems Overview 64-bit Windows Systems Modifying the Working Folder for Universal Server Components Applications Installed in the Windows System Folder Example 1 Example 2 Identifying 32- and 64-bit Workload Automation 5 Installations Overview The information on this page applies only to 32-bit Workload Automation 5 packages installed on 64-bit Windows systems. A native 64-bit Workload Automation 5 for Windows package, which was made available starting with the release, requires no special handling on 64-bit Windows systems. 64-bit Windows Systems All Workload Automation 5 components have been tested and verified on the 64-bit editions of the following Windows systems: Windows Server 2003 SP1 and higher Windows XP SP3 Windows Vista Windows Server 2008 Windows 7 Windows Server 2008 R2 This page describes some modifications that may need to be made to the default installation options to ensure that the installed Workload Automation 5 function correctly. Modifying the Working Folder for Universal Server Components On 64-bit Windows editions, the default installation folder for 32-bit applications is C:\Program Files (x86). The default installation folder for 32-bit Windows applications developed by Stonebranch is C:\Program Files (x86)\universal. The Workload Automation 5 installation package should have no problems installing its applications to this directory. Supported Stonebranch releases prior to 5.1.0, installed on 64-bit editions of Windows prior to XP SP2 or Server 2003 SP1, may receive this error - 'C:\Program' is not recognized as an internal or external command, operable program or batch file - under the following circumstances: Universal Command Manager is run using the -script option. Universal Event Monitor Server invokes an event handler that executes a script. Note Stonebranch releases starting with are only supported on Windows versions where the above error is not expected to occur. The error above is a result of the way that scripts are prepared for execution and the way that the Windows command shell interpreter reads a quoted string containing special characters (that is, & < > ( ^ ). Universal Command and Universal Event Monitor prepare scripts for execution by writing the script statements to a temporary.bat file in the application's working directory. A command line statement containing that working directory's path is then constructed to execute the.bat file. By default, this path includes the Program Files (x86) directory. Because the path includes one of the special characters listed above, the Windows command shell interpreter incorrectly parses the path, which results in the error above.

2 To resolve this issue, it is necessary to change the value (or location) of the Universal Command Server and/or Universal Event Monitor Server working directory. Either of the following changes can be made: If short path names are permitted on your system, use the dir /x command from the command prompt to find the short name of the Program Files (x86) directory (for example, Progra~2). Use this value as part of the working directory's path name. Change the working directory to a location outside of the default installation path (for example, C:\Universal). This new location can contain spaces, but it cannot contain any of the special characters listed above. The changes can be made either of two ways: 1. During installation. 2. Any time after installation via the Universal Configuration Manager, on the Component Definitions page for Universal Broker.

3 Applications Installed in the Windows System Folder The 32-bit Workload Automation 5 package installs several command-line applications in the Windows system folder. The default system folder for 32-bit applications installed on 64-bit Windows editions is the %SystemRoot%\SysWOW64 directory (for example, C:\Windows\SysWOW64). The following table identifies the affected Workload Automation 5 applications. File Name Description ucert.exe Universal Certificate ucmd.exe Universal Command Manager ucopy.exe Universal Copy uctl.exe Universal Control Manager udm.exe Universal Data Mover Manager ueld.exe Universal Event Log Dump Utility uem.exe Universal Event Monitor Manager

4 uemload.exe Universal Event Monitor Load Utility uencrypt.exe Universal Encrypt Utility umet.exe Universal Message Translator uquery.exe Universal Query urc.exe Universal Return Code Utility These applications can be executed using either the: 32-bit command shell (%SystemRoot%\SysWOW64\cmd.exe) Default 64-bit command shell (%SystemRoot%\System32\cmd.exe). By default, the %SystemRoot%\SysWOW64 directory is not part of the system path. Therefore, to execute the above command line applications using the 32-bit command shell, either: Directory must be added to the PATH environment variable. Complete path to the application and/or the 32-bit command shell must be specified. Example 1 To execute UCOPY in the default 64-bit command shell, issue the following command: %SystemRoot%\SysWOW64\ucopy Example 2 To execute UCOPY within the 32-bit command shell, use the following: %SystemRoot%\SysWOW64\cmd.exe /C %SystemRoot%\SysWOW64\ucopy Identifying 32- and 64-bit Workload Automation 5 Installations To help identify whether a 32- or 64-bit Workload Automation 5 installation exists on your system, look for the (x64) indicator in the package name or file version information. If it is present, a 64-bit version of Workload Automation for Windows package is installed. If it is missing, the 32-bit version of the Workload Automation for Windows package is installed. For example, the screen shots below show 32- and 64-bit Workload Automation for Windows installs as they appear in Programs and Features on a Windows Server system. 32-bit Workload Automation Install

5 64-bit Workload Automation Install (with x64 label) The (x64) label also appears in a component s version information, which is obtained by executing the component with the v command line option. For example, a 64-bit Universal Command Manager displays version information similar to that shown below when the v option is passed to ucmd.exe: C:\Users\Administrator>ucmd -v ucmd Level 0 Release Build 100 (x64) 11/22/11 17:24:49 xps Level 0 Build /22/11 17:18:02 (c) Copyright Stonebranch, Inc. All rights reserved.

6 The 32-bit version of Universal Command Manager displays the same version information, but the (x64) label is not shown.