Features of Process Integration PI 7.1

Features of PI7.1:

The Enterprise Services Repository and Registry is the central repository in which service interfaces and enterprise services are modeled and their metadata is stored.

It is made up of
* Enterprise Services Repository
* Services Registry: UDDI (Universal Description, Discovery, and Integration) V3 compliant registry that supports publishing, classifying and discovering services.
1. Web Services Reliable Messaging (WS - RM)
* Asynchronous messaging (EO, EOIO) based on open WS standard
* Native support through Integration Engine (w/o Adapter)
2 Principle Propagation based on SAML
* Forward user context from sender to receiver
* Authorization check in receiving system based on original user
3. High volume support


Message Packing
* Process bulk of messages in one service call (mapping, routing...)
* Reduce context switches
* Enable mass operations on Database.
* For Asynchronous Scenarios

Local Processing in Adapter Engine
* Natural Evolution of Adapter Engine
* Provides mapping , routing to by-pass integration server
* Adapter to adapter communication
* For synchronous and asynchronous scenarios

Major Enhancements for Process Automation
BPEL Adoption
* BPEL4WS 1.1
* WS-BPEL 2.0 preview and implementation
* BPEL4People planned
Human Interaction
* Generic User decision
* Language dependent texts for end user display, enriched with variables.
* Integration Paradigm (design / configuration)
Event Correlation
* Subscription and handling of business process events
* Milestone Monitoring Process definition
Embedded Event Infrastructure
* Collecting, pre-filtering and publication of events across SAP and non--SAP systems.

Major Enhancements for Mapping
Function Libraries
* Re- usable UDF's
Synchronous DB/RFC look-ups
* Use graphical function to model look-ups
Parameterizable Mappings
* Specify mapping parameters at configuration time
Function with multiple results
* Look-up function reads multiple fields
XML Payload Validation
* Validate incoming/Outgoing message against XML Schema
* Forward/Backward error handling
Unified Administration
* Key monitoring functionalities integrated in SAP NW Administrator.
* One place to monitor and administrate SAP NetWeaver

Only ASCS(ABAP SAP Central Services Instance) is supported

SAP Exchange Infrastructure - Points to Remember (Part X)

(contd....)

66. Send step with in a block with ParForEach: the elments of multiline container element are processed in parellel instances of the block at runtime. If the send step within the ParForEach sends a separate message to be received for this message for each element of the multiline container, then send step can activate the corresponding correlation.

67. Abstarct/Message interface can be cretaed from MessageType/IDOC/RFC

68. An integration Process can use all the objects available in the Software Component Version SWCV

69. Loop step in a while loop, loops while the condition is true

70. The outermost block of a process is the process itself

71. Contaner elements defined in the Process Container are visisble in all the blocks, as this is the super block for all the blocks

72. A correlation can be activated either from a Send step or from a Receive step

SAP Exchange Infrastructure - Points to Remember (Part VIII)

(contd....)

61. Receive step to start the process can be the first step of the process or a block or a fork, or a loop. In either case the later fork,block, or loop must be the first step in the process

62. If a message comes, for which there is no waiting receive step then it is received by the process and and stored temporarily

63. The Synchronous Receive step( Receive step which opens sync/async bridge) must be the first step in the Integration Process

64. You can use only one Receive step to open sync/asyn bridge for each Integration Process. This receive step must start the integration process. There must be no other receive steps to start the Integartion Process

65. The Synchronous Receive step can be inserted in the following places
-->Directly after start marker
-->As the first step in a block, if the block is the first step of the Integration Process and has the mode standard
-->As the first step in the fork. If the fork already contains some starting recevie steps, the start process indicator is automatically reset for these steps.

SAP Exchange Infrastructure - Points to Remember (Part VII)

(contd....)

55. All the Nodes or Elements which are having minimum occurance as greater than 0 i.e (mandatory) elements, have to be mapped except the one with fixed occurance(i.e minimum occurance = maximum occurance).

56. The elements or nodes with fixed occurance need not be mapped. They will be created automatically.

57. If the target elements has max occurance > 1 and it is mapped to a source elements then it is cretaed as many times as the source element occurs

58. If the target element has max occurance > 1 and it is mapped to a creating function (generating functions) then the target element is created as many times as minimum occurance and if minmum occurance is 0 then it is created only once.

59. Container supports following methods
void setParameter( String , Object)
Object getParameter(String )

60. Stalled methods can be accessed in this specified function
GlobalContainer getGlobalContainer()
MappingTrace getTrace()
Map getTransformationParameters()
Map can be used to get runtime constants
Object map.get(TransformationConstants.SENDER_SYSTEM)

SAP Exchange Infrastructure - Points to Remember (Part VI)

(contd....)

46. A mandatory element inside a non-mandatory element becomes mandatory only after the parent node is mapped

47. An element or node with Astrix sign means that the node has an maxOccurance>1

48. An element which has fixed occurance (max=min) is a mandatory element and appears in red until it is mapped

49. A node with fixed occurance do not require a mapping and it wil be created automatically

50. A node with min>0 is a mandat0ry element. It appears in red and needs to be mapped

51. Message Mapping works internally by using queues

52. Context changes have impact on UDF in breaking and insertning of hierarchy

53. When comparing two contexts with diverse number of entries, the last value of the context with lesser elements is reiterated

54. Partner Connectivity Kit (PCK) supports RFC, FILE, JMS,SOAP and JDBC adapters

SAP Exchange Infrastructure - Points to Remember (Part V)

(contd....)

38. A target field with maxOccures=N that is assigned a generating function is generated N times, if the maxOccurs = UnBounded then it is generated exactly 5 times

39. Boolean functions
-->retruns true and false string
-->They interpret 1 and true(not case sensitive) as true-value

40. Nodes(which have child elements) with fixed occurance( min==max) will be created automatically without mapping.

41. By using the assignment function we can map the homonymous child elements automatically

42. Substring function in Text category starts with index 0

43. If function interprets value true or 1 as true value

44. In general trailing Zeros of the result are truncated but to maintain the same we can use the FormatNum function of Arithmatic category

45. If max occurance of an element is > 1 then the creating function or genrating function will create node minOccurance times, if minOccurance=0 target node is created once

SAP Exchange Infrastructure - Points to Remember (Part IV)

(contd.....)

28. Each referencing object is created with in the context of the Software Component Version SWCV

29. Business Scenario can refer to any Products( Versions)

30. An action can reference any Interface of the SWCV in which the action was created

31. SWCV is assigned to a Product Version after which only it is possible to refer to Business objects in other SWCV

32. Business scenarios can inturn refer to Application Components( Product versions)

33. A Namespace is transferred to the new version of SWCV only after the development is finished

34. Only after activation the new object Version is released

35. Technically the relation between SWCV and name space is n:m( in genral it is 1:m).
Thus a namespace can appear in different Software Components in exceptional cases

36. Message Exchange in XI is Interface based

37. iXML library is used to parse the document in ABAP objects