Windows installation of secondary RMI does extract required files

book

Article ID: 211436

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

When installing a secondary RMI in a Windows environment, a number of files do not get extracted. After the installation the following steps need to be followed for the secondary RMI's installation to be complete.

1. From the installation media's V9 directory copy the following to the corresponding secondary RMI's bin or c directory:

V9\AWNFILES.zip\bin\sqloper.bat
V9\LB_nt.zip\c\awcomm.exe
V9\LB_nt.zip\c\nativecalls.dll
V9\LB_nt.zip\c\ntkill.exe
V9\LB_nt.zip\c\perl.exe
V9\LB_nt.zip\c\perl56.dll
V9\LB_nt.zip\c\ps.exe
V9\LB_nt.zip\c\watchworx.exe

Additionally, the following is behavior is observed.

Starting AWW service will start the Java, watchworx, and awcomm processes. However, stopping AWW service will only stop the watchworx process. The Java process needs to be manually killed. While the awcomm process does not stop, this is an expected behavior.

 

Environment

Release : 9.3.4

Component : APPLICATIONS MANAGER

Resolution

Fixed in version 9.3.5