B2B Document Definition - Using xpath 'or' in Identification Value

Question

Hello,
I have a requirement similar to the one below, this is an example from the Oracle documentation,
In the below example, Oracle B2B compares the value of the country attribute to the value set for Identification Value. If the values match, then the document is identified successfully.  I have a scenario, where I will receive data with value in the country attribute to be "US" or "France" or "India". Can an 'or' be used in the identification value? such as US or France or India as the Identification values for the Identification Expression "//*/@country".
Any ideas / suggestions are greatly appreciated.
Option 3: Check the Value of an Attribute
Assume that the value of the country attribute is US. Set the parameters as follows:
Field
Value
Identification Value
US
Identification Expression
//*/@country
Here is the excerpt of the XML payload for this option.
Check the Value of an Attribute
<?xml version="1.0" encoding="windows-1252" ?>
<MyAddress country="US" xmlns="http://www.example.org"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="PO.xsd">
  <name>B2B Buyer</name>
  <street>100 Oracle Parkway</street>
  <city>Redwood City</city>
  <state>CA</state>
  <zip>94065</zip>
</MyAddress>
Thanks,
Venkatesh

Answer 1

Hi,
I am interested to know if you managed to make any progress on this issue?
We have a similar requirement whereby a trading partner sends an ebMS request using a single document type with the ebMS ACTION header identifying the action the request relates to. For example, the following are the key fields from two requests:
1)
  SENDER_NAME = TradingPartnerX
  RECEIVER_NAME = OurCompanyName
  SERVICE_NAME = Manage Work
  SERVICE_TYPE = v1.0
  BUSINESS_ACTION_NAME = assignWork
  Payload = <ManageWorkRequest>...</ManageWorkRequest>
2)
  SENDER_NAME = TradingPartnerX
  RECEIVER_NAME = OurCompanyName
  SERVICE_NAME = Manage Work
  SERVICE_TYPE = v1.0
  BUSINESS_ACTION_NAME = updateWork
  Payload = <ManageWorkRequest>...</ManageWorkRequest>
Where the Payloads of the two requests could potentially be identical.
Currently, we have the following configuration:
- Custom xml document type for ManageWorkRequest:
  - Action name: (blank)
  - Service name: (blank)
  - Service type: (blank)
  - From Role: (blank)
  - To Role: (blank)
  - Validate ebMS Header: unchecked
- Custom xml document definition for ManageWorkRequest:
  - XML Identification Expression (XPath): //*[local-name() = 'ManageWorkRequest']
  - XML Identification Value: (blank)
- TradingPartnerX Documents:
  - Definition added for ManageWorkRequest
    - both 'Sender' and 'Receiver' checked
  - Document Details:
    - Override DocType Param: checked
    - Document Type ebMS:
      - Action name: (blank)
      - Service name: Manage Work
      - Service type: v1.0
      - From Role: Buyer
      - To Role: Supplier
      - Validate ebMS Header: unchecked
- Agreement setup between OurCompanyName and TradingPartnerX for inbound communication from TradingPartnerX to OurCompanyName
When TradingPartnerX attempts to send an assignWork ManageWorkRequest, B2B fails to identify which document type and agreement it relates to. After increasing the B2B logging level, the following can be seen in the soa_server1-diagnostic.log file:
[2013-11-19T11:16:39.881+10:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.repository] [tid: Workmanager: , Version: 0, Scheduled=false, Started=false, Wait time: 0 ms\n] [userId: <anonymous>] [ecid: ccce6c0f16adb222:111ddc50:142539e3958:-7ffd-000000000013a96f,0] [APP: soa-infra] [SRC_CLASS: oracle.tip.b2b.log.ToplinkLogger] [SRC_METHOD: log] 2013.11.19 11:16:39.880--ServerSession(606155273)--Connection(692532584)--Thread(Thread[Workmanager: , Version: 0, Scheduled=false, Started=false, Wait time: 0 ms[[
,10,Application Daemon Threads])--SELECT ID, DIRECTION, APPS_DOCTYPE_NAME, DOC_DEF_NAME, APPS_DOC_PROTOCOL_VERSION, DOC_DEF_TIMESTAMP, APPS_DOCUMENT, DOC_PROTOCOL_NAME, APPS_XSLTFILE, DOC_PROTOCOL_VERSION, ATTRIBUTE1, DOC_REF_NAME, ATTRIBUTE3, DOC_ROUTING_ID, ATTRIBUTE5, DOCTYPE_NAME, ATTRIBUTE7, FROM_DC, ATTRIBUTE9, BUSINESS_ACTION_NAME, LABEL, CREATED, LABEL_DESC, APPS_DOC_PROTOCOL_NAME, MODIFIED, APPS_ACTION, RECEIVER_NAME, ATTRIBUTE2, SENDER_NAME, ATTRIBUTE6, SERVICE_NAME, ATTRIBUTE10, SERVICE_TYPE, DEFINITION_MO, STATE, AGREEMENT_ID, TO_DC, ATTRIBUTE8, TPA_NAME, IS_CUSTOM, TPA_REFERENCE, ATTRIBUTE4, CREATED_BY_UI, USER_NAME, CONTROL_NUMBER_SET FROM B2B_LIFECYCLE WHERE ((SENDER_NAME = ?) AND ((RECEIVER_NAME = ?) AND ((BUSINESS_ACTION_NAME = ?) AND ((SERVICE_NAME = ?) AND ((SERVICE_TYPE = ?) AND ((DIRECTION = ?) AND (STATE = ?)))))))
        bind => [TradingPartnerX, OurCompanyName, assignWork, Manage Work, v1.0, INBOUND, Active]
[2013-11-19T11:16:39.883+10:00] [soa_server1] [ERROR] [] [oracle.soa.b2b.engine] [tid: Workmanager: , Version: 0, Scheduled=false, Started=false, Wait time: 0 ms\n] [userId: <anonymous>] [ecid: ccce6c0f16adb222:111ddc50:142539e3958:-7ffd-000000000013a96f,0] [APP: soa-infra] Error -:  B2B-50547:  Agreement not found for trading partners: FromTP TradingPartnerX, ToTP OurCompanyName with document type ACTION:assignWork Service:Manage Work ServiceTypev1.0-INBOUND.[[
        at oracle.tip.b2b.tpa.RepoDataAccessor.queryAgreementMO(RepoDataAccessor.java:866)
        at oracle.tip.b2b.tpa.RepoDataAccessor.getAgreementDetails(RepoDataAccessor.java:415)
        at oracle.tip.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:465)
        at oracle.tip.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:243)
        at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2560)
        at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1751)
        at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4258)
        at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3856)
        at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3309)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:637)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Error -:  B2B-50547:  Agreement not found for trading partners: FromTP TradingPartnerX, ToTP OurCompanyName with document type ACTION:assignWork Service:Manage Work ServiceTypev1.0-INBOUND.
        at oracle.tip.b2b.tpa.RepoDataAccessor.queryAgreementMO(RepoDataAccessor.java:866)
        at oracle.tip.b2b.tpa.RepoDataAccessor.getAgreementDetails(RepoDataAccessor.java:415)
        at oracle.tip.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:465)
        at oracle.tip.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:243)
        at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2560)
        at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1751)
        at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4258)
        at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3856)
        at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3309)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:637)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Looking at the SQL which has been logged, B2B is looking for an agreement which has the following:
  SENDER_NAME = 'TradingPartnerX'
  RECEIVER_NAME = 'OurCompanyName'
  BUSINESS_ACTION_NAME = 'assignWork'
  SERVICE_NAME = 'Manage Work'
  SERVICE_TYPE = 'v1.0'
  DIRECTION = 'INBOUND'
  STATE = 'Active'
and it fails to identify any matching agreements which is correct - there aren't any matching these constraints. However, if we specify the 'Action name' field in the DocType param overrides for TradingPartnerX, then B2B is able to identify the agreement and everything works.
Based on this behaviour, it seems that in this scenario, B2B requires a separate agreement for each possible value which can be passed as the BUSINESS_ACTION_NAME in order to identify the document type and agreement correctly. My question is - is there another way to configure B2B to allow a list of valid 'Action names' rather than having to create a separate agreement for each one with the only difference being the value of the 'Action name' field?
If anyone is able to provide advice or guidance, it would be much appreciated.
Thanks
Kevin