text
stringlengths 65
20k
|
|---|
3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.Chapter 3 Upload an SSL Certificate 3-7ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content. |
PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.Chapter 3 Upload an SSL Certificate 3-7ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format. |
Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.Chapter 3 Upload an SSL Certificate 3-7ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use. |
PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.Chapter 3 Upload an SSL Certificate 3-7ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text. |
You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.Chapter 3 Upload an SSL Certificate 3-7ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked. |
a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.Chapter 3 Upload an SSL Certificate 3-7ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties. |
i.Click Browse , then select the PGP file to upload.Chapter 3 Upload an SSL Certificate 3-7ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration. |
b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked. |
i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed. |
ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection. |
Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status . |
ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name. |
ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do? |
This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality. |
This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI? |
No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction. |
iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI. |
Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters. |
c.Click Upload .Chapter 3 Upload an SSL Certificate 3-84 Add the Oracle Utilities Adapter Connection to an Integration When you drag the Oracle Utilities Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction. |
This wizard guides you through configuration of the Oracle Utilities Adapter endpoint properties.The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page. |
The following section describe the wizard pages that guide you through configuration of the Oracle Utilities Adapter as a trigger or invoke in an integration.Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements. |
Topics Add the Oracle Utilities Adapter as a Trigger Connection Add the Oracle Utilities Adapter as an Invoke Connection Integration Activation and Runtime Add the Oracle Utilities Adapter as a Trigger Connection When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable. |
Based on your selections in the wizard, the following pages can be displayed.Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out. |
Trigger Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications. |
For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration. |
You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects. |
You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints. |
Enter an optional description of connection functionality.What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint. |
What is the endpoint's relative resource URI?(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke. |
(Available only in the REST-based trigger (inbound) direction.)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services. |
)Enter the endpoints relative resource URI.The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON. |
The endpoint must begin with a /, followed by letters.4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object. |
4-1Field Description Select an option to define the request and response endpoints (Available only in the SOAP -based trigger (inbound) direction.)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications. |
)Business Objects : Select this option to use the HTTP-based service catalog WSDL specified on the Connections page.Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration. |
Upload WSDL : Select this option, then click Browse to upload a WSDL for a particular service in which element-to-element mappings can be performed to deal with anytype elements.Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints. |
Ensure that the WSDL is available as part of the Utilities Global Business Unit (UGBU) applications and is reachable.Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint. |
Note: Remove the parts of the WSDL that are not needed instead of commenting them out.Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default. |
Trigger Request Page This page enables you to select the external system to treat as the request object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration. |
Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a request that starts the integration.Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern. |
Filter by object name Enter the initial letters to filter the display of business objects.Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern). |
Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration. |
)Select either JSON or XML as the request media type for this endpoint.For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects. |
For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows: Field Description Select a Request Object Select a service request object to invoke.Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON. |
Filter by object name Enter the initial letters to filter the display of business services.Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object. |
Request Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default. |
Select the Operation Select an operation from the published web service to perform on the service request object.Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration. |
Trigger Response Page This page enables you to select the external system to treat as the response object for this integration for OUAF applications.Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern. |
Field Description Select a Business Object Select the business object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern). |
Filter by object name Enter the initial letters to filter the display of business objects.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-2Field Description Select Media Type (Available only for REST endpoints.)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard. |
)Select either JSON or XML as the response media type for this endpoint.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter. |
Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed. |
The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file. |
This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked. |
Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern).Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed. |
Send Faults For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows: Field Description Select a Response Object Select the service response object from the Oracle Utilities application to receive as a response from the integration.Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection. |
Filter by object name Enter the initial letters to filter the display of business objects.Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status . |
Response Media Type The supported media type is JSON.Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name. |
Select the Operation Select an operation from the published web service to perform on the service response object.Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do? |
Response Type Select one of these options: Request-Response : The default.The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality. |
The Oracle Utilities application waits until a response is received from the integration.This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration. |
This is also known as the request and response message exchange pattern.Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply. |
Disable the checkbox for asynchronous calls (also known as the one- way message exchange pattern).Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke. |
Send Faults Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services. |
The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction. |
For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type. |
For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON. |
To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Chapter 4 Add the Oracle Utilities Adapter as a Trigger Connection 4-3Add the Oracle Utilities Adapter as an Invoke Connection When you drag the Oracle Utilities Adapter into the integration canvas as an invoke connection, the Adapter Endpoint Configuration Wizard is invoked.Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction. |
Based on your selections in the wizard, the following pages can be displayed.Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type. |
Invoke Basic Info Page Field Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the purpose of the connection.For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON. |
For example, LinkedInTarget_update_status .You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service. |
You can use English alphabetic characters, numbers, underscores, and dashes in the name.You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints. |
You cannot use: Blank spaces (for example, My FTP Connection ) Special characters (for example, #;83& or righ(t)now4 ) Multibyte characters What does this endpoint do?Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard. |
Enter an optional description of connection functionality.Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter. |
Invoke Operation Page This page enables you to select the business service and operation to use for the target integration.Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed. |
Select the request or response payload type through which the endpoint can reply.Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file. |
Field Description Select a Business Service Select a business service to invoke.Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back. |
Filter by service name Enter the initial letters to filter the display of business services.Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration. |
Request Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter. |
)Select the request payload type.Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided. |
Supported payload types are XML and JSON.Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center. |
Response Payload Type (Available only in the REST-based invoke (outbound) direction.)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter. |
)Select the response payload type.Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections. |
Supported payload types are XML and JSON.Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections. |
Select the Operation Select an operation from the published web service.Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page. |
Send Faults (Available only for REST endpoints.)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters. |
)By default, Send Faults is enabled.Chapter 4 Add the Oracle Utilities Adapter as an Invoke Connection 4-4Summary Page Field Description Summary Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard.The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed. |
The information that's displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration. |
For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST. |
For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST. |
To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration. |
Integration Activation and Runtime The activated integration provides one endpoint to trigger the integration.This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration.The following error message is displayed: Activation Error:- This Integration was created using REST based connection but now connection changed to SOAP. |
This endpoint has the following information: REST endpoint URL Swagger definition URL Resource URI Request and response media type For example: Chapter 4 Integration Activation and Runtime 4-55 Troubleshoot the Oracle Utilities Adapter Review the following topics to learn about troubleshooting issues with Oracle Utilities Adapter.Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration.The following error message is displayed: Activation Error:- This Integration was created using REST based connection but now connection changed to SOAP.Configure your connection to REST again or edit the integration for SOAP. |
Topics: Error Handling and Validations java.net.ConnectException Error Message Unable to Connect to OUAF Application at Run Time Error Message Unresponsive Agent Error Message Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration.The following error message is displayed: Activation Error:- This Integration was created using REST based connection but now connection changed to SOAP.Configure your connection to REST again or edit the integration for SOAP.The Oracle Utilities Adapter uses the following strategy to handle errors in the invoke (outbound) and trigger (inbound) directions for REST endpoints. |
See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration.The following error message is displayed: Activation Error:- This Integration was created using REST based connection but now connection changed to SOAP.Configure your connection to REST again or edit the integration for SOAP.The Oracle Utilities Adapter uses the following strategy to handle errors in the invoke (outbound) and trigger (inbound) directions for REST endpoints.Error Handling in the Invoke (Outbound) Direction : The Oracle Utilities Adapter in the invoke (outbound) direction returns a standard APIInvocationError for any HTTP response that it receives with an error code. |
Error Handling and Validations Note the following issues when designing an integration with the Oracle Utilities Adapter.The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration.The following error message is displayed: Activation Error:- This Integration was created using REST based connection but now connection changed to SOAP.Configure your connection to REST again or edit the integration for SOAP.The Oracle Utilities Adapter uses the following strategy to handle errors in the invoke (outbound) and trigger (inbound) directions for REST endpoints.Error Handling in the Invoke (Outbound) Direction : The Oracle Utilities Adapter in the invoke (outbound) direction returns a standard APIInvocationError for any HTTP response that it receives with an error code.In addition, it also produces an APIInvocationError if a processing error occurs within the Oracle Utilities Adapter while preparing the request, calling the endpoint, or handling the response. |
The Basic Authentication, OAuth Resource Owner Password Credentials, and OAuth Client Credentials security policies are currently supported by REST-based connections.The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration.The following error message is displayed: Activation Error:- This Integration was created using REST based connection but now connection changed to SOAP.Configure your connection to REST again or edit the integration for SOAP.The Oracle Utilities Adapter uses the following strategy to handle errors in the invoke (outbound) and trigger (inbound) directions for REST endpoints.Error Handling in the Invoke (Outbound) Direction : The Oracle Utilities Adapter in the invoke (outbound) direction returns a standard APIInvocationError for any HTTP response that it receives with an error code.In addition, it also produces an APIInvocationError if a processing error occurs within the Oracle Utilities Adapter while preparing the request, calling the endpoint, or handling the response.The format of the APIInvocationError in the mapper is as follows. |
The Username Password Token and Basic Authentication security policies are currently supported by SOAP-based connections.Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration.The following error message is displayed: Activation Error:- This Integration was created using REST based connection but now connection changed to SOAP.Configure your connection to REST again or edit the integration for SOAP.The Oracle Utilities Adapter uses the following strategy to handle errors in the invoke (outbound) and trigger (inbound) directions for REST endpoints.Error Handling in the Invoke (Outbound) Direction : The Oracle Utilities Adapter in the invoke (outbound) direction returns a standard APIInvocationError for any HTTP response that it receives with an error code.In addition, it also produces an APIInvocationError if a processing error occurs within the Oracle Utilities Adapter while preparing the request, calling the endpoint, or handling the response.The format of the APIInvocationError in the mapper is as follows.The errorDetails section contains the actual cause. |
Dragging the Oracle Utilities Adapter connection to the trigger area of the integration canvas prompts you to enter the relative resource URI on the Basic Info page.The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration.The following error message is displayed: Activation Error:- This Integration was created using REST based connection but now connection changed to SOAP.Configure your connection to REST again or edit the integration for SOAP.The Oracle Utilities Adapter uses the following strategy to handle errors in the invoke (outbound) and trigger (inbound) directions for REST endpoints.Error Handling in the Invoke (Outbound) Direction : The Oracle Utilities Adapter in the invoke (outbound) direction returns a standard APIInvocationError for any HTTP response that it receives with an error code.In addition, it also produces an APIInvocationError if a processing error occurs within the Oracle Utilities Adapter while preparing the request, calling the endpoint, or handling the response.The format of the APIInvocationError in the mapper is as follows.The errorDetails section contains the actual cause.You can handle the APIInvocationError with a fault handler in the orchestrated integration. |
The standard resource URI format starts with a /, followed by letters.If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration.The following error message is displayed: Activation Error:- This Integration was created using REST based connection but now connection changed to SOAP.Configure your connection to REST again or edit the integration for SOAP.The Oracle Utilities Adapter uses the following strategy to handle errors in the invoke (outbound) and trigger (inbound) directions for REST endpoints.Error Handling in the Invoke (Outbound) Direction : The Oracle Utilities Adapter in the invoke (outbound) direction returns a standard APIInvocationError for any HTTP response that it receives with an error code.In addition, it also produces an APIInvocationError if a processing error occurs within the Oracle Utilities Adapter while preparing the request, calling the endpoint, or handling the response.The format of the APIInvocationError in the mapper is as follows.The errorDetails section contains the actual cause.You can handle the APIInvocationError with a fault handler in the orchestrated integration.Error Handling in the Trigger (Inbound) Direction : The Oracle Utilities Adapter in the trigger (inbound) direction exposes an HTTP endpoint that HTTP clients can request for using an HTTP request, and returns an HTTP response. |
If you enter any other URI format, an error message is displayed.Handling the cross-combination connection catalog error: If you create an integration using a SOAP-based connection, changing the connection to use a REST-based catalog has the following impact on that integration: If the integration was already activated, there is no impact on the integration.If the integration was not activated and you now attempt to activate the integration, it fails with the following error message: Activation Error:- This Integration was created using SOAP based connection but now connection changed to REST.Configure your connection to SOAP again or edit the integration for REST.5-1If you create an integration using a REST-based connection, changing the connection to use a SOAP-based catalog has the same impact on that integration.The following error message is displayed: Activation Error:- This Integration was created using REST based connection but now connection changed to SOAP.Configure your connection to REST again or edit the integration for SOAP.The Oracle Utilities Adapter uses the following strategy to handle errors in the invoke (outbound) and trigger (inbound) directions for REST endpoints.Error Handling in the Invoke (Outbound) Direction : The Oracle Utilities Adapter in the invoke (outbound) direction returns a standard APIInvocationError for any HTTP response that it receives with an error code.In addition, it also produces an APIInvocationError if a processing error occurs within the Oracle Utilities Adapter while preparing the request, calling the endpoint, or handling the response.The format of the APIInvocationError in the mapper is as follows.The errorDetails section contains the actual cause.You can handle the APIInvocationError with a fault handler in the orchestrated integration.Error Handling in the Trigger (Inbound) Direction : The Oracle Utilities Adapter in the trigger (inbound) direction exposes an HTTP endpoint that HTTP clients can request for using an HTTP request, and returns an HTTP response.If successful, the Oracle Utilities Adapter returns a success response. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.