TIBCO Administrator Tutorial: Deployed Application Management through TIBCO Administrator

TIBCO Administrator Tutorial: Deployed Application Management through TIBCO Administrator

Bytechieswiki

  NOV 7, 2019   Application Management, Tibco Administrator, TIBCO Administrator Tutorial

This tutorial is about the different application management options which are available in the TIBCO Administrator GUI.

Let’s start from the Service Instances. Service instances are the par files deployed in each server. To view the same in the admin GUI, go to Application management >  [Application Name] > Service Instances. This will show you basic details about the current status of the instance, Deployed server name and the version of Business Works. By selecting the checkbox next to the instance name we can Start, Stop, Restart or kill a service instance from the administrator.

Service Instances

Now click on the Service instance to get more information specific for the Service instances. The general tab has information like the total uptime of the service and process id. The statistics section shows the information about the total number of created process, Completed Process etc.

Aborted Processes – This shows the number of processes aborted due to some failure while processing data
Average Execution (ms) – This shows the average execution time for a single transaction
Current Processes – This shows the number of active processes.

Service Instance Overview

To see the Active Processes, click on the BW Processes tab and select the Active Process from the list box. This will show the details of each transaction.

Transaction Details

Process ID – This denotes a subprocess id or can say Job IDs.
Status – Status can be Active, Idle or Dead.  Here Idle means the job is not making any progress and the Dead means the job stopped its execution for some reason.
Start Time – This shows the start time of that particular transaction or job
Duration (ms) – Total time of execution in milliseconds
Current Activity – Current activity which is processing the data
Starter – Name of the starter process for this particular transaction or job. This is helpful when we have multiple started process and calls the same subprocess to process the data.

How to Enable/Disable process starters temporarily from TIBCO Administrator?

Select Process Starters from the drop-down list to see the list of starter process. We can disable or enable the starter process temporarily from here. When the service instance gets restarted we will lose this setting.

Process Starters

Select Process Definitions from the drop-down list to see get an overview execution details of each process.

Process DefinitionsActivity execution overview

By default, it will show in the order of execution. If any activity has any failure, the number of failures will be shown in the Errors column and status as an ERROR.

Click on Tracing to see the log details of the service instance. By default, the logs have only basic details.

Service Instances tracing

How to configure Debug level tracing from Tibco Administrator GUI?

if you want to enable debug level logs, click on Configure Tracing button and mark the Check Boxes for All Activities and All Starters. Once saved it will start logs activity-wise logs. Please note that this will get disables if the integration is getting restarted. Also, this won’t log the input and output data to the logs.  we can’t do it from Administrator. To log input/output data to the log we need to add the below properties to the Application tra file and need to restart the service instances.

bw.engine.showInput=true
bw.engine.showOutput=true

Now got to Method Tabs where we have 50+ methods available which we can use to get the different statistical information about the Service instance and configure different settings. I will explain a few of them here.

Methods in Tibco Administrator

1.  ConfigureActivityTracing : This method is used to enable tracing for specific activities. This is helpful when we debug a complex integration which has many processes. We can specify the activity name in the Text box and click invoke. Please note that the activity name and other details should match exactly. even if we gave it wrong this won’t throw any error.
2. ConfigureAllTracing : Same as like the option available in the logs tab.
   These trace setting will get override when the integration restarted. So if you are looking for a permanent tracing option we need to add some values in application tra file in the below format.

    

   To trace a specific process and all activities, set

   Trace.Task.<ProcessName>.process.*=true

   To trace a process located in a folder, set

   Trace.Task.<folder>/<processName>.process.*=true

   To trace a specific activity, say RVPublisher, set

   Trace.Task.<folder>/<processName>.process.RVPublisher=true

   To trace an activity located inside a group , set

   Trace.Task.<folder>/<processName>.process.<GroupName>/<ActivityName>=true

3. GetActivities : Invoke this method to get an overview of each activity.

    

   Service Instances Execution Overview

Hope this information helps you. Please let us know you feedback and questions in the comment section below.