Seeburger: No matching inbound binding

Hi guys,
I'm having the following error :
I'm using Seeburger AS2 adapter and I'm trying to receive a message from an external partner. I've created the corresponding channels, sender and receiver agreements  but I'm getting the following error:
No matching inbound binding (message) found for
FromParty:XITest ToParty:B2BTEST subject:1209234884433
I've set on the sender cchannel the 'AS2 message subject' as 'AS2 message test' and I think the problem is related to this configuration.
So I changed the value of the field to '*' so that I'm able to catch any subjects, like the one above....
But with this configuration '*', after activating the channel I'me getting a similar error on the 'communication channel monitoring' but with new subjects and with no party entities every 2 seconds...
No matching inbound binding (report) found for FromParty: ToParty: subject:
I've checked the threads
Seeburger - async receiving MDN problem- no binding found for AS2 from Peter and
Seeburger AS2 Adapter No binding found for: AS2, http://seeburger.com/xi from Murali but nothing....
Do you have any ideas?

Hi  Prateek,
I'd already tried cleaning caches but no good...
Hi Peter,
I've found out what the problem was. What is the purpose of the flag 'Hostname check'? I'd the flag checked by default, I've unchecked it and now I'm able to receive the messages.
Answering your questions, yes, both are using parties and for the MDN i only have the sender agreement and not the receiver.
I'm sure I'll keep posting doubts in the next few days.
Thanks for your attention and patience

Similar Messages

  • Seeburger error - No matching inbound binding found

    Hi
    I am trying to buld a interface using Seeburger AS2 adapter. I have done all the config in XI and Seeburger level. But when customer sent the message he gets following error.
    HTTP/1.1 403 Forbidden^M
    server: SAP J2EE Engine/7.00^M
    content-type: text/html^M
    content-length: 826^M
    date: Tue, 18 Nov 2008 23:50:04 GMT^M
    ^M
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
       <head>
          <title>SEEBURGER AS2 Server: Forbidden </title>
       </head>
       <body bgcolor="#ffffff" text="#000000" link="#0000ee" alink="#0000ee" vlink="
    #551a8b">
          <table cellpadding="0" cellspacing="0" border="0" width="100%" bgcolor="#dc4560">
             <tbody>
                <tr><td> </td></tr>
                <tr>
                   <td> </td>
                   <td valign="middle">
                      <h3>
                         <font face="sans-serif" color="#ffffff">SEEBURGER AS2 Controller</font>
                      </h3>
                   </td>
                </tr>
             </tbody>
          </table>
          <br/>
             <font face="sans-serif" size="-1">
               <b>
    403 Forbidden
               </b>
             </font>
          <br/>
       </body>
    </html>
    When I checked the Seebuger log I noticed following
    seeburger.as2.AS2Plugin#Plain###Inbound communication from TESTEDI to GFB2BDPI not allowed: com.seeburger.conf.BackingStoreException: Unable to execute query because: com.seeburger.xi.config.ConfigException: No matching inbound binding (message) found for FromParty:PT_TOLL ToParty:PT_GOODMANFIELDER subject:<20081119091602.651278.2248792@> [LOC: com.seeburger.as2.component.AS2Server.checkInboundRelation]#
    If someone can help that will be great.
    Thanks
    Shantha Bandara

    Hi,
    403 is a standard error if the AS2-IDs are not setup correct. You can also seet his in your log-file:
    "Inbound communication from TESTEDI to GFB2BDPI not allowed"
    Looks like the SenderAgreement is not referring to the correct parties...
    Greetings
    Stefan

  • JCABinding :Unable to find suitable inbound binding

    Hi,
    I imported a 10g BPEL process to 11g and it compiled successfully. But while deploying to SOA 11g it fails with following message.
    [02:36:04 AM] Error deploying archive sca_SOAIndFileHandler_rev1.0.jar to soa_server1 [soclxs3mp13.com:8001]
    [02:36:04 AM] HTTP error code returned [500]
    [02:36:04 AM] Error message from server:
    Error during deployment: Deployment Failed: [JCABinding] [SOAIndFileHandler.readFiledataFTP/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable inbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable inbound binding.
    Please create a Service Request with Oracle Support.
    [02:36:04 AM] Check server log for more details.
    [02:36:04 AM] Error deploying archive sca_SOAIndFileHandler_rev1.0.jar to soa_server1 [soclxs3mp13.com:8001]
    [02:36:04 AM] #### Deployment incomplete. ####
    [02:36:04 AM] Error deploying archive file:/C:/Users/tmonty/SOAIndFileHandlerProcess/SOAIndFileHandler/deploy/sca_SOAIndFileHandler_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Can SOA gurus help me on this.
    Thanks.
    Tapan
    Edited by: user8891089 on Apr 12, 2010 2:34 PM

    here the solution,
    Just take out the
    callbackInterface="http://xmlns.oracle.com/pcbpel/adapter/file/WritePositivePayFile/#wsdl.interface(Write_ptt)"
    or
    callbackInterface="http://xmlns.oracle.com/pcbpel/adapter/file/WritePositivePayFile/#wsdl.interface(Read_ptt)"
    Thanks
    Kris
    Edited by: user13015650 on Apr 20, 2010 2:07 PM

  • MD04 not matching Inbound Delivery GR Qty

    Please help me understand what is happening in MD04.
    We have a month-long scheduling agreement with a vendor.  The agreement has hundreds of line items.  The vendor sends ASNs to us as shipments are made against the agreement.  The ASNs create inbound deliveries in our system.  Several ASNs are received and processed daily.
    The following situation occurred today.  A similar situation occurs most days, but it is not necessarily for the same mateirlal.
    At 5AM an inbound delivery document created in the system.  Among the dozen materials on it was material A with a quantity of 240.  MD04 shows a quantity of 180 for that material on the inbound delivery, with an MRP exception of 15 (Reschedule out).  When I drill into the detials of the element, I can see a GR quantity of 240 u2013 matching the inbound delivery document.
    At 7AM, a second inbound delivery came in, which has 120 units of material A (among other materials).  MD04 shows a quantity of 120 for this delivery.  This line also has the MRP exception 15 for the inbound delivery.
    Why would the line for the 5AM delivery show a quantity of 180 instead of the GR quantity of 240?  Why does a line for a delivery created 2 hours later show the correct quantity?
    Regards,
    Ken

    Update to this strange situation:  the ShipNt line in the stock/requirements list that appears to report a receivable quantity less than what is on the inbound delivery refers to an inbound delivery that has already been received in MIGO.  For some reason, this peculiar line item of the inbound delivery lingers on the stock requirements list after goods receipt.  Other line items on the same inbound delivery have dropped off their respective stock/requirements lists as expected.
    We see this behavior when the ShipNtu2019s start to u201Cstack upu201D in the stock/requirements list.  When the last (most recent) inbound delivery is posted as received, the peculiar line drops off the list.
    I think this has something to do with the confirmation control key 0004 for the scheduling agreement line item. 
    Still searchingu2026..
    Ken

  • Is it necessary to create matching INBOUND and OUTBOUND rules?

    RV220W - I'm trying to create a one-to-one NAT connection to a PC on my network. I have 5 static IP's assigned by my ISP. I've gone through the step of 'registering' each IP in turn on the WAN port, and pinging that IP from an external device until it starts to respond, then I set the WAN IP back to the one I want to use to manage the device.
    I think what I want to do is simple. I simply want to NAT ALL traffic hitting my 2nd IP address, let's call it 24.15.120.73 (not the real value) to 192.168.1.10 internally. I want ALL ports both UDP and TCP to be forwarded. This Server is then going to be one end of a VPN tunnel going to another site, but I don't want to complicate things with that for now.
    So I can't even seem to get one-to-one NAT working!
    I created the one-to-one NAT on the Advanced tab of the firewall and created rules for all ports for UDP and TCP, but I can still never 'see' the internal server from the Internet. Also, the server will not get out to the Internet (can't hit Google, etc).
    I'm sorry if I'm not using the correct language, but I'm not a network pro. I have enough knowledge to make myself dangerous 
    Thank you for any help you can provide.
    Also, if Cisco could provide Step by Step instruction guides on how to do various things, I think it would be a useful resource for your customers!

    Hi Charles,
    check out ;
    http://www.orinoco-systems.com/blog/bid/119630/Configuring-a-public-to-private-ip-address-NAT-on-a-Cisco-RV220W
    regards Dave

  • 403 forbidden error received at Trade Partner side while sending data to XI

    Hi XI Experts,
    We have a B2B scenario from TP1 to another TP2 via XI in our production system. The interface is working fine and messages are flowing successfully. However, the Trade Partner HUB has decided to implement a new eCommerce Business Platform at their end. That's why they have provided AS2 ID of sender and Receiver to us to make the changes in Quality environment. I have done the same in our Quality system.
    Flow: We are able to send the data successfully to the AS2 ID provided by Hubgroup. Where as we are not able to receive any data from HUB.
    Last Friday, Hubgroup has received the error while sending data to XI. And in our Sender AS2 channel, we also received the following error.
    a) HUB Side error:
                              Here is a copy of the MDN Message send to HUB:
                             The message you sent on "Thu, 14 Oct 2010 07:14:51 GMT" from "XXXXXXXX" to
                            "XXXXXXXXX" with subject "Integrator Message" has been received on 14 Oct
                             2010 19:14:52 GMT, but cannot be processed because message authentication
                             failed.
    b) XI AS2 channel error:
                             Error type: PANIC >> Error date: 10/14/10 11:48 AM >> Description: Initiate     
                             Error:com.seeburger.util.configuration.ConfigurationException: Failed to lookup report channel for failed inbound    
                             message. Reason : com.seeburger.xi.config.ConfigException: No matching inbound binding (report) found for
                             FromParty: ToParty: subject:Integrator Message [10/14/10 11:48 AM]
                      I have done the following things: 1) Cache refreshed 2) Recreated the 1st part from HUB to XI. 3) Checked the Agreements and Receiver Determination and also the AS2 ID's 4) Also checked the URL in communication channel. I have created the scenario with out any mapping. I want to receive the data from HUBGROUP with out any changes. For that, I will be using a dummy interface and dummy namespace in configuration.
    When we test last night, HUB side they have received 403 forbidden error message and we didn;t receive any message to XI.
    Note: XI3.0 version we are using currently. We are upgrading to PI 7.11 in the next month.
    Please help me on this.
    Thanks & Regards,
    Abdullah Shaik.
    Edited by: Abdullah Shaik on Oct 20, 2010 9:06 AM

    Hi Abdullah ,
    here are a few things that you can check:
    1) Message authentication failed
    - Check the authentication certificate settings.
    - Disable the u201Cauthentication requiredu201D flag, if messages without authentication are to be received.
    2) Partner received HTTP Error 403 u201Cforbiddenu201D.
    This error may have different reasons:
    a) You or your partner has entered an incorrect AS2 ID for one of the involved parties.
    b) A valid sender agreement is missing.
    c) There are more then one AS2 sender agreements with the same sender AND receiver party.
    d) The corresponding inbound channel is set to inactive.
    regards,
    Daniel

  • Change of AS2 Certificate

    Hi All,
    We have a scenario using AS2 adapter which was working fine.
    Now the AS2 Certificate has expired and our partner has given us the new certificate and asked us to upload it.
    I have changed the Certificate name in all Sender and Receiver agreements in XI ,now I receive this error:
    For AS2 receiver:
    Error type: COMPONENT_ERROR,NOT_TRANSMITTED >> Error date: 4/17/09 8:22 AM >> Description: AS2 Adapter failure java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no certificate with such alias com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:321) [4/17/09 8:22 AM]
    For AS2 Senders:
    Error type: PANIC >> Error date: 4/17/09 6:48 AM >> Description: Initiate Error:com.seeburger.util.configuration.ConfigurationException: Failed to lookup report channel for failed inbound message. Reason : com.seeburger.xi.config.ConfigException: No matching inbound binding (report) found for FromParty: ToParty: subject:SDPACK [4/17/09 6:48 AM]
    Kindly let me know what else has to be done at our end.
    Thanks.
    Regards,
    Shweta

    Hi Ravi,
    This is really a useful information.
    We have received a certificate file from our partner as you have mentioned.
    I am in contact with BASIS colleague and trying if he could do it.
    I would update the thread once it is resolved.
    Thanks.
    Best Regards,
    Shweta

  • AS2Connectivity Issue

    Hi
    We are testing connection with our customer via SEEBURGER AS2 adapter and this is for inbound.
    We have one sender channel, corresponding sender agreement and the party identifiers for both the sides are setup properly and so as the certificates. I am getting the following error.
    com.seeburger.frame.FrameStarter [Application [96]] Error: Error initiating task! Caused by: com.seeburger.util.configuration.ConfigurationException: Failed to lookup report channel for failed inbound message. Reason : com.seeburger.xi.config.ConfigException: No matching inbound binding (report) found for FromParty: ToParty: subject:Connect:Enterprise Unix AS2 Message Payload Batch Id=<AS2S EDI OUTBND CAFSEDI.PL> Batch Number=<231448>

    Hi,
         Please ensure that the communication channel (AS2) is defined under a party and the party has the AS2 ID defined under Identifiers tab in the following format :
    Agency --> Seeburger
    Scheme --> AS2ID
    Name --> 'Your AS2 ID'
    In the communication channel mention the Message Subject that is used by the sender to send the data and keep the field "Authentication Required" unchecked.
    Also, when defining your Sender Agreement, use option "Sender uses virtual receiver" and define the corresponding Receiver Communication party and component (this should not be defined as '*').
    Also, if you are using any certificated, define these under the parameters tab in the Sender Agreement.
    Regards

  • Seeburger - async receiving MDN problem- no binding found for AS2

    Hi guys!
    We have configured AS2 receiver adapter but during receiveing Async MDN we get following error (sending of message is successful) :
    Cannot receive async MDN: com.seeburger.as2.exception.AS2PluginException: Inbound communication from 90586 to 22266 not allowed: com.seeburger.conf.BackingStoreException: Unable to execute query because: com.seeburger.xi.config.ConfigException: No binding found for: AS2, http://seeburger.com/xi, Gloria, R3
    Note: Gloria & R3 are names of XI identifiers (scheme: XIParty) and 22266 & 90586 are names from AS2ID scheme - alternative identifiers.
    22266 - is sender of original message
    90586 - is receiver
    What is wrong on the settings? Why the sending message uses alternative identifiers and incoming MDN does not?
    Thanx for answers & suggestions!
    Peter

    Hi Peter
    checkm this thread discuss the same ..... hope it will solve ur all querry
    Seeburger AS2 Adapter No binding found for: AS2, http://seeburger.com/xi
    Thanks !!!
    Questions are welcome here!!
    <b>Also mark helpful answers by rewarding points</b>
    Thanks,
    Abhishek Agrahari

  • Inbound voip dialpeer matching difficulty

    Hello,
    could anyone help to clarify some voip issues related inbound dialpeet matching...
    We have a voice gateway AS5350.
    There is a partner's gateway we want to exchange voice traffic with.
    We need to apply some number translation rules (translate calling number) before the traffic from our partner can go further. In our case calling and called numbers are unknown.
    The question is how I can match inbound calls to this incoming voip dialpeer where this translation applies? Is that possible to match inbound voip dialpeer by ip address?
    Thanks in advance,
    Michael

    In fact that is possible!
    You can use 'voice source-group' feature to accomplish this. I've already cheched it, it works!
    http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Service%20Providers&topic=Voice%20over%20IP&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1dd81690/3#selected_message

  • Seeburger Sender AS2 adapter

    We have a customer who purchased Seeburger AS2 Adapter.  They have WAN setup with “Inovis” which is having AS2.  Now we are in the process of setting up the AS2 using seeburger  for them.  if we use Seeburger AS2 adapter, then trading partners have to send their documents to the following path
    http://<Server Name> :50000/SeeburgerAS2/AS2Server
    Seeburger AS2 adapter will receive the documents posted to the above URL & Process them using XI
    The problem we are facing is the Sender Seeburger AS2 adapter doesn’t have a mechanism to Poll the “Inovis” AS2 Mailbox and receive the documents.
    Does any one have a solution to Poll & fetch the documents from “Inovis” AS2 mailbox.
    With Regards
    K.Varadharajan

    HI,
    The message which are coming to XI will be picked up based on two things:
    1) AS2 ID of the partner which is dicussed above and the second one is
    2) Message subject :
    Message Subject
    This subject will be compared with the subject in the received message. This is used to find the correct channel for the inbound message. Wildcards are allowed.
    There is a defined order in which the matching inbound channel is looked up. First the adapter looks for a sender channel with a message subject configured.
    • If there is one channel with a matching subject configured, the channel is used for forwarding the received payload to the XI system.
    • If there is no channel configured with an matching subject the received payload is rejected.
    • If there is one channel configured with a matching subject and another channel with a wildcard –both channels will match. In this case the received payload is forwarded to the channel without wildcard configured.
    • If there is more than one channel configured with a matching subject, the payload is rejected.
    I hopw it has answered ur question.
    Thanks and regards,
    Chirag
    Reward points for helpful answers.

  • SAP XI Seeburger and X.400 Adpater

    Hello,
    We are trying to implement Seeburger X.400 Adapter in our XI 3.0 landscape for the first time.
    I went through Seeburgers config documentation and did all the setup and still getting errors. Not sure what I missed.
    At the log it seems to be complaining about "Resource". I did create a logical resource and assigned it to the channels.
    Following error is what I see in Comm.Channel Monitoring for both Sender and Receiver Channels:
    2009/04/21 - 14:45:34:368 Retryable fault in 'Channel:CC_NL_Receiver_Test'. Description: P7 error occured! Details: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. [4/21/09 2:44 PM]
    Error type: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. >> Error date: 4/21/09 2:45 PM >> Description: : trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. [4/21/09 2:45 PM]
    Following is the error log I see in the log files (seeburger-x400p7-readable.2.trc):
    Apr 21, 2009 3:21:47 PM    com.seeburger.p7.statemachine.TransportLayer.disconnect()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # Error while disconnecting! The transport layer is not connected.
    Apr 21, 2009 3:21:47 PM    com.seeburger.p7.MessageStore.bind()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # Failed to establish a connection. Caused by: com.seeburger.p7.exceptions.P7ConnectException: connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
         at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:262)
         at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:138)
         at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:553)
         at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:157)
         at com.seeburger.p7.statemachine.serviceelements.AssociationControl.associate(AssociationControl.java:132)
         at com.seeburger.p7.statemachine.serviceelements.RemoteOperations.bind(RemoteOperations.java:98)
         at com.seeburger.p7.statemachine.serviceelements.Bind.invoke(Bind.java:76)
         at com.seeburger.p7.MessageStore.bind(MessageStore.java:366)
         at com.seeburger.p7.orders.P7Order.run(P7Order.java:81)
         at com.seeburger.p7.P7Processor.execute(P7Processor.java:241)
         at com.seeburger.frame.core.FrameWorkListener.syncNewData(FrameWorkListener.java:429)
         at com.seeburger.xi.connector.fw.SynchronousTaskExecutor.executeTask(SynchronousTaskExecutor.java:40)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.doInboundTransmission(QueueProcessorImpl.java:1181)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.process(QueueProcessorImpl.java:585)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.run(QueueProcessorImpl.java:227)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Apr 21, 2009 3:21:47 PM    com.seeburger.p7.P7Processor.handleP7Exception()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isnt connected yet. Caused by: com.seeburger.p7.exceptions.P7Exception: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
         at com.seeburger.p7.MessageStore.bind(MessageStore.java:379)
         at com.seeburger.p7.orders.P7Order.run(P7Order.java:81)
         at com.seeburger.p7.P7Processor.execute(P7Processor.java:241)
         at com.seeburger.frame.core.FrameWorkListener.syncNewData(FrameWorkListener.java:429)
         at com.seeburger.xi.connector.fw.SynchronousTaskExecutor.executeTask(SynchronousTaskExecutor.java:40)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.doInboundTransmission(QueueProcessorImpl.java:1181)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.process(QueueProcessorImpl.java:585)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.run(QueueProcessorImpl.java:227)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.seeburger.p7.exceptions.P7ConnectException: connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
         at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:262)
         at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:138)
         at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:553)
         at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:157)
         at com.seeburger.p7.statemachine.serviceelements.AssociationControl.associate(AssociationControl.java:132)
         at com.seeburger.p7.statemachine.serviceelements.RemoteOperations.bind(RemoteOperations.java:98)
         at com.seeburger.p7.statemachine.serviceelements.Bind.invoke(Bind.java:76)
         at com.seeburger.p7.MessageStore.bind(MessageStore.java:366)
         ... 11 more
    Apr 21, 2009 3:21:47 PM    com.seeburger.xi.connector.fw.XICommunicator.reservationReleased(String)                                                                               [SAPEngine_Application_Thread[impl:3]_27] # Error # Error while releasing resource in resource-management:Cannot create reservation, reason: Cannot find reservation with id X400-Seeburger49; affected object : null
    Thanks in advance for your help,
    Sumant.

    Hi Prateek,
    Thanks for your quick response.
    As you said, there was a reservation entry and I deleted it. But still having the same issue.
    Do you know what this error means. I see this in the comm.channel monitor:
    Alert: Polling failed, caused by: Task final state is RETRY or ERROR [4/21/09 3:45 PM]
    2009/04/21 - 15:45:16:341 Retryable fault in 'Channel:CC_PollingX400'.
    Description: P7 error occured!  Details:
    trying to open a connection -->
    connecting to remote session service -->
    com.seeburger.p7.exceptions.P7ConnectException: writing to network -->
    The transport layer isn't connected yet. [4/21/09 3:44 PM]
    Error type:
    trying to open a connection -->
    connecting to remote session service -->
    com.seeburger.p7.exceptions.P7ConnectException: writing to network -->
    The transport layer isn't connected yet.
    >> Error date: 4/21/09 3:45 PM
    >> Description: : trying to open a connection -->
    connecting to remote session service -->
    com.seeburger.p7.exceptions.P7ConnectException: writing to network -->
    The transport layer isn't connected yet. [4/21/09 3:45 PM]
    Regards,
    Sumant.

  • Pls.. Help Needed.. Seeburger Mapping Names..!!

    Hi All,
    Can any one help me with the default Mapping Program names supplied by SEEBURGER for both inbound and outbound.
    <b>EDI Orders
    EDI Order Ack/Confirmation outbound
    Delivery
    Invoice</b>
    Also pls clarify below questions if you have an idea.
    1. I heard that the XSD's will be already available for all the standard EDI message types.?? If Yes, we can i get them?? I mean which location in the server do i get them.
    2. Is it mandatory that i need to use Only AS2 adapter to call the below Seeburger modules.?
    Is the below sequence is correct??
    <b>Process Sequence :</b>
    localejbs/callBicXIRaBean                        bic
    localejbs/ModuleProcessorExitBean         exit
    <b>Module Configuration :</b>
    bic       mappingName     See_E2X_ORDERS_UN_D96A
    exit      JNDIName          deployedAdapters/OFTP/sharable/OFTP
    Thanks in Advance.
    Regards
    Seema
    Message was edited by:
            reddy seema

    Hi,
    Check some links on Seeburger.
    http://www.seeburger.com
    Please see the below blogs
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
    http://www.stylusstudio.com/edi/XML_to_X12.html
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    Details on XI EDI adapter from seeburger
    Check this for Conversions-
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    SAP Adapters
    EDI with XI
    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
    http://www.seeburger.com
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.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.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
    Regards,
    Phani
    Reward Points if Helpful

  • Problems with Date bind variable

    I'm trying to use a Date as a bind variable in a View Object, and I'm running into difficulties. I've got the bind variable type set to date, and the control hints for Format Type and Format set to "Simple Date" and "yyyy-MM-dd" respectively. When I run the application module test and enter the date in the correct format, the View Object returns the expected results. However, when I try to set a Query Bind Parameters property for a JHeadstart group in my application definition in order to set the bind variable's value from an dateField input control, I get the following exception:
    30-Jan 08:49:56 ERROR (ErrorReportingUtils) -java.lang.IllegalArgumentException
    at java.sql.Date.valueOf(Date.java:104)
    at oracle.jbo.domain.Date.toDate(Date.java:348)
    at oracle.jbo.domain.Date.<init>(Date.java:279)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
    at oracle.jbo.domain.TypeConvMapEntry.convert(TypeConvMapEntry.java:73)
    at oracle.jbo.domain.TypeFactory.get(TypeFactory.java:739)
    at oracle.jbo.domain.TypeFactory.getInstance(TypeFactory.java:90)
    at oracle.jbo.common.VariableImpl.convertToJava(VariableImpl.java:546)
    at oracle.jbo.common.VariableValueManagerImpl.doSetVariableValue(VariableValueManagerImpl.java:182)
    at oracle.jbo.common.VariableValueManagerImpl.setVariableValue(VariableValueManagerImpl.java:223)
    at oracle.jbo.common.VariableValueManagerImpl.setVariableValue(VariableValueManagerImpl.java:229)
    at oracle.jheadstart.model.adfbc.v2.JhsApplicationModuleImpl.applyBindParams(JhsApplicationModuleImpl.java:173)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at oracle.adf.model.binding.DCInvokeMethod.invokeMethod(DCInvokeMethod.java:507)
    at oracle.adf.model.binding.DCDataControl.invokeMethod(DCDataControl.java:1795)
    at oracle.adf.model.bc4j.DCJboDataControl.invokeMethod(DCJboDataControl.java:1989)
    at oracle.adf.model.binding.DCInvokeMethod.callMethod(DCInvokeMethod.java:219)
    at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1289)
    at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:1802)
    at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:627)
    at oracle.adf.model.binding.DCInvokeActionDef$DCInvokeAction.refresh(DCInvokeActionDef.java:140)
    at oracle.adf.model.binding.DCBindingContainer.internalRefreshControl(DCBindingContainer.java:2521)
    at oracle.adf.model.binding.DCBindingContainer.refresh(DCBindingContainer.java:2260)
    at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.prepareRender(PageLifecycleImpl.java:534)
    at oracle.adf.controller.faces.lifecycle.FacesPageLifecycle.prepareRender(FacesPageLifecycle.java:98)
    at oracle.jheadstart.controller.jsf.lifecycle.JhsPageLifecycle.prepareRender(JhsPageLifecycle.java:1155)
    at oracle.adf.controller.v2.lifecycle.Lifecycle$1.execute(Lifecycle.java:297)
    at oracle.adf.controller.v2.lifecycle.Lifecycle.executePhase(Lifecycle.java:116)
    at oracle.adf.controller.faces.lifecycle.ADFPhaseListener.mav$executePhase(ADFPhaseListener.java:29)
    at oracle.adf.controller.faces.lifecycle.ADFPhaseListener$1.before(ADFPhaseListener.java:426)
    at oracle.adf.controller.faces.lifecycle.ADFPhaseListener.beforePhase(ADFPhaseListener.java:77)
    at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:228)
    at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:137)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:214)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:162)
    at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
    at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:228)
    at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:197)
    at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:123)
    at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:103)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    However, it seems that the value of the bind parameter did in fact change, according to the debug message issued by the JhsApplicationModuleImpl.applyBindParams(...) procedure:
    30-Jan 08:46:23 DEBUG (JhsApplicationModuleImpl) -ViewObject ViewObj: value of bind param move_date has changed: old value=null ,new value=Wed Jan 07 00:00:00 CST 2009
    One thing I have noticed that may be of interest - if I run the debugger into the JhsApplicationModuleImpl.applyBindParams(...) procedure, a default date in my bind variable shows up as an oracle.jbo.domain.Date object when it comes out of the following line:
    Object oldValue = vo.ensureVariableManager().getVariableValue(key);
    as opposed to the new value that gets sent from the input value of the dateField control, which shows up as a java.util.Date in the following line:
    Object value = args.get(key);
    In the string of functions leading up to the following in the stack trace:
                   at java.sql.Date.valueOf(Date.java:104)
    at oracle.jbo.domain.Date.toDate(Date.java:348)
    at oracle.jbo.domain.Date.<init>(Date.java:279)
    it looks like the value of the java.util.Date is converted to a string, then passed to these functions to be turned into a java.sql.Date object. However, according to the java.sql.Date.valueOf(...) function, it's expecting date in "yyyy-mm-dd" format, per the header comments:
    * Converts a string in JDBC date escape format to
    * a <code>Date</code> value.
    * @param s a <code>String</code> object representing a date in
    * in the format "yyyy-mm-dd"
    * @return a <code>java.sql.Date</code> object representing the
    * given date
    * @throws IllegalArgumentException if the date given is not in the
    * JDBC date escape format (yyyy-mm-dd)
    When the input value from the dateField input control is added as a java.util.Date, the toString() is producing the wrong date format, which could be seen in the debug output I included above that said the bind variable has changed.
    Has anyone done this before that can let me know what I am missing and how to fix this? I've search all over the web, and all the articles I've seen relating to bind variables only refer to those of numeric or string types, which aren't giving me any trouble. Even the Developer's Guide (http://database.in2p3.fr/doc/oracle/Oracle_Application_Server_10_Release_3/web.1013/b25947/bcquerying009.htm) article "5.9 Using Named Bind Variables" doesn't reference using a Date type.

    I had the same problem about a year ago (using JHeadstart 10.1.3.2.52):
    15-feb 14:10:31 DEBUG (JhsApplicationModuleImpl) -Search item matches query bind param SubjectenKernPeildatum, value set to 2000-01-01
    15-feb 14:10:33 DEBUG (JhsApplicationModuleImpl) -Executing applyBindParams for BasServiceKern.AdresRollenSubjecten
    15-feb 14:10:33 DEBUG (JhsApplicationModuleImpl) -ViewObject AdresRollenSubjecten: value of bind param peildatum has changed: old value=null ,new value=Sat Jan 01 00:00:00 CET 2000
    15-feb 14:10:33 ERROR (ErrorReportingUtils) -java.lang.IllegalArgumentException
    at java.sql.Date.valueOf(Date.java:104)
    at oracle.jbo.domain.Date.toDate(Date.java:348)
    It appears a java.util.Date gets put on the criteria Map in the searchBean, this can't be used as input for a jbo.Date bindvariable.
    My ugly solution was to override public void applyBindParams(String voUsage,HashMap args)
    in MyProjectApplicationModuleImp (which extends JhsApplicationModuleImpl of course),
    check if value is a java.util.Date, and then
    value = new java.sql.Date(((java.util.Date)value).getTime());
    Greetings, HJ
    Edited by: HJHorst on Feb 6, 2009 12:22 AM

  • Multiple incoming dial-peer matched

    Dear,
    Could someone, tell me why after matching an incoming-peer on "answer-address" system matches for same call another  incoming dial-peer based a "destination-pattern" ... shouldn't the system start looking for outbound dial-peer once first incoming diapeer matched?
    046565: Feb  3 17:56:57: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
       Result=Success(0) after DP_MATCH_ANSWER; Incoming Dial-peer=360
    046566: Feb  3 17:56:57: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
       Calling Number=1660, Called Number=, Voice-Interface=0x0,
       Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
       Peer Info Type=DIALPEER_INFO_SPEECH
    046567: Feb  3 17:56:57: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
       Result=Success(0) after DP_MATCH_ANSWER; Incoming Dial-peer=360
    046568: Feb  3 17:56:57: //-1/4C84D3B79834/DPM/dpAssociateIncomingPeerCore:
       Calling Number=1660, Called Number=+32495243137, Voice-Interface=0x0,
       Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
       Peer Info Type=DIALPEER_INFO_SPEECH
    046569: Feb  3 17:56:57: //-1/4C84D3B79834/DPM/dpAssociateIncomingPeerCore:
       Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1
    Dial-peers:
    dial-peer voice 360 voip
    corlist incoming toBRICall
    description ** AGENT COR PEER **
    translation-profile outgoing E164IncomingSIP
    preference 2
    voice-class codec 1
    session protocol sipv2
    session target ipv4:10.161.10.170
    dtmf-relay rtp-nte
    fax rate disable
    ip qos dscp cs5 signaling
    no vad
    destination-pattern 166.
    answer-address 166.
    dial-peer voice 1 voip
    session protocol sipv2
    incoming called-number .
    dtmf-relay sip-notify
    codec g711alaw
    no vad
    Thank you.
    Best regards.
    Marc

    Hi
    Dial peer matching (inbound and outbound) has a list of attributes that are used in a specific order.
    For inbound peers, 'incoming called-number' has top priority, so the other command you set are not checked as this 'incoming called-number .' matches any called number!
    Destination-pattern is the lowest priority match for an inbound peer, and answer-address is lower priroty than incoming called-number.
    See this doc for the process in detail:
    http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml#topic1
    Aaron HarrisonPrincipal Engineer at Logicalis UK
    Please rate helpful posts...

Maybe you are looking for