Split (1)

train · 94.6k rows

text stringlengths 65 20k
For example, when the input for the divisor is zero, the operation results in a fault.Using a global fault handler, the integration flow returns the fault details as a response.As input to the recipe, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or fault details as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>60</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:plnk="http:// schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:ns1="http://www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ics/fault" xmlns:dvm="http://www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:nsmpr1="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:wsx="http:// schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs30="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs31="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs9="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath119774 4749" xmlns:orajs7="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath605343Appendix A Oracle Integration Starter Recipes A-205Integration Name Description 633" xmlns:orajs8="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath185128 3090" xmlns:orajs5="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath188653 5281" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath640595 824" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath107305 9868" xmlns:orajs4="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath102406 8758" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath149642 6531" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/ addressing/policy" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns:orajs20="http:// www.oracle.com/XSL/Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs21="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs22="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs27="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs28="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs29="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs23="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs24="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171Appendix A Oracle Integration Starter Recipes A-206Integration Name Description 120" xmlns:orajs25="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs26="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath481947 08" xmlns:orajs11="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath206724 5588" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath114692 5263" xmlns:orajs17="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath182264 4184" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath133935 528" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:nstrgdfl="http://xmlns.oracle.com/procmon" xmlns:ns28="http://xmlns.oracle.com/ics/tracking/ ics_tracking_context.xsd" xmlns:msc="http:// schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:nstrgmpr="http://Example.org" xmlns="http:// Example.org"> <nstrgmpr:result>Review JavaScript error(s) and fix them: error: null@18 -> DivideByZeroError at: function=divide, loc=js/TestAPILibrary_1.0/ calc.js, line=18</nstrgmpr:result> </DivideResponse>Appendix A Oracle Integration Starter Recipes A-207Integration Name Description SOAP Library Div Inscope FaultHandlerPerforms the division operation on the input data, and uses an in-scope fault handler to catch and handle errors during the operation.For example, when the input for the divisor is zero, the operation results in a fault.The in-scope fault handler in the integration flow handles the fault by interchanging the values of the divisor and the dividend.The integration flow then completes the division operation successfully and returns the result as a response.As input to the integration, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or the output of the modified operation (in case the operators are interchanged due to a fault) as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.
Using a global fault handler, the integration flow returns the fault details as a response.As input to the recipe, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or fault details as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>60</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:plnk="http:// schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:ns1="http://www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ics/fault" xmlns:dvm="http://www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:nsmpr1="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:wsx="http:// schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs30="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs31="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs9="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath119774 4749" xmlns:orajs7="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath605343Appendix A Oracle Integration Starter Recipes A-205Integration Name Description 633" xmlns:orajs8="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath185128 3090" xmlns:orajs5="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath188653 5281" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath640595 824" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath107305 9868" xmlns:orajs4="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath102406 8758" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath149642 6531" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/ addressing/policy" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns:orajs20="http:// www.oracle.com/XSL/Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs21="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs22="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs27="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs28="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs29="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs23="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs24="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171Appendix A Oracle Integration Starter Recipes A-206Integration Name Description 120" xmlns:orajs25="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs26="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath481947 08" xmlns:orajs11="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath206724 5588" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath114692 5263" xmlns:orajs17="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath182264 4184" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath133935 528" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:nstrgdfl="http://xmlns.oracle.com/procmon" xmlns:ns28="http://xmlns.oracle.com/ics/tracking/ ics_tracking_context.xsd" xmlns:msc="http:// schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:nstrgmpr="http://Example.org" xmlns="http:// Example.org"> <nstrgmpr:result>Review JavaScript error(s) and fix them: error: null@18 -> DivideByZeroError at: function=divide, loc=js/TestAPILibrary_1.0/ calc.js, line=18</nstrgmpr:result> </DivideResponse>Appendix A Oracle Integration Starter Recipes A-207Integration Name Description SOAP Library Div Inscope FaultHandlerPerforms the division operation on the input data, and uses an in-scope fault handler to catch and handle errors during the operation.For example, when the input for the divisor is zero, the operation results in a fault.The in-scope fault handler in the integration flow handles the fault by interchanging the values of the divisor and the dividend.The integration flow then completes the division operation successfully and returns the result as a response.As input to the integration, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or the output of the modified operation (in case the operators are interchanged due to a fault) as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.
As input to the recipe, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or fault details as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>60</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:plnk="http:// schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:ns1="http://www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ics/fault" xmlns:dvm="http://www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:nsmpr1="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:wsx="http:// schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs30="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs31="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs9="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath119774 4749" xmlns:orajs7="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath605343Appendix A Oracle Integration Starter Recipes A-205Integration Name Description 633" xmlns:orajs8="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath185128 3090" xmlns:orajs5="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath188653 5281" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath640595 824" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath107305 9868" xmlns:orajs4="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath102406 8758" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath149642 6531" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/ addressing/policy" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns:orajs20="http:// www.oracle.com/XSL/Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs21="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs22="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs27="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs28="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs29="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs23="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs24="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171Appendix A Oracle Integration Starter Recipes A-206Integration Name Description 120" xmlns:orajs25="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs26="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath481947 08" xmlns:orajs11="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath206724 5588" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath114692 5263" xmlns:orajs17="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath182264 4184" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath133935 528" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:nstrgdfl="http://xmlns.oracle.com/procmon" xmlns:ns28="http://xmlns.oracle.com/ics/tracking/ ics_tracking_context.xsd" xmlns:msc="http:// schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:nstrgmpr="http://Example.org" xmlns="http:// Example.org"> <nstrgmpr:result>Review JavaScript error(s) and fix them: error: null@18 -> DivideByZeroError at: function=divide, loc=js/TestAPILibrary_1.0/ calc.js, line=18</nstrgmpr:result> </DivideResponse>Appendix A Oracle Integration Starter Recipes A-207Integration Name Description SOAP Library Div Inscope FaultHandlerPerforms the division operation on the input data, and uses an in-scope fault handler to catch and handle errors during the operation.For example, when the input for the divisor is zero, the operation results in a fault.The in-scope fault handler in the integration flow handles the fault by interchanging the values of the divisor and the dividend.The integration flow then completes the division operation successfully and returns the result as a response.As input to the integration, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or the output of the modified operation (in case the operators are interchanged due to a fault) as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .
The integration returns the output of the operation or fault details as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>60</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:plnk="http:// schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:ns1="http://www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ics/fault" xmlns:dvm="http://www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:nsmpr1="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:wsx="http:// schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs30="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs31="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs9="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath119774 4749" xmlns:orajs7="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath605343Appendix A Oracle Integration Starter Recipes A-205Integration Name Description 633" xmlns:orajs8="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath185128 3090" xmlns:orajs5="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath188653 5281" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath640595 824" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath107305 9868" xmlns:orajs4="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath102406 8758" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath149642 6531" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/ addressing/policy" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns:orajs20="http:// www.oracle.com/XSL/Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs21="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs22="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs27="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs28="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs29="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs23="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs24="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171Appendix A Oracle Integration Starter Recipes A-206Integration Name Description 120" xmlns:orajs25="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs26="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath481947 08" xmlns:orajs11="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath206724 5588" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath114692 5263" xmlns:orajs17="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath182264 4184" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath133935 528" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:nstrgdfl="http://xmlns.oracle.com/procmon" xmlns:ns28="http://xmlns.oracle.com/ics/tracking/ ics_tracking_context.xsd" xmlns:msc="http:// schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:nstrgmpr="http://Example.org" xmlns="http:// Example.org"> <nstrgmpr:result>Review JavaScript error(s) and fix them: error: null@18 -> DivideByZeroError at: function=divide, loc=js/TestAPILibrary_1.0/ calc.js, line=18</nstrgmpr:result> </DivideResponse>Appendix A Oracle Integration Starter Recipes A-207Integration Name Description SOAP Library Div Inscope FaultHandlerPerforms the division operation on the input data, and uses an in-scope fault handler to catch and handle errors during the operation.For example, when the input for the divisor is zero, the operation results in a fault.The in-scope fault handler in the integration flow handles the fault by interchanging the values of the divisor and the dividend.The integration flow then completes the division operation successfully and returns the result as a response.As input to the integration, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or the output of the modified operation (in case the operators are interchanged due to a fault) as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.
Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>60</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:plnk="http:// schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:ns1="http://www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ics/fault" xmlns:dvm="http://www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:nsmpr1="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:wsx="http:// schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs30="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs31="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs9="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath119774 4749" xmlns:orajs7="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath605343Appendix A Oracle Integration Starter Recipes A-205Integration Name Description 633" xmlns:orajs8="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath185128 3090" xmlns:orajs5="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath188653 5281" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath640595 824" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath107305 9868" xmlns:orajs4="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath102406 8758" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath149642 6531" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/ addressing/policy" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns:orajs20="http:// www.oracle.com/XSL/Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs21="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs22="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs27="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs28="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs29="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs23="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs24="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171Appendix A Oracle Integration Starter Recipes A-206Integration Name Description 120" xmlns:orajs25="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs26="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath481947 08" xmlns:orajs11="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath206724 5588" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath114692 5263" xmlns:orajs17="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath182264 4184" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath133935 528" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:nstrgdfl="http://xmlns.oracle.com/procmon" xmlns:ns28="http://xmlns.oracle.com/ics/tracking/ ics_tracking_context.xsd" xmlns:msc="http:// schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:nstrgmpr="http://Example.org" xmlns="http:// Example.org"> <nstrgmpr:result>Review JavaScript error(s) and fix them: error: null@18 -> DivideByZeroError at: function=divide, loc=js/TestAPILibrary_1.0/ calc.js, line=18</nstrgmpr:result> </DivideResponse>Appendix A Oracle Integration Starter Recipes A-207Integration Name Description SOAP Library Div Inscope FaultHandlerPerforms the division operation on the input data, and uses an in-scope fault handler to catch and handle errors during the operation.For example, when the input for the divisor is zero, the operation results in a fault.The in-scope fault handler in the integration flow handles the fault by interchanging the values of the divisor and the dividend.The integration flow then completes the division operation successfully and returns the result as a response.As input to the integration, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or the output of the modified operation (in case the operators are interchanged due to a fault) as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.
For example, when the input for the divisor is zero, the operation results in a fault.The in-scope fault handler in the integration flow handles the fault by interchanging the values of the divisor and the dividend.The integration flow then completes the division operation successfully and returns the result as a response.As input to the integration, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or the output of the modified operation (in case the operators are interchanged due to a fault) as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.
The in-scope fault handler in the integration flow handles the fault by interchanging the values of the divisor and the dividend.The integration flow then completes the division operation successfully and returns the result as a response.As input to the integration, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or the output of the modified operation (in case the operators are interchanged due to a fault) as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.
The integration flow then completes the division operation successfully and returns the result as a response.As input to the integration, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or the output of the modified operation (in case the operators are interchanged due to a fault) as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.
As input to the integration, you must specify the dividend as the first input and the divisor as the second input.The integration returns the output of the operation or the output of the modified operation (in case the operators are interchanged due to a fault) as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).
The integration returns the output of the operation or the output of the modified operation (in case the operators are interchanged due to a fault) as the response.Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.
Example Input Payload: <exam:Divide> <!--Optional:--> <exam:a>10</exam:a> <!--Optional:--> <exam:b>0</exam:b> </exam:Divide> Example Output Payload: <DivideResponse xmlns:wsa="http:// schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns0="http://www.oracle.com/XSL/Transform/java/ oracle.tip.dvm.LookupValue" xmlns:ns1="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.resources.icsxpathfunctions.ICSInstanceT rackingFunctions" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http:// schemas.xmlsoap.org/wsdl/" xmlns:wsp="http:// schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:nsmpr0="http://www.oracle.com/2014/03/ic/ integration/metadata" xmlns:dvm="http:// www.oracle.com/XSL/Transform/java/ com.bea.wli.sb.functions.dvm.DVMFunctions" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:orajs10="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath428770 522" xmlns:orajs11="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath151171 120" xmlns:wsaw="http://www.w3.org/2006/05/addressing/ wsdl" xmlns:wsa10="http://www.w3.org/2005/08/ addressing" xmlns:orajs16="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath126454 0111" xmlns:orajs17="http://www.oracle.com/XSL/Appendix A Oracle Integration Starter Recipes A-208Integration Name Description Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath908143 547" xmlns:orajs18="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath889320 555" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/ soap12/" xmlns:orajs19="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath226366 833" xmlns:orajs12="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath754435 699" xmlns:orajs9="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath137275 3807" xmlns:orajs13="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath248742 258" xmlns:orajs7="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath591907 397" xmlns:orajs14="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath213040 8426" xmlns:orajs15="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath178652 5844" xmlns:orajs8="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath263876 15" xmlns:orajs5="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath132287 2458" xmlns:orajs6="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath917958 894" xmlns:orajs3="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath86288" xmlns:orajs4="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath199629 1323" xmlns:orajs1="http://www.oracle.com/XSL/ Transform/java/ oracle.tip.pc.services.functions.JsExecutor_xpath729152 639" xmlns:orajs2="http://www.oracle.com/XSL/Transform/ java/ oracle.tip.pc.services.functions.JsExecutor_xpath161156 5945" xmlns:orajs0="http://www.oracle.com/XSL/ Transform/java/Appendix A Oracle Integration Starter Recipes A-209Integration Name Description oracle.tip.pc.services.functions.JsExecutor_xpath503065 307" xmlns:msc="http://schemas.microsoft.com/ws/ 2005/12/wsdl/contract" xmlns:wsap="http:// schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:nstrgmpr="http://Example.org" xmlns:soap="http:// schemas.xmlsoap.org/wsdl/soap/" xmlns="http:// Example.org"> <nstrgmpr:result>0</nstrgmpr:result> </DivideResponse> System and Access Requirements Oracle Integration Install, Configure, and Run the Recipes For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.
To use the recipes in the Oracle Integration SOAP \| Calculator Operations package, you must configure the Oracle SOAP Connection.You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.
You only need to configure this connection once.All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.
All the recipes in the package use the same connection.You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.
You must supply the following information when you configure this connection.Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?
Connection Name Parameters Oracle SOAP Connection Connection Properties WSDL URL: Specify the WSDL URL to receive the input data.For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .
For more details, see Create a SOAP Adapter Connection in Using the SOAP Adapter with Oracle Integration .Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.
Related Documentation Using the SOAP Adapter with Oracle Integration Get Stocks Data Use this recipe to get the stock-related data of a company from an external source and send the details to the caller as a response.Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.
Note: This recipe is available as Oracle REST Stock Service in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).
Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.
The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.
No support is provided for this recipe.Appendix A Oracle Integration Starter Recipes A-210Overview This recipe demonstrates how to get the stock-related data of a particular company on a certain date from an external source and send the stock details to the caller as a response.To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.
To use the recipe, you must configure the Oracle REST Get Stock Quote Connection by specifying the connection URL of a stocks application (for example, https:// api.polygon.io/v1/open-close ).Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.
Subsequently, you can trigger the first REST Adapter of the recipe by specifying a company symbol, date, and the API key for the connection URL.The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.
The second REST Adapter (which uses the REST connection you configured) is then invoked in the integration, and it fetches the stock details from the specified connection URL.The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.
The response containing the stock-related data is returned to you.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.
A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.
You can also track the integration and monitor the message status.You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.
You can invoke the REST API using the following command to get the stock-related data through the recipe: GET: https://host:port/ic/api/integration/v1/flows/rest/ORCL-R- REST_STOCK_SERVICE/1.0/v1/open-close?symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.
symbol={company_symbol}&date={date}&apiKey={api_key} Example Response Payload: { "status": "OK", "from": "2020-09-09", "symbol": "IBM", "open": 122.13, "high": 123.7, "low": 121.29, "close": 122.26, "volume": 3875357, "afterHours": 122.7, "preMarket": 121.95 } System and Access Requirements Oracle Integration A stocks application's connection URL and API key Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.
To use this recipe, you must configure the Oracle REST Get Stock Quote Connection.You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.
You must supply the following information when you configure this connection.Appendix A Oracle Integration Starter Recipes A-211Connection Name Parameters Oracle REST Get Stock Quote ConnectionConnection Properties Connection Type: REST API Base URL.Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.
Connection URL: The connection URL of a stocks application (for example, https://api.polygon.io/v1/open-close ).Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.
Security Security Policy: API Key Based Authentication.API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.
API Key: The API key for the connection URL.For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.
For more details, see Create a REST Adapter Connection.Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.
Related Documentation Using the REST Adapter with Oracle Integration Say Hello World Use this recipe to see how you can use simple log and email notification actions with a REST Adapter in an orchestrated integration.Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.
Note: This recipe is available as Oracle Integration REST \| Say Hello World in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.
Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.
The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.
No support is provided for this recipe.Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.
Description This recipe demonstrates how to use simple log and email notification actions with a REST Adapter in an orchestrated integration.The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.
The REST Adapter gets triggered when you specify a URL.The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.
The integration has a switch activity with two rules is defined.If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.
If you provide both an email address and a name when triggering the REST Adapter, then a browser response and email response are sent to you.If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.
If you provide only a name when triggering the REST Adapter, then only a browser response is sent to you.With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.
With either switch rule, a logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.
You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.
System Requirements Oracle Integration Related Documentation Run the Hello World SampleAppendix A Oracle Integration Starter Recipes A-212Say Hello World Invoke Use this recipe to call and invoke a simple REST web service in an orchestrated integration.Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.
Simple logging is also used.Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.
Note: This recipe is available as Oracle Integration REST \| Say Hello World Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.
Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.
The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.
No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.
Description This recipe demonstrates how to call and invoke a simple REST web service in an orchestrated integration.The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.
The REST Adapter is triggered when you specify a URL.The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.
The Hello World REST Adapter that you previously used in the Say Hello World recipe is invoked in the integration.The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.
The name and email address response are sent to you in JSON format.A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.
A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.
You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.
System Requirements Oracle Integration Related Documentation Run the Hello World Invoke Sample Say Hello World Map Data Invoke Use this recipe to call and invoke a simple REST web service using the Map Data integration pattern.Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.
Note: This recipe is available as Oracle Integration REST \| Say Hello World Map Data Invoke in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.
Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.
The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.
No support is provided for this recipe.Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.
Description This recipe demonstrates how to call and invoke a simple REST web service using the Map Data integration pattern.The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.
The REST Adapter is triggered when you specify a URL.The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.
The Hello World Invoke REST Adapter is invoked in the integration.The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.
The name and email address response are sent to you in JSON format.Appendix A Oracle Integration Starter Recipes A-213A logging message is created and logged to the activity stream for viewing.You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.
You can also track the integration and monitor message status.System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.
System Requirements Oracle Integration Related Documentation Run the Hello World Map Data Invoke Sample Send Files from Your Application by Email Use this recipe to send files from an external application to a specified email address.Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .
Note: This recipe is available as REST Oracle Integration \| Send Files by Email in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.
Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.
The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.
No support is provided for this recipe.Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.
Overview When this recipe receives a REST request containing a file from an external application or from another integration flow in Oracle Integration, it sends the file as an email attachment to a specified email address.The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.
The recipe contains an app-driven orchestration integration, which uses the standard REST Adapter.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.
To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .
Subsequently, you can activate the integration flow of the package and send a REST request containing a file to the integration's endpoint URL from an external application.When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .
When triggered, the integration flow sends the file received to the specified email address as an attachment.If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.
If your REST request doesn't contain a file, the integration flow isn't triggered and the email message isn't sent.Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.
Note: You can send only one file at a time with this recipe.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .
System and Access Requirements Oracle Integration, Version 21.2.1.0.0 or higher Topics: Install and Configure the Recipe Activate and Run the RecipeAppendix A Oracle Integration Starter Recipes A-214Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.
1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.
2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.
3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.
4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .
5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.
The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .
Configure the following resources before you activate and run the recipe.Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.
Configure the Oracle REST Trigger Connection Configure the Lookup Table Configure the Oracle REST Trigger Connection Test and save the Oracle REST Trigger connection.1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.4.Click Back to return to the Configuration Editor page.
1.On the Configuration Editor page, select Oracle REST Trigger Connection .2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.4.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.Appendix A Oracle Integration Starter Recipes A-2151.On the Configuration Editor page, click Activate in the title bar.
2.Click Edit .3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.4.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.Appendix A Oracle Integration Starter Recipes A-2151.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.
3.On the Oracle REST Trigger Connection page, click Test to ensure that your connection is correctly configured.A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.4.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.Appendix A Oracle Integration Starter Recipes A-2151.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.
A confirmation message is displayed if your test is successful.4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.4.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.Appendix A Oracle Integration Starter Recipes A-2151.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.
4.Click Save .If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.4.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.Appendix A Oracle Integration Starter Recipes A-2151.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Run the recipe from an external application.
If prompted, click Save for a second time.5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.4.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.Appendix A Oracle Integration Starter Recipes A-2151.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Run the recipe from an external application.a.On the Configuration Editor page, select the integration and click Run .
5.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.4.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.Appendix A Oracle Integration Starter Recipes A-2151.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Run the recipe from an external application.a.On the Configuration Editor page, select the integration and click Run .b.On the resulting pop-up dialog, click the Metadata URL link.
Click Save again if prompted.Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.4.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.Appendix A Oracle Integration Starter Recipes A-2151.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Run the recipe from an external application.a.On the Configuration Editor page, select the integration and click Run .b.On the resulting pop-up dialog, click the Metadata URL link.c.From the new tab that opens, copy the Endpoint URL value.
Configure the Lookup Table Edit the lookup table and enter the recipient email address to which you want the files sent.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the SenderEmail and RecipientEmail fields, enter the corresponding email addresses.3.Click Save .If prompted, click Save for a second time.4.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.Appendix A Oracle Integration Starter Recipes A-2151.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Run the recipe from an external application.a.On the Configuration Editor page, select the integration and click Run .b.On the resulting pop-up dialog, click the Metadata URL link.c.From the new tab that opens, copy the Endpoint URL value.This is the integration flow's endpoint URL.

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.