Windows agent messenger no longer shows "Connected with agent ..." message
Article ID: 254471
Updated On:
Products
Issue/Introduction
The 12.0 messenger showed the following (specific message shows in bold)
Program 'UC4 Job Messenger' version '12.0.2+build.15' started
UCMDJP: *********************************************************************
UCMDJP: ** JOB 0319341229 (ProcID:0000002196) START AT 16.03.2022/18:08:10 **
UCMDJP: ** UTC TIME 16.03.2022/22:08:10 **
UCMDJP: *********************************************************************
Connected with agent 'AGENTNAME'
Program 'UC4 Job Messenger' version '12.0.2+build.720' terminated normally
After updating from 12.0 to 21.0, this is no longer the case. Now it shows the IP as seen below:
Program 'UC4 Job Messenger' version '21.0.4+build.15' started
UCMDJP: *********************************************************************
UCMDJP: ** JOB 0325614657 (ProcID:0000005576) START AT 25.10.2022/16:35:41 **
UCMDJP: ** USED: 0.000 CPU **
UCMDJP: *********************************************************************
Initiating connection to server '10.10.10.10:2301' using WebSocket URI: wss://10.10.10.10:2301/agent'.
Program 'UC4 Job Messenger' version '21.0.4+build.15' terminated normally
Disconnected from '10.10.10.10' (socket handle = '1').
Is it possible for you to set the SQL server name instead of the IP address in the report
Environment
Release : 12.1, 12.2, 12.3, 21.0
Resolution
This behavior as designed and is built into the agent messenger, UCXJWX6M.EXE. The change went into effect with version 12.1 in 2017. 12.1 through 12.3 didn't have anything about agent name or IP address when the messenger was called. The 12.0 messenger showed the agent name. There's no way to force the messenger to do this sort of thing as it is hardcoded and can be changed by Broadcom at any time since this information is meant for consumption by the Automic system.
There is a way to accomplish what you're trying to do which is to put the same line into a header. You may need to take this into account if the server name should be used instead of agent name at any point in the future. If you do need this, you will need to talk to your system admins about the correct command line commands to get this info. Please see below for how you can do this:
- Login to Client 0
- Create an include (JOBI) object called HEADER.WINDOWS.USER.START if it doesn't already exist
- Put something like the following into the process tab (I've put comments in to explain what's happening):
!Turn echo off so that the actual commands don't show up in standard out, just the results
@echo off
!Echo the desired lines
echo Connected with agent '&$agent#'
@Turn echo back on so that commands are shown in standard out
@echo on - Save the JOBI
Now you should be able to run the job and have the additional line:
Program 'UC4 Job Messenger' version '21.0.4+build.15' started
UCMDJP: *********************************************************************
UCMDJP: ** JOB 0001104011 (ProcID:0000007304) START AT 10.11.2022/13:09:36 **
UCMDJP: ** --------------------------------------------------------------- **
UCMDJP: ** USED: 0.000 CPU **
UCMDJP: *********************************************************************
Program 'UC4 Job Messenger' version '21.0.4+build.15' terminated normally
Disconnected from '127.0.0.1:21045' (socket handle = '1').
Connected with agent 'WIN01'
Feedback
