Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 20 views

    b2b Error2

    Uploaded by

    balakrishnakadapa
    The document describes an error that occurs when processing an outbound message from a composite in an Oracle SOA Suite B2B Engine. The error is caused by missing properties in the B2B Adapter invoke activity that specify the trading partners and document type. The solution is to set the "b2b.fromTradingPartnerId", "b2b.toTradingPartnerId", "b2b.documentProtocolVersion", and "b2b.documentTypeName" properties in the invoke activity.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    b2b Error2

    Uploaded by

    balakrishnakadapa
    20 views2 pages
    The document describes an error that occurs when processing an outbound message from a composite in an Oracle SOA Suite B2B Engine. The error is caused by missing properties in the B2B Adapter invoke activity that specify the trading partners and document type. The solution is to set the "b2b.fromTradingPartnerId", "b2b.toTradingPartnerId", "b2b.documentProtocolVersion", and "b2b.documentTypeName" properties in the invoke activity.

    Original Description:

    b2b error2

    Original Title

    b2b error2

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document describes an error that occurs when processing an outbound message from a composite in an Oracle SOA Suite B2B Engine. The error is caused by missing properties in the B2B Adapter invoke activity that specify the trading partners and document type. The solution is to set the "b2b.fromTradingPartnerId", "b2b.toTradingPartnerId", "b2b.documentProtocolVersion", and "b2b.documentTypeName" properties in the invoke activity.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    20 views2 pages

    b2b Error2

    Uploaded by

    balakrishnakadapa
    The document describes an error that occurs when processing an outbound message from a composite in an Oracle SOA Suite B2B Engine. The error is caused by missing properties in the B2B Adapter invoke activity that specify the trading partners and document type. The solution is to set the "b2b.fromTradingPartnerId", "b2b.toTradingPartnerId", "b2b.documentProtocolVersion", and "b2b.documentTypeName" properties in the invoke activity.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 2

    3/13/24, 12:27 AM Knowledge

    Copyright (c) 2024, Oracle. All rights reserved. Oracle Confidential.

    Sending Outbound Message from Composite B2B-50547: Agreement Not Found (Doc ID 2128721.1) To Bottom

    Modified: Jan 14, 2020 Type: PROBLEM

    In this Document

    Symptoms
    Changes
    Cause
    Solution

    APPLIES TO:
    Oracle SOA Suite - Version 11.1.1.7.0 to 12.2.1.0.0 [Release 11gR1 to 12c]
    Information in this document applies to any platform.

    SYMPTOMS
    On : 12.2.1.0.0 version, B2B Engine
    When B2B attempts to process an outbound message coming from a composite, the following error occurs.

    ERROR
    -----------------------

    Error -: B2B-50547: Agreement not found for trading partners: FromTP (remote trading parnter name), ToTP null with document type
    ACTION:null Service:null ServiceTypenull-OUTBOUND.[[
    at oracle.tip.b2b.tpa.RepoDataAccessor.queryAgreementMO(RepoDataAccessor.java:1008)
    at oracle.tip.b2b.tpa.RepoDataAccessor.getAgreementDetails(RepoDataAccessor.java:469)
    at oracle.tip.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:557)
    at oracle.tip.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:229)
    at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1716)
    at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:930)
    at oracle.tip.b2b.engine.Engine.outgoingContinueProcess(Engine.java:4414)
    at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:4221)
    at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3738)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:780)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:243)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:184)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:207)
    at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
    at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
    at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
    at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
    at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:617)
    at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:595)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)
    Error -: B2B-50547: Agreement not found for trading partners: FromTP (remote trading parnter name), ToTP null with document type
    ACTION:null Service:null ServiceTypenull-OUTBOUND.
    at oracle.tip.b2b.tpa.RepoDataAccessor.queryAgreementMO(RepoDataAccessor.java:1008)
    at oracle.tip.b2b.tpa.RepoDataAccessor.getAgreementDetails(RepoDataAccessor.java:469)
    at oracle.tip.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:557)
    at oracle.tip.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:229)
    at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1716)
    at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:930)
    at oracle.tip.b2b.engine.Engine.outgoingContinueProcess(Engine.java:4414)
    at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:4221)
    at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3738)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:780)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:243)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:184)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:207)
    at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
    at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
    at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
    at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
    at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:617)
    at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:595)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)

    ]]

    STEPS
    -----------------------
    The issue can be reproduced at will with the following steps:
    1. Create and deploy outbound agreement.
    2. Invoke B2B Adapter to send message to the b2B Server.
    3. Exception occurs.

    CHANGES

    CAUSE
    B2B properties, b2b.fromTradingPartnerId, b2b.toTradingPartnerId, b2b.documentProtocolVersion, and b2b.documentTypeName, are not set for the B2B Adapter
    invocation.

    The null value for 'ToTP' and document type in the error message indicate that the B2B Adapter invocation properties have not been set.

    Error -: B2B-50547: Agreement not found for trading partners: FromTP (remote trading parnter name), ToTP null with document type ACTION:null Service:null
    ServiceTypenull-OUTBOUND.

    https://support.oracle.com/cloud/faces/DocumentDisplay?_afrLoop=219704353490981&_afrWindowMode=0&id=2128721.1&_adf.ctrl-state=12yd… 3/4
    3/13/24, 12:27 AM Knowledge

    SOLUTION
    Please resolve this issue as follows.

    1) In the composite, open the invoke activity for the B2B Adapter reference.
    2) Click the Property tab.
    3) Find the following properties and set them using the appropriate string literal.
    For example:

    b2b.fromTradingPartnerId -> 'Acme'


    b2b.toTradingPartnerId -> 'GlobalChips'
    b2b.documentProtocolVersion -> '4010'
    b2b.documentTypeName -> '850'

    NOTE: The string literals can be assigned to global variables, and these can be assigned to the properties instead.

    4) Apply changes to the invoke activity.


    5) Redeploy the composite.
    6) Retest this issue to verify it no longer occurs.

    ▼ Related
    Products

    Middleware > Service-Oriented Architecture > SOA Suite/Platform > Oracle SOA Suite > B2B Engine > Core B2B Engine

    Keywords
    AGREEMENT NOT FOUND; DOCUMENT TYPE; INVOKE ACTIVITY; OUTBOUND; PROPERTY

    Back to Top

    © Oracle Site Maps Terms of Use & Privacy Cookie Preferences Contact Support

    https://support.oracle.com/cloud/faces/DocumentDisplay?_afrLoop=219704353490981&_afrWindowMode=0&id=2128721.1&_adf.ctrl-state=12yd… 4/4

    You might also like