they have sapm user roles on the abap part of the SAP web as that is available on the J2ee part as groups.
Technical System correlates the software to the physical host on which it is installed. Each technical System can have multiple business system associated with it. Business systems are Logical systems that function as senders and receivers in XI.
Process Integration can be used as a Middleware Engine to communicate in a distributed environment. The heart of XI is Integration Engine that is used for integrating different technologies using Standard Messaging techniques e.g XML. Different mapping tools are avilable for mapping the distributed system which can be mapped without having any expertice of Technical Details.
As a real world example, XI can be helpful in integrating different banks with SAP R/@XI Engine also support previous releases of SAP R/3 like 4.6C and have many more adapters to communicate with legacy systems.
SAP XI is an integration technology and platform for:
@ SAP and Non-SAP systems,
@ A2A and B2B scenarios,
@ Synchronous and Asynchronous communication,
@ Cross component Business Process management and it include built-in engine for designing and executing integration process (Business process).
@ The goal of SAP XI is to provide single point of integration of all systems inside and outside the corporate boundary across technologies and organizational boundaries.
@ The important feature of XI is openness, flexible and transparency to the integration process. It is based on ESA and SOA.
@ The overall key concept of SAP XI is to drive integrated business process across heterogeneous and highly dynamic landscapes in a more manageable cost effective way.
@ The basic idea is to provide runtime infrastructure which allows heterogeneous systems to be tied together with fewer connections and at the same time, in order to connect those applications and let messages flow from one application to other, have a centralized storage of integration knowledge.
mobile infrastructure, enterprise portals, biw and MDM, sap xi (integration broker and bpm) WEB AS.
enables partners of XI customers to conduct XML document exchange with XI.
Alert are used to monitor the abap and java components (Including the Business Process Engine) of Exchange Infrastructure centrally, and to identify different categories of system errors and application errors in the various interfaces and interface namespaces of the components involved.
Integration Directory to drive the specific configuration of Integration scenarios. Routing Relations in the Integration Directory point to the Business Systems that are maintained in the System Catalog of the SLD, and through the appropriate association, to the technical systems.
1) Java stack
2) ABAP Stack
Technical system represents the physical system, it contains all the physical characteristics of your system for eg while creating a Technical system for your R3 system - u specify the host name, message server, OS, the clients etc.
you use performance monitoring to display statistical data on the performance of message processing. The data comes from the Integration Server (IS) or the Process Monitoring Infrastructure (PMI).The central tool for performance monitoring is the Runtime Workbench, which you call from the Integration Builder start page.
you cannot use Java APIs and Classes in it. There might be cases in your mapping when you will have to perform something like a properties file look up or a DB lookup, such scenarios are not possible in XSLT.
Proxies are interfaces, which will get executed in the application system. They can be created only in the system from message interfaces using the proxy generation functions. You can use proxies for systems with WAS >=6.20.
XI will communicate in native language with SAP systems via proxies. Proxies uses XML - SOAP based communication for both ABAP and Java Proxies.
Adapters will convert one format into another expected/target format. means from SAP standard formats and as well as 3rd party formats to target formats
they allow to add your own functions to the message mapping.
XI is not responsible for posting idocs. XI is just responsible for populating the idoc structure with the data. The function module associated with idoc structure is posting the actual data into the R/3 tables.
SXMB_MONI is based on the ABAP stack while the runtime workbench is on the JAVA stack. Moreover the runtime workbench has other features like component monitoring, mesg. Monitoring, end-end monitoring, alert confg. , Performance monitoring etc.
ccms (computer center management system), pmi (process monitoring infrastructure) and alert frame work.
Product: Represents a collection of all versions of a product. In an SAP environment, a product corresponds to an SAP technicalcomponent, e.g. 4.6c, 4.6d, 4.@Software Component: Represents a collection of all versions of a software component. Examples of Software Components are SAP_APPL, SAP_ABA, SAP_HR, etc.
Context Object is simply pointer to a specific XML tag. if you want to simplify your delopment you can define Context object for some fields and use the context objects. many message types come with their own context objects.
a) for SAP and non-SAP applications.
b) For A2A and B2B Scenarios
c) For asynchronous and synchronous communication
d) For cross component Business Process Management
you use component monitoring in the following cases:
People integration, information integration, process integration and application platform.
http://<host>:5<sys#>00/repExchange Infrastructure Tool
http://<host>:5<sys#>00/sldSystem Landscape Directory
http://<host>:5<sys#>00/MessagingSystemMessage Display Tool
http://<host>:5<sys#>00/exchangeProfileExchange Infrastructure Profile
http://<host>:5<sys#>00/mdt/amtServlet CPA Cache: Monitoring
http://<host>:5<sys#>00/CPACache/refresh?mode=delta Delta CPA cache refresh
http://<host>:5<sys#>00/CPACache/refresh?mode=fullFull CPA cache refresh.
Integration Repository to organize development efforts. Software Component Version organizes all design work in the Integration Repository. This makes sense, as interfaces logically belong to a software component and to a particular version.
Business System is a logical entity, which represents logical view of your technical system. (Eg a client in R3 system can be represented as business system in SLD) For one technical system you can have multiple business systems.
removeContext, splitByValue, collapseContext, Copy value, createIf, exits, useOneAsMany
1.removeContexts: "There is absolutely no difference between my children or grand children or great grand children". Material Group is sent in the item node of the source idoc but I want it in the header node of the target idoc. So I need to fool the mapping runtime that Material Group is coming in the header node of the source. removeContext exactly does that.
2.SplitByValue: "I need a different parent for every instance of me"
I will try to explain the function with the same mapping as readers can correlate well. Each instance of Itemno in the source structure should generate a target itemNo and item under a different instance of the header node in the target. As we can observe that occurrences of item in the source an target structure are different we cannot map the elements of the item node directly. We use splitbyValue to achieve the same.
3.collapseContexts: " There is just a slight difference between my children or grand children or great grand children". Similar to removeContext but context change is replaced with "". If we need to create empty tags in the target for every context change in the source we can use it. I did not find it useful so I don't like to explain in detail.
4 copyValue: "How many ever times I occur I am copied just once". This is not a node function but I am explaining it as it is used very frequently in real-time.
Let us take an instance of material group, which can occur as many times as the item node. But since we are mapping it to the header in the target node I just want to copy the first occurrence of material group and map it to the header node. copyValue exactly does that.
5.createif: "I have a criteria for existing". It is used when you want to create target node or element based on some condition.
a) Integration Builder
b) Integration Server
c) System Land Scape Directory,
d) Runtime Work Bench.
message monitoring, component monitoring, performance analysis and message alerting.
1) Get the Functional Specification/Business Requirments
2) Set up the Procedures/Process
3) Give the solution Roadmap
4) Design the Solution
exactly once and exactly once in order.
Pre-Delivered integration content:
(Def: -SAP solutions bring their integration Meta data like CRM, SRM, SCM, xRPM, etc.) As delivered with the integration repository of XI
A) Out-of-the-box of integration solution
B) Simplified upgrade of SAP solutions
C) Versioning and modification management of integration of Meta data.
Openness and interoperability:
(Def: -Connect to existing integration solutions) like
Process Integration is an Integral part of SAP Net weaver.The aim of PI is to integrate different versions of both SAP and non-SAP systems implemented on different flat forms (Java, ABAP, and so on). PI enables you to implement cross-system business processes.PI is based on an open architecture, makes use of open standards and offers services that are essential in a heterogeneous and complex
system landscape: namely a runtime infrastructure for message exchange, configuration options for managing business processes and message flow, and options for transforming message contents between the sender and receiver systems.
The application-specific contents are transferred from the sender to the receiver in a freely defined XML schema (XML: extended Markup Language) using the Integration Engine. The structure of a message is therefore determined by the interface data structures used.
The central concept is that, during the design phase, all interfaces required are initially developed independently of a platform and made available in the form of a WSDL description (WSDL: Web Service Description Language). Using this description you can, for example, define mappings between interfaces without this having an effect on an existing system landscape. All design phase data is saved in the Integration Repository to be implemented later in a particular system landscape. In this second phase, the configuration phase, you can select components, interfaces, and mappings saved in the Integration Repository that are appropriate for your system landscape and business processes, and assign them to each other in logical routing. The data resulting from this configuration process is saved in the Integration Directory and you can call and evaluate it from the runtime of the PI.
PI enables you to do the following:- Develop cross-system applications. You can exchange multiple system messages using the runtime infrastructure and synchronous or asynchronous communication. You can either develop new and platform
-independent interfaces, or connect to existing interfaces at runtime, using adapters.
Adjust message values and structures for the receiver, using mappings.
- Centrally maintain the message flow between logical systems in the system landscape, using logical routing.- Connect the logical receiver to a technical system, using Services; this system can easily be switched using this abstraction level (technical routing). Describe your system landscape as the basis for the description of your cross-system business process.
Receiver determination rules and interface determination rules (includes mapping assign).
The Software Catalog describes the installed products and their constituent components. The Systems Catalog describes the systems in the data center from two perspectives.
XI is a middleware like many others. It is well suited for connecting SAP systems with each other and with non-SAP.If your focus is not on SAP systems, other solutions might be a better choice today. SAP XI provides an integrated workflow engine that allows to define adapters to non-XML-protocols and mappings to convert data content from source to target.
Any fully mature middleware should provide these three layers.
@An independent Message Queue
@A data consolidator and mapping engine
XI is lacking full-fledged Message Queue compared to other established Middleware products. Currently, SAP XI does not have the features like IBM Websphere, Seeburger or TIBCO.SAP's next XI release might provide this missing piece and many more features, which is due 2007 i guess. Here are the advantages of SAP XI from my point of view. There are lots of advantages but to list a few:
* Easy Integration with SAP products & components (RFC, IDOC, Proxy).
* Data security as expected from any SAP product.
* Standards based - XML, XSD, Xpath etc
* Ability to communicate with other messaging systems/products.
* Business Process Management
* Synchronous & Asynchronous communication possible.
* Complex processes for communication possible instead of only sending and receiving (business process management) (connect e.g. asynchronous and synchronous steps, define complex communication scenarios)
* Mapping etc possible to accomplish in Java. Platform independent Java components.
* Java & .Net support.
* Big range of adapters for different technologies / tools (SOAP, Mail, JDBC, CDIX...)available in standard or offered by other companies (EDI e.g. by Seeburger).
* Process functionalities inside XI to modify content in the communication channel on own defined rules for business purposes.
* Central monitoring for data communication for all your communication between different systems.
* And the marketing issue: SAP and its partners provide high volume of development capabilities to make XI always up-to-date for new requirements.
inbound handling, receiver determination, interface determination, channel determination, mapping, outbound handling.
basically XI adapter is used in case of ABAP and JAVA proxies.
1) Develop the Technical Specification (sometimes part of Architect)
2) Develop the Interfaces according to the requirement
3) Test the scenario
TREX is a product from SAP for searching and classifying large collections of documents. TREX stands for SAP NetWeaver Search and Classification (TREX) finds information in both structured and unstructured data.
TREX is a like a search engine which provides SAP applications to search structured and unstructured data.And it can read the images for the searching query.