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

Limitations of SAP PI 7.3(single-stack Java installation)

Introduction

Two options while installing SAP PI 7.3 :

1.) Single stack Java installation

2.) Traditional Dual stack installation

*This presentation will cover limitations of Single stack installation.

*But in some of the case alternatives will be provided.

*SAP introduced the Advance Adapter Engine (AAE) in PI 7.10. The AAE provides end-to-end message processing to be executed completely in the java-stack. This increases performance significantly since messages will no longer be passed back-and-forth between the ABAP and the java stacks. With this java-only processing, a new configuration object is also introduced in the Integration Directory to configure the end-to-end scenarios. This new configuration object is “Integrated Configuration Object”, or ICO, and is used to configure the scenarios which will only be processed in the java-only engine.

*With PI 7.30, AEX was created. AEX, a java-only ESB, is built on AAE

*The dual-stack installation continues to be available as an installation option. The architecture remains unchanged from the previous releases.

Note: *Please note the distinction between AAE and AEX

*AAE: AAE is an adapter engine which provides message processing in the java-only stack. AAE is installed in both dual-stack and single-stack PI installations of PI 7.1 and above.

*AEX: AEX is a java-only installation of PI, which uses the AAE.

1.) Decentralized adapter Engine doesn’t work in ICO/ ICO works with only same type of adapter engine.

*Error while assigning different adapter engine in sender and receiver communication channel: “Assigned sender and receiver communication channels are not configured for the same adapter engine; ensure that all channels are configured for the same adapter engine”

*So, If you want to work on Java based adapter and decentralized adapter engine then use classic configuration, as classic configuration supports both java based adapter and classic configuration. This can be monitor in SXMB_MONI transaction of ABAP stack.

Even this functionality is not supported on PI 7.3.1

2.) Advance Adapter Engine can not use Idoc adapter. As Idoc adapter is based on ABAP stack

*AAE cannot use Idoc adapter as Idoc adapter is based on ABAP stack but in PI 7.3 (Java stack) we have IDOC_AAE adapter available.

*If you still want to work with IDOC adapter only then install Dual stack

3.) Advance Adapter Engine can not use HTTP adapter.As HTTP adapter is based on ABAP stack

*AAE cannot use HTTP adapter as HTTP adapter is based on ABAP stack but in PI 7.3 (Java stack) we have HTTP_AAE adapter available.

* If you still want to work with HTTP adapter only then install Dual stack.

4.) AAE cannot use the WS adapter. As WS is an ABAP adapter

*If you want to work with WS adapter then install Dual stack.

Note: For all ABAP based adapter

*We can assign only java based adapter in ICO. It will not allow to assign ABAP based adapter in ICO as they are on Integration Engine.

*For Ex. Below are the list of ABAP and JAVA based adapters for a communication component

Below are the list of communication channels available in ICO for a communication component

Only Java based adapters are available in ICO

5.) ccBPM is not available for AAE

*ccBPM is not available for AAE. As ccBPM uses ABAP’s work-flow engine to orchestrate the messages.

*In case if it is required in your project then install Dual Stack.

6.) Extended Receiver Determination is not available in ICO

*Extended receiver Determination have used earlier in classic configuration.

How ever Routing based on XPath expression is available

*Install Dual Stack for Extended Receiver determination in case it is required

7.) Using Integration Directory’s Receiver Rule is not available

*Receiver Rule is not available using Integration Directory

8.) Parameterized Mapping

*Using mapping parameters in Operations Mapping is not available in ICO.

*No parameterized mapping in ICO

*This is still available with Dual Stack

9.) ABAP mapping cannot used by AAE

*ABAP mapping is executed in ABAP, therefore cannot be used by AAE.

ABAP mapping is present in PI 7.3 with Dual stack installation.

10.) AAE does not support “Maintain Order at Run Time”

*Maintain Order at run Time is not available in ICO. This was available in Classic configuration.

with Dual stack installation functionality of Maintain order at Run Time can be achieved with Java based adapter

*Below is the result of Maintain Order at Run Time in classic configuration for Java Based adapter.

11.) No more SXMB_MONI transaction

No message will be available in SXMB_MONI transaction of PI(ABAP Stack) system for Configuration scenario which are based on ICO.

But in SAP PI 7.3 we still have many option for monitoring the message in NWA for Single stack.

Summarizing AAE Limitations

AAE limitation in ICO for PI7.3 and PI 7.31 release:

Terms to understand

*AAE : AAE is an adapter engine which provides message processing in the java-only stack. AAE is installed in both dual-stack and single-stack PI installations of PI 7.1 and above.

*AEX: AEX is a java-only installation of PI, which uses the AAE. With PI 7.30, AEX was created. AEX, a java-only ESB, is built on AAE, but with all the ABAP dependencies removed

*ICO: “Integrated Configuration Object”, or ICO, and is used to configure the scenarios which will only be processed in the java-only engine.

*Classical configuration : Integration Directory configuration with Receiver Determination, Interface Determination, Sender and Receiver Agreements, and Communication Channels. These configurations are what we will call as “classical” configuration, and will be processed by both ABAP and java engines.

SAP PI7.3 Online Training

Contact:+918008002022

What is new in SAP NetWeaver PI 7.3 EHP1

by http://scn.sap.com/people/rajasekhar.reddy14

This document describes some of the new features available in PI 7.3 EHP1.

Single Stack ESB:

Hardware requirement reduced by 50% compare to dual stack installation.

Up to 60% less in energy conceptions and easy maintenance.
Higher volume scenarios can be handled effectively.

Integration Flows:

Enterprise Integration Patterns is heart for any middleware implementations, Patterns can help in easily realizing common integration challenges. Each pattern-based integration flow lists all the steps required in SAP Net Weaver PI to realize the scenario.

One Central ES Repository for Multiple PI Domains:

Optionally a single ES Repository can be leveraged for multiple PI domains.

Central governance incl. re-use of design objects across multiple PI domains.
Largely improved flexibility for landscape setup.
The ES Repository from any PI domain, i. e. double stack or Java Only PI with / without non-central adapter engines, can be leveraged for other PI domains.
But: One domain can only use one ES Repository: Either its own or another domain‘s one.Local ES Repository is disabled; Central ES Repository will belong to all PI domains of SLD model
Central SLD required.
Configuration via CTC template and optionally also manual.

Logging of Synchronous Messages:

Synchronous messages can be logged optionally on Java Only PI.
Logging can be configured via global parameter (default) and scenario specific (also for asynchronous scenarios).
Support also in user defined message search to search for payload values.

Integration with FTP Proxy Server via File / FTP Adapter:

File / FTP adapter supports direct integration with FTP proxy server without any work around.
Host name and port of FTP proxy server can be configured in FTP connection parameter settings of File / FTP communication channel with transport protocol FTP.

Completion of Java IDoc Adapter:

Functionality of ABAP IDoc adapter fully included in Java IDoc adapter.
IDoc packaging on receiver side to simplify IDoc processing, increase performance , simplify monitoring & error handling
IDoc flat file module support for IDoc packages (multiple IDocs in a single IDoc flat file of same message / IDoc types).

JMS Adapter Enhancements:

Support of further security standards (SSL Support), simplified configuration for integration with IBM Web sphere AS, optimized connection pooling for integration with MQ version 6.
Support for Web sphere AS 7
JMS connection pool optimization-Connection pooling with MQ version 6;not required anymore for MQ version 7(default configuration setting)
JMS topic support –MQ set ClientId, Include Client Id and further connection settings for MQ in channel configuration (previously these were required as additional parameters).

Principal Propagation for SOAP Adapter (XI Protocol):

Principle propagation between ABAP and Java proxies based on SAP logon / assertion ticket.
Supported now additionally via XI message protocol of SOAP adapter, similar to SOAP & RFC protocol as well XI message protocol in Integration Server.
Message execution under propagated user
Based on trusted relationship configured between SAP Net Weaver PI and sender as well receiver system.

Completion of Integration between Java Proxies and SOAP Adapter:

All scenarios for communication between SOAP adapter and Java Proxy Runtime via XI 3.0 message protocol are supported.
For acknowledgements provider Java proxies and SOAP adapter can run on any Adapter Engine
Consumer Java proxies and SOAP adapter can run on any Adapter Engine
With this the limitations in SAP Net Weaver PI 7.3 for integration between Java proxies and SOAP adapter (XI protocol) are removed in EHP1 for SAP NetWeaverPI 7.3.

Integrated Stack:

Common deployment of AEX and BPM/BRM on one single System ID.
Reliable connectivity between messaging and process layer via proven Java Proxy Runtime.
Preserve your investments by calling PI mappings (Java, XSLT) from within a BPM process.
Model-driven development environment based on BPMN standard
Leverage SAP NetWeaver BRM for business rules.
Reduce TCO with single System ID installation.
Reliable connectivity between BPM and PI/AEX at lower costs (as an alternative to WS-RM).
Enhance mapping capabilities within a BPM process by calling PI mappings (e.g., calling XSLT).

SAP PI 7.3 Online Training

Contact:+918008002022

PI 7.1 EHP1 Delta Features over PI 7.1

1. Service interface generation for WSDL import into ESR
The import of externally defined WSDL files into the ESR and the creation of service interface objects are supported via a wizard. The service interface definitions can be modified once they are imported into the ESR. The external services can be directly used for proxy generation. Multiple WSDL files can be imported.

2. Classification support in ESR
Classifications, which provide an option to add a semantic meaning, can be directly assigned in the ESR to one service interface or to a group of service interfaces. The ESR also allows searching for services by their classifications.

3. Security profile settings for service interfaces
Security levels can be directly assigned to the service interfaces in the ESR. The security level value is sent to the provider system during proxy generation and defines the minimum security configuration of the service definition.

4. Where-used list in Services Registry
The Services Registry allows searching for Service Groups. A Service Group bundles all services that are provided by the same logical service provider. If a service definition is assigned to a Service Group, it indicates that the service is used by a consumer. Service Groups can be published in SR and enable configuration of multiple services in one go.

5. Add information to services published in the Services Registry
The publication wizard of the Services Registry supports to classify the published service, add provider system information and a link to the documentation of the service, and add user name and password if the service requires authentication.

6. User defined usage profiles in the ESR & Service Registry
The ESR allows creating customized usage profiles to define sets of object types, software component versions and business modeling filters that are of interest to different user groups. The usage profiles can be assigned to specific users, roles, or groups, and are personalized filters that provide a fine granular control of who can view and edit SOA artifacts; with this a simplified UI is offered since all the other SOA artifacts are hidden. The Services Registry supports an elaborate authorization concept for its users and provides user-specific views on the content of the Services Registry. Security permissions can be defined that assign User Management Engine (UME) roles to classifications.

7. Cleanup of Services Registry
In the SAP NetWeaver Administrator tasks can be defined that provide information about invalid URLs and URLs that cannot be reached. The jobs can be either scheduled to run on a periodic basis or triggered as an event when required. Based on the information about the unavailable entities it can be decided to either correct a service endpoint or to remove the service definition from the Services Registry.

8. Generation of outbound interfaces based on inbound interfaces
The ESR provides a wizard to automatically create an outbound service interface for a given inbound service interface and assign a link between the service interfaces to indicate that the two interfaces match. The outbound service interface and the inbound service interface can reside in the same or in different software component versions.

9. Content Based Routing (CBR), Receiver Split+(RS) & Operation-dependent receiver determination in Advanced Adapter Engine (AAE)+
The integrated configuration, that determines the routing condition for the local processing on the AAE, supports the configuration of different receivers for different message payload values; i. e. a message that is processed locally on the AAE can be sent to different receivers depending on values of the message payload. The integrated configuration supports configuration of multiple receivers; i.e. a message that is processed locally on the AAE can be sent to multiple receivers. The receiver determination, that determines the routing condition on the Integration Server, supports definition of different receivers for different operations of same outbound SI.

11. Integration Directory API supports new objects types
The Integration Directory API, that provides a web services based API to access, edit, and activate objects in the Integration Directory, supports new object types and attributes that have been introduced with SAP NetWeaver PI 7.1, such as direct connections.

12. Enhanced search for communication channels
The Integration Directory allows searching for communication channels with adapter type specific attribute values; e. g. to search for communication channels with adapter type File/FTP who has configured a specific file name.

13. Scenario view in Integration Directory
The scenario view in the Integration Directory allows grouping assigned objects according to configuration scenarios.

14. Enhancements of Adapter Engine Java SE
Remote configuration: The remote configuration allows to add, start, and change remote adapter instances of the Adapter Engine Java SE; a message containing the configuration information is sent from the central Integration Server to local Adapter Engine Java SE.
Empty file handling: The empty file handling controls how the File/FTP sender adapter of the Adapter Engine Java SE handles empty files: The messages with empty files can be either processed or stopped with the creation of an error message.
Prevent overwriting files: The File/FTP receiver adapter of Adapter Engine Java SE allows to control whether files with names that already exist in target directory are to be overwritten.

15. Configuration based on Process Component Interaction Models
The model configurator, that creates the relevant configuration objects in the Integration Directory and groups them in a configuration scenario, allows to use one or multiple Process Component Interaction Models from the Enterprise Services Repository as a template for configuration; i. e. the Model Configurator creates the configuration objects in the Integration Directory based on the SOA artifacts saved in the Process Component Interaction Models together with additional assignments.

16. XI message protocol is supported in the AAEThe XI message protocol is supported via the SOAP adapter. With this messages that are sent to or received from ABAP proxies, other AAE's or Partner Connectivity Kits can be processed locally on AAE. The SOAP adapter is enhanced to accept XI message protocol.

17. End to end IDoc packaging
IDoc sender adapter allows optionally processing an IDoc package that reaches inbound channel of Integration Server from sender to receiver as IDoc package, i.e. IDoc package is not split into single messages that might have to be collected in integration process.

18. IDoc conversion adapter module
The IDoc conversion adapter module allows to convert an IDoc Xml message payload to an IDoc flat file format and vice versa. This IDoc conversion adapter module can be used together with a Java based sender and receiver adapter, optionally with local processing on the AAE, in order to connect to systems with IDoc entry points.

19. WS-Secure Conversation 1.3
This standard defines how to establish and maintain a persistent context for a secure session over which multiple web service invocations might be sent without requiring authentication each time. Currently supported is WS-Secure Conversation for SCT over SSL bootstrap.

20. User-defined message search for business criteria
A new, user-defined message search is available in the message monitoring that allows to search for business relevant information criteria contained in the message payload, such as sales order number or customer ID, as well as adapter-specific message attributes, such as file name for the File/FTP adapter. This new, user-defined message search does not require TREX. The previously introduced index-based message payload search using TREX is still available as well.

21. Cross domain message status overview
The SAP NetWeaver Administrator for PI offers a message overview for all domains that are connected to the SAP NetWeaver Administrator for PI. This enables an overview of the message processing at many levels, from the entire system landscape over domains to individual components, such as Integration Engines, Advanced Adapter Engines, Business Process Engines; therefore this is one further step towards monitoring the overall landscape of SAP NetWeaver PI systems.

22. PI monitoring and configuration capabilities available through SAP Solution Manager
The SAP Solution Manager, which is the central, IT role-based administration and monitoring infrastructure across the whole SAP landscape, provides direct access to main configuration and monitoring capabilities of SAP NetWeaver PI, such as SAP NetWeaver Administrator for PI or SOA Manager.

23. SOA configuration for connectivity of WS & consumers based on SOA Manager
The configuration for connectivity enables the configuration of groups of web services and web service clients in one go; i. e. multiple web services and web service clients do not have to be configured individually, but can be assigned to a configuration setting. The configuration is based on reusable objects, such as Service Groups; as mentioned above, Service Groups bundle all services that are provided by the same logical service provider.

24. Enhancement in migration controller for smooth upgrades of Java proxies to PI 7.1

The migration controller can automatically modify Java proxy based applications of previous SAP NetWeaver PI releases (SAP PI 7.0, SAP XI 3.0) and deploy the modified proxies to the target location of SAP NetWeaver PI 7.1.

SAP PI 7.3 Certification Books (BIT100,BIT400,BIT430,BIT460)

Hi Are you looking for SAP PI 7.3 Certification Books
1.BIT100_EN_Col95_FV_Part_A4 (2011)
2.BIT400_EN_Col95_FV_Part_A4_Notes(2011)
3.BIT430_EN_Col95_FV_Part_A4 (2011)
4.BIT460_EN_Col95_FV_Part_A4_Notes(2) (2011)
4 Books ((~~399$~~) Discount price 99$ Only

Paypal ac : sapmdmtutorials@gmail.com

Once you pay the money send a conformation mail to info@sapnwtraining.com
We will send Download links.

All books for knowledge sharing purpose only. all rights reserved by SAP

SAP PI 7.3 Online Training

SAP PI 7.3 Online Training

For More Information contact

Vist :sapnwtraining.com

info@sapnwtraining.com

cell:918008002022

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