Sample Outputs

Below are few sample outputs that may be seen while doing a Notification Transport Server Configuration update.

  • Validation Failures

    A wrong group_name or invalid connection parameters in the qin_data.xml results in a failure. For example, in the sample output shown below, the Notification Transport Server Configuration update has failed as the "test-admin" group_name is invalid.

    Command: ant -f qin_build.xml setNotifyConfig 

    C:\tibco_data_Admin\data_Qin2\admin\amxadmin\samples>ant -f qin_build.xml setNotifyConfig
Buildfile: C:\tibco_data_Admin\data_Qin2\admin\amxadmin\samples\qin_build.xml

-test.targets.order:
     [echo] Invoked targets: setNotifyConfig
     [echo] Specified Ant targets are in order hence proceeding with Notification Transport Update.

setNotifyConfig:
[AMXAdminTask] 05 Oct 2016 22:12:42  INFO - Initializing JSSE's crypto provider class com.sun.net.ssl.internal.ssl.Provider in default mode
[AMXAdminTask] 05 Oct 2016 22:12:42  INFO - Connecting to AMX Admin server at 'http://Win2k8r2M21:8120' as user 'root'.
[AMXAdminTask] 05 Oct 2016 22:12:42  INFO - Executing action 'editStatusTransport' for 1 objects from data file 'C:\tibco_data_Admin\data_Qin2\admin\amxadmin\samples\qin_data.xml'
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Current Notification Transport:
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Group Name: amxadmin
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - User Name: admin
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Password: ******
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Recovery Attempt Delay: 500
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Recovery Timer Timeout: 15000
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Server URL: tcp://Win2k8r2M21:7222
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - enableSSL: false
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Notification Transport will be updated with below details:
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Group Name: test-admin
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - User Name: admin
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Password: ******
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Recovery Attempt Delay: 600
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Recovery Timer Timeout: 6000
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - Server URL: tcp://10.197.198.148:7222
[AMXAdminTask] 05 Oct 2016 22:12:44  INFO - enableSSL: false
[AMXAdminTask] 05 Oct 2016 22:12:47  INFO - Test Connection to Server URL tcp://10.197.198.148:7222 was successful.
[AMXAdminTask] 05 Oct 2016 22:12:47 ERROR - Exiting Notification Transport Update as the provided Group Name "test-admin" is invalid.

BUILD FAILED
C:\tibco_data_Admin\data_Qin2\admin\amxadmin\samples\qin_build.xml:42: TIBCO-AMX-CLI-000042: Failed on error : 'Exiting Notification Transport Update as the provided Group Name "test-admin" is invalid.'

Total time: 9 seconds

C:\tibco_data_Admin\data_Qin2\admin\amxadmin\samples>
  • Using 'verifyHostsEligibility' along with 'setNotifyConfig'

    The TIBCO ActiveMatrix Administrator CLI validates the parameters provided in the qin_data.xml and prints the eligibility of the various Hosts in the Enterprise. After this, the TIBCO ActiveMatrix Administrator CLI exits.The actual Notification Transport Server Configuration update is not performed. For example, in the sample output shown below, the update is carried out for the eligible Host RemoteHost_1, but not on ineligible Hosts RemoteHost_2, RemoteHost_3 and RemoteHost_4.

    Command: ant -f qin_build.xml verfiyHostsEligibility setNotifyConfig 

    E:\tibco_data_Admin\admin\testamxadmin\samples>ant -f qin_build.xml verfiyHostsEligibility setNotifyConfig
Buildfile: E:\tibco_data_Admin\admin\testamxadmin\samples\qin_build.xml
-test.targets.order:
     [echo] Invoked targets: verfiyHostsEligibility,setNotifyConfig
     [echo] Specified Ant targets are in order hence proceeding with Qin (StatusTransport) parameters update.
verfiyHostsEligibility:
-test.targets.order:
setNotifyConfig:
[AMXAdminTask] 07 Sep 2016 00:35:19  INFO - Initializing JSSE's crypto provider class com.sun.net.ssl.internal.ssl.Provider in default mode
[AMXAdminTask] 07 Sep 2016 00:35:19  INFO - Connecting to AMX Admin server at 'http://amx-server-18:8080' as user 'root'
[AMXAdminTask] 07 Sep 2016 00:35:20  INFO - Executing action 'editStatusTransport' for 1 objects from data file 'E:\tibco_data_Admin\admin\testamxadmin\samples\qin_data.xml'
...
...
...
[AMXAdminTask] 07 Sep 2016 00:35:23  INFO - TIBCO-AMX-HPA-050281: This action is tracked in logs by operationID: 'root_QinUpdate_20160907003522'
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - TIBCO-AMX-HPA-050264: Notification Transport will be updated on below hosts:
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - ---------------------------------------------------------
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - RemoteHost_1
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - ---------------------------------------------------------
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - TIBCO-AMX-HPA-050265: Notification Transport will NOT be updated on below hosts. This could be because the host itself OR the nodes on the host OR the system application "com.tibco.amx.platform" is not RUNNING.This action is tracked in the logs by operationID: 'root_QinUpdate_20160907003522'
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - ---------------------------------------------------------
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - RemoteHost_2
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - RemoteHost_3
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - RemoteHost_4
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - ---------------------------------------------------------
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - Printing status cache in SystemNode log.
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - Status cache has been printed in SystemNode log.
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - Found 3 TIBCOHosts that will be excluded from Qin Update as they are not eligible for the update.
[AMXAdminTask] If Qin Update is run, it will exit as a result. To proceed with the update for host(s) that are eligible, please run the Ant script with the "force" option as follows: "ant -f qin_build.xml force setNotifyConfig"
[AMXAdminTask] 07 Sep 2016 00:35:25  INFO - Action finished at 9/7/16 12:35 AM in 3.635 seconds
BUILD SUCCESSFUL
Total time: 10 seconds
E:\tibco_data_Admin\admin\testamxadmin\samples>