Data Scrub Highway Setup > Highway Configuration > Asynchronous Model
  
Asynchronous Model
The asynchronous model allows you to place a number of request files into an input folder for background processing. This section contains the setup necessary for the asynchronous model.

Asynchronous Model
Payload Type
In Highway, select System Definition | Payload Types and add a new entry.

Payload Fields
 
Field
Value
Payload ID
CSV
Description
CSV text message
Format
TEXT
Extension
cvs

Payload Entry
Message IDs
In Highway, select System Definition | Message IDs and add two new entries.

Message ID Compliance Request Fields
 
Field
Value
Message Id
COMPLY_CSV_ASYNCH
Description
Compliance CSV request (Asynchronous)
Payload
CSV

Message ID Compliance Request Entry

Message ID Compliance Reply Fields
 
Field
Value
Message Id
COMPLY_CSV_ASYNCH_REPLY
Description
Compliance CSV Result (Asynchronous)
Payload
CSV

Message ID Compliance Reply Entry
Endpoint
In Highway, select System Definition | Endpoints and add three new entries.

Endpoint Fields
 
Field
Value
Endpoint ID
COMPLY_CSV_IN
Description
Receive Compliance CSV Requests (input folder)
Type
Input (Reader)
Storage
Folder
Target name
C:\PRECISION\WebUI\highway\messages\COMPLY_CSV_IN
Server
FILE
Default Message Id
COMPLY_CSV_ASYNCH
Number of readers
1

Endpoint Fields
 
Field
Value
Endpoint ID
COMPLY_CSV_OUT
Description
Store Compliance CSV Replies (input folder)
Type
Output (Writer)
Storage
Folder
Target name
C:\PRECISION\WebUI\highway\messages\COMPLY_CSV_OUT
Server
FILE

Endpoint Fields
 
Field
Value
Endpoint ID
COMPLY_CSV_ASYNCH
Description
Process compliance CSV messages (Asynchronous)
Type
Output (Writer)
Storage
JMS Queue
Target name
OUT3
Server
JBOSSMQ
Program
a2a.ComplianceCsvHandler
Return message endpoint
COMPLY_CSV_OUT
Rules
In Highway, select Message Center | Rules and add a new entry.

Rule Entry Fields
 
Field
Value
Message ID
COMPLY_CSV_ASYNCH
Sequence
10
Description
Move Compliance CSV requests for processing
Write Endpoint
COMPLY_CSV_ASYNCH

Rule Entry