Resolution:
For the C++ TIBCO ActiveMatrix Adapter for SAP, there are three types of components. One is the stop subscriber. Two are the various adapter services that were configured by the user using the IDoc or RFC/BAPI schema. Third are the internal components that are used by the adapter for initialization, etc.

1). In the case of the stop subscriber, the transport is automatically done by the adapter based on the adapter services configured by the user. If the user configured the adapter services as RV then it would be RV. If JMS then the "Stopsubscriber" would be JMS.

2). For the adapter services, it is straightforward since the user selects the transport when configuring the service.

3). The internal components used by the adapter rely on RV sessions. If you see the components available through the Hawk agent, there are components available at runtime but those components are not visible at Design time in TIBCO Designer. This is intentional and those components and corresponding sessions cannot be removed.

If switching the transport to JMS, there should be no issue using JMS for the adapter services as well as the "StopSubscriber". But in the case of the internal components maintained by the adapter, those rely on RV only.