XML AND XSD validation

.xml file .xsd file

<!-- Add XML Data --> <xs:schema
<Productlist> xmlns:xs="http://www.w3.org/2001/XMLSchem
<product> a">
<name>apple</name> <xs:element name="Productlist" >
<color>red</color> <xs:complexType>
<price>100</price> <xs:sequence>
</product> <xs:element name="product"
<product> maxOccurs="unbounded">
<name>apple</name> <xs:complexType>
<color>red</color> <xs:sequence>
<price>100</price> <xs:element name="name" />
</product> <xs:element name="color" />
</Productlist> <xs:element name="price"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>

DTD

DTD Stands for Document type Definition

DTD does the same job of XSD

It does not follow the Xml syntax like XSD

XSD Xml schema definition DTD Document type definition

XSD follows the xml syntax DTD is not based on xml syntax

XSD has wide range of datatypes DTD does not have wide range of
datatypes
XSD supports namespace DTD does not support namespaces
XSD is extensible DTD is not extensible
XSD can define the order of the child DTD does not define the order of the
element child element

XPATH: -

Path expression Usage

/ Select the root node
// Select any node matches the name
 . Select the current node
../ Select the parent node
[] Specify the condition
“@” Access the attributes
count(), last(), text() functions

WEB Services

WEB means interlinked servers in network of networks

Web service relies on 4 important things: -

• XML as a data format.

• SOAP (Simple Object Access Protocol) As communication protocol.

• Used exchange only xml based requests and response

• WSDL (Web services description language) as definition of service.

• Used to define the web service. It provides information about what

methods are available in the web server and how to call that service.

• UDDI (universal Description, discovery, and integration) as web service

directory.

• UDDI is a dictionary to register and search web services. [service

broker]

Service provider, broker & consumer

Service consumer is the person sending and receiving the XML file as SAOP.

Service Provider is the Server

Service broker is the UDDI, an external source which takes the WSDL file and gives
the consumer the service. The consumer must search for the service he wants and
download the WSDL file from the UDDI.

Loosely coupled service Is a Service which performs one single operation.

Loosely coupled service Architecture is a service that performs one single operation
with thoughtful planning according to a set of rules and guidelines.

SOA (Service oriented architecture)

When a company's business process is Split into loosely coupled architectures then
its IT architecture is Built on SOA.
Service Orchestration is a process of integrating two or more services together to
automate a business process.

ESB Enterprises Services Bus: -

To perform and function properly a company needs its services to communicate with
each other but in doing so creates an unnecessary problem. So ESB is used as a
middleman or all the services to communicate for smooth and uninterrupted
function of the company.

ESB is a transportation mechanism which transports messages from one location to

another.

A2A transaction is an electronic transaction inside the same company such as a

transaction between HR department and sales department etc.

B2B transaction is between two different companies or Businesses. B2B transactions

are protected by a firewall.

EDI (Electronic Data Interchange) is used to transfer Business data from one
company to another.
Defirent regions us diverse types of EDI for Example All the companies in the North
America and Canada use ANSI X12 and all the companies in Europe and Asia use
EDIFACT

ROSETTANET is a term representing a group of companies which agreed upon a

business transaction standard to be used globally.

PIP Stands for partner Interface Process.

PIP is the definition of the transaction, or it tells how that transaction needs to be
done.

RNIF Stands for ROSETTANET IMPLEMENTATION FRAMEWORK.

RNIF is a protocol to exchange PIP.

SAP NetWeaver is a Tecnology Platform for running business Applications.

SAP NetWeaver ==> SAP Business suite ==> SAP ERP, SAP CRM, SAP SRM, SAP
SCM,
SAP PLM.

In this flow chat of SAP Think Business suite as a platform like MS office and all the
sub parts are applications that perform different tasks such as the excel performs a
specific task in MS office.

SAP NetWeaver has applications that connect people, process, and Information.

Application platform includes both the server (java, ABAP) and the database (Oracle,
Hana).
Hear java is an Enterprise portal and ABAP is an SAP ECC. The new SAP PO uses
both the java and ABAP servers.

SAP PI/PO

PI -> process Integration

PI is a tool for EDI (electric data integration) to mediate travel of information
between applications.

PO -> process Orchestration

PO= PI + BPM (Business Process management) + BRM (Business rules

management)

PI is replaced by AEX (Advanced Adapter Engine Extended)

AEX Contains components like Data Conversion, Routing, Connectivity, and

messaging System.

AEX first sends the message received from the application to BPM with or without
data conversion ones the BPM receives the information and processes that
information and sends it back to the BPM.

AEX Architecture: -

Design --> ESR (enterprise service landscape)

Configuration --> ID (Integration Directory)

Runtime --> Runtime cache, AAE (Advance Adapter Engine), AS java (NetWeaver
service)

Components --> SLD (System Landscape Directory), SR (Service registry),

monitoring (PIMON, NWA).

Note – Only AEX transfers the data between applications. BPM does not transfer or communicate with
applications

BPM uses notations such as events, Activities, and gateways.

Events are functions

Activities are grout of events

Gateways are Routing conditions.

Lifecycle of BPM

Design  Model Execute  Monitor  Improve Design

SLD (SYSTEM LANDSCAPE DIRECTORY)

SLD acts as a central repository of System landscapes and Software components
together.

SLD is split into 3 parts Landscape, software catalog and development.

Landscape => is used to define technical system, landscape, and business system

Software catalog is used to define software catalog and product.

Development is used to define name reservation and CIM instance.

Business System is linked to technical system.

Software components are linked to product.

Business systems are imported in ID.

Software components are imported in ESR.

ID Integration directory AND ESR Enterprise service

repository
End to End flow of a basic SAP PO

Steps 1 to 5 are done in ESD (Enterprise Service Builder).

From step 6 ID (Integration Definition) is used.

Step 1: - Create a name space in ESB tool then create a Data type inside the
namespace.

Step 2: - Create a message type from the data type created earlier.

Step 3: - Create Two Service Interfaces for receiving messages (inbound) and for
sending messages (outbound).

Step 4: - Create a message mapping for the message that was created earlier.
Source message and the target message are the same message that was created
but can be manipulated according to the requirement.

Step 5: - Now create an operation mapping with the inbound and outbound
interfaces (drag and drop the inbound interface and outbound interface). If the
above process is done right, then the relevant message mapping needed for the
operation mapping is automatically displayed in the help box in the message
mapping section of the operation mapping editor. [important]

Step 6: - Now Open the ID tool in SAP NetWeaver.

Step 7: -In the ID tool create a Scenario/folder and assign a business system to the
Scenario.

Step 8: - Create two party components in the Scenario one for the Source and one
for the Target.

Step 9: - Create two business Component with the party in the scenario. Business
component can be created without the help of the party also. If we use a Logical
business system then there is no use of Business component we Either use business
system or a business components in our scenario according to our requirements.

Step 10: - Create a Communication channel for the sender and receiver.
Communication channel is where you assign the type of adapter the sender or the
receiver uses in the transaction of their message. [important]

Step 11: - Go to the two business components that were created in step 9. Now
Assign the proper interface you have created in the ESD. Use the outbound
interface for the Source (Sender) BC and inbound (Receiver) for the target BC.

Step 12: -Create an integration configuration or IOC Configuration. To create an

integration configuration component u will need the source party if u assign the
Business component to the party the communication channel is automatically
populated. The interface is assigned to its respective Business component so the
interface is also available in the help box.

Step 13: - After IOC is created the u need to assign the inbound process Which is the
sender channel.

Step14: - In the receiver section assign the receiver business Component in the
communication Component box.

Step 15: -in the receiver interface section select the BC and choose the proper
Operation Mapping created in the EDS tool

Step 16: - navigate to the outbound process and select the receiver communication
channel.

Note: - do not forget to save and activate your components.

Adapters
1. File Adapter
1.1. An FTP server is used to check if our message is being sent from one file to another
without any interruptions or corruption of the data.
1.2. Credentials need to be used in Communication channel are hostname, directory path,
username and password.
2. JDBC Adapter
 2.1. Data grid from JetBrains to create a table in oracle data base and make the data available
for the sender and receiver channel to access the data
2.2. The data type for sender and receiver varies because a statement needs to be executed
in the SQL format to pull the data from the database.

Sender data type format Receiver data type format

1. Row STATMENT
1.1. ID 1. DB TABLENAME
1.2. WID 1.1. ACTION (INSERT, UPDATE OR
1.3. NAME DELETE)
1.4. GENDER 1.2. TABLE
1.5. DEPARTMENT 1.3. ACCESS
1.6. STARTDATE 1.3.1. ID
1.7. ENDDATE 1.3.2. WID
1.8. SHIFT 1.3.3. NAME
1.9. HOURS 1.3.4. GENDER
1.10. STATES 1.3.5. DEPARTMENT
1.3.6. STARTDATE
1.3.7. ENDDATE
1.3.8. SHIFT
1.3.9. HOURS
1.3.10. STATES

Example data structure showing the difference between the input petameters and output
parameters of a JDBC-to-JDBC scenario.

3. SOAP Adapter
3.1. Soap adapter uses a webservice created using tomcat server in the eclipse.
3.2. Navigate to dynamic web project mode select the tomcat server in configuration and
create a server
3.3. Now create a java file (.class file) and add it to a web service.
3.4. To create a web service, navigate to web service in new tab and attach your .java file to
the webservice.
3.5. Select Apache axis2 if Apache axis (deprecated) is selected. Publish the server.
3.6. A web service channel can be tested in two ways using WSNavigater(in the sap
NetWeaver) or using SOAPUI Tool
4. HTTP_AAE Adapter
4.1. Created using eclipse (dynamic web project)
4.2. Import jersey bundle and copy paste it in lib folder
4.3. Import path annotation and give the .java file a path name in the annotation
4.4. Now write a return statement in a function inside the class and use languages like xml or
html for the return statement.
@GET
4.5. Add "GET” annotation
4.6. Add “Producer” annotation so that the compiler understands in what language the
return statement should be read in. Mention that the MediaType of the language is xml
 or html.
@Producer(MediaType.TEXT_XML)
4.7. In web.xml file add the servlet configurations
4.8. Run the project
4.9. After execution add the path name to the URL to get the output.
4.10. Copy the URL and use it while developing the interface.
5. REST Adapted
5.1. REST adapter uses a JSON to pull the data
5.2. Create a dummy JSON data or use a placeholder for practice
5.3. Copy the URL and use it while creating an interface.
6. IDOC_AEE connection Inbound
6.1.
7. IDOC_ACC connection Outbound
8. RFC Adapter
8.1. Used to call a sincereness call to an SAP ECC while a transaction is happening and bind
the fetched data to the output of the current transaction
9. Mail Adapter
9.1. The mail adapter their r some
manhttps://learning.sap.com/service/media/topic/cdf0ea27-92f7-4a64-956e-
1b9ba61e590d/BIT500_22_en-US_media/BIT500_22_en-US_images/
SAP_PI_JAVA_Evolution_Image.pngdatory fields like from address, to address, subject
either the sender can manually enter such details or Thay can be integrated in xml file
and select “use mail package” check box
9.2. It reduces errors by limiting access to the input data for the sender company.

Each Adapter has its own Requirements and mandatory fields need to be filled.

Async and Sync bridge

An async sync bridge creates a connection between two channels but instead of assigning both the
channels with the same type of communication method it assigns deferent communication methods for
sender and receiver channel. In this case the sender channel communication method is a Async but the
receiver communication channel is a synchronies communication channel

The receivers answer to the call is rerouted to another channel which is not the original sender channel.

Sync, async bridge is the exact opposite of the async, sync bridge

Sync, async bridge is the bridge

Intermediate Document (IDoc)

Intermediate Document (IDoc) is the standard SAP format for Electronic Data Interchange (EDI) between
systems. Different message types (such as delivery confirmations or purchase orders) normally represent
different specific formats, the IDoc types. However, multiple message types with related content can be
assigned to one IDoc type: For example, the IDoc type ORDERS01 transfers the "logical" message types
ORDERS (purchase order) and ORDRSP (order confirmation).
Business Application Programming Interfaces (BAPI)