Split (1)

train · 94.6k rows

text stringlengths 65 20k
The connection details are already configured.The connection is ready to be used.Oracle Alerting Service Invoke This REST connection handles the invoke operation.You must configure the following parameters: Connection Type: REST API Base URL Connection URL: Any valid URL Security Policy: No Security Policy Lookups The Alert Notification technical accelerator uses three lookups.Edit the lookup values to customize the notification service for your organization.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR_MSGID lookup accepts these parameters: Message_IDAppendix B Alert Notification B-2Message_Subject Notification_Type The ORCL-T-GENRIC_ENS_NOTIFICATION_DATA lookup stores the actual parameters for each notification type.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR accepts two parameters that define the notification type for the calling service.IntegrationCode_Version Specifies the integration code and version combination of the calling service.Notification_Type Specifies the kind of notification.For example, PAGERDUTY or Email.Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .
The connection is ready to be used.Oracle Alerting Service Invoke This REST connection handles the invoke operation.You must configure the following parameters: Connection Type: REST API Base URL Connection URL: Any valid URL Security Policy: No Security Policy Lookups The Alert Notification technical accelerator uses three lookups.Edit the lookup values to customize the notification service for your organization.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR_MSGID lookup accepts these parameters: Message_IDAppendix B Alert Notification B-2Message_Subject Notification_Type The ORCL-T-GENRIC_ENS_NOTIFICATION_DATA lookup stores the actual parameters for each notification type.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR accepts two parameters that define the notification type for the calling service.IntegrationCode_Version Specifies the integration code and version combination of the calling service.Notification_Type Specifies the kind of notification.For example, PAGERDUTY or Email.Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.
Oracle Alerting Service Invoke This REST connection handles the invoke operation.You must configure the following parameters: Connection Type: REST API Base URL Connection URL: Any valid URL Security Policy: No Security Policy Lookups The Alert Notification technical accelerator uses three lookups.Edit the lookup values to customize the notification service for your organization.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR_MSGID lookup accepts these parameters: Message_IDAppendix B Alert Notification B-2Message_Subject Notification_Type The ORCL-T-GENRIC_ENS_NOTIFICATION_DATA lookup stores the actual parameters for each notification type.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR accepts two parameters that define the notification type for the calling service.IntegrationCode_Version Specifies the integration code and version combination of the calling service.Notification_Type Specifies the kind of notification.For example, PAGERDUTY or Email.Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.
You must configure the following parameters: Connection Type: REST API Base URL Connection URL: Any valid URL Security Policy: No Security Policy Lookups The Alert Notification technical accelerator uses three lookups.Edit the lookup values to customize the notification service for your organization.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR_MSGID lookup accepts these parameters: Message_IDAppendix B Alert Notification B-2Message_Subject Notification_Type The ORCL-T-GENRIC_ENS_NOTIFICATION_DATA lookup stores the actual parameters for each notification type.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR accepts two parameters that define the notification type for the calling service.IntegrationCode_Version Specifies the integration code and version combination of the calling service.Notification_Type Specifies the kind of notification.For example, PAGERDUTY or Email.Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.
Edit the lookup values to customize the notification service for your organization.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR_MSGID lookup accepts these parameters: Message_IDAppendix B Alert Notification B-2Message_Subject Notification_Type The ORCL-T-GENRIC_ENS_NOTIFICATION_DATA lookup stores the actual parameters for each notification type.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR accepts two parameters that define the notification type for the calling service.IntegrationCode_Version Specifies the integration code and version combination of the calling service.Notification_Type Specifies the kind of notification.For example, PAGERDUTY or Email.Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.
The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR_MSGID lookup accepts these parameters: Message_IDAppendix B Alert Notification B-2Message_Subject Notification_Type The ORCL-T-GENRIC_ENS_NOTIFICATION_DATA lookup stores the actual parameters for each notification type.The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR accepts two parameters that define the notification type for the calling service.IntegrationCode_Version Specifies the integration code and version combination of the calling service.Notification_Type Specifies the kind of notification.For example, PAGERDUTY or Email.Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.
The ORCL-T-GENRIC_ENS_NOTIFICATION_SELECTOR accepts two parameters that define the notification type for the calling service.IntegrationCode_Version Specifies the integration code and version combination of the calling service.Notification_Type Specifies the kind of notification.For example, PAGERDUTY or Email.Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.
IntegrationCode_Version Specifies the integration code and version combination of the calling service.Notification_Type Specifies the kind of notification.For example, PAGERDUTY or Email.Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.
Notification_Type Specifies the kind of notification.For example, PAGERDUTY or Email.Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.
For example, PAGERDUTY or Email.Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.
Here are the values required for each notification type.Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.
Notification Type Parameter Value To Be Provided Email param1 Email of the user to whom the notification will be sent PagerDuty param1 param2 param3 param4PagerDuty Admin Email ID PagerDuty API token PagerDuty Service ID PagerDuty Assignee JIRA param1 param2 param3 param4 param5 param6JIRA Admin Username JIRA Access token JIRA Project Name JIRA Issue Type Name JIRA Assignee ID JIRA Base URL CUSTOM param1 param2Custom values Usage Every integration should call the GenericErrorNotification Service from the Global Fault Handler.You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.
You must configure the following parameters for the GenericErrorNotification Service: IntegrationCode_Version: For example, ORCL-BA- NS2SFDC_INVENITEM_CREATE::01.00.0000.InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.
InstanceID: Use the mapper function to get the instance ID of the calling service.For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.
For example, fn:format-number(nsmpr2:getFlowId(), "#") .FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.
FaultCode: Map the errorCode from GlobalFaultObject.FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.
FaultReason: Map the reason from GlobalFaultObject.FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.
FaultDetails: Map the details from GlobalFaultObject.Appendix B Alert Notification B-3Resequence Messages The Resequence Messages technical accelerator provides a means for you to ensure that messages entering the system are processed in a specific order.Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.
Note: Oracle Integration comes with the Resequence Messages technical accelerator automatically installed.Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.
Therefore, this accelerator will already be listed as INSTALLED on the Accelerators and Recipes page when you sign in.Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.
Topics: Description Prerequisite Key Parameters Connections Architecture Error Handling Description You often need to ensure that messages are processed in a strict order.Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.
Let's look at a pattern that enforces an order using Oracle Integration and the Resequence Messages technical accelerator.The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.
The pattern also deals with the case where you must limit the concurrency of calls to an endpoint system.The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.
The Sequencing Problem The basic problem is that you have a stream of requests that must be executed in order, for example, create account, update account address, and update account contacts.The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.
The latter two activities can't occur until the first one has completed.Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.
Before you can sequence messages, you need to know the order in which the messages should be processed.So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.
So, you need to use some sort of sequencing ID.This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.
This ID could be a timestamp or an actual sequence identifier.If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.
If you're using timestamps, then the closer to the message origin that the timestamp is applied the better.For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.
For example, if you take the timestamp from when the message arrives in Oracle Integration, then a network delay may have already caused our messages to be out of order.Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.
Typically, you don't want all messages to be in the same ordered sequence.In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.
In our account example, only messages for a given account need to be ordered.Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.
Messages for different accounts can execute in parallel.So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .
So, now you also need some sort of group ID to identify different sequence streams within your message stream.After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.
After you have the messages and know their order, you can process them.Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.
Inherent in a resequencing solution is some sort of delay to allow messages to arrive out of orderAppendix B Resequence Messages B-4and then be sorted into order.The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.
The size of the delay specifies how much time you can accept a message to be delayed before you go ahead without it.The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.
The Resequencing Solution The Resequence Messages technical accelerator includes a set of integrations, connections, and scripts that use standard Oracle Integration features.The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.
The integrations that handle the message resequencing are generic.You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.
You can use and reuse the technical accelerator to resequence different types of business integrations without modification to the integrations provided in the technical accelerator package.The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.
The Resequence Messages technical accelerator: Processes the input message based on the desired sequence ID rather than on the order in which the messages arrive.Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.
Parks each message in storage for a certain period of time (parking time) so that any out- of-sequence messages have a chance to be processed in the desired order.Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.
Lets you configure the maximum number of message groups being processed in parallel in order to throttle the outgoing calls.Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.
Takes care of all error handling, including system errors, network errors, and bad requests.Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.
Prerequisite The solution uses a database to store the input messages.You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.
You can create the required database tables by using a SQL script.To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.
To create the required database tables: Search and download the DDL SQL script provided in this blog .Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.
Run the script to create the database tables.Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.
Key Parameters The Resequence Messages technical accelerator uses the following key parameters to reorder messages.Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.
Field Description gtype - Group Type The type of stream.Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.
Different message types can be sequenced in parallel, for example, account updates and personnel updates are different group types.gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.
gid - Message Group A field in the request that identifies a specific stream of messages to be sequenced.id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.
id - Message Identifier A unique identifier for this message.sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.
sequenceId - Message SequenceA field in the request or a timestamp that is used to determine how to sequence the messages in a stream.Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.
Parking Time The amount of time that messages may be delayed in order to ensure messages are processed in the desired order.Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.
Message Concurrency The maximum number of message groups to be processed in parallel.Appendix B Resequence Messages B-5Connections The Resequence Messages technical accelerator uses the following connections.After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.
After you install the accelerator, you need to configure each connection.Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.
Connection Type Description RSQ DB Invoke ATP database used by the resequencer RSQMessageConsumer Trigger and invoke Used to cause load distribution of calls to message consumer RSQManager Trigger Used to invoke manager interface RSQProducer Trigger Used to invoke producer interface RSQDispatcher Trigger Used to invoke dispatcher interface TestService Invoke Used to invoke a sample test service Architecture Let's look at the architecture for the Resequence Messages technical accelerator.Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.
Business Front-end Integrations An integration in this tier serves as the front end to the resequencer and the real business integration so that the message can go through the resequencer integrations to be reordered.The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.
The front-end integrations are specific to the use case and act as a means of converting typed requests into a common format, including group and sequencing fields.Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.
Also, the front-end integrations receive the typed business payload, extract ID, and group ID from the message before calling the standardized producer message.Appendix B Resequence Messages B-6Resequencer Integrations The Resequence Messages technical accelerator includes a set of reseqencer integrations.These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.
These integrations handle the message resequencing and are generic.You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.
You can use them to resequence different types of business integrations.No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.
No additional modifications are necessary.Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.
Resequencer IntegrationsDescription Producer Serves as the entry point of the resequencer.The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.
The producer integration receives the resequencing message, creates a new row in the group table if its not already there, and sets the status of the group to N. It then creates a message in the message table.Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.
Sample message payload: { "gid": "gid", "gtype": "order", "id": "mid", "sequenceId": 123, "payload": "string repesentation of the payload" } Group Consumer Detects the active groups and invokes the message consumer integration.The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.
The integration is scheduled to run every minute.When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.
When scheduling, use this expression: FREQ=MINUTELY;INTERVAL=1; The group consumer integration finds active groups, limiting parallelism to throttle outgoing calls to prevent overloading the target system.For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.
For each active group, the integration invokes a message consumer.Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.
Message Consumer Processes active messages of the given group.It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.
It receives the group ID and type from the group consumer integration.It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.
It loads active messages of the group ordered by sequenceID.The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.
The messages have to be at least as old as the parking time.This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.
This ensures that theres a window for the message to arrive out of order but be processed in order.The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.
The integration loops through active messages, marks the message status as P, and invokes the dispatcher.Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.
Note that exceptions can occur here.After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.
After the dispatcher returns for a given message it is delete and the group status may be updated to mark the group status to be C if there are no active messages, or N if there are new active messages.Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.
Sample message payload: { "id": "Engineering", "type": "employee" } Manager The manager integration supervises the resequencer.It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.
It supports three operations.Appendix B Resequence Messages B-7Operation Path and Method Description Get configs Path: /configs Method: GETReturns the config of all the types.Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.
Example of invocation: $ curl https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs -v -u username:password Update config Path: /configs/{type} Method: PUTUpdate the config for the given type.Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.
Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/configs/employee -v -u username:password -H "Content-Type: application/ json" [email protected] config.json example: { "maxConcurrent": 5, "timeWindow": 11 } Recover Group Path: /types/{type}/groups/ {group}/recover Method: PUTDeletes stuck messages in the message table and reactivates the group by setting its status to N. Example of invocation: $ curl -X PUT https:// my.integration.cloud/ic/api/ integration/v1/flows/rest/ RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content- length: 0" Dispatcher The dispatcher is a request/response integration that reconstructs the original payload and sends it to the real backend integration.Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.
Unlike the resequencer integrations, the dispatcher isn't generic because it needs to invoke specific business integrations.The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.
The dispatcher receives the message and converts the payload to the original typed business payload.It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
It uses the group ID to find the business end point and invoke it synchronously.Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
Exceptions can happen here.Appendix B Resequence Messages B-8Here is the dispatcher interface: { "id": "Engineering", "gid" : "Zebra", "gtype" : "order", "sequenceId" : 123, "payload" : "original payload" } Business Integrations A business integration is the real integration that processes the business messages.It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.
It has its own typed interface.For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.
For each business front-end integration, there should be a corresponding business integration.Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
Error Handling Exceptions can occur when the dispatcher integration invokes the business integration.Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
Exceptions bubble up to the message consumer integration and cause the message consumer instance to fail.When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.
When this happens, the group status stays at P in the database.On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.
On the Monitoring Integration page, you can see the failed dispatcher instance and the message consumer instance.Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.
Appendix B Resequence Messages B-9Recover System Error If the problem is caused by a system error, such as a networking issue, then you can recover by resubmitting the failed message consumer instance after the system error is resolved.Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.
Recover Bad Request If the error is caused by a bad request, then resubmitting the request will not help.In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.
In this case, you need to skip the bad request and move on.To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
To do this, invoke the resequencer manager integration to remove the stuck message and reactivate the group: $ curl -X PUT https://my.integration.cloud/ic/api/ integration/v1/flows/rest/RSQMANAGER/1.0/types/employee/ groups/eng/recover -v -u username:password -H "Content-length: 0"Appendix B Resequence Messages B-10Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2 F25322-10 December 2022 Oracle Cloud Using the Slack Adapter with Oracle Integration Generation 2, F25322-10 Copyright 2020, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.
Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.
Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.
The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.

Subsets and Splits

No community queries yet

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