SAP PI Tutorials | SAP PI Training | SAP PI 7.5 Tutorials|SAP PI Step by Step Senarioas: 2012

PI 7.3 Enhanced Features

PI 7.3 has so many enhanced features as compared to the previous release of the netweaver that enables compact and featured SOA architecture and many custom attributes, meeting developer's needs and leveraged solution as per the industry standard.

Highlighting some of the important features:

1.Centralized monitoring via SAP solution manager7.1 .
There's technical monitoring work center embedded in solution manager, which provides a central view which is a featured tool to monitor the overall state of Process Integration. Components with error along with the error message can be easily tracked and troubleshot.

There's a good morning page, through which multiple PI domains can be monitored, which clearly reduces the root cause analysis time.

2.Single stack ESB capabilities.
PI 7.3 provides single stack ESB capabilities through advanced adapter engine, runtime and local monitoring capabilities, which results in almost half the processing time and efficient performance.

Single stack deployment option along with dual stack , wherein java only option could be selected when ABAP stack isn't being used.

Hardware requirement as compared to dual stack is quiet elegant with only one hour installation time and 60% less energy consumption.

3. Cache Refresh
There's an optimisation algorithm for full cache refresh with high performance and lot less memory and time consumption.

4. Fault Tolerance Capability
Large sized messages are termed as black-listed messages that could be decided by the administrator and schedule them as per the requirement so that the overall fault tolerance capability could be improved.

5. Improved design governance
User centric perspective in ESR.
Mass import of external data types in ESR.
Find SOA assets by documentation URL in ESR.
Mass publication of services from ESR to Service Registry.
Auto publication of service interfaces from ESR to Service Registry.
Wizard based configuration of a central ESR.
Usability improvements in Service Registry.

6.Key Governance features:
Extend SAP's pre-delivered entities with custom attributes.
Define custom lifecycle for assets including possible transitions and authorisations.
Subscribe to object changes to be notified via email on specific action(edit, delete).
Web based UI for specific scenarios (search, view, subscribe to objects).

7. Editors in Eclipse:
NWDS based editors for creating and editing service interface and data type.
Support to use Eclipse based standard editors for viewing ESR content.
Subscribe to object changes via ES browser in NWDS.

8. Increased productivity and richer connectivity on AAE:
Idoc and HTTP adapters in AAE. Java type Idoc and HTTP adapters available which helps in leveraging the adapter module for these adapters.
Very large(binary)file to file transfer.
Mapping-based message split on AAE.
Timeout configuration per communication channel.
Automated transport for Schema Validation.
Increased Integration Directory API support.
Creation of Integrated Configuration with Model Configuring

Source : SDN.SAP.COM

SAP XI / PI Tutorials: SAP XI Basics

The SAP Exchange Infrastructure consists of the following components:

1. System Landscape Directory

2. Integration Repository

3. Integration Directory

4. Integration Server

5. Integration Adapters

6. Integration Clients

Applications need the following proxy components to use the SAP Exchange Infrastructure directly and without adapters.

-Proxy Framework

-Proxy Generator

-Proxy Runtime

Integration Server (IS):

The Integration Server is the central part of the SAP Exchange Infrastructure. It receives messages from the sender applications and then applies routing and mapping rules to these messages and finally sends them to the receiving application. Each SAP Web Application Server has the Integration Server Software built in but it is the specific configuration that activates its role as a central Integration Server.

Integration Adapters (IA):

Integration Adapters are used to convert various protocols and data formats into the Integration Servers XML based message objects and vice versa. The Integration Server comes with some built in adapters but most adapters are additional components.

Integration Repository (IR):

The Integration Repository provides collaboration knowledge available at design time, for example, mappings, interfaces, and components. It is built in Java and follows Java 2 Enterprise Edition (J2EE) standards. The information in the Integration Repository is used by the Integration Directory, which adds configuration-specific information that is needed for execution.

Integration Directory (ID):

The Integration Directory contains detailed collaboration knowledge about the current system landscape around the SAP Integration Server. It is a description of routing rules, active services, executable mappings and the specific system landscape. The Integration Directory details the information from the Integration Repository that is specific to the configuration.

The goal of the Integration Directory is for the customer to configure the sender.Once Integration content has been created in the Integration repository, scenarios are configured in the Integration Directory.

SAP XI Interview Questions and Answers

1. why do we use MT?
A. we use message type to describe the message which is going to be sent.
2. Where u use Catch whole queue?
3. What makes an XI object unique?
4. what r the adapters that related to sap r/3?
A. IDoc ,RFC.
5. what r mapping techniques?
6. advantages & disadvantages of BPM?
7. Difference between Adapter & proxies?
8. What is BS, TS?
9. How many components have in xi?

10.What is global container?

11.How many IE are in XI?

12.How many functions r in xi?

13.What is synchronization?where it use?

14.What is idoc? where it use?

15.difference between UDF & Advanced UDF?

16.When we go for File scenario?

17.How many containers r in xi?

18.What is correlation?when we go for?

19.How many patterns have u done?

20.When u go for BPM?

21.Use of JAVA web start?

22.Components of JAVA ABAP?

23.Difference between URN/URL?

24.What r the parameters in JDBC adapter?

25.How to configure Alerts?

26.What do u do basically in office?

27.what is the role in ur office?

28.Ur office address?

29. ur TL Name?

30. ur desk color?, etc..;

Answers:

1. Message type defines the structure of the message instance.

3. Namespace can make XI objects as unique objects.

4. Idoc, RFC adapters are for SAP R/3.

5. Java mapping , Abap mapping, XSLT mapping and Graphical mapping.

6. advantage: If multiple receiver or senders then it is very easy to handle.
Disadvantage : Because of BPM performance is goes down.

7. Adapter can convert the messages into XML format and send to integration server and Proxy directly sends messages to Integration server.

8. Business system is Logical system for example a specific client on SAP server, Technical system is physical system for example SAP server is physical system with multiple clients.

9. SLD, IR, ID, RWB, Integration Server.

10. Global container is used in User defined function, which can be used to cache the value , that can be called in any user defined function of the message mapping.

11. Integration server having the one Integration Engine and one Adapter Engine. Integration engine runs on ABAP stack and Adapter engine runs on Java stack.

12. Standard functions and user defined functions.

15. UDF(simple) : This function type can process individual field input values for each function call. Therefore, simple functions expect strings as input values and return a string.

Advanced UDF: Advanced user-defined functions can access more than just individual field values. Instead, you can import a complete context or an entire queue for a field as an array before your function is called. This enables you, for example, to perform calculations on all field values of a context as well as to divide up the contexts themselves further by inserting a context change.

Advanced user-defined functions can import either just one context into the input arrays, or complete queues. Make your selection by selecting or deselecting the Save Entire Queue in Cache checkbox in the function editor.

18. When you need to collect multiple messages in XI ,you need correlation.
Assume that there are 2 systems sending data to XI and Xi needs to collect the messages of the Systems.

System A has sent the message to XI and BPM is waiting for message from System B. Even before System B can send its message, another message from System A has come in XI and another BPM is instantiated. Now, when System B sends the message how do you know which BPM it belongs to?

Correlation as the name implies is used to correlate / connect the message so that they are assigned to the correct process Instance / BPM.
19. Integration Scenario Patterns:

1. Synchronous versus Asynchronous Scenario
2. Collection of Messages
3. Split of Messages
4. State full Processing - Integration Process
5. Serialization

20. We use BPM when we need to do:

1.Controlling or Monitoring of messages in XI
2. Collect or Merge the messages in XI
3. Split the messages in XI
4. Multicast a Message
5. Need to send an Alert
6. Transformation
when we need to maintain the state of a message we use BPM.
eg. collect messages specific condition like Collect message up to defined no. or up to a specific time of a day.
-> merging of messages and sending as a single message.
->splitting of messages
->synchronous/asynchronous bridge

21. Java Webstart is a cache applications mainly used to support the fat clients, since our IR and ID are fat clients we need this Webstart to work on these....now in simple word to define fat clients is that you are working on client and data gets updated on server.....so Webstart allows you to download all the jar files required to work from the client at once, so you will notice when you open your IR and ID for the first time in the systems it takes time to open.Reason is it download all the necessary jar files required to work IR and ID from your system

22. Integration Server, Business Process Engine are components of ABAP,
Adapter frame work, Mapping engine, ID, IR, and RWB are components of Java.

23. The namespace could be any string that uniquely defines the scope of those determined fields of the XML file. Usually, you use a URI to define that unique string, and since URLs are the most common URIs, people tend to use plain http URLs as the namespace (it doesn't need to be a valid url). But using "urn:test" for example isn't wrong.
From the specification:
URI
URI = Uniform Resource Identifier
There are two types of URIs: URLs and URNs
URL
URL = Uniform Resource Locator
<protocol>:// <host> :<port> <path> ? <query>

URN
URN = Uniform Resource Name.
URNs define XML schemas.

urn:<namespace>:<string>

URN: Uniform Resource Name
urn:sap-com:xi:demo (URI with out protocol assignment)

URL: Uniform Resource Locator
http://sap.com/xi

24. Transport Protocol

JBDC 2.0
Message Protocol

? XML SQL format

Table values can be inserted, updated, or deleted in one or more tables. In the database, stored procedures can be called using transfer parameters. In the case of synchronous queries, results from database queries or return values of stored procedures can also be transferred.

? Native SQL String

An arbitrary SQL statement is expected as the message content. This statement is transferred unaltered to the database for processing.Depending on the message protocol you selected, the adapter expects special XML document formats in the message from the Integration Server or the PCK. For more information about the document formats, see: Document Formats for the Receiver JDBC Adapter.
Adapter Engine
Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine. This selection is not available in the PCK.
Connection Tab Page
Database Connection
Specify the following to establish the database connection:

Field

Entry
JDBC Driver

Java class of the JDBC driver that the JDBC adapter must load to be able to access the driver. The specification varies according to the JDBC driver; see material from the respective provider for exact details.

Connection

Address with which you can establish a database connection using the JDBC driver. The specification varies according to the JDBC driver; see material from the respective provider for exact details.

User Name

User name for logging on to the database.

Password

Password for logging on to the database, including confirmation.

25. Alerts within XI give us a simple way to monitor only those errors that we want and send alert messages to different people depending on the alert category. You can send alert to alert inbox, mail and even on SMS if your cell phone operator gives you the possibility of sending an sms through a web service.

At first we have to create an alert category:
- go to TCODE - ALRTCATDEF

- change mode, define you alert category

- define the attributes which you want to receive in the alert.

- Add the receivers who will receive the alerts

- save and activate

- Inside alert configuration define the settings for example: Interface name for which you want to receive the alerts in your inbox.

- save and update abap table