Saturday, April 9, 2011

Setup Oracle SOA B2B for Secured payload (Digitally Signed & Encrypted) using AS2 2.0 protocol


For a large EDI initiative MindTelligent Team was involved in, the assignment was to setup a Oracle B2B exchange for payload using AS 2.0 protocol  This blog discusses the steps to configure Oracle SOA suite 11.1.1.4 B2B server to exchange secured payload (Digitally Signed and Encrypted) using AS2.0 protocol. The post assumes that the user has some prior knowledge of Oracle SOA B2B servers

  • Setup Two WAY SSL on Weblogic 10.3.4 using the link.
  • Ensure that the B2B console can be accessed by using the https://hostname:7002/b2bconsole

  • Document Definition: as2XMLOrder_def 
    • In this example, we are processing a XML using AS  2.0. The option we choose is
      "XML"
    • Identification Expression://*[local-name()='PurchaseOrder']


Setting up "Delivery Channel" for you outbound payloads.

  • Click on Partners-->Channels
  • Select Protocol as AS2-2.0
  • Enter Transport Protocol Parameters
    • URL: http://hostname:port/b2b/httpReceiver
    • User Name: Weblogic user name of remote server
    • Password: Password of the remote server
  • Security Attributes
    •  Ack Signed Checked
    • Message Signed Checked
    • Message Encrypted Signed

















Develop a composite to initiate the process. Ensure that the following assignments are made in the composite

<assign>
            <copy target="$out.property.b2b.fromTradingPartnerId"
                  expression="'AskMind'"/>
            <copy target="$out.property.b2b.toTradingPartnerId"
                  expression="'DST'"/>
            <copy target="$out.property.b2b.documentTypeName"
                  expression="'as2XMLOrderType'"/>
            <copy target="$out.property.b2b.documentProtocolRevision"
                  expression="'as2XML_Version_1.0'"/>
          </assign>

For questions, comments and feedback,  please contact:
 Harvinder Singh Saluja

2 comments:

  1. Hi Harvinder Saluja

    I'm sending an EDI document signed and encrypted, but they can't decrypt the file.
    The documents they send me I can decrypt without any problem, the issue is sending the files.
    Can you help me with this?

    Thanks,

    Best regards!!

    ReplyDelete
  2. Jo, you need to send them your public certificate using which they can decrypt the EDI document. Did you specify a JKS file with private key in the B2Bconsole? Please send then a public key corresponding with that private key.

    ReplyDelete

ForgeRock IAM : OpenDS (Open Directory Server). Importing LDIF files

The most efficient method of importing LDIF data is to take the OpenDJ server offline. Alternatively, you can schedule a task to import the ...