JDBC to MAIL

Hi All;
I am doing JDBC to Mail adapter scenario, I just like to now how my mail adapter
will send the message to the targer mail server.
How can I come to know my XI server is connected with Net or not. I am using XI3.0 SP-9, please let me know I can achive success in thi scenario.
I want to send the JDBC - XML as a mail from XI to the target mail server. If any one tried this please share your thought with me. I want to try with Gmail, Yahoo, AOL or Rediff server.
Thanks
Farooq.

Typically you would do this with your company's SMTP server or IMAP4 if you have that type of setup.
Since you dont have one - you can try this --- if it works, pls report so we all know.
In communication channel config use SMTP...
URL -- URL: smtp://smtp.google.com
Use your gmail account login and it seems the reply to will be overwritten.
<a href="http://lifehacker.com/software/email-apps/how-to-use-gmail-as-your-smtp-server-111166.php">See Here for more details.....</a>
post the results...
sincerely,
--NM

Similar Messages

JDBC to Mail scenario with XSLT mapping

Hi all,
I am working on JDBC to Mail scenario. We have to pick the data from Oracle system and mail has to be sent with an attached Excel file.
I am doing this scenario by using of following blog.
eMail Report as Attachment (Excel/Word)
I am getting the output as an attachment but iam not getting the data.
the same xslt coding iam using which has given in blog.
any idea........
Thanks,
Sreedhar Goud.

Hi Gaurav,
JDBC is picking the data.In SXMB_MONI outbound payload iam able to see the data but in inbound payload there is no data.i think the problem is in XSLT code only.
My source structure:
<?xml version="1.0" encoding="utf-8" ?>
<ns:MT_ORMS_Errors xmlns:ns="http://mg.adityabirla.com/mg/orms/mail">
    <row>
        <INTERFACE_NAME>MG_SAP_RMS_ITEM_PKG</INTERFACE_NAME>
        <RECORD_DETAIL>Item</RECORD_DETAIL>
        <ERROR>item</ERROR>
        <CREATE_DATE>2008-11-03 00:00:00.0</CREATE_DATE>
        <MAIL_SENT>N</MAIL_SENT>
    </row>
</ns:MT_ORMS_Errors>
XSLT code:
<?xml version='1.0'?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:variable name="break"><br></xsl:variable>
<xsl:variable name="tableB"><table></xsl:variable>
<xsl:variable name="tableE"></table></xsl:variable>
<xsl:variable name="trB"><tr></xsl:variable>
<xsl:variable name="trE"></tr></xsl:variable>
<xsl:variable name="tdB"><td></xsl:variable>
<xsl:variable name="tdE"></td></xsl:variable>
<xsl:variable name="nbsp">&nbsp;</xsl:variable>
<xsl:variable name="thB"><tr BGCOLOR="#CCCC99"></xsl:variable>
<xsl:template match="/">
   <ns1:Mail xmlns:ns1="http://sap.com/xi/XI/Mail/30">
    <Subject>Deliveries from XI</Subject>
    <From></From>
    <To></To>
    <Content_Type>application/vnd.ms-excel</Content_Type>
    <Content>
     <xsl:text xsl:space="preserve">These deliveries has been completed:</xsl:text>
     <xsl:value-of select="$break"/>
     <xsl:value-of select="$break"/>
     <xsl:value-of select="$tableB"/>
     <xsl:value-of select="$thB"/>
     <xsl:value-of select="$tdB"/>
     <xsl:text xsl:space="preserve">INTERFACE_NAME</xsl:text>
     <xsl:value-of select="$nbsp"/>
     <xsl:value-of select="$tdE"/>
     <xsl:value-of select="$tdB"/>
     <xsl:text xsl:space="preserve">RECORD_DETAIL</xsl:text>
     <xsl:value-of select="$nbsp"/>
     <xsl:value-of select="$tdE"/>
     <xsl:value-of select="$tdB"/>
     <xsl:text xsl:space="preserve">ERROR</xsl:text>
     <xsl:value-of select="$nbsp"/>
     <xsl:value-of select="$tdE"/>
     <xsl:value-of select="$tdB"/>
     <xsl:text xsl:space="preserve">CREATE_DATE</xsl:text>
     <xsl:value-of select="$nbsp"/>
     <xsl:value-of select="$tdE"/>
     <xsl:value-of select="$trE"/>
    <xsl:for-each select="MT_ORMS_Errors/row">
      <xsl:value-of select="$trB"/>
      <xsl:value-of select="$tdB"/>
      <xsl:value-of select="INTERFACE_NAME"/>
      <xsl:value-of select="$nbsp"/>
      <xsl:value-of select="$tdE"/>
      <xsl:value-of select="$tdB"/>
      <xsl:value-of select="RECORD_DETAIL"/>
      <xsl:value-of select="$nbsp"/>
      <xsl:value-of select="$tdE"/>
      <xsl:value-of select="$tdB"/>
      <xsl:value-of select="ERROR"/>
      <xsl:value-of select="$nbsp"/>
      <xsl:value-of select="$tdE"/>
      <xsl:value-of select="$tdB"/>
      <xsl:value-of select="CREATE_DATE"/>
      <xsl:value-of select="$nbsp"/>
      <xsl:value-of select="$tdE"/>
      <xsl:value-of select="$trE"/>
     </xsl:for-each>
     <xsl:value-of select="$tableE"/>
    </Content>
   </ns1:Mail>
</xsl:template>
</xsl:stylesheet>
Thanks,
Sreedhar Goud.

How to send a text attachment by using jdbc to mail scenario Using single stack 7.31

Hi Experts...
We are currently Single Stack SAP 7.31
I have a Scenario that is "JDBC to MAIL" ...here i need to pick a data from data base and i have to sent that data as a .txt attachment to mail by using mail adapter...
here i have created DT, MT SI, MM,OP > ESR PART
when coming to ID > BC,CC,ICO
Were all the channels are running... MESSAGE ID is generated ... But I was not getting any MAIL to my Email ID...
While i was configuring the RECIEVER mail communication channel i have seen the tab that is "MODULE CONFIGURATION"
DO we have to do any MODULE CONFIGURATION.. If it is needed please let me know how to do....?
It would be appreciated can some one explain me step by step Of this MODULE CONFIGURATION ... Are send me some SCREEN CHARTS OR LINKS to under stand......
Thanks in Advance ...!!!!!!!!!!!!
Thanks,
vinay

Hi Experts...
We are currently Single Stack SAP 7.31
I have a Scenario that is "JDBC to MAIL" ...here i need to pick a data from data base and i have to sent that data as a .txt attachment to mail by using mail adapter...
here i have created DT, MT SI, MM,OP > ESR PART
when coming to ID > BC,CC,ICO
Were all the channels are running... MESSAGE ID is generated ... But I was not getting any MAIL to my Email ID...
While i was configuring the RECIEVER mail communication channel i have seen the tab that is "MODULE CONFIGURATION"
DO we have to do any MODULE CONFIGURATION.. If it is needed please let me know how to do....?
It would be appreciated can some one explain me step by step Of this MODULE CONFIGURATION ... Are send me some SCREEN CHARTS OR LINKS to under stand......
Thanks in Advance ...!!!!!!!!!!!!
Thanks,
vinay

JDBC to Mail Adapter

Hi All,
i need some help regarding my scenario with JDBC to Mail adapter.I have to read a table and <b>then sent the values in it to a email.i have finished design and configuring ,but still i am getting this mapping error.
<b>"com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_sp_mail_MM_: RuntimeException in Message-Mapping transformatio~</"
</b>
when i check the trace it says
" com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:sp_mail_MT. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start"
</b>
Let me give the details of my scenario especially my mapping where it fails
This is my message mapping with <b>1:1 mapping</b>
Source Message Type:
sp_jdbc_DT            1..1
                    Record             1
Row             1..unb
Create_Date 1
Message        1
Flag               1
Status            1
Target Message Type
sp_jdbc_DT                     1..1
Record                    1
Row                      1
Create_Date        1
Message             1
Flag                    1
Status                  1
the payload i get
<?xml version="1.0" encoding="utf-8" ?>
- <Record>
- <row>
<Create_Date>2007-02-13 14:17:20.78</Create_Date>
<Message>An Error Occured in the Stored Procedure</Message>
<Mail_Flag>H</Mail_Flag>
<Status>new</Status>
</row>
</Record>
I have Created source mt as outbound and target mt as inbound. and also defined interface mapping.
in the configuration i have created a comm channel for database as sender jdbc and reciver as mail adapter.i have defined sender agreement,reciever agreemane and interface and reciver determination.
my idea is to send the payload as message to the reciepient email.i have not downloaded any mail package.
Any Help appreciated..

Hi Aravind,
      Is ur target msg type correct
<i>Cannot produce target element /ns0:sp_mail_MT</i>
I cannot see any sp_mail_MT in ur target structure. I think thr is prob with the message mapping. You dont hv to use mail package over hr. Just give the sender and receiver details in the receiver mail adapter
Also, check the following link
<a href="https://websmp209.sap-ag.de/form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202&_OBJECT=011000358700004556712005E">https://websmp209.sap-ag.de/form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202&_OBJECT=011000358700004556712005E</a>
Regards,
Akshay

Adapter Limitations Of Sender JDBC and Mail Adapter

hi All,
could you tell me the limitations of JDBC and Mail Adapter .i need to document these details .
Regards
Vidya Sagar

HI Vidya,
If i was you, i would do a list of things that i would need about these adapters, o i would search the SAP.help documentation for a first view and later ask about this possibility. Another way is to read the SCN doubts about these adapters and you can find some problems. You should think about the PI version as well.
Regards.

JDBC to Mail Scenario

Hi SDNers,
I am currently facing a scenario where I need to select records from a database table and then convert the resultset to CSV file (FIle which can be opened using MS Excel), this CSV file needs to be sent in a mail as an attachment.
Kindly guide me on how to achive this.
Is BPM required for this scenario?
Regards,
Gautam Purohit

No BPM is required to do XML-----> Excel file conversion (since you are using Mail receiver).
The only thing that you need to take care is that you populate the Content_Type node of the receiver Mail.xsd with the proper value to convert the file into Excel..
Check this blog it will help solve your problem:
/people/community.user/blog/2006/09/08/email-report-as-attachment-excelword
Regards,
Abhishek.

Best Effort (BE) Quality Service in JDBC & Mail Sender Adapter

Hi Experts,
I have confusion for Mail & JDBC Sender adapters.
Why BE QoS is provided in the sender JDBC & Mail Adapters. Can anybody explain me with how will be Synchronous JDBC or Mail scenario.
Thanks in advance.
Abdur

Use of BE in JDBC can be seen here
http://www.klickklack.wg.am/RFC_Request_Response_without_BPM.doc
For mail sender, usually there are no such logical requirement.
Regards,
Prateek

RFC- JDBC- Mail

Hi
I want to send something through RFC adapter to JDBC to update or insert some data and I want to have return code and send it through mail adapter.
RFC sender interface should be Async, other interface can be sync or aync but as far as I know, in order to get return code from JDBC, the receiver JDBC interface should be sync, actually everything is ok so far, I could handle until this part but when I try to forward the return code from JDBC to Mail adapter, thats where I stuck, how can I handle this scenario with async mail interface?
Thanks

hi,
>>>>I could handle until this part but when I try to forward the return code from JDBC to Mail adapter,
you have to use BPM in order to do this
all you have to do is to map jdbc sync response to the mail adapter (message interface) - so just another transformation step in your BPM and then
you'll have your return code in your mail adapter message
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

PI 7.11 Adapter Metadata

I have installed a new PI 7.11 system.
According to the PI sap help at http://help.sap.com/saphelp_nwpi711/helpdata/en/12/f9bb2fe604a94cbcb4c50dc510b799/frameset.htm
SAP ships adapter metadata for all the adapter types it provides. You can find the adapter metadata shipped by SAP in software component SAP BASIS, software component version SAP BASIS 7.10, in namespace http://sap.com/xi/XI/System.
But in our newly installed PI 7.11, under ESR-Software Component u2018SAP Basisu201D, I see SAP Basis 7.11. But I do not find u201CAdapter Metadatau201D under the name space http://sap.com/xi/XI/System
Is it expected? If not, which part could have been missed. What could be done to see the u201CAdapter Metadatau201D (which list all the sub items: BC, CIDX, File, HTTP, IDoc, JDBC, JMS, Mail, Marketplace, RFC, u2026.).
I appreciate any inputs you have.
Thank you very much, and best regards,
Joanna

Abhishek,
You are amazing in response.
The item 8 is:
"XI CONTENT SAP_BASIS 7.11
Maintenance Software Component (Current View)"
This 8th item lists SP01, SP02, SP03, SP04 for XI CONTENT SAP_BASIS 7.11.
Is this item what you've recommended? Or should I down load the
"XI CONTENT SAP_BASIS 7.11
Installation Software Component (Current View)" (which does not have download file on SMP swdc )
Over one week ago, I downloaded the SP04 for XI Content SAP_Basis 7.11 (the file name is XICNTSAPBASIS04_0-10005649.ZIP, size of 5408393 bytes).
I unzipped it, getting the file XI7_11_SAP_BASIS_7.11_04_00.tpz
and then imported it using "Import Design Object" in ESR, and getting the message:
"Import source XI7_11_SAP_BASIS_7.11_04_00_2010-01-15_10-58.tpz imported successfully
Import file moved to server directory importedFiles
4224 object(s) imported"
Also, checked the component system info:
SAP_CNT_SAP_BASIS 7.1100.20081021173332.0000
There is one OSS note 1119255 (not sure it applied to PI 7.11), pointed to by SAP. The note says for PI 7.1:
24/MAR/08....III...XI_CNT_SAP_BASIS and XI_CNT_SAP_ABA stay at start SP
Wirth SP04 import for XI Content SAP_Basis 7.11, I see our version stays at the start SP with 7.110 (instead of expected 7.114).
This problem has been my road blocker for over the last few days. I was not able to get much help from SAP through OSS message.
Thank you very much for all your inputs, and regards,
Joanna

Error in build.properties, how to set j2ee.home?

Hi,
I'm newbie for J2EE platform. I downloaded J2EE tutorial from sun site. I try to compile a app which ConvertApp using the asant build comannd.
I get this error.
build
Buildfile: build.xml
j2ee-home-test:
BUILD FAILED
D:\Projects\j2ee-1_4-doc-tutorial_7\j2eetutorial14\examples\common\targets.xml:1
0: The j2ee.home property is not properly set in <INSTALL>/j2eetutorial14/exampl
es/common/build.properties.
Set the j2ee.home property to the location of your Application Server installati
on.
On Windows, you must escape any backslashes in the j2ee.home property with anoth
er backslash or use forward slashes as a path separator. So, if your Application
Server installation is C:\Sun\AppServer, you must set j2ee.home as follows:
    j2ee.home = C:\\Sun\\AppServer
    or
    j2ee.home=C:/Sun/AppServer
j2ee.home is currently set to:
Total time: 0 secondsIn which line i should add the j2ee.home value?
my build.properties look like this :
# general
build=build
sql.script=create.sql
delete.sql.script=delete.sql
# database
conpool.name=DerbyPool
jdbc.resource.name=jdbc/ejbTutorialDB
# mail
mailhost=mail_server_ip
mailuser=user_id
fromaddress=email_address
mailjndi=mail/MySession
# cmp
pm.resource.name=jdo/cmp-roster
pm.factory.class=com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl
db.schema=APPPlease enlighten me on this.
Thanks in advance

Hi,
Updated "j2ee.home" and "j2ee.tutorial.home" properties in "build.properties" file which is stored in
\j2eetutorial14\examples\common
use forward slash as path seprator.
e.g
j2ee.home=D:/ProgramFiles/Sun/AppServ8.1UR2
j2ee.tutorial.home=E:/Ishtiaque/eBooks/Sun/2EE/j2eetutorial14
Regards,
Ishtiaque

Adapter specific tips

Hi Group,
Can any body suggest on Adapter tips while using various Adapter types (JDBC/JMS,MAIL,HTTP ,File etc..) what are the things we need to consider while configuring these adapters and what are the recommeded

Hi,
>Adapters connect the Integration Engine to SAP legacy systems, as well as to external systems to communicate with different applications.
>Adapters convert XML- and HTTP-based messages to the specific protocol and format required by these systems, and the other way around.
>You configure the adapters in the configuration part of the Integration Builder. You define the parameters of the respective adapter during the definition of collaboration profiles in the communication channel
The Adapter Engine provides adapters, which you use to do the following, depending on their configuration:
● Communicate with SAP systems using the RFC interface (RFC adapter)
● Enable data exchange with the SAP Business Connector (SAP Business Connector adapter)
● Exchange data with external systems using a file interface or an FTP server (file/FTP adapter).
● Access databases using JDBC (JDBC adapter).
● Communicate with messaging systems using the JMS API (JMS adapter).
● Integrate remote clients or Web Service providers using the SOAP adapter (SOAP adapter)
*For Frequently Asked Questions (FAQs) about adapters , see SAP Note 821268.*
Also walk through these blogs :
1. Choose the Right Adapter to integrate with SAP systems
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
2. Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part III
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
Regards,
Chandra

Busine Process Monitoring: define alert in XI for HTTP adapter

Hi Experts,
Iu2019m working with SAP XI 7.0 and solution manager 701. Iu2019m configuring BPM.
I want to monitor the error in XI. I have three systems:
Legacy System --> SAP PI --> ECC
The legacy System, communicate whit SAP PI with HTTP request so the adapter sender in PI is an HTTP Adapter.
I want to monitor the errors in the http adapter so I created the alert category HTTP_ERROR_ADAPTER in the abap stack (transaction alrtcatdef).
When I try to configure the alert in the Runtime WorkBanch I canu2019t find u201CHTTP Adapteru201D in the field u201CAdapter Engineu201D . I can see only jdbc, rfc, mail u2026. Adapters.
I think that I canu2019t see the http adapter because the HTTP Adapter is not a java adapter.
So, how can I monitor the errors in the HTTP adapter sender in SAP PI? Can I monitor the http adapter sender errors using the field u201CIntegration Engineu201D (u201Cerror categoryu201D = * and u201Cerror codeu201D = * )?
Thank you a lot in advance for collaboration.
Best regards
Giou2019

how can I monitor the errors in the HTTP adapter sender in SAP PI?
Alert category option you are trying won't work. The only thing you may check in PI perspective is whether http service is running in smicm. I am not sure but CCMS monitoring could take care of this specific category. Other way without thinking about alerts could be using manual TCPGateway procedure to trace http calls.
Can I monitor the http adapter sender errors using the field u201CIntegration Engineu201D (u201Cerror categoryu201D = * and u201Cerror codeu201D = * )?
Integration Engine category here won't be actually the http related error, it would be pipeline steps related error.
Regards,
Prateek

Schedule Receiver RFC communication channel to call R3 RFC-FM.

Hi,
I have requirement that I need to schedule/trigger from PI to RFC call R3 function module. Wonder if anyone here has done similar thing before? I tried to use ATP (Availability time planning) in RWB. But this seem does not success for me as there is no response and error message for this.
Below is my configuration detail:
Configured:
1. Receiver communication channel - RFC
2. Receiver agreement with the RFC message type assigned.
3. Scheduled receiver RFC communication channel via ATP daily
*(It is possible to make scheduling job in R/3 but we are not considering this way)
Please let me know if anyone has done this before or any other suggestion to do the scheduling from PI.
Thanks!
Regards,
SP

Hi SP,
As you mentioned, ATP would allow adapter to be open and in start state. Adapter's RFC, SOAP, JMS would need some other application to trigger the message processing because these are not like pooling adapter's File, JDBC and Mail. RFC adapter channel always listening to the RFC port and FM execution. Once FM from R/3 executed then the RFC adapter would trigger it's message processing.
For Sender RFC channel: In order to trigger the RFC adapter execution at particular time then you should write a simple ABAP code which would act a batch application and which does the triggering the FM and Sender RFC channel.
For Receiver Channel: For Receiver RFC channel it's bit trichy because here you have force Receiver RFC adapter to connect backend the execute or initialize the variables without having any XI message triggered from Sender PI channel.
I have 2 ideas:
1. A little difficult approach, similar to the ABAPbatch code, you need to write a java adapter module which can trigger RFC receiver channel to connect and do an initialisation at FM at regular interval.
2. Simple approch configure a File-> 2-> RFC receiver scenario, configure File sender adapter to pick a dummy file at regular interval and RFC receiver channel does the rest.
Please let me know still you have any doubts,
Thanks,
RK

Blank field for Adapter engine

Hi Experts,
I am facing a problem while configuring my communication channel.
When I am trying to selct a server in ADAPTER ENGINE column from drop down , I am not getting anything (it is blank) for FILE,RFC,JDBC,JMS,Mail and SOAP Adapters. But in case of HTTP,IDOC and XI i am getting my adapter engine as Integration Server.
I have checked with basis guy , he is also not able to resolve the issue .
Kindly suggest something on this.
Regards
Dheeraj

Try these
1. Re-import SAP BASIS SWCV 7.0 into Integration repository
2. Apply SAP Note 764176.
3. /people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory
Regards,
Prateek

Message Flow in Integration Engine

Dear Friends,
Kindly can someody share how the message is flowing in Intergration engine after the message taken from Adapter engine.
If you have any block diagram it will be helpful for me

Hi Karthik,
There are 6 stpes for the message processing thats only called
PIPELINE Steps.
what are all the steps involved in the Pipeline processing.
Sender Adapter picks up the file from the file system, converts it to XML and places it in the payload of an XI-SOAP message. Then it posts this message to the Integration Server pipeline via http(s).
XI pipeline steps are:-
->Sender Agreement
->Receiver Determination
->Interface Determination
->Interface Mapping
->Receiver Agreement.
When a source message reaches the Integration server, it performs 6 steps before the message reaches the destination. The steps are:
1) Receiver Determination: This steps determines the system that participates in the exchange of the message.
2) Interface Determination: For each receiver determine which interface will should receiver the message.
3) Message Split: If more than one receivers are found, Xi will instantiate new message for each receiver.
4) Message Mapping: Mapping to transform the source message to destination message format.
5) Technical Routing: Bind a specific destination and protocol to the message.
6) Call outbound Adapter: Send the transformed message to the adapter or a proxy.
One can examine these steps in Runtime Workbench using the Transaction: SXMB_MONI.
message flow in XI
The life cycle of the message is explained in detail by taking an example scenario. The file is picked up by the Sender File adapter and the data is inserted into DB table by Receiver DB Adapter.
       The adapter engine uses the messaging system to log the messages at every stage. This log is called the Audit Log. The audit log can be viewed from the runtime work bench (RWB) to look into the details of the lifecycle of the message. During our journey we will also have a look at the messages that are logged at different stages.
Note: This article is targeted for the newbieu2019s who want to understand the message flow in Adapter Engine. So the insight into the message lifecycle is provided here by taking only the Technical adapters (File/ JDBC/ JMS/ Mail) into consideration. It doesnu2019t delve into the lifecycle of the messages that have reached XI Adapter Engine using RNIF/ BC/ CIDX adapters.
ONWARD JOURNEY:
Fig1. Message flow from Adapter Engine to Integration Server
1.     For the message to be picked up by the communication channel, the channel should be associated with a sender agreement. Here creation of a communication channel doesnu2019t ensure the message to be polled and picked up by the adapter. The message reaches the adapter in its native message format. As the communication in SAP XI happens in XI message format, a module inside the adapter converts the message in native format into XI message format.
2.     During this process, a message ID is generated for the message. To build the XI header (sender agreement details like the sender system, sender message interface and the interface namespace) the details are fetched by performing a CPA lookup(collaboration-partner-agreement are the configuration object details that have been created using the configuration time. The details are updated into the runtime cache when you activate the Configuration objects in Integration builder u2013Configuration time. This cache is referred to as CPA cache).
3.     This message is then sent to module processor for further processing. During the process of sending the message to module processor, the message u201CApplication attempting to send an XI message asynchronously using connection AFWu201D is logged.
4.     The module processor performs steps like structure conversion, communication channel specific conversions (that have been specified in the u201Cmodule tabu201D of the adapter channel). These conversion modules are executed in the same sequence as mention in the communication channel.
5.     After the successful execution of the conversion modules, the appropriate module (call SAP adapter module) of the module processor is called which will send this message for persistent storage. This message is put into the Send Queue of the messaging system for further processing. Messages like u201CMessage trying to put into the send Queueu201D and u201CMessage successfully put into the queueu201D are logged during this process. A confirmation message (success/ failure) is sent back to the sender application at this stage. This confirmation message is used by the channel to perform various steps like deleting the file that has a processing mode as delete.
6.     The message that has been put in the Send Queue has to be picked up and sent to the Integration Engine. The Adapter Engine and XI Integration server use XI Adapter for internal communication purposes. So the XI Adapter picks up message from the send queue and parses the XI message. In this process, the status of the message is set to DLNG and. Messages like u201CThe message was successfully retrieved from the send queue and message status set to DLNGu201Dare logged.
7.     The XI adapter performs a SLD look up (System landscape Directory) to find the Integration server with which the Adapter framework has register itself.
8.     On successful SLD look up, the message is sent via HTTP to the XI IS pipeline, using the pipeline URL (http://hostname:abap-httpport/sap/xi/engine?type=entry). . If this is successful, a message u201CThe message was successfully transmitted to endpoint http://hostname:8000/sap/xi/engine?type=entry using connection AFWu201D is logged and the message statues is set to DLVD means message has been successfully delivered to the endpoint( XI IS in this case)
Fig2. Audit Log of message during onward journey
RETURN JOURNEY:
The return journey commences when the IS has successfully processed the message and delivers it to the Messaging system using the URL u201Chttp://hostname:50000/MessagingSystem/receive/AFW/XIu201D
br>
Fig3. Message flow from Integration Server to Adapter Engine
1.     When the Integration Server (XI IS) finishes processing of the pipeline steps (like receiver determination, interface determination and interface mapping), the message has to be delivered to the required Receiving system. So the XI Integration server will send the message to the messaging system of the Adapter Engine (AE) using the mentioned above. Once the message is successfully received by messaging system, the message u201CThe message was successfully received by the messaging system. Profile: XI URL: http://hostname:50000/MessagingSystem/receive/AFW/XIu201D is logged.
2.     As discussed Integration server and Adapter Engine use XI adapter for internal communication purposes. So the XI message that has been received by the messaging system URL is parsed by the XI Adapteru2019s protocol handler.
3.     The XI message is put into the receive queue and persisted. During this stage messages like u201CUsing connection AFW. Trying to put the message into the request queue; Message successfully put into the queue.u201D are logged.
4.     The XI messages that are put in the receive queue are retrieved by an application (Worker thread) and are sent to AFWListenerBean. AFWListenerBean is a module (an EJB) in Adapter Engine that is capable of parsing the XI message. On successful receive of the XI message by the AFWListenerBean, messages like u201CThe message was successfully retrieved from the request queue.u201D are logged and the status of the XI message is set to DLNG.
5.     The AFWListenerBean reads the receiver agreement and the corresponding channel from the XI header to determine the appropriate adapter. In this stage the adapter channel is logged in the audit log. u201CDelivering to channel: XYZ_Channelu201D
6.     The message is forwarded to the module processor where additional steps like structure conversions and extra modules specified in the adapter are performed.
7.     The exit module is called and the message is sent to the appropriate adapter (DB Adapter in this case). The format conversion will be executed within the specific adapter and sent to the Receiving system (DB in this case) using the channel that has been determined by the AFWListenerBean and the required action is reformed (select statement is performed in this case). On successful processing of the message the status is set to DLVD.

JDBC to MAIL

Similar Messages

Maybe you are looking for