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

SAP Exchange Infrastructure - Points to Remember (Part III)

(contd....)

19. XI has extended the actual SOAP format by extending SOAP header with Error Header or Hop List

20. XI SOAP body will only contain the Manifest element which inturn will actually point to actual document that is being sent

21. There are three type of payloads in XI Soap Body Main Payload, Trace Payload and Optional Payload

22. Technically XI is sent as a multipart MIME document

23. MIME is the Internet standard that allows arbitrary digital documents to be sent over Internet

24. Text files that are to be processed by the Integration Server must be based on the code page UTF-8. The file/adapter can use every code page that is installed in the Java Runtime environment

25. The Sender Http-adapter is an ICF service on the Integration Service on path /sap/xi/adapter_plain

26. Tracing is not activated by default

27. Logging is activated by default

SAP Exchange Infrastructure - Points to Remember (Part II)

(contd....)

10. Each system is related to one particular Integration Server which makes change management in the XI land scape easier

11. All design work in the Integration Directory IR is organised by Software Component Version SWCV

12. Proxies are generated from the WSDL description of Interface objects

13. Proxies will have the same attributes as Messages Interface

14. The type of Message Interfaces detemrines the type of Proxies generated

15. The message type will become parameters for Proxies. The output message type is named with OUTPUT and Input message type is named with INPUT.

16. Integration Server uses the cached copy of the Configuration developed in Integration Directory ID to process the messages delivered to the pipe line

17. SOAP message is sent in the HTTP Post request

18. Runtime WorkBench ( RWB) Messaege Monitoring is only available for asynchronous messages unless the XI pipeline is configured to persist synchronous messages

SAP Exchange Infrastructure - Points to Remember (Part I)

1. UDDI: Universal Description, Discovery and Integration

2. XI is not a single component rather it is a collection of components that work together flexibily to implement Integration Scenarios

3. At Runtime, Integration Engine is based on the solid architecture of SAP Web Application Server

4. Integration Directory ID & Integration Repository IR are fat client apllications

5. SLD is a server application and XI is a client application for SLD

6. XI Adapter engine runs on SAP WAS J2EE engine

7. CrossComponent Bussiness Process = Integration process

8. A product can come in many versions. Each product can have one or more Software Components and each Software Component can come in one or more versions

9. While creating a Business System the Logical System name is mandatory if the system is a sender or receiver of IDOCS. The IDOC adapter will make use of this name to resolve the Business System into ALE logical system name and viceversa.

SAP Exchange Infrastructure - BPM Concepts FAQ (Part III)

(contd....)

20. What is the URL for CPACache?
Answer: http://host:port/CPACache

21. ............... Url is used to refresh the cache in pull mode
Answer: :/CPACache">http://:/CPACache

30. CPA-Cache is updated using PULL mode by URL: :/CPACache/refresh?mode=delta/full">http://:/CPACache/refresh?mode=delta/full

31. CPA-Cache is updated using PUSH mode by Integration Directory ID

32. Pull-Mode : use XIDIRUSER

33. If cache type is PCK then one can upload schema with http://host:port/CPACache/schemaupload.jsp

SAP Exchange Infrastructure - BPM Concepts FAQ (Part II)

(contd....)

10. What is a loose coupling for messages?
Answer: Correlation

11. What are the unique steps that exist in BPM but not in workflow?
Answer: Transform, Send

12. When ever the Start event occurs in XI which user starts the Workflow?
Answer: WF-BATCH logs in to start the workflow

13. Which transaction code is used to see the generated work flow of Integration process?
Answer: SWDD

14. Which transaction is used for customizing the Bussiness Process Engine?
Answer: SWF_XI_CUSTOMIZING

15. What is the return code when the Workflow version is created without errors?
Answer: ZERO

16. Which transaction code is used for monitoring Sync/ Async messages?
Answer: SXMB_SAMONI

17. Which transaction code is used for monitoring processing and workitems?
Answer: SWI1

18. Which transaction code is used for checking events?
Answer: SWEQADM

19. Which report is used for checking active correlations?
Answer: RSWF_CRL_MAINTAIN

SAP Exchange Infrastructure - BPM Concepts FAQ (Part I)

1. How many Sync/ Async bridges can be defined in an Integration Process?
Answer: One

2. What are the possible values for Acknowledgement property for Asynchronous Send step?Answer: a) None( Default) b) Transport Acknowledgement c) Application Acknowledgment

3. What are the various possible options for Receiever from property of Send step?
Answer: a) SendContext( Default) b) ReceiverList c) ResponseMessage

4. How many Send steps can be defined in an Integration Process which has mode as closes sync/async bridge?
Answer: One

5. Is it possible to to do value mapping with in the transformation step of BPM?
Answer: NO. Since no Receiver information is available in the transformation step.

6. What are the possible values for Mode property for Block step?
Answer: a) ParForEach b) ForEach

7. When does the WSDL view available in BPM(In Output Area)?
Answer: When Edit area has BPELWS view

8. Which control can trigger a process?
Answer: Receiver step

9. What is the basis for the visibility of Container variables?
Answer: Block Hierarchy