User talk:Rafaelgramajo

Transaction codes | TBIT 40 errors

Dudas sobre las 100 preguntas de exámen que nos pasó Maxi
1. En la pregunta 18 la opción correcta es b? (creo que si, un integration process es lo mismo que una BPM)

18. Integration Processes are built using... (choose the correct answer) a. WSDL b. BPEL c. XSD d. JCL (Java Connector Language)

El TBIT40 en la página 23 dice All XI objects are described using web standards: Web Services Description Language (WSDL) for interfaces, XML Schema Definition Language (XSD) for messages and data types, XPath for “slicing and dicing” data in XML documents, and Business Process Execution Language (BPEL) for Integration Processes (Business Processes).

Y en la página 30 dice Integration Processes are built using the web standard Business Process Execution Language for Web Services (BPEL4WS or just BPEL).

2. Alguien encontró algo en algún documento acerca de la 27?

27. How do you classify NAME SPACE in an R/3 Environment? a) Equivalent to function group    b) Equivalent to devepment class c) Equivalent to function module    d) Equivalent to BAPI

3. En la 29 la opción correcta es la c?

29. A Customer has WAS 6.2 and has decided to use XI... (choose the correct answer) a) He cannot use XI unless WAS 6.2 is upgraded to WAS 6.4    b) Can use XI with some additional patches c) WAS 6.2 already has XI in it. No need of any additional software

El TBIT40 en la página 20 dice There are no additional adapters needed, when the Integration Server connects to a new mySAP solution which is based on the SAP Web Application Server 6.20, as the components of these solutions carry themselves a “small” Integration Engine – those systems can directly interact and communicate with the Integration Server to exchange XML messages.

4. Alguien encontró algo sobre la 32?

32. What doesn’t get transported when the configuration is released? (choose the correct answer) 1. All Objects will get transported 2. Generated proxies and application coding in the application components does not get   transported when the configuration is released. 3. Only application coding will not get transported. 4. Only generated proxies will not get transported.

5. Un sender agreement define un binding entre un sender communication channel y una output interface. ¿Porqué los HTTP y IDOC adapters no necesitan un sender agreement?

38. What adapters don’t need Sender Agreement? 1. HTTP, IDOC 2. IDOC, RFC. 3. IDOC, JMS 4. JDBC, JMS

6. Existe un mail adapter? ver pregunta 39

39. What is the Protocol followed for Mail Adapter? (choose the correct answers) 1. SMTP 2. IMAP 3. POP3 4. POP4

7. Un JDBC adapter se puede configurar como sender communication channel? Cómo sería el caso? Una base de datos no actúa siempre como Receiver? Ver pregunta 40

41. Can a JDBC adapter query the database table? If yes, what are different possibilities? a) Yes. You can configure sender and receiver communication channels. A special XML format       is defined for content coming from the Integration Engine. This canonical format        enables SQL Insert, Update, Select, Delete or stored procedure statements to be        processed. A message is always processed in exactly one database transaction.     b) JDBC adapter cannot insert records in the database. c) We should not insert, update records in the database directly.

8. Alguien puede por este medio explicar la 46 en 3 líneas?

46. “ Fields under a node with a minoccurs of ZERO has been mapped.” The values don’t appear in the target result, what could be wrong? 1. The parent node has not been assigned 2. Parent node has cardinality 0…unbounded 3. Parent node has many fields

9. Además de la opción 1 también es correcta la opción 3?

56. Which of these are true/false with user defined functions? 1. User defined functions are accessible only in the mapping where they are created 2. User defined functions are visible across namespace 3. User defined functions accessed in other mapping by copying it to that mapping 4. User defined functions are accessible in any mapping in a software component version

10. Alguien tiene clara la 58?

58. An Idoc has been sent by a sender system to XI, but the idoc is not received at the XI system which of these could be true/false 1. The destination system from the sender system to XI is not configured correctly 2. The metadata in XI was copied/generated from the sender Idoc is corrupted 3. The destination system from XI to sender system is not defined correctly 4. Sender channel is not configured

11. La respuesta 2 no es también una opción válida?

60. To import the metadata from an R/3 system which of this is true/false 1. The import permitted in Software component need to be selected 2. You have to create ‘ALE’ Name in SLD 3. You need to login to the destination (R/3) with a valid user 4. You need to login to destination(R/3) with a User having administrator rights

12. Es correcta la opcion b? El monitoring no es siempre centralizado?

65. You would install Adapter engine de-centrally a. To install PCK b. To monitor the messages de-centrally c. To share load with the central adapter engine and increase performance

13. En la 66 no se necesitan ambos communication channels? (sender para ir a XI y receiver para llegar a la base de datos) Ver también la 7 mas arriba.

66. To Receive the data using ‘Select with JDBC adapter you would a. You would configure a receiver channel b. you would configure a sender channel

14. Qué es BP?

67. You find that the status in transaction ‘SXI_CACHE’ is not equal to 0. Which of the following would you perform? a. Check the condition of BP in Integration Repository b. Activate the BP in ‘SXI_CHACHE’ c. Activate the BP in Integration Directory

15. Alguien puede explicar esto?

77. While testing message mapping the source message occurs 3 times but the target message occurs only once? What can be the reason ? a) Target cardinality is not defined sufficiently    b) Source cannot repeat c) Message mapping cannot handle multiple values

Dudas sobre el 2do doc (el de las 72 preguntas)
1. Agregar aca

Otras dudas

 * 1) EL TBIT 40 está equivocado en la página 26 donde dice 6.40 debería ser 6.20? Diferencias entre 6.20 y 6.40?
 * 2) Hay un SAP XI adapter que es distinto al RFC adapter y al IDOC adapter?
 * 3) ¿Qué campos se utilizan en la definición de un Software Product?
 * 4) ¿Qué campos se utilizan en la definición de cada uno de los tipos de Technical System?
 * 5) ¿Para cada tipo de Technical System como es la relación con un Business System?
 * 6) ¿Se puede crear un Technical System sin Software Products?
 * 7) ¿Se puede crear un Technical System sin Software Components?
 * 8) ¿Cómo es la relación entre un Sofware Product y un Software Component Version (SWCV)?
 * 9) Cuando se define un SWC Dependency hay 3 opciones (build time, installation time, metadata request). ¿Qué es cada opción?
 * 10) Cuando se importa un SWCV, ¿hace falta importar sus Dependent SWCVs? TBIT 40, page 58: A dependency can be defined in the SLD. This dependency will be automatically detected in the Integration Repository
 * 11) ¿Es posible editar un SWCV en el Integration Directory (ID) para agregarle namespaces y SAP connection data?
 * 12) ¿Porqué no se puede usar un Message Interface de tipo Abstract para proxy generation? Porque necesita mode (sync | sync) and direction (in | out).
 * 13) ¿Qué son los data types enhancements for ABAP? ¿Para Java no hay tal cosa? Para Java no existen
 * 14) ¿El nombre de un Message Interface es único para XI? No. Tiene que ser único dentro de un namespace
 * 15) ¿Cómo se define como Service un Business System del SLD en el ID? ¿Se importa?
 * 16) ¿Hay un error en el TBIT40 en 4-33?
 * 17) ¿Se puede crear un mismo namespace en distintos SWCV? Si.
 * 18) ¿El Integration Runtime es todo ABAP?
 * 19) ¿Se pueden definir Message Types utilizando Data Types de distintos namespaces?
 * 20) ¿El namespace de un Message Type puede ser distinto del de su Data Type?
 * 21) ¿Un Interface Mapping tiene un namespace propio? ¿Éste puede ser distinto a los namespaces de las Interface Message?
 * 22) En TBIT40 ejercicio 3, página 8, dice "Note that for plain http communicationn, no Sender Communication Channel is required". ¿Cómo es esto? Porque XI corre sobre el SAP WebAS y utiliza un ICF Service de este para plain HTTP.
 * 23) En TBIT40 ejercicio 5, Maxi dijo que corrijieramos el nombre de un Message Interface, pero ¿no estaban bién todos nombres?
 * 24) Para una BPM nunca se define un Receiver Agreement o Communication Channel. ¿Porqué?
 * 25) ¿El workflow engine del SAP WebAS es ABAP? Si
 * 26) ¿Porqué en BMP 8-7 dice que una 'BPM is concerned with human interaction, planned of expontaneous'? ¿A qué se refiere con 'technical monitoring of business processes'?
 * 27) TBIT40 9-4. ¿El Runtime Workbench (RWB) es J2EE y la Business Process Engine e Integration Engine ABAP?
 * 28) ¿Qué son los CCMS templates?
 * 29) ¿Cuál es la diferencia entre trace y log?
 * 30) Hay 2 tipos de log viewers, integrated y standalone. The standalone access any number of WebAS servers (ABAP/J2EE). El integrated solo accede al WebAS Java?
 * 31) ¿Qué son las Conditions y Actions for troubleshooting?
 * 32) TBIT41-4. The business scenario in the ID is not the same object in the IR. ¿Es así? En otro lugar dice que un escenario solo se puede crear en el ID. ¿? Un Business Scenario se crea en el IR y se importa en el ID via a wizard. En el TBIT40, page 138,
 * 33) ¿Después de la ejecución de una BPM se puede ejecutar el Pipeline?
 * 34) TBIT44-10. A namespace is transferred to a new version of a SWC after development is finished (Release-Transfer). ¿Se puede crear una nueva versión de un SWC en base a una anterior versión?
 * 35) TBIT44, ejercicio 0. Un SWCV puede tener una Usage Dependency de un SWCV que esta en otro Software Product?
 * 36) Además del los SWCVs ¿qué mas se importa en el ID desde el IR?
 * 37) En el ID es necesario importar los Business Systems?
 * 38) Un Business System, lo mismo que un un Technical System puede ser de 4 tipos (WebAS ABAP, WebAS Java, Standalone Java, Third party)?
 * 39) TBIT 40, página 133. The receiver can be a party or a service. A party?
 * 40) Donde se crea un Business Service? En el ID
 * 41) Que adaptadores no necesitan sender agreement y cuales no necesitan receiver agreement?
 * 42) PCK requires to install a WebAS only J2EE? Si
 * 43) Un mapping puede hacer esto? n:1 Transformation: Bundles multiple messages into one message, for example, individual purchase order items into one purchase order. Y esto? 1:n Transformation: Splits a message into multiple messages, for example, a purchase order into the individual purchase order items.
 * 44) Porque esto? For a BPM no receiver agreement or communication channel is necessary. Porque una BPM esta dentro de XI, todo es XML, no hace falta un adapter.

Datos para estudiar de memoria
1. Preset namespaces para IDOCs y RFCs


 * urn:sap-com:document:sap:idoc:messages
 * urn:sap-com:document:sap:rfc:functions

2. Pipeline. A Pipeline Service is an ABAP Objects class that performs a particular processing step on a message. http:// : /sap/xi/engine?type=entry

Receiver Identification Interface Determination (o Interface Identification) Message Branch (o Message Split according to Receiver list) Message Mapping (o Request Message Mapping) Output Binding (o Technical Routing) Call Adapter Request Message Mapping (esto aveces no aparece en los docs)

Config: | Sender agree | Recvr detr | IF detr | Mapping | Recvr agree Piplne: |             | Recvr iden | IF detr | Branch  | Out binding | Call adapter | (Req Mess Mapping) BMP:   | - Routing - | Mapping | Chnnl deter Process Execution <-  Correlation Handling

3. XSLT statements not supported:  and 

4. Container types: Simple, Abstract interface and Receiver

5. Un Java mapping tiene que implementar com.sap.aii.mapping.api.StreamTransformation Y tiene que llamar a los métodos execute and setParameter

6. For ABAP mapping in Exchange Profile must set com.sap.aii.repository.mapping.additionaltypes = R3_ABAP | Abap-class; R3_XSLT | XSL

7. JAR file required to perform a Java mapping: aii_map_api.jar

8. The 3 IDOC related transactions in XI are: IDX1 IDX2 IDX5

9. Class that must be implemented for ABAP mapping: IF_MAPPIG... Hay otras??

10. Basic message flow: Receiver determination -> Channel determination -> Mapping

11. Error handling: Sync (error message sent back to sender) | Async (error made persistent)

12. Information from the software catalog is used in the IR to organize development

13. Information from the systems catalog is used in the ID to drive the specific configuration of Integration scenarios

14. The logical system name (ALE name) is mandatory in case the Business system will act as a sender or receiver of IDOCs (Business system is of type WebAS ABAP). ALE name is uppercase and it is maintained in the R/3

15. In the ID you set connection data to R/3 (system, client, message server, group) and one or more namespaces. You can also set control information ¿?

16. Every object in the IR is identify by SWCV, namespace, and name

17. The message interface is the starting point for proxy generation (Java and ABAP)

18. In message interfaces there are fault messages corresponding to SOAP Fault type (except for outbound asynchronous case)

19. Message types in the Integration Repository translate to message elements in the WSDL standard; Data Types in the Integration Repository map to type elements in WSDL; and Message Interfaces are portType elements in WSDL.

20. A context object is able to access data that is in the payload or in the header of a message

21. Proxy. Separete business logic from XI. Outside-in development approach. Adapterless. SAP WebAS 6.20+. Hides technical details from app. developer. Guaranteed delivery. Generated from WSDL of message interfaces (MI). Same attributes as message intefaces (in/out sync/async). Some restrictions in data types conversions. Java proxy generated in IR. ABAP proxy generated in the Application System (not in the Integration Server) -> HTTP destination in the Integration Server is maintained in SM59 to retrieve the WSDL of the MI. Outbound MI generate client proxies. Inbound MI generate server proxies. ABAP proxy methods: EXECUTE_SYNCHRONOUS, EXECUTE_ASYNCHRONOUS

22. When a message arrives: (Sender Service, Sender interface, Namespace) as key

23. ID tasks: Collaboration Profile | Logical Routing | Collaboration Agreement
 * Collaboration profile: Specify all possible configurations of Services and Communication channels for a message exchange
 * Logical Routing: Determine the Receiver Service and the Message Interface in that Receiver Service
 * Collaboration Agreement: Define the Communication Channel (adapter configuration) to use for a particular combination of Sender Service and Receiver Service.

24. A Party (Party name, Description, Agency, Schema, Identifier) is defined in the ID. New for Business Service or Business Process and Assign Business System

25. Communication Channel common configuration: adapter type, URL, mode (sender | receiver), transport protocol, message protocol, adapter engine)

26. In receiver agreements, you can also change elements of the message header. Header mapping (sender party, sender service, receiver party, receiver service). Content can be provided from (Constant value, Message Payload, Context object)

27. In the Business Scenario wizard services must not be assigned to a communication party

28. The value mapping function is inserted into a mapping in the Integration Repository at design time; but the value mapping table is maintained in the Integration Directory at configuration time

29. The following changes have been made in the Integration Directory to fulfill B2B requirements: The new object “Agency” has been introduced | The terms “Namespace“ and “Object Type“ are subsumed under the new term “Identification Scheme“. Two types: Value Mapping Agencies | Value Mapping Group

30. Preliminary receiver determination: Find out at the application level whether a receiver exists for a given outbound interface. Avoid unnecessary construction and parsing of message by runtime engine.

31. Cache activated when the change list is activated. Cache notifications are a history of cache updates in ID.

32. XI message is sent as a multipart-MIME document.

33. The Adapter Engine has built in capabilities for message queueing, tracing, logging. It uses a different runtime mechanism for sending message than an Integration Server; in other words, the adapter engine can formulate and send an XI-SOAP message without requiring an integration engine.

34. The SAP Web Application Server (version 6.20 or higher) has a built-in Integration Engine to enable communication with the Integration Server in the native XISOAP format. This enables out-of-the-box integration of SAP applications via proxies.

35. RFC es siempre syncr? Synchronous messages are not persisted on the Integration Server unless logging is switched on.

36. Para pensar. Quality of Service can be BE, EO, or EOIO. Those correspond to sRCF, tRFC, and qRFC; but they apply for all adapter types including RFC?

37. SXI_CACHE Runtime cache (party, services, recei det, interf det, send/recei agree, comm.chann, mapping, swcv, bus.proc.) Access to Adapter Engine cache (AE cache). Transaction IDX1 is used to configure a port to use for retrieving this IDOC metadata. The IDOC cache can be viewed in transaction IDX2. Log on to the XI system and check the inbound queue to see if the IDoc was received (IDX5)

38. Runtime WorkBench RWB. Java monitoring tool (web-based interface)

39. Message Monitoring. Similar to SXI_MONITOR (Based on SAP standard monitoring solutions). Used by En-to-End monitoring. For async messages and sync only if Pipeline config. set to persist sync (BE). Centralization of Integration Engine and Adapter Framework message monitorings. You can also view referencing and referenced messages.

40. Component Monitoring. For ABAP and Java components (configuration and CCMS status(red, yellow, green, or gray -> all, red, red & yellow)), including decentral adapter engine). Ping and sending of messages. For integr. engines, adapter engines, IR, ID, RWB itself.

41. Performance Monitoring. Enhance performance statistics (user defined criteria). Meassuring of throughput and latency | Message Alerting. Based on Central Alerting Framework (e-mail, SMS)

42. End-to-End Monitoring Configuration. Prerequisite: active PMI by SXMB_ADM. a) Monitor message processing steps in a number of components (to be configured). b) Monitor the path of individual messages through these components, from start to end. How it works: - select and configure components - send messages - choose end-to-end monitoring - choose display. # Process overview: total number of processed messages and the number of messages with errors for each component. # Instance view: displays graphically the path of a specific message through the components involved.

43. Performance Monitoring. Only displays messages that are processed successfully within the specified time interval. Measured data: throughput and latency. Selection and aggregation by XI component, time range, and Message attributes (sender, receiver, message type). Extended search by using sender and receiver. Data to display: | Aggregated throughput data for message processing | Aggregated detailed data for message processing performance | Individual detailed data for message processing performance.

44. Alert Configuration. Active monitoring (CCMS Alerts + message-oriented alerts). Transaction ALRTCATDEF to define the text, the priority, number of delivery, etc. for the alert. a) Define an alert category. b) Create a rule in which you use a defined alert category... ? ver mejor esto

45. Cache Monitoring. Enables you to display representations from the value mapping table that are currently located in the runtime cache of the Integration Engine or Adapter Engine (Context, Issuing agency, Identification schemes, Value)

46. '''TBIT40. Page 20''': Certain adapters are needed in cases where the Integration Server is to exchange messages with an R/3 system based on a basis kernel lower than 6.20 (RFC adapter, IDoc adapter), or in order to connect to a specific marketplace (depending on the marketplace product). There are no additional adapters needed, when the Integration Server connects to a new mySAP solution which is based on the SAP Web Application Server 6.20, as the components of these solutions carry themselves a “small” Integration Engine – those systems can directly interact and communicate with the Integration Server to exchange XML messages. Page 262: Applications based on SAP Web Application Server version 6.20 or higher can communicate with the XI in the native XI-SOAP format via proxies. All other applications, including “legacy” SAP systems (those on Basis releases lower than Version 6.20), communicate with the XI via adapters. Page 194: The SAP Web Application Server (version 6.20 or higher) has a built-in Integration Engine to enable communication with the Integration Server in the native XISOAP format. This enables out-of-the-box integration of SAP applications via proxies. Page 26: Communication between mySAP systems based on the SAP Web application Server version 6.40 or higher communicate natively with the XI; other systems, including those using B2B standards such as RosettaNet, CIDX, and PIDX, communicate via adapters.

47. Dual Connectivity Strategy: 1. The Adapter Framework allows SAP and partners to deliver adapters that plug in to the XI environment; 2. Adherence to web standards allows easy integration with other EAI providers.

48. BPMs are concerned with human interaction, planned or spontaneous. No

49. Service Service users: XIREPUSER RWB DIR IS LD APPL AF; password XIPASS; roles:        SAP_XI_IR_SERV_USER ID APPL IS RWB SAP_XI_AF_SERV_USER_MAIN SAP_BC_AI_LANDSCAPE_DB_RFC http://. /exchangeProfile;

50. CPACache http://host:port/CPACache/refresh?mode=delta|full (XIDIRUSER user) Registration/Push Mode | Pull Mode (delta or full refresh)

51. SXI_CACHE

52. TBDL DLNG DLVD FAIL HOLD WAIT NDLVD

Siglas no muy comunes
CIM Common Information Model

ICM Internet Communication Manager

ICF Internet Communication Framework

CAF Composite Application Framework

ESA Enterprise Services Architecture

UDDI Universal Description, Discovery and Integration

CCMS (SAP) Computing Center Management System

PPMS

ALE Application Link Enabled

PMI Process Monitoring Infrastructure

PAM Process Architecture Model

PCM Process Configuration Model

PEM Process Execution Model

SAP transaction codes
SXMB_ADM, Integration Engine Administration

SXMB_IFR, Start Integration Builder

SXMB_MONI, Integration Engine monitoring (tambien SXI_MONITOR?)

SXI_CACHE, Integration Server runtime cache (BPE, Integration Engine). Trigger a partial of full refresh

CPA CACHE, Central and Decentral Adapter Engine cache (AE cache)

SPROXY, ABAP proxy generation

SICF, Pipeline entry point

ALRTCATDEF define an alert: text, priority, number of delivery (role SAP_XI_ADMINISTRATOR)