Connecting mobile clients to SAP CRM has a mobile scenario includes an OLTP R/3 system, the CRM Server, the Communication Station,and several other Cell Clients.. The CRM Server consists of an R/three system, the place the core software components (like HR,LO, FI) have been changed by the CRM on-line parts and the Middle ware functionality. It also features a database server that comprises the consolidated database (CDB).The Communication Station hosts the Microsoft Transaction Service (MTS) and the DCOM Component Connector, which controls the access of the sales/service staff by approach of their frontends (laptop computer, workstation, PC). In addition, it might also include the Administration Console. . Crucial for connection purposes on the mobile consumer are the transaction layer, the connection handler and the switch service.
CRM Objects as Communication Interface
SAP components (written in ABAP or ABAP Objects) and . COM components (written in VB, Java, C++, Cobol, Delphi, etc.) n Part Object Mannequin (COM) is an open architecture for cross-platform improvement of client/server applications based mostly on object-oriented programming. The purposes and programs might even be provided by completely different vendors. This expertise supports improvement in numerous programming languages. With the COM technology, clients have access to an object via interfaces carried out on that object. COM is language-independent, so that any language that produces ActiveX parts also can produce COM applications.
Distributed COM (DCOM) allows COM software program components to communicate immediately over a community, e.g. between a mobile consumer and the CRM Middle ware. The DCOM Part Connector (DCOM CC) runtime setting gives a general interface to call the distant function modules used on this context.The Microsoft Transaction Server (MTS) serves as a transaction processor over distributed systems. It effectively helps connection pooling and will increase network safety by offering an authentication system.As soon as the connection between the consumer and the object on the server aspect is established (through MTS and DCOM CC), the various strategies of an object might be called.
The Transaction Layer on the cellular consumer handles the access to the native database. At the similar time (i.e. in the same COMMIT cycle), it stores the information in a local queue in a format that can then be transferred to the server.When the user decides to begin out the communication course of by invoking the ConnTrans program, the Connection Manager on the consumer aspect establishes the connection to the server and then activates the Message Transfer Service , which transfers the info to the server by calling the Switch Proxy on the Communication Station. Other switch companies might be included within the connection session, so that the consumer has to initiate the communication only once.
DCOM is used for client/server communication. The DCOM Element Connector, an SAP Middle ware product, acts as the interface between the Microsoft and ABAP environments by making RFC function calls available as COM components.The DCOM Component Connector translates the DCOM operate calls from the Message Switch Service into RFC function calls to the Inbound Adapter on the CRM Server. The incoming DCOM operate calls are not queued or saved on the Communication Station.On the client aspect the Connection Supervisor triggers the Transaction Layer to read the inbound queue when new data arrived.There are two principal causes to run the Microsoft Transaction Server (MTS) on the Communication Station: higher safety (authentication) and better performance (connection pooling).
Communication Layers
So really communication between the CRM Server and the mobile shoppers is carried out through three totally different layers:
The MTS is totally built-in into the Home windows NT safety mechanism. It presents two sorts of safety management:
DCOM Connector
After having put in the DCOM Connector, the subsequent step is to create locations that define a set of parameters required to join to an R/3 system. You may create or modify these destinations.This entails the following duties:
Usually it is doable to configure the DCOM CC to use NT person credentials for accessing R/3. In
this case no user or password have to be specified. 
Mobile Client
On the networking level it is sufficient to provide a TCP/IP connection to the Communication Station. When installing the Cellular Shopper application, you're asked whether or not to change replication on or off. f the replication is switched off, the installation routine provides a pre-stuffed database for the client application. On this case, it's not potential to exchange data with the CRM Middle ware. For those who enable replication, you might be requested for the IP tackle of the communication station. The QmtCheck.exe program may be used to test the DCOM connection between the cellular clients and the Communication Station. It might be launched on the mobile shoppers by approach of the Shopper Console. The settings for the DCOM connection might be specified utilizing this system dcomcnfg.exe.
For the safe first communication, an RFC connection between the shopper and the CRMMiddle ware needs to be established once. This RFC connection is configured and used by the program ASiteID (it could be known as through the Shopper Console), which requires that the customers and the mobile clients are already identified on the CRM Server. The user and sites administration on the CRM Middle ware as well because the safe first communication might be mentioned in the Unit Replication & Realignment Overview.
Roles in SAP CRMSAP CRM Organizational Model
People Centric SAP CRM IntroductionCRM Technical Infrastructure
CRM Interaction Center Agent Perform
CRM Technical Architecture
REUSE COMPONENTS IN ABAP DAY 10
MANAGING ABAP PROJECT OBJECTS DAY 11
CRM Objects as Communication Interface
SAP components (written in ABAP or ABAP Objects) and . COM components (written in VB, Java, C++, Cobol, Delphi, etc.) n Part Object Mannequin (COM) is an open architecture for cross-platform improvement of client/server applications based mostly on object-oriented programming. The purposes and programs might even be provided by completely different vendors. This expertise supports improvement in numerous programming languages. With the COM technology, clients have access to an object via interfaces carried out on that object. COM is language-independent, so that any language that produces ActiveX parts also can produce COM applications.
Distributed COM (DCOM) allows COM software program components to communicate immediately over a community, e.g. between a mobile consumer and the CRM Middle ware. The DCOM Part Connector (DCOM CC) runtime setting gives a general interface to call the distant function modules used on this context.The Microsoft Transaction Server (MTS) serves as a transaction processor over distributed systems. It effectively helps connection pooling and will increase network safety by offering an authentication system.As soon as the connection between the consumer and the object on the server aspect is established (through MTS and DCOM CC), the various strategies of an object might be called.
The Transaction Layer on the cellular consumer handles the access to the native database. At the similar time (i.e. in the same COMMIT cycle), it stores the information in a local queue in a format that can then be transferred to the server.When the user decides to begin out the communication course of by invoking the ConnTrans program, the Connection Manager on the consumer aspect establishes the connection to the server and then activates the Message Transfer Service , which transfers the info to the server by calling the Switch Proxy on the Communication Station. Other switch companies might be included within the connection session, so that the consumer has to initiate the communication only once.
DCOM is used for client/server communication. The DCOM Element Connector, an SAP Middle ware product, acts as the interface between the Microsoft and ABAP environments by making RFC function calls available as COM components.The DCOM Component Connector translates the DCOM operate calls from the Message Switch Service into RFC function calls to the Inbound Adapter on the CRM Server. The incoming DCOM operate calls are not queued or saved on the Communication Station.On the client aspect the Connection Supervisor triggers the Transaction Layer to read the inbound queue when new data arrived.There are two principal causes to run the Microsoft Transaction Server (MTS) on the Communication Station: higher safety (authentication) and better performance (connection pooling).
Communication Layers
So really communication between the CRM Server and the mobile shoppers is carried out through three totally different layers:
- The TCP/IP layer for the community connection. Alternatively UDP/IP or HTTP tunneling may be used because the community connection between the mobile shopper and the Communication Station.
- The qRFC/DCOM layer that allows communication between the ABAP and Microsoft environments.
- The BDoc messages layer for the precise message transfer.
- The MTS safety settings should be specified. This specifies the authentication stage and information encryption between the mobile consumer and the Communication Station.
- An RFC destination has to be defined for the DCOM Element Connector on the Communication Station.
- The communication between the Communication Station and the Middle ware might be tested using the program QmtCheck.
The MTS is totally built-in into the Home windows NT safety mechanism. It presents two sorts of safety management:
- declarative safety (controls access to the business objects and denies access to customers who do not have the required privileges)
- programmatic safety (permits the enterprise object itself to decide what the person is allowed to do; it has more detailed safety checks than the declarative safety)
- Begin the MTS Explorer from the menu:
- Programs -> Home windows NT 4.zero Choice Pack -> Microsoft Transaction Server -> Transaction Server Explorer.
- On the appropriate hand side of the window there could be an icon with a number of hats which denotes a role. Several users may be assigned to every role. The definition of roles is simply legitimate for a specific package and for elements contained on this package. A task can contain one or more Home windows NT customers/groups.
- A package deal is a form of container for numerous parts which usually serve a associated purpose.Several components can belong to at least one package. Throughout utilization of a component, the associated icon is rotating.
- On the correct facet of the window you see the accessible roles on this package deal (Person and Administrator on this instance). Different customers are assigned to 1 role.
- Roles can be defined on the package, element (proven in the slide) or interface stage, relying on the granularity of security required.
DCOM Connector
After having put in the DCOM Connector, the subsequent step is to create locations that define a set of parameters required to join to an R/3 system. You may create or modify these destinations.This entails the following duties:
- Select the name of the model new connection, e.g.
_ . Select the connection type (here R/3 connection), the dedicated server, the R/3 system quantity, the client of the used R/3 system and the log on language. Specify the user (user ID and password); this user must have the best to call RFCs on the CRM Middle ware. Choose a particular operation mode (normally none).
For the safe first communication, an RFC connection between the shopper and the CRM
Roles in SAP CRMSAP CRM Organizational Model
People Centric SAP CRM IntroductionCRM Technical Infrastructure
CRM Interaction Center Agent Perform
CRM Technical Architecture
REUSE COMPONENTS IN ABAP DAY 10
MANAGING ABAP PROJECT OBJECTS DAY 11
No comments :
Post a Comment