If your project has JAR files for custom functions or third-party software, you must manually copy them to the runtime location. Copy them to a location on the classpath of the deployed application. The recommended location is the BE_HOME/lib/ext/tpcl directory. If you choose a location that is not in the classpath, then update the classpath in the TRA file to include the location.
3. The deployment unit that you configured to deploy on that machine in the site topology file deploys.
5. Verify the login details or provide them (see Host Settings for details).
6. Click OK. The engine or engines configured to deploy to that machine deploy.
To see if an engine or agent is deployed Hover the pointer over its name in the explorer panel. A tooltip shows if it is deployed or undeployed.
1. From the Cluster Explorer, select the engine you want to start, stop, pause, or resume. (You resume a paused engine.) Note that you can’t start an unpredefined engine.
2. Click the appropriate icon: Start, Stop, Pause, or ResumeSee Chapter 11, Hot Deployment for details on hot deployment. You can hot deploy to a running engine deployed by MM if the following are true:
• You have modified the TIBCO BusinessEvents Studio project and built the EAR file, following the limitations shown in Modifications Allowed in Hot Deployment.
• The deployed processing units that you want to hot deploy to were enabled for hot deployment before they were deployed (see Enabling Hot Deployment)To hot deploy in MM, replace the master EAR file with the updated one, and then deploy the engines again using MM Console. There is no need to restart the engines.
Copyright © TIBCO Software Inc. All Rights Reserved.