Support Contact Information
Collected Questions and Answers
- Shutting down TCM cleanly
- Is there a good way to shutdown TCM cleanly?
To shut down a TCM gateway you can do either of the following;
- In the Webconsole, click the details link to the right of the gateway name. In the gateway details you
can then click on Shut down the gateway “GatewayName”.
- In TT_HOME/bin there is a killTCMServer script. You can run the command as follows ./killTCMServer –n GatewayName.
- What about shutting down the webconsole itself?
- In the TT_HOME/bin/ folder there is also a killMonitor script which will shutdown
the monitor process.
- When the monitor is started using the runMonitor script and another instance of
the monitor is running, is the existing process is killed by the script?
- Yes, the runMonitor script will kill an existing monitor process (if it is running)
before starting the new one.
- Editing a standard message
- I have a gateway with two FIX 4.3 connections. I want to change the format of the
logon message for one connection to add two tags and give them static values.
What do you recommend as the easiest way to implement this change?
- You can write a Validation Transformation Extension (VTE) which can populate these
fields in the logon, based on properties you configure on the connection.
Take a look at the sample ext_validation in TT_HOME/samples/ttCONNECT, which will give you an idea of how
the VTE should work.
I'll just add that when creating a VTE, it's good practice to put all static information into the xml
configuration file and pull that data in programmatically. That way you don't have to recompile when you
want to update/modify the static data.
- Scheduling connections
- JVM Settings
- Does the TCM5 User Guide explain how to configure JVM memory settings? I would like to check how much memory is being allocated to my custom router/gateway process, and possibly change the values.
- Take a look at the script in your TT_HOME/bin/ directory called “runTTConnect.bat” or “runTTConnect.sh”
You should see that the file mentions the environment variable, MEMFLAGS. The script checks to see if the variable is set. If not, it defaults the value to the following:
So you can either modify this in the script or actually define the variable in your environment.
Unfortunately, there’s no discussion of this process in the TCM documentation.
collected by Greg Chabala