i have few questions can you please look at these

[Former Member]

What Messaging System statuses are possible for messages?

Which key concepts of XI are making integration more cost effective?

Is it possible to import a customer developed RFC interfaced into the Int Repository?

Can a Mapping Template be applied to source/target nodes where child nodes have the same names but with different capitalization?

Why is Message Mapping better than XSLT?

Thanks

Samuel

[Former Member · Accepted solution]

Hello Samuel,

here is an overview about the possible message status in SXMB_MONI:

Table: SXMSPMAST

Statusoverview in SXMSPMAST-Table (Field MSGSTATE):

001 --- Recorded

002 --- Being Processed

003 --- Processed Successfully

007 --- Archieved

008 --- Deleted

009 --- Automatic Restart

010 --- Message Branched

011 --- No Receiver Found

012 --- Recorded for Outbound Processing

014 --- System Error --- Manual Restart Possible

016 --- Manual Restart

017 --- Application Error --- Manual Restart Possible

018 --- System Error --- After Automatic Restart

019 --- Changed manually

020 --- Cancelled --- Since already present

021 --- Cancelled manually

022 --- Acknowledgement message stopped

023 --- System Error --- Restart not Possible

024 --- Application Error --- Restart not Possible

025 --- Application Error --- After Automatic Restart

029 --- Transfer to process engine

regards

Dirk

[Former Member]

Possible status message can be different based on the message type (SYNC/ASYNC) also the situation of the runtime instance of the interface.

XI is an EAI and ESB framework which enable us to build integration based on implementation independent services which also provide a lot of agile features such as loose coupling, async and sync mode of integration, adaptor based protocol support, transformation, translation and routing of application data between consumer without having tight coupling between integration parties.

Above mentioned features build a lot of dynamic nature to the integration framework, so that loose coupled configuration of integration scnarios are possible without worrying about application consuming intetation scenario from consumer or provider perspective.

You can import any interfaces into Repository as long as your interfaces are defined using web service technologies such as WSDL, XML, XSD etc

XSLT mapping is running inside an XSLT engine, usually XSLT engine is much resource consuming process.

Thanks

[agasthuri_doss]

Hi,

>>Which key concepts of XI are making integration more cost effective?

Reuse of the developed objects,End to End Montoring, etc

Regards

Agasthuri Doss

[Former Member]

Hi,

Why is Message Mapping better than XSLT?

XI basically provides two types of mappings:

- XSLT mappings (processed by the SAP XSLT processor)

- Java mappings (XI Mapping Toolkit or customer development)

Resource consumption for the mapping depends on the complexity of the mappings and the source document sizes. In general, XSLT mappings require more memory than mapping classes generated by the XI Mapping Toolkit.

So if you have complex and huge messages to transfer it is better to used Grahilca mapping( which interanlly generates Java functions) than xslt.

Let us know if you need more details.

Nilesh

[Former Member]

Hello again,

=> Is it possible to import a customer developed RFC interfaced into the Int Repository?

Of course, you can import any RFC into your Repository.

Develop one and try to import it. You will find it on your import list from the corresponding system in your repository import screen.

Regards

Dirk