Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 Deploying and Managing Engines with MM : Deploying Engines with MM

Deploying Engines with MM
You can deploy engines using MM Console or using the command-line utility, MM-tools.
Before Deployment — Copy Custom Function and Third-Party Jars
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. See Updating Classpath, Environment Variables, Path, and Copying JAR Files.
Deploying Cluster Engines in MM Console
Deploy the engines configured to run on a predefined machine node as follows.
1.
2.
3.
4.
The deployment unit that you configured to deploy on that machine in the site topology file deploys.
5.
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.
Deployment Time  Deployment time information is saved to a file located under BE_HOME/mm/deployed, and the last deployment time is displays in the UI.
Hot Deployment
See Chapter 9, Hot Deployment for details on hot deployment. You can hot deploy to a running engine deployed by MM if the following are true:
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
Copyright © TIBCO Software Inc. All Rights Reserved