15 OpenScape Trace Manager Configuration File

When installing OpenScape Trace Manager (OSTM) server the option to use an XML configuration file is provided. install.xml can be used as the definition file for the OSTM installation.
The configuration file assumes that the OSTM application is installed on the C: drive and that the tracedata folder used to transfer and store the trace files is created on the D: drive. If this is not the case then the installation and configuration using install.xml file will not work.
install.xml creates an sftp user 'tracedata' with password 'Asd123!.' to allow traces to be transferred from all systems included in the solution (OSV, OSBs, SBCs, media server(s), UC server, etc.) to the OSTM server.
1.
Transfer OSV_CTraceConfig.sh to the OSV filesystem
2.
Login as srx user
3.
Start CLI as sysad user:
Replace /tmp with the folder that you copied the file to.
If OpenScape Voice is deployed as an integrated simplex, then the OSV_CTraceConfig.sh file activates continuous tracing on the integrated OSV.
If it is deployed as a duplex, then the OSV_CTraceConfig.sh file activates continuous tracing on both OSV nodes. The '24_7_extern' filter is used to collect OSV trace data and the trace is turned on indefinitely. Additionally, the OSV_CTraceConfig.sh file instructs OSV to use sftp user 'tracedata' with password 'Asd123!.' to transfer trace data to the OSV-TM server using sftp transfer mode.
/opt/siemens/common/conf for offboard installations
/enterprise/common/conf for onboard installations
Note: If Continuous Tracing is enabled for the solution, then WebCDC will include in the configuration file the data to enable continuous tracing on the OSBs and SBCs.
Verify that the sftp user
ID and password in the OSB and SBC config files correspond to the sftp user ID and password used on the OSTM server for file transfer.