Sender AS2 Issue

Hello,
We are designing an EDI 820 interface from a third party to a file using AS2 inbound adapters with SSL. We have installed the certificates and they are showing status green in NWA. But the partner is getting a 403- Forbidden error.
I have checked the URL sent to the partner is valid. It comes with a status 405.
I have checked for multiple sender agreements but none although we have one for MDN with a diff receiver interface.
I have checked the public key of the partner and the private keys of us are properly set in the sender agreement.
I have checked the AS2 id used by the partner and us and they are set right in the party definition.
What else could trigger a 403 issue?
Teresa

Hi,
The firewall proxy looks good as the network team could see a packet come and hit PI but then it never showed up in any loggs at PI.
Thanks Doss for the forum discussion link. It just made me think we have another sender agreement for our MDN with the same sender and receiver Party but with a different sender interface for the MDN. Could this be an issue as I dont see any problem with the SSL setup?
Teresa

Similar Messages

Reg Sender AS2 module configuration for text file

Hi Experts,
I am working on an inbound scenario where Sender is AS2 and Receiver is SAP system in PI7.4. The Sender Trading Partner is Sending a text file which should be converted to xml. I have added the module parameter localjbs/PlainConverterModule .It is throwing the error as per the attached file.
Could anyone please guide me on this issue. Also Please let me know whether any configuration needs to be set in EDI content Manager.
Cheers,
Neethu

Hi Neethu,
according to the b2b help the module is used to convert EDIFACT message standards into XML. I your case you have flat file comming from AS2. you can use message transform bean to convert flat file to XML in sender as2 adapter. Or you need to define ED XML converter. Please refer the below link
SAP PI: Using the B2BADDON EDI<>XML Convertor Modules - Basics
You configure the communication channels of any Process Integration adapter with the PLAIN-XML converter module to convert business documents encoded in EDIFACT message standards into XML and the other way round. It must be configured in the sender and receiver channels based on the business scenario. The PLAIN-XML converter module runs on the SAP NetWeaver Process Integration Adapter framework.
You use this procedure to configure the parameters of the PLAIN-XML converter module.
source - Configuring the PLAIN-XML Converter Module - SAP NetWeaver Process Integration, business-to-business add-on 1 - SAP Libr…
regards,
Harish

Sender AS2 to SAP PO; 403 forbidden error

Hello Experts,
I am using the AS2 adapter from the B2B Addon.
I am stuck in the scenario Sender AS2 -> SAP PO; with the 403 forbidden error.
Few queries;
1. Is virtual receiver mandatory ?
2. Is is mandatory to have party for sender and receiver. Currently I am having only Sender ( Party + Comm. Component ) and Receiver ( Comm. Component ( Partner Type = LS )).
Can you help please.
Thanks
Saurabh

Hi Harish,
Thanks for your quick response.
I have configured with the following details :
Sender Party : ABC ( 009 | GLN | 333333333 )
Sender Component : DEF
Receiver Party : PQR ( 009 | GLN | 111111111 )
Receiver Component : XYZ
Sender AS2 adapter :
Expected URL : http://10.194.35.20:8080/as2/HttpReceiver
Message ID Left : .*
Message ID Right : .*
Sender AS2 name : 333333333
Receivers AS2 name : 111111111
Expected subject : AS2 message
Partners in Mendelson :
Partner 1 :
( Local station )
1. Name : Mendelson_AS2
2. AS2 ID : 333333333
3. Email : [email protected]
MDN tab : http://<Mendelson desktop PC IP>:8080/as2/HttpReceiver
Parnter 2 :
1. Name : PQR
2. AS2 ID : 111111111
3. Email : [email protected]
Receipt URL : http://<PI-Host>:<PI-PORT>/AS2/.*
Payload subject : AS2 message
Error details :
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: Transmission failed, remote AS2 server reports "Forbidden".
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: HTTP 403
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: Message payload stored to

Error in Sender AS2 adapter

Hi Expert,
I have configured sender AS2 adapter as per the sap guide. and share our url and AS2 name.Now when the partner is trying to send the file from their side they are gettting the following error message and in SAP PO we have not received any file via AS2 sender adapter.
We have checked the fire walls and its working fine.
2014.04.09
01:15:03:128 0326030999 PHDR OK HTTP Response-Line = (HTTP/1.1 302 Found)
2014.04.09 01:15:03:128
0326030999 PHDR ERR Trading Partner rejected the transaction
2014.04.09 01:15:03:128 0326030999 HPOS ERR Requested synchronous receipt not
returned
2014.04.09 01:15:03:128 0326030999 HPOS ERR One or more errors occurred with
this transaction. m_nErr=(2103)
Regards
Kasturika

Hi Harish,
I have change the as2 url from http://<host>:<port>/AS2 to http://<host>:<port>/AS2/B2B and now are partner is facing differnt error
2014.04.22
03:06:04:400 0637647174 PHDR OK HTTP Response-Line = (HTTP/1.1 401
Unauthorized)
2014.04.22 03:06:04:400 0637647174 PHDR ERR Trading
Partner rejected the transaction
I had checked with my partner to use the http authentication and share our user id and password. but they said that they are not using http authentication.
we also shared our public key certificate and import theirs in our nwa- certificates and keys .
Please share if anything more i need to configure.

Sender AS2 MDN XML Channel error

Hi,
I am trying to configure a sender AS2 adapter to receive asynchronous MDN. But as soon as I create the channel ,it goes in error "Channel configuration is erroneous: java.nio.charset.UnsupportedCharsetException: The target charset iso885915 is not supported".
1. I don't see any other option to configure character set once AS2 MDN transport protocol is selected. Am I missing any configuration?
2. Also I am testing from mendelson and as per the mendelson log MDN is sent to PI system but I do not see any MDN in PI. We are using B2B addon SP1 on PI 7.11.
mendelson log :
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: Outgoing MDN has not been signed.
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: MDN created, state set to [processed].
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: Sending async MDN to http://<PI_Host>:50000/AS2/AS2_Sender/mdn.
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: Message sent successfully (HTTP 200); 791 Byte transfered in 353ms [2.19 KB/s].
[3:27:36 PM] 17ef0d18-1e19-11e4-c6b8-0000004bc76a@PI7: AS2 communication successful, payload 1 has been moved to "C:\Users\Pankaj\Desktop\mendelson\opensource\as2\messages\EDI_Partner\inbox\17ef0d18_1e19_11e4_c6b8_0000004bc76a@PI7".

Hi Pankaj,
This is what I did:
The most important parts of the configuration are
Receiver AS2 communication channel, requesting a synchronous MDN message
Sender AS2 communication channel processing the incoming MDN message
Receiver AS2 communication channel
Sender AS2 communication channel
Within the SAP PO monitoring tools, you see something like this:
Kind regards,
Dimitri

Sender AS2 Configuration...

Hi All,
I am doing configuration on AS2 (AS2 -> File)..
We are getting the EDI Messages. Thru Sender AS2 CC, how to pick the messages into XI...
Please help me out ...
Thanks in advance..
Regards,
Vasu

Hi,
I will tell you something about Seeburger Adapters in detail, Just see if it helps...
Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.
These transformed EDI-XML messages are then converted to EDI specific format using the Seeburger's BIC(Business Integration Converter)adapter. In addition, Seeburger provides adapters like AS2,FTP(EDI specific) and so on to route these EDI messages to external EDI Partners.
Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
3. create a one to one mapping between input en output.
4. export the metadata in xsd or sda format for import in XI
5. generate an SDA which can be deployed in XI and used as a module.
Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf

DtReport structure and Alerts Settings from sender AS2 Reports adapter

Hi,
I have imported DtReport for MDN's from SeeBurger AS2 adapter documentation as external definition into PI. However, in the mapping, when I select DtReport as source, I could see only the following structure:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:DtReport xmlns:ns0="http://uri.seeburger.com/dt/master/schema">
   <ns0:clientId/>
   <ns0:correlationId/>
   <ns0:category/>
   <ns0:state/>
   <ns0:finalReport/>
   <ns0:freeText/>
   <ns0:specificData/>
   <ns0:reportAttachment/>
   <ns0:archiving/>
</ns0:DtReport>
But when I import the test MDN message that we received it has key and value elements underneath the tag 'specificData'. How do I get these two elements from external definitation?? Anything that I should in External References??
How does the following 'Alerts Settings' work from sender AS2 Reports adapter:
Enable alerts
Negative transmission report alert
Negative delivery repot alert
Negative receipt report alert
Thanks,
Riya

Here is the XSD:
?xml version="1.0" encoding="ISO-8859-1"?
xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:att="http://uri.seeburger.com/bisas/message/schema" xmlns:tns="http://uri.seeburger.com/dt/master/schema" xmlns="http://uri.seeburger.com/dt/master/schema" targetNamespace="http://uri.seeburger.com/dt/master/schema" elementFormDefault="qualified" attributeFormDefault="unqualified"
     xsd:import namespace="http://uri.seeburger.com/bisas/message/schema" schemaLocation="attachments.xsd" /
     xsd:include schemaLocation="dtglobaltypes.xsd" /
     xsd:include schemaLocation="dtarchiving.xsd" /
     xsd:element name="DtReport" type="tns:DtReportType" /
     xsd:complexType name="DtReportType"
          xsd:sequence
               xsd:element name="clientId" default="000" type="tns:stringLength3Type"
                    xsd:annotation
                         xsd:documentation
                         Logical System ID
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="correlationId" type="tns:uuidType" /
               xsd:element name="category" type="tns:reportCategoryType" /
               xsd:element name="state" type="tns:reportStateType" /
               xsd:element name="finalReport" type="xsd:boolean"
                    xsd:annotation
                         xsd:documentation
                         True if this report is the last one for the given correlationId
                    E.g. if this report is a deliveryReport but there is also a remaining ReadReceipt, then finalReport would have the value 'false'
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="freeText" type="xsd:string" minOccurs="0" /
               xsd:element name="specificData" type="tns:keyValueType" minOccurs="0" maxOccurs="unbounded"
                    xsd:annotation
                         xsd:documentation
                         Optional report data specific to the components and protocols
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="reportAttachment" type="att:AttachmentRefType" minOccurs="0"
                    xsd:annotation
                         xsd:documentation
                         Optionally holds the report as attachment in its raw format.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="archiving" type="tns:archivingType" minOccurs="0" maxOccurs="unbounded" /
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="responseReportHandlingType"
          xsd:annotation
               xsd:documentation
               Information in a DtResponse about the report handling of the sent payload.
               /xsd:documentation
          /xsd:annotation
          xsd:sequence
               xsd:element name="reportsExpected" type="xsd:boolean"
                    xsd:annotation
                         xsd:documentation
                         True if at least one report is pending (false if the one and only report is contained in response).
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="expectedReports" type="tns:expectedReportsType" minOccurs="0" maxOccurs="unbounded"
                    xsd:annotation
                         xsd:documentation
                         List of expected reports - also including the one optionally included in the response.
                        If reportsExpected is true then this list must contain at least one entry, else it must be empty.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="dtReport" type="tns:DtReportType" minOccurs="0"
                    xsd:annotation
                         xsd:documentation
                         Optional report if it was synchronously received.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="initiationReportHandlingType"
          xsd:annotation
               xsd:documentation
               Information in a DtRequestInitiation about the report handling of the received payload.
               /xsd:documentation
          /xsd:annotation
          xsd:sequence
               xsd:element name="reportsExpected" type="xsd:boolean"
                    xsd:annotation
                         xsd:documentation
                         True if at least one report was requested.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="preparedReports" type="tns:preparedReportsType" minOccurs="0" maxOccurs="unbounded" /
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="expectedReportsType"
          xsd:sequence
               xsd:element name="category" type="tns:reportCategoryType" /
               xsd:element name="timeoutDate" type="xsd:dateTime" /
               xsd:element name="deliveryState" type="tns:deliveryStateType" /
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="preparedReportsType"
          xsd:sequence
               xsd:element name="category" type="tns:reportCategoryType" /
               xsd:element name="timeoutDate" type="xsd:dateTime" minOccurs="0" /
               xsd:element name="reportMessage" type="att:AttachmentRefType" /
          /xsd:sequence
     /xsd:complexType
     xsd:simpleType name="reportCategoryType"
          xsd:restriction base="xsd:NCName"
               xsd:enumeration value="DeliveryReport"
                    xsd:annotation
                         xsd:documentation
                         Report informing about the state of the delivery on a physical base
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="ReceiptReport"
                    xsd:annotation
                         xsd:documentation
                         Report informing about the state of the receipt on a semantic base
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="TransmissionReport"
                    xsd:annotation
                         xsd:documentation
                         Report informing about the state of the transmission on a physical base
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
          /xsd:restriction
     /xsd:simpleType
     xsd:simpleType name="deliveryStateType"
          xsd:restriction base="xsd:NCName"
               xsd:enumeration value="DELIVERED"
                    xsd:annotation
                         xsd:documentation
                         Delivery proceeded
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="PENDING"
                    xsd:annotation
                         xsd:documentation
                         Delivery pending
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
          /xsd:restriction
     /xsd:simpleType
     xsd:simpleType name="reportStateType"
          xsd:restriction base="xsd:NCName"
               xsd:enumeration value="SUCCESS"
                    xsd:annotation
                         xsd:documentation
                         Positive report
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="FAILURE"
                    xsd:annotation
                         xsd:documentation
                         Negative report
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="EXPIRED"
                    xsd:annotation
                         xsd:documentation
                         No report received in time
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
          /xsd:restriction
     /xsd:simpleType
/xsd:schema
Edited by: Riya Patil @SAP on Feb 4, 2010 9:05 PM
Edited by: Riya Patil @SAP on Feb 4, 2010 9:05 PM

How to configure alerts for sender AS2 reports channel?

Hi,
We have configured sender AS2 reports channel to receive MDN back from our partner. Scenario is working fine and we are receiving MDN. How does "Enable alerts" option under Alerts Settings in Sender AS2 Reports channel work?
I see following options, but dont know how to trigger an alert when we dont receive successful MDN back:
Negative transmissionreport alert
Negative delivery report alert
Negative receipt report alert
Has anyone trigger any kind of alrert and route them to an email for negative mdn?
Regards,
Riya Patil

Hi Riya,
I tried to use 'Enable alerts' option,but it didn't work.
Please let me know if you get a success in this.
Thanks.
Regards,
Shweta

Sender AS2 Adapter Setup

Hi,
I am trying to send an EDIFACT file to IDOC through AS2 Adapter (sender). Can you please tell me how to configure the sender AS2 Channel.I have configured it, but it is giving me the following error in Channel Monitoring.
Alert: Maximum number of retries reached. Retry 20. Message initiation failed: Adapter call failed. Reason: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: failed to lookup CPA cache: Couldn't retrieve outbound binding for the given P/S/A values: FP=B2B_Certipost;TP=B2B_PH_BE;FS=B2B_SND;TS=B2B_RCV;AN=MI_E_ORDERS_D96A_oa;ANS=urn:novartis.com:pi:ph:be:OM_DD_750_LBE_L0X:Order;, failed to lookup CPA cache: Couldn't retrieve outbound binding for the given P/S/A values: FP=B2B_Certipost;TP=B2B_PH_BE;FS=B2B_SND;TS=B2B_RCV;AN=MI_E_ORDERS_D96A_oa;ANS=urn:novartis.com:pi:ph:be:OM_DD_750_LBE_L0X:Order; [4/30/09 4:19 PM]
Please share your valuable inputs.
Thanks,
Amit..

Hi,
follow the below steps;
AS2 identifier is the party identified which will be provided by the WAN network provider.
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A
-S

JMS sender adapter issue for encrypted message

Hello Folks,
We have JMS to AS2 interface facing issues when JMS sender channel read the encrypted files placed in MQ queue, messages size is
increasing to almost double when it reaches PI.
When sending an encrypted message from MQ to AS2, message is showing in success flag but inbound file size is increasing almost double the size, when compared to message size placed in the MQ Queue. When partner is decrypting the message he is getting total garbage values. But it working fine for unencrypted messages,we are getting the same size as it is in MQ queue.
Can you please trrough some light on the issue not getting excatly issue is in MQ or JMS sender adapter.
Kind Regards
Praveen Reddy

Hi Praveen,
the issue seems to be with your encryption/decryption mechanism rather then JMS adapter. if you have encrypted file in JMS queue then channel only pick the file and sent to target (i am assuming there is no tranformation). So it will not alter the file size.
Please check how the file is encrypted before it places in JMS queue.
regards,
Harish

Unable to send AS2-MDN ack

Hi
We have configured an AS2 with one of our partner, we are able to send/receive 850 but our partner is unable to receive an MDN back from us for the 850, verified all the setups everything looks good..
I put in an SR also, but if anyone of you had experienced the similar issue before, please advise..
Thanks
Sri

hi all..
Im new to this technology and wanna learn and try to program some simple applications using Smart Card...
Reading thru all the topics above, Im wonderring is the Card Reader able write codes to the Smart Card, or maybe jux simply able to update the info inside the card??
I also heard about Card Decoder as well, I mean if the Card Reader can do the task.. why do we need Card Decoder ?!
Sorry if I stated something wrong... Im new and hope that someone could share some valuable knowledges here...
Thanks much much !!

Reg Module for ANSI 12 in Sender AS2 in PI7.4

Hi Experts,
I am facing the below error while testing a Scenario with Sender as AS2.I have configured a Sender Party which is the receiver id for the trading partner (AS2). I have added the module as localejbs/X12ConverterModule and given the parameters as per the blog
Configuring the Module Configuration Parameters - SAP NetWeaver Process Integration, business-to-business add-on 1 - SAP…
Could anyone guide me on this issue.
Cheers
Neethu.

Hi Neethu,
Have you configured operation specific Iflow/ICO?, Please don't associate any operation and if possible please provide your IFlow/ICO configuration screenshot here.
This problem could be because of sender interface , check the sender payload/message type and compare with the test payload (source XML) in ESR.
Regards,
Pooja

Mail Sender adapter issue in PO7.4

Hello Experts,
We are migrating from PI7.0 to PO7.4, where in we are struck up with an issue of Mail Sender Interface.
Here we have a scenario of Mail to Proxy where we are processing attachment(CSV file). But here when I we run the interface mail body is being processed not the attachment. Also could nt see the Payload as when I click on the Attachment payload a pop up is coming and closing automatically.
Can someone please suggest where it went wrong as this is working in existing PI7.0 version.
Thanks.
VR

Hi VR
Have you tried swapping by Payload name?
Please try it out with the following configuration, and remove any extra lines - there are duplicate key names and values in your configuration.
You should be able to see the successfully swap by payload name in the audit log as shown below.
Rgds
Eng Swee

External send output issue

Hi Friends,
We have 3 output types ZNEU, ZCON & ZCMR for which we send email to vendor. For three vendors, ZNEU external send is working fine (Medium 5) , where as for ZCON & ZCMR (medium 5) is giving error, it gives error as below "
1. Please enter an address number
2. Communication type cannot be used
Message no. SVN000
Diagnosis
Message type ZCON should be sent with communication type .
System Response
Communication type is not supported by the conversion module.
Procedure
Use one of the supported communication types:
Printer (LET)
Fax (FAX)
Telex (TLX)
X.400 (X40)
Mail via Internet (INT)
Mail via SAPoffice (RML)
This ZCON & ZCMR ouput type with external send is working fine for other vendor, can you please help me to understand what we are missing here , we have checked the condition records also , which is fine, any specifc condition record to be mainatained for this ?
Please help , as this is a very critical issue for us.
Thanks & Regards,
Vikas

Hi,
Thanks for your reply.
Email id is maintained for these vendors, as output type ZNEU is already getting sucessfully transited with external send process for these vendors. External send is failing for ZCON & ZCMR output only.
Kindly advice.
Regards,
Vikas Mayekar

Sender JDBC Issue

hi friends,
In JDBC-ServerProxy-Clientproxy-file
In this scenario i am triggering client proxy in the server proxy.. all are asyncronious connections..
now the issue is JDBC adapter is triggering after the poll time evry time eventhoough it is updated in the table. i mean i am executing on base of flag and after that i am getting updating that flag.. after that when i monitor CC monitoring i can see the jdbc adapter is keep on triggering after 10 sec9poll intervel).. even though data is not there.. any suggestion how to stop that...what i need to check to solve this...
Thanks & Regards
Vijay

This is a standard behaviour. JDBC and File adapter when used at sender side always keep on polling the sender system continuosly. This is the only way by which any update in database could be picked up by XI. Otherwise XI wont be able to understand the changes at sender side.
If u want to change the behaviopurm then u may schedule ur communication channel if required.
Regards,
Prateek

Sender AS2 Issue

Similar Messages

Maybe you are looking for