| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Duplicate content check is imicroservice s used to classify input messages to into duplicate and unique based on content in input XML at XPath provided using CPS. Depending on Cache Duration Time and Sleep Interval, input messages are retained in cache and sent in on sleep intervals.
Configuration
Figure 1: Component Property SheetConfigure Schema of Input:
Validate Input
- yes: The microservice tries to validate the input received.
no: The microservice will not validate the input and hence the performance increases.
Warning Setting this to "no" may cause undesired results if the input XML is not valid
Error handling configuration
Allows configuring actions to be taken when an exception occurs during the execution. Following are the configuration options:
- JMS Error
- Response Generation Error
- Request Processing Error
- Invalid Request Error
| Tip |
|---|
For descriptions, refer to the Error Handling section in the Common Configurations page. |
Input Source
The source type that has to be taken as input. Choose one of the below:
- XML
- Text
Configure schema of input
Using schema editor, load/enter xml schema of input messagethe XML schema for the input message.
Sleep Interval
...
The time gap with which duplicate messages are throttled out to through the Duplicate port.
Cache Duration Time
...
Time duration for which message should be retained in cache. If in case cache is not empty and duration exceeds, then cache is not cleaned until all messages are throttled to duplicate ports. XPath :
Cache Duration Time Unit
The unit of the cache duration time can be set here. While the default unit is milliseconds, other options are:
- Seconds
- Minutes
- Hours
- Days
Duplicate Identifier Source
The message is checked if it is duplicate of the earlier message based on the parameters below:
- Body (Text or XML)
- Header
XPath
Choose XPath from which content should be extracted.
| Tip |
|---|
Refer to the XPath Editor section in the Message Body XPath selector page to know more. |
Functional Demonstration
Scenario 1
Configure component as shown in Figure 1. Using Feeder send input messages and it can be observed that messages with the same "STNO" are classified into duplicate and unique and sent to respective displays.
Figure 2: Sample Event Process
Sample Input
Figure 3: Sent 10 messages with same "STNO"
...