Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

RFC (Remote Function Call)

The data in BW are converted to UTF-8(*1) in the ABAP Client and sent from a Gateway in the ABAP system to the TREXRfcserver. Serialization/Deserialization are done in the TREXRfcServer.  Performance for indexing with RFC is slower than ICM due to many codepage conversions in the TREX ABAP API. If there is an error during a process which uses RFC, its advisable to check the gatewayserver traces in transaction SMGW (in each application servers from transaction SM51) and the RfcServer trace files.     

(*1) ABAP uses UTF-16 and BWA uses UTF-8. 

This method is used for the following cases:

SAP_BASIS700 - SAP_BASIS702

  • Creating a RFC destination
  • Creating index
  • Prepare optimize call
  • Commit optimize call
  • Deleting an index
  • Indexing call for F/D/X/Y tables
  • Aggregation call (query execution)

Special case

  • Indexing call for S and temp indexes (when Solution (B) in note 1091088 is implemented.)

SAP_BASIS730 - SAP_BASIS740

  • Creating a RFC destination
  • Prepare optimize call
  • Commit optimize call


BXML (Binary XML)

Communication method itself is RFC but the data formation is different from the way used above. Here 'BXML' is used to distinguish from RFC used in BW700. BXML is a SAP specific format for storing XML files in binary form. The data conversion to BXML is done within the ABAP Kernel and this leads to performance benefits when storing and transporting. The ABAP system communicates with the TREXRfcServer using this method.

This method is used for the following cases:

SAP_BASIS700 - SAP_BASIS702

  • Creating a BIA index

SAP_BASIS730 - SAP_BASIS740

  • Creating an index
  • Creating a BIA index, F4 (name '*_f4') index
  • Deleting an index

Special case:

  • Query Execution (when 'RFC with bXML' for 'Communication method for aggregation' is selected)

ICM (Internet Communication Manager)

The data in BW are converted to XML in the ABAP Client and sent to the TREXIndexserver. The communication is done between the BW System and the BWA landscape using the protocol HTTP. Using ICM helps to enhance the communication especially for huge date volumes. If there is an error, please check the trace in ICM via transaction SMICM and the TREXIndexserver trace files. If an error occurred during a background job, you should also check the trace in the work process (developer-trace) where the job was running.

This method is used for the following cases:

SAP_BASIS700 - SAP_BASIS702

  • Indexing call for S table and temp indexes

Special case:

  • Indexing call for F/D/ X/Y tables (when Solution (B) in the note 1091088 is implemented)
  • Query execution (when 'Use RFC for aggregation call' is deselected in TA:TREXADMIN)

SAP_BASIS730 - SAP_BASIS740

  • Indexing for BW tables, VirtualProvider, Query as InfoProvider

  • Query exectuion

ICM with HTTPS is NOT supported.

TCM (TREX Communication Method)

 TCM was formerly known as DBSL and this method is used for ByD. TCM is slightly faster than ICM and does not do any implicit commits, but can only be chosen if the MaxDB client is installed. Please see the note 1753874 for prerequisites for TCM.

Therefore, for BWA scenario, option 'TCM' for Communication method in TREXADMIN should not be selected.

 

 

  • No labels