Oh, your test machines (e.g. machine1) is specifying option "MACHINE
1722W7.Fekete.com" on the STAX EXECUTE request to indicate that the xml
file to be executed resides on the STAX service machine (instead of on the
machine that is submitting the STAX EXECUTE request) so that explains why
the STAX service log Start entries show "Machine: 1722W7.Fekete.com"
instead of the host name of machine1 because the "Machine:" value in the
logged Start message is the machine where the xml file to be executed
resides.
Information about the machine that originated this request is not logged
in the STAX service log, or anywhere else. It is provided to the STAX job
in variable STAXJobSourceMachine as I explained previously so you could
have your STAX jobs log this in the STAX Job User Log for each job (or
log it whereever you liked). But, this data is not currently logged by
the STAX service. You could request a new feature to have the STAX
service log information about the machine that submitted each STAX EXECUTE
request via http://staf.sourceforge.net by selecting "Request New
Feature" from the navigation panel on the left.
STAF has access to what machine originated each request so you can enable
STAF tracing to log trace information about STAX service requests. For
example, you could enable STAF tracing as follows on your STAX service
machine (e.g. 1722W7.Fekete.com):
STAF local TRACE DISABLE ALL SERVICES
STAF local TRACE ENABLE SERVICE STAX
STAF local TRACE ENABLE TRACEPOINTS "ServiceRequest RemoteRequests"
STAF local TRACE SET DESTINATION TO FILE C:\temp\stafproc.trc
Or tracing could be set within the STAF.cfg file using TRACE configuration
lines instead of dynamically using the TRACE service.
Then the STAF trace file (e.g. C:\temp\stafproc.trc or whatever you set
the trace file name to in the above command) will contain information
about every STAX service request submitted (not just EXECUTE requests
submitted to the STAX service but all requests submitted to the STAX
service). For example, if machine machine1.Fekete.com submitted a STAX
EXECUTE request to your STAX service machine, a trace message would be
written to the STAF trace file such as the following where the value for
the "Client:" would contain the machine that originated the request.
C:\>type C:\temp\stafproc.trc
20140107-12:09:45;16116;00000001;STAX Service Request - Client:
ssl://machine1.F
ekete.com@6550, Handle: 1216, Process: STAF/Client, Request: EXECUTE FILE
D:\Dis
tributedTesting\SilkTestDistribution\RunFromMediaFolder_Harmony.xml
MACHINE 1722
W7.Fekete.com JOBNAME HarmonyRegressionTestMediaFolder FUNCTION main ARGS
['Harm
ony', '%runVersion%'] SCRIPT PRODUCT='Harmony' SCRIPT VERSION='0.0.0.0'
SCRIPT B
UILD='MainBuild' SCRIPT BRANCHVER='Main' SCRIPT
TESTHOST=1722W7.Fekete.com' CLEA
RLOGS ENABLED
However, note that trace information for every request submitted to the
STAX service will be logged, not just trace information for STAX EXECUTE
requests. Also, no information about the STAX Job ID is logged because
the job has not begun execution yet so a STAX Job ID has not been created
yet.
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
From: "Zhu, Cindy" <cindy....@ihs.com>
To: Sharon Lucas/Austin/IBM@IBMUS,
Cc: "staf-users@lists.sourceforge.net"
<staf-users@lists.sourceforge.net>
Date: 01/07/2014 10:40 AM
Subject: RE: [staf-users] Machine sending the STAF command
Hi Sharon,
Attached is the architecture of our company’s automation system. Machine
1a and Machine 1b will send the requests to start the STAX jobs on Machine
3a and Machine 3b.
I tried the query you suggested and the query always returned this
“Machine: 1722W7.Fekete.com”, which was not what I wanted.
What I really need is to know what machine (Machine 1a or Machine 1b)
sends that STAF command to start the STAX job.
Thank you very much.
Cindy
From: Sharon Lucas [mailto:luc...@us.ibm.com]
Sent: January-06-14 3:33 PM
To: Zhu, Cindy
Cc: staf-users@lists.sourceforge.net
Subject: RE: [staf-users] Machine sending the STAF command
Hi Cindy,
This information is provided in the STAX Service Log (which is STAF log
file -- e.g. written by the STAF LOG service). See section
"Listing/Querying STAX Service Log" in the STAX User's Guide at
http://staf.sourceforge.net/current/STAX/staxug.html#Listing/Querying%20STAX%20Service%20Logs
for more information about querying the STAX service log. It describes
this log as follows:
STAX service log - This log contains messages generated by the STAX
Service for all jobs. This log contains a start and stop message for each
STAX Job. The job start message includes additional information about the
job such as job ID, XML file name, machine name, starting function, job
name, and arguments passed to the starting function.
For example, to query a STAX service log on your local STAX service
machine and just show the "Start" level messages logged since the last
time STAFProc was started on the STAX service machine, you could use the
following STAF LOG QUERY request (assuming STAX is the registered name
for the STAX service):
C:\>STAF local LOG QUERY MACHINE {STAF/Config/MachineNickname} LOGNAME
STAX_Service LEVELMASK Start FROM {STAF/Config/StartupTime}
Response
--------
Date-Time Level Message
----------------- -----
-------------------------------------------------------
20140106-16:21:34 Start JobID: 1, File: c:/stax/delay.xml, Machine:
local://loc
al, Function: , Args: , JobName: Delay Test
20140106-16:21:57 Start JobID: 2, File: C:/stax/prodTest.xml, Machine:
tcp://cl
ient1.company.com@6500, Function: , Args: ,
JobName: <N
/A>
20140106-16:24:01 Start JobID: 3, File: C:/stax/prodTest.xml, Machine:
tcp://cl
ient2.company.com@6500, Function: , Args: ,
JobName: <N
/A>
So you could parse each "Start" message to obtain the endpoint of the
machine that submitted the STAX EXECUTE request (e.g. the value between
"Machine: " and "," in the message).
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
From: "Zhu, Cindy" <cindy....@ihs.com>
To: Sharon Lucas/Austin/IBM@IBMUS,
Cc: "staf-users@lists.sourceforge.net" <
staf-users@lists.sourceforge.net>
Date: 01/06/2014 03:24 PM
Subject: RE: [staf-users] Machine sending the STAF command
Hi Sharon,
I guess what I want to know is where is the STAF log file to find out
information (e.g. what machines send requests), not a STAX job to log the
information.
Sorry for the confusion.
Thanks,
Cindy
From: Sharon Lucas [mailto:luc...@us.ibm.com]
Sent: January-03-14 2:57 PM
To: Zhu, Cindy
Cc: staf-users@lists.sourceforge.net
Subject: Re: [staf-users] Machine sending the STAF command
So you want a STAX job to be able to determine the machine that submitted
a STAX EXECUTE request? This is provided in a STAX Python variable named
STAXJobSourceMachine (contains the endpoint of the machine submitting the
EXECUTE request).
Note that section "STAX Variables" in the STAX User's Guide at
http://staf.sourceforge.net/current/STAX/staxug.html#Header_StaxVariables
describes the variables (such as STAXJobSourceMachine) that are set in
Python during Job Execution by the STAX service and that can be referenced
by your STAX job.
For example, if you wanted your STAX job to log this information:
<log message="1">
'Machine endpoint that submitted the STAX EXECUTE request is: %s' %
(STAXJobSourceMachine)
</log>
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
From: "Zhu, Cindy" <cindy....@ihs.com>
To: "staf-users@lists.sourceforge.net" <
staf-users@lists.sourceforge.net>,
Date: 12/20/2013 10:49 AM
Subject: [staf-users] Machine sending the STAF command
Hi,
I have multiple machines send STAF command to one testing machine to
launch STAX jobs.
How can I find out the machine name that sent the STAF command?
Thanks,
Cindy
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users [attachment
"HarmonyAutomationArchitecture.docx" deleted by Sharon Lucas/Austin/IBM]
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
