For troubleshooting, the RFA logging can be enabled by setting the configuration parameters mountTrace to true (for connection information) and ipcTraceFlags to 7 (for in-bound and out-bound messages), and the log file named RFA_RSSL.log (or RFA_SSL.log) will be generated automatically. The log messages show which server the application connects to as well as which service the application makes item requests for.

The example log messages below show the application connected to server 192.168.27.46 and the item request was for the service #2114.

Jun 07, 2016 5:53:50 PM com.reuters.ipc.TraceLogger traceData
FINER: 
Thread: myNS::mySession Session EventQueueGroup
Connection 0
RSSL Transport attempt to connect to 192.168.27.46:14002

Jun 07, 2016 5:53:50 PM com.reuters.ipc.TraceLogger traceData
FINER: 
Thread: myNS::mySession Session EventQueueGroup
Connection 0
RSSL Transport connected to 192.168.27.46:14002

...

Jun 07, 2016 5:53:50 PM com.reuters.ipc.TraceLogger traceData
FINER: 
Thread: myNS::mySession Session EventQueueGroup
Connection 0
RSSL Client Message
SEND: 22
---DATA TRACE---
MESSAGE
	Msg Type: MsgType.REQUEST
	Msg Model Type: MARKET_PRICE
	Indication Flags: REFRESH
	Hint Flags: HAS_ATTRIB_INFO | HAS_QOS_REQ
	Stream Id: 3
	QosReq: (RT, TbT)
	AttribInfo
		ServiceId: 2114
		Name: JPY=
		NameType: 1 (RIC)
	Payload: None

You may request a "source directory" which enumerates all the available services. The RFA/Java package includes various examples, omm/postingConsumer/DirectoryClient.java may be the most convenient starter for exporting a simple list of services.