Resolution:
Description:
=========
When clicking the “BW Processes” in Administrator  GUI, it shows one of the following errors and does not display the BW process stats:

1). Error Message: java.lang.ClassCastException: com.tibco.ix.uac.monitor.plugin.EngineMonitorImpl
    at com.tibco.bw.administrator.consoles.containers.ActiveBusinessProcessesTracingTab.init(ActiveBusinessProcessesTracingTab.java:52)

Or

2).  Error Message:java.lang.ClassCastException: com.tibco.uac.monitor.server.ServiceContainerBindingMonitorImpl at com.tibco.bw.administrator.consoles.containers.ActiveBusinessProcessesTracingTab.init(ActiveBusinessProcessesTracingTab.java:52)


Environment:
==========
Operating Systems: All
TIBCO Administrator: 5.6 and Higher
TIBCO Runtime Agent: 5.6 and Higher
TIBCO ActiveMatrix BusinessWorks (BW) All

Symptoms:
=========

1).  When clicking the “BW Processes” in Administrator GUI, it shows “java.lang.ClassCastException: com.tibco.ix.uac.monitor.plugin.EngineMonitorImpl” or java.lang.ClassCastException: com.tibco.uac.monitor.server.ServiceContainerBindingMonitorImpl

2). You cannot see BW process stats.

3). You will see the following  error stack in Administrator.log:

a).     java.lang.ClassCastException: com.tibco.ix.uac.monitor.plugin.EngineMonitorImpl
        at com.tibco.bw.administrator.consoles.containers.ActiveBusinessProcessesTracingTab.init(ActiveBusinessProcessesTracingTab.java:54)
        at com.tibco.bw.administrator.consoles.containers.EngineDetailProcessesTab.init(EngineDetailProcessesTab.java:58)
  
Or

b).      java.lang.ClassCastException: com.tibco.uac.monitor.server.ServiceContainerBindingMonitorImpl
        at com.tibco.bw.administrator.consoles.containers.ActiveBusinessProcessesTracingTab.init(ActiveBusinessProcessesTracingTab.java:52)
        at com.tibco.bw.administrator.consoles.containers.EngineDetailProcessesTab.init(EngineDetailProcessesTab.java:58)



Cause:
======

The below mentioned defect has been logged to investigate the root cause:

ADM-5275  
"java.lang.ClassCastException" is seen in Administrator log when the service instance is selected for the deployed BW Application in EMS based domain
 

Increase the implementation version in BWAdmin.war file  to force the TIBCO Administrator to re-load the correct BW plugin.

Perform the following steps to reload the correct BW plugin:
1) Log in Administrator GUI, click All Service Instances, then TIBCO Administrator, then click tab Plug-Ins, check the "Implementation-Version"  of "TIBCO BusinessWorks".
2). Unzip $(tibco_home)/bw/5.x/admin-plugins/BWAdmin.war  
3). Increase the Implementation-Version value in the MANIFEST.MF file and make it bigger than the one you see in step 1). For example, if the Implementation-Version shown in Administrator GUI is "5.14.0.11", please increase Implementation-Version in MANIFEST.MF to "5.14.0.12". 
4). Rebuild the war file (which actually is a .zip file. You can rebuild the .war file with any compress tools that can generate .zip files.).
5). In the Administrator GUI, click All Service Instance -> &ltmachine name-&gtTIBCO Administrator -> Plug-Ins tab, click the Add button and upload the .war file you just created.
6). Back to BW processes and check the information again. 
NOTE: Please find attached "How to Increment Impl-Version.pdf" , document shows different options to Increment Implementation Version in war file.

Please note ADM-5275 was fixed in Administrator 5.10.0. Please contact TIBCO Support if you have further questions or using Administrator 5.10.0 or higher. 

TIBCO Business Works Application'sProcesses Tabis missing, shows error or does not display the process stats from Admin GUI.