Split (1)

train · 94.6k rows

text stringlengths 65 20k
If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion vi Related Resources vi Conventions vi 1 Understand the Oracle Utilities Adapter Oracle Utilities Adapter Capabilities 1-1 Oracle Utilities Adapter Restrictions 1-3 What Application Version Is Supported?1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion vi Related Resources vi Conventions vi 1 Understand the Oracle Utilities Adapter Oracle Utilities Adapter Capabilities 1-1 Oracle Utilities Adapter Restrictions 1-3 What Application Version Is Supported?1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.
Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion vi Related Resources vi Conventions vi 1 Understand the Oracle Utilities Adapter Oracle Utilities Adapter Capabilities 1-1 Oracle Utilities Adapter Restrictions 1-3 What Application Version Is Supported?1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.
Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion vi Related Resources vi Conventions vi 1 Understand the Oracle Utilities Adapter Oracle Utilities Adapter Capabilities 1-1 Oracle Utilities Adapter Restrictions 1-3 What Application Version Is Supported?1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion vi Related Resources vi Conventions vi 1 Understand the Oracle Utilities Adapter Oracle Utilities Adapter Capabilities 1-1 Oracle Utilities Adapter Restrictions 1-3 What Application Version Is Supported?1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion vi Related Resources vi Conventions vi 1 Understand the Oracle Utilities Adapter Oracle Utilities Adapter Capabilities 1-1 Oracle Utilities Adapter Restrictions 1-3 What Application Version Is Supported?1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.
UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion vi Related Resources vi Conventions vi 1 Understand the Oracle Utilities Adapter Oracle Utilities Adapter Capabilities 1-1 Oracle Utilities Adapter Restrictions 1-3 What Application Version Is Supported?1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?
This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion vi Related Resources vi Conventions vi 1 Understand the Oracle Utilities Adapter Oracle Utilities Adapter Capabilities 1-1 Oracle Utilities Adapter Restrictions 1-3 What Application Version Is Supported?1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion vi Related Resources vi Conventions vi 1 Understand the Oracle Utilities Adapter Oracle Utilities Adapter Capabilities 1-1 Oracle Utilities Adapter Restrictions 1-3 What Application Version Is Supported?1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.
Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion vi Related Resources vi Conventions vi 1 Understand the Oracle Utilities Adapter Oracle Utilities Adapter Capabilities 1-1 Oracle Utilities Adapter Restrictions 1-3 What Application Version Is Supported?1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.
1-4 Workflow to Create and Add an Oracle Utilities Adapter to an Integration 1-4 2 Oracle Utilities Adapter Concepts Authentication Support 2-1 About OAuth 2.0 Grants 2-1 Use OAuth 2.0 Grants 2-5 Authentication Types 2-14 Mapper Connectivity Properties Support 2-14 Asynchronous Trigger Support in Orchestrated Integrations 2-15 3 Create an Oracle Utilities Adapter Connection Prerequisites for Creating a Connection 3-1 Create a Connection 3-2 Configure Connection Properties 3-3 Configure Connection Security 3-3 Configure an Agent Group 3-5 Test the Connection 3-5 Upload an SSL Certificate 3-6 iii4 Add the Oracle Utilities Adapter Connection to an Integration Add the Oracle Utilities Adapter as a Trigger Connection 4-1 Add the Oracle Utilities Adapter as an Invoke Connection 4-4 Integration Activation and Runtime 4-5 5 Troubleshoot the Oracle Utilities Adapter Error Handling and Validations 5-1 java.net.ConnectException Error Message 5-3 Unable to Connect to OUAF Application at Run Time Error Message 5-3 Unresponsive Agent Error Message 5-3 ivPreface The Oracle Utilities Adapter integrates Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.
The Oracle Utilities Adapter lets you integrate Oracle Utilities applications with applications from any vendor.Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.
Simplified integration with your existing legacy or non-Oracle applications makes for faster implementation and reduces cost.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.
The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
Using the Oracle Utilities Adapter includes information and procedures to help you configure the Oracle Utilities Adapter as a connection in an Oracle Integration integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.
These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).
Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?
Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).
Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.
vDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.
Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.
As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.
We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.
Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.
Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .
italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.
monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the Oracle Utilities Adapter As a developer, you can use the Oracle Utilities Adapter to integrate Oracle Utilities applications with your sales, human resources, customer service, contact center, marketing, and reporting applications.The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.
The Oracle Utilities Adapter supports web service standards for the creation of open and reusable service-oriented applications (SOA).Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.
Topics: Oracle Utilities Adapter Capabilities Oracle Utilities Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.
Workflow to Create and Add an Oracle Utilities Adapter to an Integration Oracle Utilities Adapter Capabilities The Oracle Utilities Adapter lets you integrate the Oracle Utilities application suite with other Oracle applications such as Oracle Enterprise Resource Planning (ERP) and Oracle Field Service (OFS).The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.
The Oracle Utilities Adapter provides trigger (inbound) and invoke (outbound) support.This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.
This enables Oracle Utilities Applications to trigger an integration in Oracle Integration or invoke an Oracle Utilities Application using web services from Oracle Integration.Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.
Both inbound and outbound services are exposed using the Oracle Utilities service catalog.This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.
This catalog provides a simplified user experience to create data mappings at design time while constructing integrations with utilities applications using the Oracle Utilities Adapter.Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.
Every inbound and outbound service structure is exposed using a SOAP-based WSDL or REST Swagger definition/OpenAPI URL-based connection.You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.
You can also manually upload a WSDL in the trigger (inbound) direction for a specific service instead of parsing the WSDL from the HTTP-based service catalog WSDL specified on the Connections page.This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .
This option enables you to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.
You can integrate with on-premises Oracle Utilities applications using the on-premises connectivity agent.You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.
You can implement the following message exchange patterns on inbound SOAP and inbound REST endpoints: Synchronous request/response One-way request See Asynchronous Trigger Support in Orchestrated Integrations .Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.
Secure WSDL Support The Oracle Utilities Adapter provides secure WSDL support.1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.
1-1The Oracle Utilities Adapter works with the new SOAP catalog exposed in the Oracle Utilities Application Framework (OUAF) in the cloud using a SOAP proxy.SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.
SOAP proxy and OUAF changes for the cloud are made so that the behavior of the SOAP catalog is similar as in on-premises environments except for the following important changes: The WSDL to retrieve the catalog is secured by default.Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.
Therefore, the credentials must be passed to retrieve the WSDL.Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.
Individual WSDLs of all services exposed by the SOAP catalog are secured by default.Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.
Therefore, credentials must be passed to retrieve the WSDL.The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.
The WSDL link used to retrieve the catalog and individual WSDLs is different.It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.
It points to the SOAP proxy server.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.
For example: http:// host:port/soap/api/iws/F1-SOAPCatalog?WSDL The endpoint within the WSDLs also points to the SOAP proxy.For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.
For example: http:// host:port/soap/api/iws/F1-SOAPCatalog Whenever you use the secured/protected WSDL from a cloud environment, ensure that the security policy for SOAP-based integrations is Basic Authentication.See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.
See Configure Connection Security .REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.
REST Support The Oracle Utilities Adapter provides REST support.You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.
You can create SOAP-based and REST-based integrations using the Oracle Utilities Adapter with a catalog of inbound/outbound services exposed by an OUAF and non- OUAF application.Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.
Users of the Oracle Utilities Adapter can either create the integration using a SOAP catalog URL or REST Swagger definition/OpenAPI URL-based connection.The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.
The existing SOAP catalog works as is and only fetches SOAP-based inbound and outbound services that are available in the SOAP catalog.The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.
The Oracle Utilities Adapter consumes inbound and outbound REST-based services that are available as part of the Swagger definition or an OpenAPI URL provided by OUAF and non-OUAF applications.For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.
For each REST interface (inbound or outbound), an OpenAPI/Swagger definition URL is provided to Oracle Integration as part of the catalog.The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.
The OpenAPI/Swagger specification describes the REST interface.The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.
The current version of Oracle Integration supports the Swagger Version 2 and OpenAPI version 3 specification for the REST Adapter.Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.
Therefore, the Oracle Utilities Adapter should receive Version 2 of the Swagger document or the OpenAPI version 3 catalog URL.The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .
The Oracle Utilities Adapter also supports REST service versions 1.0 and 2.0 inbound web services.Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.
Using the Oracle Utilities Adapter as an invoke connection in an integration invokes the inbound OUAF or non-OUAF REST web services.Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.
Using the Oracle Utilities Adapter as a trigger connection in an integration consumes an outbound message from an OUAF or non-OUAF application.Chapter 1 Oracle Utilities Adapter Capabilities 1-2Catalog format for an OUAF application.https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.
https:// host:port/ouaf/rest/ouaf/openapi/iws/catalog or https:// host:port/../../../rest/openapi/iws/catalog Catalog format for a non-OUAF application.https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.
https:// host:port/nms- application_code /rest/v1/catalog Where: ###application_code is code for application.Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?
Please refer to non-OUAF application documentation for the application code.OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.
OAuth 2.0 Support The Oracle Utilities Adapter supports the Open Authorization (OAuth 2.0 ) security policy for REST-based connections.This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .
This enables you to configure the Oracle Utilities Adapter to consume a Swagger 2.0 or an OpenAPI 3.0 API protected with OAuth 2.0 Token-Based Authentication.Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.
Under Token-Based Authentication, OAuth Resource Owner Password Credentials are supported.This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.
This policy is useful when the Basic Authentication security policy is not sufficient.Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.
Most HTTP or HTTPS services typically use the OAuth authorization framework to protect their resources.In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.
In accordance with the OAuth 2.0 specification, the OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service.This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?
This is either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service or by enabling the third-party application to obtain access on its own behalf.See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.
See Configure Connection Security .Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.
Oracle Utilities Adapter Restrictions The Oracle Utilities Adapter can only be used with Oracle Utilities applications that support web services.If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.
If you are using DB file or Java Message Service (JMS) integration services, generic Oracle Integration adapters must be used and not the Oracle Utilities Adapter.Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.
Note: There are overall service limits for Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).
A service limit is the quota or allowance set on a resource.See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.
See Service Limits.Chapter 1 Oracle Utilities Adapter Restrictions 1-3What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.
For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.
See Connectivity Certification Matrix .Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.
Workflow to Create and Add an Oracle Utilities Adapter to an Integration You can set up the Oracle Utilities Adapter by completing the tasks listed in the table.This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.
This image represents the workflow for setting up an adapter: Step Description More Information 1 Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.
The connections can be reused in multiple integrations and are typically created by the administrator.Create a Connection 2 Create the integration.When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.
When you do this, you add trigger and invoke connections to the integration.Create Integrations and Add the Oracle Utilities Adapter Connection to an Integration 3 Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 4 (Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 5 Activate the integration.Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.
Manage Integrations in Using Integrations in Oracle Integration Generation 2 6 Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 7 Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 8 Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.
1-42 Oracle Utilities Adapter Concepts The following sections describe Oracle Utilities Adapter capabilities in detail.Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.
Authentication Support Mapper Connectivity Properties Support Asynchronous Trigger Support in Orchestrated Integrations Authentication Support The following sections describe Oracle Utilities Adapter authentication capabilities in detail.About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.
About OAuth 2.0 Grants Use OAuth 2.0 Grants Authentication Types About OAuth 2.0 Grants The following sections describe Oracle Utilities Adapter authentication capabilities in detail.This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.
This authentication scheme enables external clients to acquire a token that is also sent as part of the request sent to invoke Oracle Utilities application APIs.The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.
The most important step for an application in the OAuth flow is how the application receives an access token (and optionally a refresh token).A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.
A grant type is the mechanism used to retrieve the token.OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.
OAuth defines several different access grant types that represent different authorization mechanisms.Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.
Applications can request an access token to access protected endpoints in different ways, depending on the type of grant type specified in the Oracle Identity Cloud Service application.A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.
A grant is a credential representing the resource owner's authorization to access a protected resource.The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.
The following sections discuss the various grant types and their pros/cons, along with instructions on how to configure the specific grant type.There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.
There are several OAuth 2.0 grant types you can use in Oracle Integration with the Oracle Utilities Adapter.Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.
Review the following information to identify the grant type to use for your use case.2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.

Subsets and Splits

No community queries yet

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