Resolution:
Running TIB/MessageBroker in Engine mode is advantageous because less memory is required due to the fact that the MessageBroker GUI is not part of the running application.

Some of the disadvantages of running only in Engine mode are that you cannot change anything on the transform as it is running.

Also, the transform becomes harder to debug because you cannot see the transform or its state.

At the command line prompt use the following to start MessageBroker in Engine mode:

engine.bat for Windows NT.
engine.sh for Solaris
engine_hp.sh for HP-UX
then use the following command syntax:

engine (-local repo_file | -url repo_url)
-transformation &lttransformation_name1> -engine &ltengine_name1>
[-transformation &lttransformation_name2> -engine &ltengine_name2> ...]
-local repo_file

The repo_file is the location of the repository found locally on your system.

-url repo_url
The URL is the pathname of the location of the remote repository. For example, tibcr://MyMBInstance:subject=foo.bar:
service=7500:network=le0:daemon=tcp:target=7500:timeout=120
where subject is the subject to be used for repository discovery service. Also, network and daemon are TIB/Rendezvous parameters, and timeout is the time value in seconds for any TIB/Repository communication to be aborted.

-transformation &lttransformation1> &lttransformation2>
Name of the transform that you want the MessageBroker Engine to run

-engine &ltengine_name>
Name of the MessageBroker Engine that you want to run the transform on.

Please refer to the TIB/MessageBroker documentation for more detailed information.

How do I run MB 3.X in engine mode only and what are the advantages?

Product: TIBCO MessageBroker Version: 4.1, 3.2.1.5, 2.5.0 OS: All --------------------