Oracle SOA for Healthcare - Setting Endpoint Acknowledgement Acceptance

Acknowledgment acceptance in SOA Suite for Healthcare is globally set through the console at the document level. Currently there is no way to override the global setting for an endpoint in the SOA for Healthcare console. The illustration below shows acknowledgment acceptance being set in the document type definition in the SOA for Healthcare console


 At this time, the only way to work around this problem is to use the B2B console to override the document type parameters for a given endpoint. This is generally frowned upon by Oracle Product Management and should only be considered a temporary fix. Oracle does not encourage users of SOA Suite for Healthcare to use the B2B console to modify HL7 endpoint configurations created in the SOA for Healthcare console. Doing so, in some cases may cause inconsistent results.

The illustration below shows the HL7 endpoint configuration as viewed through the B2B console. The B2B console has the ability to override the global document type parameter settings by trading partner (or endpoint in SOA for Healthcare).

The proceedure to set the acknowledgment acceptance method for an SOA for Healthcare endpoint is as follows. The illustration above shows the B2B console being used to modify the DocType Parameters for an SOA for Healthcare HL7 endpoint configuration.

  1. Bring up the B2B console for the SOA for Healthcare instance with the URL http://<hostname>:<port>/b2bconsole
  2. On the Partners page, select the desired endpoint in the Partner window on the left side of the page. Next click the Documents tab in the top of the right hand window of the same page.
  3. In the Document Details section of the right hand window, check the box next to ‘Override DocType Param’.
  4. Select the Document Type tab in the Document Details section of the page. The transaction tab will appear below it.
  5. Select the ‘Accept Acknowledgment’ parameter from the drop down list.
  6. ‘Save’ the new DocType Parameter settings.
    Then Deploy/Redeploy the agreement for the endpoint/document type.

    Comments:

    Post a Comment:
    • HTML Syntax: NOT allowed
    About


    This is the blog for the Oracle FMW Architects team fondly known as the A-Team. The A-Team is the central, technical, outbound team as part of the FMW Development organization working with Oracle's largest and most important customers. We support Oracle Sales, Consulting and Support when deep technical and architectural help is needed from Oracle Development.
    Primarily this blog is tailored for SOA issues (BPEL, OSB, BPM, Adapters, CEP, B2B, JCAP)that are encountered by our team. Expect real solutions to customer problems, encountered during customer engagements.
    We will highlight best practices, workarounds, architectural discussions, and discuss topics that are relevant in the SOA technical space today.

    Search

    Archives
    « April 2014
    SunMonTueWedThuFriSat
      
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
       
           
    Today