![]() All process-type-specific queues are based on the XI standard queue XBQO and therefore cannot be configured individually. In this setting, there is one qRFC queue for each process type, in which all messages for this process type are queued (XBQO$PE_WS…). However, you can make this queue configurable and achieve performance improvements by configuring it appropriately. If load balancing is not suitable for a particular process, all messages for this process type must be put in one qRFC queue. For example, if the performance of a particular process is not critical, you can define that it is to be processed without load balancing even though the developer specified load balancing as permissible in the semantics of the process. However, you as administrator can decide to select different options when configuring inbound processing for the relevant process. The process developer can, for example, specify that the process is suitable for load balancing using multiple queues. The properties area displays the properties of the process, including the options for queue assignment. For this purpose, click anywhere in the editing area in the process editor. For this reason, the process developer can specify exactly which settings are possible when they define the process in the process editor. ![]() The possible settings that you can make for load balancing depend on the semantics of the process concerned. The correlation is so selective that the act of determining the queue name from the correlation values results in the load being balanced as required.The content of the correlation container does not change during the lifetime of a process instance.Ī correlation cannot therefore be activated more than once by using different values.The request message corresponds to the container element of the receiver step that opens the sync/async bridge. All inbound interfaces are part of this correlation in the process.įor a synchronous interface, the related asynchronous interface of the request message must be part of the correlation.The process definition contains one correlation only.Prerequisites: Select this setting only if the process meets the following conditions: ![]() For this reason, the order in which the messages are sent to the process is identical to the order in which the Integration Server received them. This ensures that all messages for this customer are processed by the same queue. Therefore, the system determines the name of the queue from the customer number in this case. The correlation is defined by using the customer number. In a collect scenario, a process instance collects all sales-order messages for a particular customer. Consequently, all messages that satisfy the same correlation are processed by the same queue, as illustrated in the following example. The system determines the name of the queue from the message fields in the correlation container. If you select this setting, the system takes the content of the messages into account when distributing the messages to the queues. This setting must not be used even if the order the messages are processed in is not important because lock conflicts can occur that cancel out the advantages of parallel processing. The process then sends these messages and waits for an answer in each case by using a correlation.ĭo not use this setting to send messages to a process instance when using multiple queues. However, this setting is not suitable in an enhanced split scenario, as in the following example: A process receives a message, which a transformation step then splits into multiple messages. This is the case in a simple split-scenario, for example: A process receives a message, which a transformation step then splits into multiple messages. A process such as this receives exactly one message with the receive step. ![]() This condition is always met if the process does not have a correlation. None of the messages sent to this process type are dependent on each other: The order in which the messages are processed is not important. Prerequisites: Select this setting only if the process meets the following condition: Consequently, the messages are not sent to the process instance in the same sequence in which the Integration Server received them. If you select this setting, the system distributes the messages randomly among the available qRFC queues. In load balancing, you define the number of queues and specify whether the system is to distribute the messages randomly, or whether it should take the content into account. ![]() For example, you can define which server the entries in the qRFC queue of a particular process type are to be processed on. Applying load balancing incorrectly in a process can lead to messages being processed incorrectly or even to data loss.Ĭonfigurable qRFC queue: If load balancing is not suitable for a particular process, you can nevertheless improve system performance by configuring the appropriate qRFC queue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |