The Latest Oracle E-Business Suite Technology News direct from
Oracle E-Business Suite Development & Product Management

March 2019 Update to Integrated SOA Gateway for EBS 12.1.3

Rekha Ayothi
Product Management

Contributing Author:  Robert Farrington

[Note: This article was slightly revised on 19 March 2019, to enhance the structure.]

I am pleased to announce availability of consolidated patch for Oracle E-Business Suite Integrated SOA Gateway for Oracle E-Business Suite Release 12.1.3. Oracle strongly recommends all EBS R12.1.3 Integrated SOA Gateway customers apply this set of updates.

You can download the patch from here:

This cumulative update includes all previously released ISG updates for EBS R12.1.3, plus minor enhancements and key fixes for stability and performance of the product. View the patch Readme for a complete listing of bugs fixed in this patch.

The minor enhancements in this update include:

  • Post-clone script for SOAP and REST based web services provided by Integrated SOA Gateway in EBS R12.1.3.
  • Automated design time operations in multi-node configuration.
    This patch eliminates the mandate to perform service generation and deployment from the backend for multi-node configuration of Integrated SOA Gateway in Oracle E-Business Suite R12.1.3 (see MOS Note 1081100.1). With this patch, you can generate, deploy SOAP Services, and deploy REST Services from the Integration Repository UI for multi-node environments as well.

Key fixes included in this update relate to:

  • REF CURSOR and SYS_REFCURSOR data types in PL/SQL interface types.
  • Design time operation from the Integration Repository UI when the API contains more than 10 operations.


Related Articles

Join the discussion

Comments ( 4 )
  • Ravi Monday, August 26, 2019
    If we are using backend soadeploy.sh script to deploy a web service using command soagenerate.sh irepname=FND_GLOBAL before this patch upgrade, what will be the command after the patch upgrade? On a dev environment I used: soagenerate.sh target=deploy irepname=FND_GLOBAL and it is working for first time deployment or redeployment. Can you officially confirm if this is a correct usage?

    Thank you!
  • Rekha Ayothi Tuesday, August 27, 2019
    Hi Ravi,

    Refer following document for usage of soagenerate.sh:

  • Ravi Tuesday, September 3, 2019
    Hi Rekha,

    Thank you very much for your reply. I have gone through the article you suggested, it has useful information. However I could not find information on the command soadeploy.sh.

    My question was related to soadeploy.sh.

    Before this patch upgrade we used:

    $FND_TOP/bin/soadeploy.sh irepname=TEST_HELLO_WORLD logfile=TestHelloWorld.log

    After this patch upgrade can we use below command?

    $FND_TOP/bin/soadeploy.sh target=deploy irepname=TEST_HELLO_WORLD logfile=TestHelloWorld.log

    If yes, can we use the same command multiple times after the service is deployed?

    Do we need to detect if the service is already deployed, then first undeploy by passing target=undeploy and then issue the same command with target=deploy?

    Appreciate your help in providing clarification.

    Thanks & Regards,
  • Rekha Ayothi Tuesday, September 3, 2019
    Thanks for kind words, Ravi. This patch (28785455:R12.OWF.B) does not introduce any change in the usage of soadeploy.sh command. You can continue to use it as you were using it prior to applying this patch.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.