A Comm Bridge running as a system service configured to target a NonStop server environment has special requirements not seen with other target server environments.
The Comm Bridge uses a third party product, HP RSC/MP, as the transport mechanism when communicating with NonStop target servers. When the Comm Bridge is configured to run as a system service the RSC/MP product must also be configured to run as a system service.
At the time of this writing the RSC/MP product contains two separate but dependent processes, RSC and Piccolo. For proper operation of the Comm Bridge as a system service these products must also be installed as system services. This can be accomplished through the RSC/MP products rscserv.exe command. (rscserv.exe –install).
For proper operation of the Comm Bridge to NonStop communications both the RSC and Piccolo system services must be running prior to a transaction being attempted. For more information, see the RSC/MP product documentation.
During normal operation transaction mapping data is down loaded from the NonStop host and stored in a local file within the Comm Bridge's host machines file system. If the Comm Bridge is operating as a system service then this mapping file will be located in:
%APPDATA%\CA\Gen xx\cfg\cb\RSCMP\<Path-Mon>\tirtmt.tbl
Where <Path-Mon> is the RSC/MP configured Pathway Monitor configuration setting.
The value of %APPDATA% is dependent upon the Windows User Id under which the Comm Bridge is executing. If the Comm Bridge service was installed without specifying a User Id, the default User Id is the Local System account. In this case %APPDATA% would equate to LocalService\AppData which would translate the above to a path similar to:
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\CA\Gen xx\cfg\cb\RSCMP\<Path-Mon>\tirtmt.tbl
Note: xx refers to the current release of CA Gen. For the current release number, see the Release Notes.
|
Copyright © 2013 CA.
All rights reserved.
|
|