How to setup multiple asg-engines running different configurations?
Article ID: KB0085019
Updated On:
| Products | Versions |
|---|---|
| TIBCO API Exchange | - |
| Not Applicable | - |
Description
Description:
This article provides inputs on setting up multiple asg-engines running different configurations on the same machine. The steps for setting FT/HA configuration are available in the documentation.
Resolution
Here are some inputs on running multiple configurations on the same machine:
Make copies of the asg.properties and provide them using the command line option:
"--p <full path of asg_copy.properties>"
Running separate CDD files using the "-c" parameter is the recommended approach. Update each CDD to make sure they point to a different Log Folder (Configured under <log-configs> element in the CDD).
You can also specify the engine name using "-n <name>" command-line parameter.
If you have changes in the asg-engine.tra file, it can be specified using the command-line parameter "--propFile <tra_file>'.
Instead of Apache you could use the built-in Facade HTTP Channel and specify separate ports in each properties file.
A sample command would be:
asg-engine -p <asg_copy.properties_full_path> -n <engine_name> -c <cdd_file> -a <project_name>
It is not recommended to run different configurations in the same cluster.
Make copies of the asg.properties and provide them using the command line option:
"--p <full path of asg_copy.properties>"
Running separate CDD files using the "-c" parameter is the recommended approach. Update each CDD to make sure they point to a different Log Folder (Configured under <log-configs> element in the CDD).
You can also specify the engine name using "-n <name>" command-line parameter.
If you have changes in the asg-engine.tra file, it can be specified using the command-line parameter "--propFile <tra_file>'.
Instead of Apache you could use the built-in Facade HTTP Channel and specify separate ports in each properties file.
A sample command would be:
asg-engine -p <asg_copy.properties_full_path> -n <engine_name> -c <cdd_file> -a <project_name>
It is not recommended to run different configurations in the same cluster.
It should not matter if Manager and Gateway are part of a different cluster as the communication between them is over HTTP.
Issue/Introduction
How to setup multiple asg-engines running different configurations?
Feedback
Yes
No
Powered by
