Resolution:
The following WireFormats and palette activities can be used with the adapter.
(1)WireFormat is ActiveEnterprise
  (a) A message sent using PublishToAdapter activity in BW is processed successfully.
  (b) A message sent using PublishRendezvous message is not processed.

(2)WireFormat is XMLFormat
  (a) A message sent using PublishToAdapter activity in BW is processed successfully.    
  (b) A message sent using PublishRendezvous message is not processed.

(3)WireFormat is Rendezvous
  (a) A message sent using PublishToAdapter activity in BW is NOT processed successfully.    
  (b) A message sent using PublishRendezvous message is NOT processed successfully.


The reason for 1(b) and 2(b) is:

When the wire format for the adapter is AE or XML, then the adapter successfully processes requests sent by AE palette in BW but not from RV palette, because for these wireformats, the adapter(an ActiveEnterprise product) expects additional AE control information(AE fields) in the incomfing message.

3(a) and 3(b) fail because when the WireFormat is Rendezvous, the message format expected is different.
Please refer to adapter documentation --> Chapter 7 --> Using the Request-Response Service --> Request-Response Mode for details.

Also, as confirmed by BW team(in SR#1-A6UM3Z) RV palette does not have such properties to add in any additional AE headers or other properties other than the Data . What ever we send through RV transport is RV Message and if sent via AE Adapter activities, it takes care of the AE headers for you so the receiving adapter can deserialize it just fine.

Note:
But JMS palette can be used to send AE messages by adding the AE fields in the JMSApplication Properties.

What is the behavior of adapter w.r.t different Wire Formats available with RV Transport?