When you configure the APIX Gateway to use a RV transport, the following errors may be observed:

- Caused by: java.lang.RuntimeException: Action failed even after 10 attempts. Giving up.

- Caused by: java.lang.Exception: Invalid destination uri [/Common/Channel/AS/TransactionReports] specified. Event will not be sent.

This can be resolved by disabling the AS channels in asg_core.cdd because the Gateway transport needs to be either AS or RV. As observed, the  APIX Engine tries to send messages to the AS channels but eventually fails with error messages.

This article describes a known issue when trying to configure the APIX Gateway to use a RV transport instead of AS.

All Supported Operating Systems

Add the error reporting AS channels to the deactivate list in the CDD property "be.channel.deactivate".

An example follows.

 ;property-group comment="" name="Channel";
 ;property name="be.channel.deactivate" value="/DefaultImplementation/Channels/SouthboundEsb0Channel, .....;list of deactivate channels ; ..... ,/Common/Channel/AS/TransactionReports, .... "/;

If you have enabled reporting on CL, then configure what type of transport is to be used between ASG_Core and CL. Valid values are "AS", "RV" and "JMS". The default is "AS".

Option 1). If you have not enabled CL reporting then turn it off by setting reportingEnabled=false in asg.properties file. This will solve this issue.
>>>>>>
# Turn on or off reporting to CL
tibco.clientVar.ASG/Logging/reportingEnabled=false
tibco.clientVar.ASG/Logging/errorReportingEnabled=false
>>>>>>

Option 2). If you have enabled reporting to CL (say reportingEnabled=true), then change the transport value as desired (RV) in the asg.properties file. Use the following  property.
>>>>>>
tibco.clientVar.ASG/Logging/transport=RV
>>>>>>