Using ROBOTBATCHSETTING.EXE to configure probes
This Robotbatchsetting.exe tool is integrated with NEP solution on your NMC server. The default path is :
C:\Program Files (x86)\ip-label\Newtest\ClientModules\Exe\
For an NEP V2.2.x, you will first need to define the following registry keys to use this tool :
How to use this tool
Please note that you will need to execute this tool in "Run as administrator" mode
You may find the utilities of this tool by using the following command:
RobotBatchSetting.exe /?
1. To define a secondary server for probes
In the following code :
SecondaryServer$: the key for a secondary server. "$" should be a digital value starting from 0. For a first SecondaryServer, "$" should be 0 which gives SecondaryServer0
XXX-XXXXXX: the company key of the secondary server
YYY-YYY-YYY-YYY: the software key of the secondary server
STCPIP:<ServerName1>: Replace <ServerName1> by IP address or server name of the secondary server. Remove "STCPIP" if you are using standard TCPIP protocol
port: connection port to the secondary server
-do: provide the real action. Without this argument, only the command syntax will be checked.
-update: provide an immediate update notification to the selected robot
-restart: force a robot reboot to the selected robot
RobotBatchSetting.exe -robot <robot_name> -set [NEWTEST_PROTOCOL]SecondaryServer1=XXX-XXXXXX,YYY-YYY-YYY-YYY,STCPIP:<ServerName1>,<port>,,,,,-1,-1 -update -do
RobotBatchSetting.exe -robot <robot_name> –swap <server_name> –update –restart –do
RobotBatchSetting.exe -robot <robot_name> -set [NEWTEST_PROTOCOL]SecondaryServer1 -update -do
To select all existing robots, replace <robot_name> by *.
RobotBatchSetting.exe -robot *
Here are two examples :
c:\Program Files (x86)\ip-label\Newtest\ClientModules\Exe>ROBOTBATCHSETTING.EXE
-robot nwt100 -set [NEWTEST_PROTOCOL]SecondaryServer1
08:47:34.458 START LOG: ROBOTBATCHSETTING-7.6.0 R1 PID: 5176
08:47:34.458 LOADED MODULE: ROBOTBATCHSETTING-7.6.0 R1
Robot bactch setting utilities 7.6.0 R1
In D:\NewtestData\ClientModules\NewtestBridge\Probes\
[Not] remove 'D:\NewtestData\ClientModules\NewtestBridge\Probes\NWT100\NEWTEST.INI' [NEWTEST_PROTOCOL]SecondaryServer1='200-004390,220-000-000-002,STCPIP:ServerName1,48181,,,,TUIMIVTQITISIRIXIPTNTOTWJXGQ,-1,-1'
c:\Program Files (x86)\ip-label\Newtest\ClientModules\Exe>ROBOTBATCHSETTING.EXE
-robot nwt100 -swap BIWPNEP000
08:48:21.227 START LOG: ROBOTBATCHSETTING-7.6.0 R1 PID: 5812
08:48:21.227 LOADED MODULE: ROBOTBATCHSETTING-7.6.0 R1
Robot bactch setting utilities 7.6.0 R1
In D:\NewtestData\ClientModules\NewtestBridge\Probes\
[Not] set primary '200-004390,220-000-000-001,STCPIP:ServerName1,8181,,,,NROCQJJRIAHXPAFLQUPBFMODGXGM,-1,-1' -> '200-004390,300-000-000-001,STCPIP:ServerName2,47100,,,,NVPPEYPJMAASAPBFHJDUCRBDRXML,-1,-1'
[Not] set secondary '200-004390,300-000-000-001,STCPIP:ServerName2,47100,,,,NVPPEYPJMAASAPBFHJDUCRBDRXML,-1,-1' -> '200-004390,220-000-000-001,STCPIP:ServerName1,48181,,,,NROCQJJRIAHXPAFLQUPBFMODGXGM,-1,-1' [2]
2. To add an extra key
In order to add an extra key to all Newtest.ini files of all existing probes, you may use the following code :
RobotBatchSetting.exe -robot * -set [SECTION]KEY=VALUE -do
Here is an example of adding the NO_PCID option to all Newtest.ini files :
RobotBatchSetting.exe -robot * -set [SECTION]KEY=VALUE -update -do
3. Remotely install a fix patch
You may use the following command to install fix patch from NMC server to one or several of your robots.
RobotBatchSetting.exe -robot <Robot_Name> -patch <File_path> -setup -reboot -do
The patch will be installed after the next reboot.
If you wish to apply the patch immediately, you may add "-update" :
RobotBatchSetting.exe -robot <Robot_Name> -patch <File_path> -setup -reboot -update -do
Replace <Robot_Name> by * could apply patch to all robots.
Comments