Description:
=========
In BusinessEvents 3.x, Exception com.tibco.wfc.util.ServletRuntimeException: com.tibco.be.deployment.tsm. is thrown when trying to deploy BusinessEvents (BE) Application from Administrator.

Exception com.tibco.wfc.util.ServletRuntimeException: com.tibco.be.deployment.tsm. is thrown when trying to deploy BusinessEvents Application from Administrator.
         java.lang.ClassNotFoundException: com.tibco.be.deployment.tsm.TSMBEEngineDeployActions
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at com.tibco.pof.admindomain.impl.ContainerSoftwareImpl.getActionsPlugIn(ContainerSoftwareImpl.java:258)
        at com.tibco.administrator.consoles.deploymentconfiguration.DeployUndeployDialog.a(DeployUndeployDialog.java:477)
        at com.tibco.administrator.consoles.deploymentconfiguration.DeployUndeployDialog.if(DeployUndeployDialog.java:449)


Environment:
==========
TIBCO BusinessEvents 3.x
TIBCO Designer


Symptoms:
========
BE Engine throws the following exception.

java.lang.ClassNotFoundException: com.tibco.be.deployment.tsm.TSMBEEngineDeployActions
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
         at com.tibco.pof.admindomain.impl.ContainerSoftwareImpl.getActionsPlugIn(ContainerSoftwareImpl.java:258)
         at com.tibco.administrator.consoles.deploymentconfiguration.DeployUndeployDialog.a(DeployUndeployDialog.java:477)
         at com.tibco.administrator.consoles.deploymentconfiguration.DeployUndeployDialog.if(DeployUndeployDialog.java:449)
        ... 41 more
        

Resolution
=======

Solution 1). Check if the .vpd files have been manually modified. If yes, the incorrect modification may lead to this exception. If this is the case BE will have to be reinstalled.

Solution 2). Restart the Hawk Agent and Administrator.

Solution 3). 

1). The class files from be-admin.jar will be uploaded to the appropriate directories by the Hawk agent. Some times this may not fully complete. In these cases restart the Admin and Hawk agent and wait for a while before deploying the BE projects.

2). The class files are usually uploaded in the following directory:

<rootdir>\tibco\administrator\domain\<domainname>\tomcat\server\webapps\administrator-<domainname>-beadminplugin-2.0.0\WEB-INF\classes\com\tibco\be\deployment\administrator

Check this directory to see for the presence of the .class  files.

3). The other way to verify if BE is recognized by Administrator is to check the Admin GUI.  Open the TIBCO Administrator, login with user name/pwd and then navigate to the  
Application Management -> all service instances -> <service instance name> -> Plug ins tab. You should see an entry for be-admin plugin. If not, try adding this jar (be-admin.jar) file manually with the options given in this screen.


Solution 4). 

1). Check the Hawk agent for the domain and also the tibhawkhma as to what user.

2). Check if the user has write permission to the directory:  /opt/mesh/app/tibco directory

3). Change the permissions on this directory so that all users can write to it (777) and then restart the domain Hawk agent and tibhawkhma.

Solution 5). Completely reinstall BE.