Deploying the Application

Deploying the Application
Prev	Chapter 3. Deployment	Next

Complete these steps to deploy the fraud detection application.

Run the deploy tool (deploy.jar) to deploy a TIBCO BusinessEvents® Extreme application into a JVM. The command line to do this is:
```
java - jar <installation path>/deploy.jar hostname=<host name> \
     adminport=<node administration port> \
     username=<administrator name> \
     password=<administrator password> \
     <path to EAR> \
     descriptor=<path to CDD> \
     processingunit=<processing unit name> \
```
where:
- installation path - Specifies the TIBCO BusinessEvents® Extreme installation path (TIBCO_HOME/be-x/<bex-version>/sdk).
- hostname - Specifies the machine name on which the node is running. Defaults to localhost.
- adminport - Node administration port. Displayed when node is started.
- username - Administrator user name.
- password - Administrator password.
- path to EAR - Location of the TIBCO BusinessEvents® Extreme Enterprise Application Archive being deployed.
- descriptor path to CDD - The path to the Cluster Deployment Descriptor (CDD) for the application being deployed
- processingunit - Optional name of processing unit if the default processing unit is not used.
Information on all of the deployment tool parameters are documented in the TIBCO BusinessEvents® Extreme Java Developer's Guide.


Information on all of the deployment tool parameters are documented in the TIBCO BusinessEvents® Extreme Java Developer's Guide.

Example 3.3, “Deploying the application” shows the output when deploying the FraudDetection application. The output has been edited for space.

Example 3.3. Deploying the application

java -jar deploy.jar hostname=kabira-server.local adminport=2001 username=guest password=guest FraudDetection.ear descriptor=fd.cdd 
DEBUG: Connecting to [kabira-server.local:2001] ...
INFO: Deploying TIBCO BusinesEvents Extreme(R) Application [FraudDetection.ear]
INFO: deploy.jar version: [TIBCO BusinessEvents(R) Extreme 1.1.0 (build 120608)] starting at [Sat Jun 16 06:54:16 PDT 2012]
INFO: JVM remote debugger agent running on [kabira-server.local:47566] ...
INFO: node version: [TIBCO BusinessEvents(R) Extreme 1.1.0 (build 120608)]
INFO: Starting application [com.tibco.cep.container.standalone.BEMain] ...
INFO: Component [com.tibco.cep.container.standalone.BEMain] started on JVM [com_tibco_cep_container_standalone_BEMain3].
Listening for transport dt_socket at address: 47566
INFO: JMX Management Service started at:
	kabira-server:2099
	172.16.208.139:2099
	service:jmx:rmi:///jndi/rmi://kabira-server:2099/jmxrmi
Using property file: be-engine.tra

****************************************************************************
	TIBCO BusinessEvents 5.1.0.115 (2012-05-24)
	Using arguments :-c deploy/resources/deploy-1339854856165/fd.cdd deploy/resources/deploy-1339854856165/FraudDetection.ear 
	Copyright 2004-2012 Cloud Software Group, Inc. All rights reserved.
	
****************************************************************************
2012 Jun 16 06:54:30:946 GMT -7 kabira-server Info [main] - [container.standalone] 
****************************************************************************
	TIBCO BusinessEvents 5.1.0.115 (2012-05-24)
	Using arguments :-c deploy/resources/deploy-1339854856165/fd.cdd deploy/resources/deploy-1339854856165/FraudDetection.ear 
	Copyright 2004-2012 Cloud Software Group, Inc. All rights reserved.
	
****************************************************************************

 ...

2012 Jun 16 06:54:51:368 GMT -7 kabira-server Info [main] - [runtime.service] [inference-class] Starting AgentTimeManager for session: inference-class
2012 Jun 16 06:54:51:422 GMT -7 kabira-server Info [main] - [runtime.service] Agent inference-class-0: Starting Channels
2012 Jun 16 06:54:51:427 GMT -7 kabira-server Info [main] - [driver.http] Started Channel [/Channels/HTTP]
2012 Jun 16 06:54:51:428 GMT -7 kabira-server Info [main] - [runtime.service] Agent inference-class-0: Activating Event Subscriber
2012 Jun 16 06:54:51:442 GMT -7 kabira-server Info [main] - [runtime.service] Agent inference-class - 0: Activated
2012 Jun 16 06:54:51:444 GMT -7 kabira-server Info [main] - [runtime.service] Started [DefaultAgentManager]
2012 Jun 16 06:54:51:449 GMT -7 kabira-server Info [AgentMgr.Thread.1] - [runtime.service] 
Currently known [inference-class] agents = 1
   Member: ac10d08b-c356, Agent name: inference-class, Agent id: 0, Agent priority: 10, Status: INITIALIZED

2012 Jun 16 06:54:51:455 GMT -7 kabira-server Info [AgentMgr.Thread.1] - [runtime.service] 
Currently known [inference-class] agents = 1
   Member: ac10d08b-c356, Agent name: inference-class, Agent id: 0, Agent priority: 10, Status: PREPARETOACTIVATE

2012 Jun 16 06:54:51:459 GMT -7 kabira-server Info [AgentMgr.Thread.1] - [runtime.service] 
Currently known [inference-class] agents = 1
   Member: ac10d08b-c356, Agent name: inference-class, Agent id: 0, Agent priority: 10, Status: ACTIVATED

2012 Jun 16 06:54:51:481 GMT -7 kabira-server Info [main] - [studio.core] Hot Deployment disabled
2012 Jun 16 06:54:51:587 GMT -7 kabira-server Info [main] - [runtime.service] Registering all BE-Engine level Group MBeans...
2012 Jun 16 06:54:51:591 GMT -7 kabira-server Info [main] - [runtime.service] All BE-Engine level Group MBeans SUCCESSFULLY registered
2012 Jun 16 06:54:51:591 GMT -7 kabira-server Info [main] - [runtime.session] BE Engine kabira-server started
2012 Jun 16 06:54:53:366 GMT -7 kabira-server Info [HTTP-Channel-Startup] - [driver.http] Channel server for HTTP Channel[Port:8108] starting
2012 Jun 16 06:54:57:530 GMT -7 kabira-server Info [HTTP-Channel-Startup] - [driver.http] Channel server for HTTP Channel[Port:8108] successfully started

Prev	Up	Next
Starting Nodes	Home	Sending Events