text
stringlengths 65
20k
|
|---|
This information is sent from Oracle Integration to the Oracle ERP Cloud application.Email & Bell Notification : Select to receive both email and bell notifications.Email notification : Select to receive only an email notification.Bell Notification : Select to receive only a bell notification.Occurrence Select when to receive a notification about data import status: Send in any case Send on import success Send on import failureChapter 3 Invoke Response Page 3-10Element Description Enable Callback Select to enable callback behavior for the import job selected on the Operations page.When you select this option for new integrations, the ErpImportBulkData event of Oracle ERP Cloud is raised once the import job completes.When you select this option for existing integrations, you must also provide the callback integration and callback identifier described in the fields below.Integration Flow Identifier (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Optionally specify a callback integration in which to receive details about the status of the outbound Oracle ERP Cloud request flow (failed records) (for example, enter 01.00.0000 ).This is a completely separate integration that handles callbacks.The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction. |
Email & Bell Notification : Select to receive both email and bell notifications.Email notification : Select to receive only an email notification.Bell Notification : Select to receive only a bell notification.Occurrence Select when to receive a notification about data import status: Send in any case Send on import success Send on import failureChapter 3 Invoke Response Page 3-10Element Description Enable Callback Select to enable callback behavior for the import job selected on the Operations page.When you select this option for new integrations, the ErpImportBulkData event of Oracle ERP Cloud is raised once the import job completes.When you select this option for existing integrations, you must also provide the callback integration and callback identifier described in the fields below.Integration Flow Identifier (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Optionally specify a callback integration in which to receive details about the status of the outbound Oracle ERP Cloud request flow (failed records) (for example, enter 01.00.0000 ).This is a completely separate integration that handles callbacks.The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration. |
Email notification : Select to receive only an email notification.Bell Notification : Select to receive only a bell notification.Occurrence Select when to receive a notification about data import status: Send in any case Send on import success Send on import failureChapter 3 Invoke Response Page 3-10Element Description Enable Callback Select to enable callback behavior for the import job selected on the Operations page.When you select this option for new integrations, the ErpImportBulkData event of Oracle ERP Cloud is raised once the import job completes.When you select this option for existing integrations, you must also provide the callback integration and callback identifier described in the fields below.Integration Flow Identifier (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Optionally specify a callback integration in which to receive details about the status of the outbound Oracle ERP Cloud request flow (failed records) (for example, enter 01.00.0000 ).This is a completely separate integration that handles callbacks.The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits. |
Bell Notification : Select to receive only a bell notification.Occurrence Select when to receive a notification about data import status: Send in any case Send on import success Send on import failureChapter 3 Invoke Response Page 3-10Element Description Enable Callback Select to enable callback behavior for the import job selected on the Operations page.When you select this option for new integrations, the ErpImportBulkData event of Oracle ERP Cloud is raised once the import job completes.When you select this option for existing integrations, you must also provide the callback integration and callback identifier described in the fields below.Integration Flow Identifier (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Optionally specify a callback integration in which to receive details about the status of the outbound Oracle ERP Cloud request flow (failed records) (for example, enter 01.00.0000 ).This is a completely separate integration that handles callbacks.The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 . |
Occurrence Select when to receive a notification about data import status: Send in any case Send on import success Send on import failureChapter 3 Invoke Response Page 3-10Element Description Enable Callback Select to enable callback behavior for the import job selected on the Operations page.When you select this option for new integrations, the ErpImportBulkData event of Oracle ERP Cloud is raised once the import job completes.When you select this option for existing integrations, you must also provide the callback integration and callback identifier described in the fields below.Integration Flow Identifier (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Optionally specify a callback integration in which to receive details about the status of the outbound Oracle ERP Cloud request flow (failed records) (for example, enter 01.00.0000 ).This is a completely separate integration that handles callbacks.The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page. |
When you select this option for new integrations, the ErpImportBulkData event of Oracle ERP Cloud is raised once the import job completes.When you select this option for existing integrations, you must also provide the callback integration and callback identifier described in the fields below.Integration Flow Identifier (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Optionally specify a callback integration in which to receive details about the status of the outbound Oracle ERP Cloud request flow (failed records) (for example, enter 01.00.0000 ).This is a completely separate integration that handles callbacks.The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file. |
When you select this option for existing integrations, you must also provide the callback integration and callback identifier described in the fields below.Integration Flow Identifier (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Optionally specify a callback integration in which to receive details about the status of the outbound Oracle ERP Cloud request flow (failed records) (for example, enter 01.00.0000 ).This is a completely separate integration that handles callbacks.The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file. |
Integration Flow Identifier (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Optionally specify a callback integration in which to receive details about the status of the outbound Oracle ERP Cloud request flow (failed records) (for example, enter 01.00.0000 ).This is a completely separate integration that handles callbacks.The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration. |
)Optionally specify a callback integration in which to receive details about the status of the outbound Oracle ERP Cloud request flow (failed records) (for example, enter 01.00.0000 ).This is a completely separate integration that handles callbacks.The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page. |
This is a completely separate integration that handles callbacks.The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API. |
The name of the integration is only required to trigger a second integration.Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration. |
Otherwise, this field can be left blank.The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use. |
The inbound integration is expected to handle callbacks from Oracle ERP Cloud.The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection. |
The integration must have an Oracle ERP Cloud Adapter configured in the trigger (inbound) direction.You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources. |
You select As a Callback on the Request page in the trigger direction.Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts. |
Integration Flow Version (This field is visible when using an Oracle ERP Cloud Adapter connection in an existing integration.)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming. |
)Enter the integration version in two digits.For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object. |
For example, enter 01 if the identifier version is 01.00.0000 .Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field. |
Invoke Child Resources Page Select the child resources to include with the parent resource selected on the Operations page.This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming. |
This helps to minimize the size of the integration WSDL file.If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts. |
If you do not select any child resources, all child resources (including custom resources) associated with the parent resource are included by default in the integration WSDL file.This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API. |
This increases the size of the WSDL file and can cause memory issues in Oracle Integration.This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts. |
This page is only displayed if you select a top-level parent resource on the Operations page.Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page. |
Select a maximum of ten child resources to include in either the request payload sent to the external API or the response message received from the external API.Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard. |
Do not select child resources that are not required for use by this integration.Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter. |
Element Description Select Child Resources Select the child resources to use.Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed. |
Only the child resources associated with the parent resource you selected on the Operations page are displayed for selection.Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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. |
Your Selected Child Resources Displays the selected child resources.Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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. |
Invoke Descriptive and Extensible Page Select the descriptive flexfield (DFF) or extensible flexfield (EFF) and associated contexts.A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns. |
A flexfield is a flexible data field that your organization can customize to meet your businessChapter 3 Invoke Child Resources Page 3-11needs without programming.It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations. |
It provides a set of placeholder fields (segments) associated with a business object.Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements. |
Two types of flexfields are supported for selection: Descriptive flexfield: A field you customize to enter additional information for which your Oracle Fusion Applications product has not already provided a field.Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions. |
Extensible flexfield: Similar to a descriptive flexfield in that it provides a customizable expansion space that implementers (such as Oracle Fusion Applications users) can use to configure additional attributes (segments) without additional programming.Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center. |
Element Description Select Flexfields(s) Select a flexfield to see the configured contexts.Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page. |
Select Context(s) Select a maximum of 20 contexts to include in either the request payload sent to the external API or the response message received from the external API.Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page. |
Number of Contexts Selected Displays the number of selected contexts.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received. |
Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs. |
Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails. |
The information that is 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback 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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter. |
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.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted. |
To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario. |
To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-124 Implement Common Patterns Using the Oracle ERP Cloud Adapter You can use the Oracle ERP Cloud Adapter to implement the following common patterns.Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role. |
Topics: Configure Callbacks Upload a File to Oracle WebCenter Content Invoke an Endpoint Dynamically Invoke a File-Based Data Import (FBDI) Job Invoke a Non-File-Based Data Import (FBDI) Job Use Multiple Callback Integrations for the Same FBDI Job Select Extensible and Descriptive Flexfields in an Integration Get the Job Name and Parameters of Oracle ERP Cloud Bulk Import Jobs Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox. |
You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration. |
Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas. |
See the Recipes page on the Oracle Help Center.Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard. |
Configure Callbacks For new integrations, you do not need to consume an explicit event when configuring the Oracle ERP Cloud Adapter as a trigger connection on the Request page.When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) . |
When you design a callback integration, you select the Receive Callback Message upon completion of FBDI bulk import job submitted via another integration option on the Request page.After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs. |
After selecting this option, you must select the specific bulk data load or import process for which the callback event is received.When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name. |
When this callback integration is activated, event subscription automatically occurs.The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group. |
The event is raised by the Oracle ERP Cloud application regardless of whether the load or import job succeeds or fails.The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server. |
The Oracle ERP Cloud application then invokes the Oracle Integration endpoint that is the callback integration.4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications. |
4-1Upload a File to Oracle WebCenter Content You can upload a file to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter.The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport . |
The file to upload can be either encrypted or unencrypted.This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload. |
This section provides a high-level overview for performing this scenario.To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it. |
To upload a file to Oracle WebCenter Content: 1.Create an Oracle ERP Cloud Adapter connection with the Invoke role.During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write. |
During connection configuration, you can select to optionally encrypt the file to upload by selecting the PGP Public Key for UCM Upload checkbox.2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions. |
2.Create an orchestrated integration.3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File . |
3.Drag the Oracle ERP Cloud Adapter to the invoke part of the integration canvas.This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM. |
This invokes the Adapter Endpoint Configuration Wizard.4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime. |
4.On the Actions page, select File Upload to WebCenter (UCM) .5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned. |
5.On the Operations page, select the following mandatory values: Security Group : Select the security group to which the file to upload belongs.A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing. |
A security group is a set of files grouped under a unique name.Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration. |
Every file in the UCM server repository belongs to a security group.Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details. |
Access to security groups is controlledChapter 4 Upload a File to Oracle WebCenter Content 4-2by permissions assigned to roles on the content server.Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection. |
Roles are assigned to users where they are maintained on Oracle Fusion Applications.The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time. |
The default security group in Fusion Applications FAFusionImportExport .Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint. |
Doc Account : Select the doc account for the file to upload.In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint. |
In Fusion Applications, every content item has an account assigned to it.You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions. |
You must have the appropriate permission to the account such as read and/or write.Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration. |
Access to the document is the intersection between account permissions and security group permissions.6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties. |
6.If you selected to encrypt the file to upload on the Connections page in Step 1, select Encrypt the File .7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL. |
7.Once the UCM file upload endpoint is saved, provide the reference to the file to upload to UCM.You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime. |
You can also override the security group and doc account that you previously set by hard coding new values in the mapper that receive reference during runtime.Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL. |
Chapter 4 Upload a File to Oracle WebCenter Content 4-3 If file upload is successful, a document ID is returned.Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header. |
Use the document ID for downstream processing.8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints. |
8.Complete design of the integration.Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object). |
Chapter 4 Upload a File to Oracle WebCenter Content 4-4Invoke an Endpoint Dynamically You can dynamically invoke a REST endpoint/URL at runtime without configuring additional invoke connection or REST outbound details.As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows. |
As long as the Oracle ERP Cloud REST APIs return a response with HATEOS links, you can use this feature by mapping the HATEOS link to the invoke connection.This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API. |
This feature is useful in situations that require invoking a REST endpoint dynamically or when the endpoint is not known at design time.This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects. |
This feature is also useful in situations that require invoking multiple REST services, all of which accept the same input payload and return the same response payload as configured for the outbound endpoint.For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object). |
For these cases, this feature eliminates the need to create multiple connections to invoke each REST endpoint.Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support. |
Note: Note the following restrictions.The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element. |
The request and response schema must be the same as provided during endpoint configuration.Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration. |
Template parameters are not supported while mapping these properties.The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter). |
The HTTP verb cannot be changed for the endpoint URL.For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard. |
For example, if the endpoint is configured to use POST, the outgoing request uses POST even if the endpoint URI changes at runtime.Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation. |
Because the endpoint URL is determined at runtime, there is no facility to test whether the security credentials provided during connection configuration also work with the new endpoint URL.If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address . |
If you think the endpoint URL determined at runtime requires a different authorization header then the original URL, you may need to provide a mapping for the authorization standard header.This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements. |
This use case provides a high level overview of one way to design an integration that uses dynamic endpoints.You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element. |
You retrieve child objects using the REST API (for example, Primary Address is a child object of the Account parent object).The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links. |
The integration is designed as follows.An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object. |
An initial invoke is configured to get the Account object by using the REST API.The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object. |
The response of this REST API does not provide the child objects.Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection. |
Instead, there are HATEOS links to the child objects (that is, the Primary Address object).A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation. |
A second invoke uses the HATEOS links from the earlier response to make another invoke connection to the REST endpoint to fetch the child Primary Address object using dynamic REST endpoint support.To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support. |
To change the endpoint configuration at runtime, you map one or more of the various properties under the ConnectivityProperties target element.1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links. |
1.Create an orchestrated integration.2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section. |
2.Drag an adapter into the integration canvas as an trigger connection (it can be any adapter).3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties . |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.