1 Configuration of CTS connection (in Application system)

1.1 NW SP13: Via Confi gurati onAdapter (in Visual Admi ni strator)
Go to Visual Administrator Services Configuration Adapter. Choose Runtime tab and apps sap.com
tc~com.sap.tmw.clients~_ctsa_manager appcfg. In the corresponding property sheet the following values
are defined:
target.client: client of communication system (as defined in TMS for development system, via parameter
NON_ABAP_WBO_CLIENT)
target.system: SID of communication system (as defined in TMS for development system, via parameter
COMMUNICATION_SYSTEM)
target.url: host name for message server of communication system (i.e. fitting to value of target.system)
tms.system: SID of development system (as configured in TMS either as Non-ABAP System or as J ava
Stack).
Here development system named PS2 has been created in TMS, referring to PSU as communication system
(reachable via message server on machine pwdf2821) and using client 001 on PSU as representation (i.e.
defined as value in NON_ABAP_WBO_CLIENT in TMS configuration of PS2).
NOTE: With SP13 details of the user handling (which user is used to logon, via password or ticket exchange)
is defined by the application, i.e. the login data are handed over from the application to CTS.
1.2 NW SP14 or hi gher: Via RFC Destinati on (i n Visual Admini strator
or NWA [7.1 onl y])
Go to Visual Administrator Services Destinations Runtime tab Destinations - RFC
sap.com/com.sap.tc.di.CTSserver
- Please check the exact spelling of the RFC destination (hint: there is an error in the SP14 documen-
tation do not use CTSServer with a capital S for Server).
In 7.1 you can alternatively use NetWeaver Administrator Configuration Management Destinations
sap.com/com.sap.tc.di.CTSserver
Here again the development system refers to PSU as communication system (reachable via message server
on machine pwdf28212) and using client 001 on PSU as representation (i.e. defined as value in
NON_ABAP_WBO_CLIENT in TMS configuration of the development system).
NOTE: Since SP14 the SID of the development system is used for the name of the system in TMS. Also
since SP14 details of the user handling (which user is used to logon, via password or ticket exchange) is
defined by the settings of the RFC destination.
2 Anal ysis of log entries
2.1 Using diagtool (cf. note 1045019)
Deploy tool from note 1045019 and call http://<host>:<port>/diagtool.
- Select "All" in the Component field
- Add "com.sap.tc.di" in the Search pattern field
- Press "Go" and "Add All"
- change the "Set severity for selected locations to" "Error"
- uncheck the "Set severity for all other locations to" checkbox
- uncheck the "Collect traces from all locations" checkbox
Before proceeding prepare everything to retry the failing use-case (this helps keeping the log files small).
Then press the Start button, retry the failing use case, and immediately press the Stop button.
The next page will contain the possibility to show all traces, wherein you will find the exception stack trace.
2.2 Using NWA (NetWeaver Admini strator)
Go to NetWeaver Administrator System Management Monitoring Logs and Traces.
Select Show Predefined View - Default Trace as shown below.
Select the button Open Fi l t er .
Go to Filter by Content Choose Location from the listbox and enter com.sap.tc.di as value to filter.
Choose Appl y Fi l t er s.
The resulting list of entries will contain the entries on error level, wherein you will find the exception stack
trace (via record details).
2.3 Using LogVi ewer (i n Visual Admini strator)
Go to Visual Administrator Services Log Viewer. Choose Runtime tab and select defaultTrace.trc (usu-
ally below Cluster Server <SID>\J C<nn>\j2ee\clusterserverX\log).
Filter records by restricting search to com.sap.tc.di in column Location, cf. following screen shot:
The resulting list of entries will contain the entries on error level, wherein you will find the exception stack
trace (via double click).