Ans: SAP Process Integration is part of SAP NetWeaver platform and in NetWeaver 7.0 ehp2 and older versions it is called SAP NetWeaver Exchange Infrastructure XI. SAP NetWeaver Process Integration is part of NetWeaver software component and is used for exchange of information in company’s internal system or with external parties.
SAP PI/XI enables you to set up cross system communication and integration and allows you to connect SAP and non-SAP systems based on different programming language like Java and SAP ABAP. It provides an open source environment that are necessary in complex system landscape for integration of systems and for communication.
SAP Process Integration is a middleware to allow seamless integration between SAP and non-SAP application in a company or with systems outside the company.
Ans: 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.
Features:
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.
Ans: 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/3. 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
1. SAP and Non-SAP systems,
2. A2A and B2B scenarios,
3. Synchronous and Asynchronous communication,
4. Cross component Business Process management and it include built-in engine for designing and executing integration process (Business process).
5. 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.
6. The important feature of XI is openness, flexible and transparency to the integration process. It is based on ESA and SOA.
7. 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.
8. 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
Ans: People integration, information integration, process integration and application platform.
Ans: mobile infrastructure, enterprise portals, biw and MDM, sap xi (integration broker and bpm) WEB AS.
Ans: inbound handling, receiver determination, interface determination, channel determination, mapping, outbound handling.
Ans: Receiver determination rules and interface determination rules (includes mapping assign).
Ans: exactly once and exactly once in order.
Ans: they have sapmuser roles on the abap part of the SAP web as that is available on the J2ee part as groups
Ans: ALRTCATDEF.
Ans: ccms (computer center management system), pmi (process monitoring infrastructure) and alert frame work.
Ans: integration engine.
Ans: enables partners of XI customers to conduct XML document exchange with XI.
Ans: message monitoring, component monitoring, performance analysis and message alerting.
Ans: oracle and ms sql
Ans: classification of errors and alerting channels.
Ans: JCA
Ans: message monitoring.
Q19: What are the two types of monitoring handled by message monitoring?
Ans: End to end and performance.
Ans: process and instance views.
Ans: 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.
Ans: overview data and detailed data.
Ans: XI Adapter Engine.
Ans: Java proxy environment.
Ans: cross component and takes care of the execution and persistency.
Ans: a) Error Handling
b) Splitting of messages
c) Combining of messages
d) Message Persistency.
Ans: Processing messages, mapping, routing, guaranteeing quality of service.
Ans: scenario editor, process editor, mapping editor, condition editor, interface editor.
Ans: Routing, mapping, channel determination.
Ans: process execution and correlation handling.
Ans: sonic mq, mq series.
Ans: simple object access protocol.
Ans: publish/subscribe & request/response.
Ans: This object enables you to cache the value that you want to read again when you next call any user-defined function that is in the same message mapping.
Ans: This object enables you to cache the value, which you want to read again when you next call the same user-defined function.
Ans: you have an option of sending a message to multiple receivers and waiting for a response from the each of the receivers. This procedure of sending a message to multiple receivers and waiting for a response message is also known as 'multi cast'.
Ans: a) Remove Contexts: - remove all higher level contents of the source level message in order to map with the target message field. So you can get the node contexts removal.
b) Split by value: - Insert Context change for an element split by value is some as counter part of remove context. Here instead of delivering the context you can insert a context change in the source value queue.
c) Collapse contexts: - Copies first values of the all contexts to one context empty context are replaced by empty string.
d) Copy Value: - 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.
e) Create if: - It will create a target node or element based on some condition.
f) Exists: - Function to determine whether a particular source field exists in instance to be processed. If it does it gives true or else false.
g) Use one as many.
h) Replace value: - Replace the value I with the value that you desired in the dialogue for function properties.
i) Sort: - Sorts all values of the multiply occurring inbound field with in the existing or set context.
Ans: a) Container
b) Global Container
c) Mapping Trace.
Ans: This object enables to transfer message to the mapping trace if the trace level set correspondingly then the trace is visible to message monitoring.
Ans: An alert is a notification informing its recipients that a critical or very important situation has arisen. The situation is as severe that an action must be taken immediately in order to solve the situation.
Ans: 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.
Ans: Graphical Mapping
Java Mapping
XSLT Mapping
ABAP Mapping
Ans: 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.
Ans: 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.
Ans: 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.
Ans: 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
Ans: For RFC-RFC Destination of type TCP/IP
For idoc - rfc destination of type R/3
Ans: they allow to add your own functions to the message mapping
Ans: BPM will execute in the Integration Engine in the Integration Server.
Ans: 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
Ans: 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.
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
Ans: a) Integration Builder b) Integration Server c) System Land Scape Directory, d) Runtime Work Bench.
Ans: Abstract interface is similar to other interface (outbound or inbound) but does not have direction. It can be used as either outbound or inbound. It is used only inside BPM.It is also called as hidden Interface.
Ans: SXMB_MONI_BPE
Ans: IDOC and HTTP adpter run on ABAP stack.....rest on Java stack
Ans: As they run on ABAP stack.....
Ans: Run a report RSALERTTEST
Ans: SXMB_MONI for ABAP atck and RWB for java STACK
Ans: ABAP and JAVA stacks
Ans: This object enables you to transfer information for the mapping trace during mapping to a container that can be viewed by users in the message monitoring
Ans: Repository used for storing landscape information. Its does not provide any landscape administration tools .SLD manages software components and platform dependencies. It acts as a central information provider for NetWeaver systems and other administration tools. Facilitates Installations, upgrades and transports
Ans: By using the Hypertext Transfer Protocol (HTTP)
Ans: The Software Catalog describes the installed products and their constituent components. The Systems Catalog describes the systems in the data center from two perspectives
Ans: 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.
Ans: 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.
Ans: 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.7. Software Component: Represents a collection of all versions of a software component. Examples of Software Components are SAP_APPL, SAP_ABA, SAP_HR, etc.
Ans: 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
Ans: 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
Benefit: -
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
Through JMS messaging (e.g MQ series) and SOAP.
Use open, XML standards for integration
Incorporate existing functionality in to new process (Adapters (JCA),
Ans: you use component monitoring in the following cases:
If you want to get an overview of the status of the individual components of SAP Exchange Infrastructure (XI).If you want to call the configuration data of individual XI components. If you want to use test messages to check whether the XI runtime is functioning correctly. If you want to test whether cache connectivity is functioning correctly. If you want to archive message security settings or entire messages.If you want to check the status of your communication channels or the adapters configured in the communication channels.
Ans: Totrack the status of messages.
To find errors that have occurred and establish what caused them
Ans: If you want to monitor message processing steps in a number of SAP components (to be configured). If you want to monitor the path of individual messages through these SAP components, from start to end.
Ans: Element is a simple XML TAG
Ans: Properties of XML TAG
Ans: Logical set of group of XML TAG.
Ans: two types of transform protocols 1) NFS (Network File System, 2) FTP (File Transfer Protocol)
Ans: Software components represent the reusable modules of a product
Ans: represents a particular version of a software component.
Ans: Product: A software product is composed of one or more software components.
It represents a collection of all versions of a product. A product is a unit that
can be delivered, is visible to the customer, and that is installable and renewable.
Ans: 1) Java stack 2) ABAP Stack
Ans: No
Ans: Messages are delivered with the same queue names (supplied by the application) in the same sequence that they were sent from the sender system.
Ans: Java mapping runs on J2EE engine, ABAP Mapping runs on ABAP Stack.I guess ABAP mapping makes more sense if you have a requirement wherein you need to perform multiple RFC classes for RFC Lookup's etc as you can do this very easily Using your ABAP Code. Java Mapping provides a easier means to use Java API's etc and it uses SAX parser which provides better performance while ABAP Mapping uses DOM Parser (I am not very sure on this though) which can cause a performance bottleneck.
Ans: 1) Component monitoring
2) Message monitoring
3) End-to-End monitoring
4) Alert Configuration
5) Cache monitoring
6) Index administration
Ans: 1) If you want to get the overview of the status of individual components
2) If you want to call configuration data of individual XI Component
3) If you want to use test messages to check whether the XI Runtime is functioning correctly.
4) if you want to test whether cache connectivity functioning correctly.
Ans: 1) If you want to monitor message processing steps in a number of SAP Components.
2) If you want to monitor the path of individual messages through these SAP Components from start to end.
Ans: Cache monitoring displays objects that are currently in the runtime cache of either of the following receives of cache data.
Ans: 1) It support Parsing Techniques.
2) It is very easy to use and execute through developing by code
3) Easy to implement interface.
4) In java Mapping we can achieve even the interface(outbound and Inbound) structer are too difficult.
Ans: SXMB_IFR - Starting Builder
SXMB_MONI Integration Engine, Monitoring
SXI_MONITOR XI Message Monitoring
SLDCHECK Test SLD Connection
SLDAPICUST SLD API Customization
SXMB_ADM Integration Engine, Administration
SXI_CACHE XI Directory Cache
SXMB_MONI_BPE Process Engine, Monitoring
Ans: 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.
Ans: WE 60 Documentation for IDOC types
BD87 Status Monitor for ALE Messages
IDX1 Port Maintenance in Idoc Adapter
IDX2 Metadata Overview in Idoc Adapter
WE05 Idoc Lists
WE02 Display Idoc
WE19 Test tool
WE20 Part ner Profiles
WE21 Port definitions
Ans: http://:5<sys#>00/repExchange Infrastructure Tool
http://:5<sys#>00/sldSystem Landscape Directory
http://:5<sys#>00/rwbRuntime Workbench
http://:5<sys#>00/MessagingSystemMessage Display Tool
http://:5<sys#>00/exchangeProfileExchange Infrastructure Profile
http://:5<sys#>00/mdt/amtServlet CPA Cache: Monitoring
http://:5<sys#>00/CPACache/refresh?mode=delta Delta CPA cache refresh
http://:5<sys#>00/CPACache/refresh?mode=fullFull CPA cache refresh.
Ans. we use Business service then system is not your landscape in these we don't these others system details we use Business services. Business system we use we have the Business System in our landscape and we know it.
Ans: a) Conversions b) Boolean c) Node Functions d) constant e) date
f) Text g) static h) arithmetic
Ans: Send step:To send a message asynchronously from within an integration process, you use a send step in Asynchronous mode. When a message is sent asynchronously, the send step does not wait for a reply message from the receiver after the message is sent. However, you can specify that the send step must wait for a confirmation of receipt from the receiver, in the form of an acknowledgment.
Container:
You use a container operation to set a value for a target container element at runtime The target container element and the assigned value must have the same data type. To specify the value, use the expression editor.
Receive:
An integration process is always started when a message is received. To receive the triggering message, use the receive step and set the Start Process indicator.
Loop:
You use a loop to repeat the execution of steps within the loop. The loop continues to run while the end condition returns true (while loop).
Fork Step:
You use a fork when you want to continue a process in branches that are independent of each other, for example, to communicate with two systems that are independent of each other. The branches of the fork join in a union operator.
You can specify the required number of branches and then define whether the process must run through all branches, or just a particular number of branches. Furthermore, you can define an end condition for the fork
As soon as a branch reaches the union operator at runtime, the system checks the following conditions in the specified order:
? The process has run through the required number of branches
? The specified end condition has returned true
The step is complete as soon as one of the conditions returns true.
Control Step:
You use a control step to do the following:
Terminate the current process
Trigger an exception
Trigger an alert for Alert Management
Wait Step:
You use a wait step to incorporate a delay in a process. Usually, you use a delay to define when the next step in the process is to start. You can define a delay as either a point in time or a period of time. At runtime, the step waits until the specified point in time is reached or the specified period of time has passed. The system then continues the process by proceeding with the next step.
Ans: Alerts are messages, which can be raised in case of failure. Alert Category can be defined in transaction ALRTCATDEF on abap stack. We can assign recipients to every alert category which specifies who will receive alert in case of error.
Alert rules can be defined in RWB.
Ans: 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.
1. An independent Message Queue
2. A data consolidator and mapping engine
3. Workflow processor.
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
Ans: 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.
Ans:
Ø To track the Status of message
Ø To find errors that have occurred and established what cause them.
Ø Display and manage messages
Ø Search for messages using an index
Ø Filter the displayed messages by specific criteria. Configure the message display.
Ans: Alerts are messages, which can be raised in case of failure. Alert Category can be defined in transaction ALRTCATDEF on abap stack. We can assign recipients to every alert category which specifies who will receive alert in case of error.
Alert rules can be defined in RWB.
Ans: Web AS Java: Web AS Java systems consist of one or more instances and each instance is installed on a separate host. An instance itself consists of cluster nodes that can communicate with each other.
Standalone Java: Standalone Java technical systems are standalone Java applications that are installed in a computer system from an administration perspective. They can also be installed as an operating system service or as a daemon.
Ans: 1.Multimapping without BPM is possible if you have SP14.
2. Multimapping without BPM is possible only for 1:N scenario.
3. For N: 1scenario you have to use BPM.
4. Multimapping without BPM is possible ONLY for those adapters, which resides in the Java Stack.
Ans: Collobration Profile: It is nothing but the binding of the sender interface to the sender system to the receiver interface in the receiver system using the specific mapping.
Collaboration Agreements: It is nothing but the binding between sender/receiver systems, reciever/sender interface to the communication protocol/channel.
Ans: Context of an element is nothing but just the level (with reference to its parent node) where the XML tag appears in the given XML document.
Ans: it is a Web Application Server for SAP.
Ans: its just path to XML tag. Path is an expression language for addressing portions of an XML document, or for computing values (strings, numbers, or boolean values) based on the content of an XML document. Path is also a specification of the XML family. Using XPath you can address any node in an XML document. XSLT implements XPath expressions to select substructures of an XML document. Using templates in XSLT you can define the mapping rules for the selected substructures.
Ans: payload is actual content of message (Business data).
Ans: Transport protocol gives information about outside of message details, kind of system, security details. A transport protocol is a network protocol that has the capability of transferring some payload from one node to another, thus providing some level of transparency from the underlying network.
Transport protocols are used as a mechanism to move payloads around a network. Typically, a payload will have a transport binding associated with it. For example, SOAP (acting as a payload) has a predetermined binding for HTTP (a transport protocol). Some common transport protocols include: HTTP, HTTP-R, SMTP and BEEP. Message protocol gives you an idea of message type XI payload
Ans: Data types (DTD): defines a data structure (like the Java types int, String, double etc). Message types (XSD): defines the message structure, based on data types or standard XML types (like a defined variable of some type: int Counter = 0; String s = "aaa";)Message Interfaces (WSDL): defines the interface of a service that uses that message type to export/import data (like when you have a method that returns or consumes some parameters of determined types: int parseInt (String s) ).
Ans: SAX is Simple API for XML, DOM is Document Object Model. SAX parser is a memoryless parser and is recommended when the XML structure is huge. DOM parser loads the entire XML into the memory and so when the XML size is to big, DOM parser is to be avoided.
Ans: a) CCMS b) PMI c) Adapter Framework
Ans: Central Component Monitoring System.
Ans: Component Monitoring
Ans: Process Monitoring Infrastructure.
Ans: a) Message Monitoring b) Performance Monitoring
Ans: Message alerting.
Ans: tRFC and qRFC.
Ans: use when u wants to establish an rfc connection between two sap systems. say for example. r3 and xi box. u would use r3 connection
Ans: use this when connecting to external systems.
Ans: basically XI adapter is used in case of ABAP and JAVA proxies.
Ans: In ccBPM We can use Multi Mapping.
Ans: Message Mapping is used to transform your Source XML into the target XML structure.
Ans: converting a value in the source to another in target) Value Mapping is used for specific mapping structures / mapping rules. Example, Currency Conversion Mapping Rules. Instead of creating this conversion rule in every mapping program, you can create a VALUE mapping that is stored in a value mapping table and use this is your Message Mapping and There by save up redundant mapping logic. Also, if the conversion rate changes, if you have used value mapping, you need to make a change only in once place and result will be reflected in every mapping. If value mapping was not used , then you would have had to make the change in all mapping programs.
Ans: 1. Create your communication channel.
the communication channel is the means using which XI gets and passes information. XI can understand only XML and so, the communication channels ( or adapters ) do the task of passing XML messages to and from XI. If the message is not in XML format, content conversion is performed at the Adapter.
2. Create your sender and receiver agreement.
Whenever XI is the recipient of some information, you create a sender agreement for the corresponding adapter, sender system and sender interface. Whenever XI is going to send some information to an external system, as the external system is the recipeint of the information, create a receiver agreement for the same.for IDOC and HTTP adapters, no sender agreement is required.
3. Receiver Determination: In this stage, you tell XI, the recipient Interface of the scenario. You can also provide conditions on which the receiver is determined.
4. Interface Determination: The stage where the Inbound Interface and the Interface mapping program are defined. Conditional Interface determination is also possible.
Ans: Mercury load runner.
Ans: Business systems, Business Services, Business Process
Ans: Header mapping is a part of the collaboration agrement and allows you to overwrite specific fields of the header add payload information to the xi message header.
Ans: specify inbound message
Specify outbound message
Define message processing
Confirm configuration data
Ans: Common Information model, XI has developed means Ans) CIM the SLD is for central repository of information about software and system in the data center, expressed in Common information model. CIM was developed by DMTF (Distributed Management Task Force). It is an industry consortium whose goal is to enable management of IT systems in distributed environment using webstandars.
Ans: The JMS adapter (Java Message Service) enables you to connect messaging systems to the Integration Engine or the PCK.
Ans: To perform application-level validation of the data, before sending it to the backend. To populate fields of the XML document with some additional data found in the backend application.
Ans: a) File Level Transport - Files are exported and imported into SAP XI OS level folders of development and QA respectively. This is relatively easy as there is no need of setting up any additional software's but its risky as the process is not automated as the files have to be FTP'ed from development to QA XI boxes and any failure of the transport cannot be tracked and audit logs will not be available.
b). Change Management System (CMS): This is a GUI based tool, which has to be installed on the XI box for providing the user-friendly browser which is used for automating the transport mechanism and tracking any transport failures. However there is an initial level effort for setting up the CMS and stabilizing it.
Ans: urn means uniform resource navigator, which does'nt uses any protocal in which while giving this urn it should be unique in ur system.url means uniform resource locator, which uses the protocal i.e http.
Q151. What are mapping lookups?
Ans: you can use mapping lookups to check some values.
Ans: correlation are the one that are used to make some relation between objects
like in bpm suppose u r collecting some idocs and after colecting some idocs u bunch them and send it to receiver then u need to define a corelation variable which will collect the idocs on the basis of this corelation variable.
Ans: 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.
Ans: 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
Ans:
1) Get the Functional Specification/Business Requirments
2) Set up the Procedures/Process
3) Give the solution Roadmap
4) Design the Solution
Ans:
1) Develop the Technical Specification (sometimes part of Architect)
2) Develop the Interfaces according to the requirement
- All ABAP/Java Developments
- Design/Configuration
3) Test the scenario
Ans: SWF_XI_ADM_BPE
SWF_XI_ADM_BPE_DISP
SXMB_ADM_BPE
SXMB_MONI_BPE
Ans: Patterns are more like example where u can refer to the IS or u can make use of those in ur scenario
SWEQADM - Check Events
RSWELOGD- Delete Event trace
SWEL- Display Event trace
SWELS - Switch on Event trace
SWI1- Processes and work items,
SWF_XI_SXPR - Restart workflow with errors
SWF_XI_SWI14 - To find workflow log by interface name &namespace.
SWF_SI_SWI2_DIAG -Diagnosis process with errors.
Ans: data types just define the abstract XSD structure . but since In XI we are using XML langauge. so We need a Root element in our message. that root element is added by Message type.
Ans: Enterprise Service Repository
Ans: 1) Java Web Start is used to deploy standalone java applications over the network. When it comes to XI, the Integration Repository and Directory require specific Java client software, which is stored on the Integration Server and will be automatically installed on the client side using Java Web Start. This client software can be used during design time to develop new interfaces and mappings and to configure services, routings and mappings. As it allows applications to be started from the Internet using a web browser.161) What is cache and how many types of Caches are there in XI and what are their purposes?
Ans) Two Types
1) CPA cache: - CPA cache - is your Collaboration profile agreement cache, ie to mean it will contains the cache copy of all objects created during configuration time (ID).CPA (Collaboration profile agreement )Cache-mainly for J2EE engine/Adapter engine.
2) Runtime Cache:- Runtime cache - it will contain cache copies of all the objects in XI (IR/ID) and active version of all your objects during runtime.
Ans: smq1 outbound, smq2 inbound.
Ans: using command prompt.
Ans: SOAP is used to connect with remote system. Http is resided in ABAP Stack. It uses native http format i.e no SOAP Envelops.For HTTP no need to create Sender communication channel,
Ans: First check Inbound quing using smq1 if no messages are in queue go to Transaction smq2. This is outbound queue. Go to message monitoring there u can find message from component there u can set adapterengine from drop down box and click disply and again click on start button there u can find messages.
Ans: go to component monitoring click on Test message button there there u can give the payload.
Ans: Value mapping: value-mapping function to map different representations of an object to each other. You save the mapping rules for different objects in a value mapping table.
Ans: Context object is alternative to XPath; this will be used to access the content of an element in message in Runtime. This will be used create in IR, and refer in Message Interface, In ID we will define where it is to be used, Based on this runtime value we can route the message processing.
Ans: Repository used for storing landscape information. Its does not provide any landscape administration tools
• SLD manages software components and platform dependencies
• It acts as a central information provider for Net Weaver systems and other administration tools
• Facilitates Installations, upgrades and transports
Ans: a) Local Integration Engine b) Web Services Framework
Exchange Infrastructure (XI) is an Integral part of SAP Net weaver. Position of XI is in the process integration layer of Net weaver stack.The aim of XI is to integrate different versions of both SAP and non-SAP systems implemented on different platforms (Java, ABAP, and so on). XI enables you to implement cross-system business processes.XI 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 Exchange Infrastructure.
Exchange Infrastructure 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 available for mapping the distributed system, which can be mapped without having any expertise of Technical Details. As a real world example, XI can be helpful in integrating different banks with SAP R/3. XI Engine also support previous releases of SAP R/3 like 4.6C and have many more adapters to communicate with legacy systems.171) Briefly explain about Net weaver?
Ans) SAP Net Weaver provides an open integration and application platform and permits the integration of the Enterprise Services Architecture. Net weaver covers following topics:
a) People Integration
b) Process Integration
c) Information Integration
d) Application Platform.