Entering content frame

Background documentation System Architecture Locate the document in its SAP Library structure

Generally, the mobile client stays disconnected from the CRM Server for long intervals of time. Usually once a day, the sales representative establishes a connection to the CRM Server. The client and server then exchange the necessary data. Once the transmission is finished, the sales representative can disconnect the mobile client from the CRM Server.

This graphic is explained in the accompanying text

When the sales representative uses the mobile client, the application layer changes business data. These changes are reported to the BDoc Layer which is responsible for making them persistent. For changes which have to be communicated to the CRM Server, the BDoc Layer additionally creates BDoc messages and calls the qRFC agent with the BDoc messages as parameters. This call is actually a queued remote function call (qRFC) for the inbound message adapter in the CRM Server. The remote function call is not performed directly. Instead, it is recorded in the outbound queue of the mobile client. The changes to business data and the creation of the call record are committed together to ensure that the local database of the client and the data sent to the CRM Server remain consistent. After the sales representative has started ConnTrans and specified whether to receive and / or transmit BDoc messages, ConnTrans establishes a connection to the CRM Server via dial-up networking or through the local area network. It calls the message transfer service client to take BDoc messages (which actually are recorded RFCs) out of the client message queue and transfers them to the CRM Server. The data is transported via DCOM and is received by the message transfer service server on the Communication Station.

The message transfer service server forwards the incoming BDoc messages to the CRM Server using qRFC. A qRFC is a transactional RFC with guaranteed sequence. The qRFC agent puts the incoming calls from the message transfer service server into the inbound queues. Every mobile client has its own inbound queue. The scheduler triggers the execution of the queued RFCs. These calls activate the inbound message adapter, which imports the BDoc message contained in the call and starts a flow for processing the BDoc message by activating the flow control.

The outbound message adapter exports BDoc messages to the outbound queues for the mobile clients, i.e. it initiates qRFCs with the mobile clients as destinations. Every mobile client has its own outbound queue on the CRM Server. When the mobile client connects to the CRM Server, the message transfer service client requests the queued calls and stores them in the client inbound queue. The mobile client retrieves the incoming RFCs from the client inbound queue and processes them the next time it is started.

 Leaving content frame