{"id":7824,"date":"2020-03-12T14:30:57","date_gmt":"2020-03-12T21:30:57","guid":{"rendered":"https:\/\/minisoft.com\/support\/?p=7824"},"modified":"2020-03-12T14:38:14","modified_gmt":"2020-03-12T21:38:14","slug":"using-data-queues-in-eformz","status":"publish","type":"post","link":"https:\/\/c002.minisoft.com\/support\/using-data-queues-in-eformz\/","title":{"rendered":"Using Data Queues in eFORMz (Director)"},"content":{"rendered":"\n

NOTE: For accessing Data Queues from within an eFORMz project, consult the following post: iSeries Data Queue<\/a><\/p>\n\n\n\n

The Director Toolkit can use Data Queues from an iSeries in two ways for processing input.<\/p>\n\n\n\n

Data Queue Paired with an Input Queue (OUTQ)<\/h2>\n\n\n\n

A Data Queue (DTAQ) can be associated with a Director\nInput Queue (aka \u201cOUTQ\u201d), so that when a spool file is placed in the Input Queue,\nthe associated Data Queue wakes up the eFORMz Director queue so that it\nimmediately processes the spool file. This is more efficient than frequent\npolling of the Input Queue and provides more real-time processing of the\nspool files.<\/p>\n\n\n\n

Configuring an Input Queue for an associated Data Queue simply requires specifying the full path name of the Data Queue in the Input Queue definition. The dialog box below is for configuring a Remote iSeries queue, and it is almost identical to the dialog box for configuring a Local iSeries queue:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Enter the Data Queue path in the field labeled \u201cDTAQ\nWatch\u201d. In the example above, this path is:<\/p>\n\n\n\n

\/QSYS.LIB\/QGPL.LIB\/EFORMZD101.DTAQ<\/pre>\n\n\n\n
When you configure an Input Queue with an associated\nData Queue, you can specify a relatively large value for the \u201cCheck\ninterval\u201d, since the Data Queue will cause the Input Queue to be\ncalled immediately when a spool file is placed in the Input Queue.<\/p>\n\n\n\n
Data Queue as Mechanism for Passing Data to eFORMz<\/h2>\n\n\n\n
To process data from a Data Queue, a Director queue can be\nset up to monitor the Data Queue and process any data that is placed in the\nData Queue, typically from an iSeries application. The steps to configure a\nDirector queue to process a Data Queue are shown below. Note that when\nconfiguring a Data Queue, you never specify a polling interval; this is because\nthe Data Queue immediately calls the Director queue when data is ready for\nprocessing, with no polling required.<\/p>\n\n\n\n
In the Configure tab of the Director, select the root node of the configuration file. Then click the Add button on the right side of the window, and select the \u201ciSeries Data Queue\u201d from the popup menu:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Define Director Queue for\nData Queue<\/h3>\n\n\n\n
Enter values for the fields in the \u201ciSeries Data Queue\u201d dialog box:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Name:<\/strong> A descriptive name for the Director queue<\/p>\n\n\n\n
Host:<\/strong> The name or IP address of the iSeries box<\/p>\n\n\n\n
User:<\/strong> user name for logging into the iSeries<\/p>\n\n\n\n
Password:<\/strong> password for the user name<\/p>\n\n\n\n
Data Queue Path:<\/strong> the fully qualified path to the Data Queue<\/p>\n\n\n\n
CCSID (\u201ccoded character set identifier\u201d):<\/strong> the code page to be used for reading data from the Data Queue.<\/p>\n\n\n\n
Click OK to add this queue to the Director.<\/p>\n\n\n\n
Add Message Selector for Data Queue<\/h3>\n\n\n\n
Right click on the Data Queue just added, and select the \u201cAdd Message Selector\u2026\u201d command from the popup menu:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Enter values for the fields on the \u201cMessage Selection\u201d dialog box:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
MatchString:<\/strong> A regular expression which is run against up to the first 2,000 characters in the message. If the message in the Data Queue matches the MatchString, it will be processed; otherwise, it will be ignored. <\/p>\n\n\n\n
Format:<\/strong> Select a value from the Format dropdown list, specifying the expected format of the data.<\/p>\n\n\n\n
Disposition:<\/strong> Select an option for the Disposition. We recommend \u201cDelete selected file\u201d to delete the message from the Data Queue after processing.<\/p>\n\n\n\n
Handle each message as a SPLF request:<\/strong> Non-SPLF messages can currently only be handled as text strings. The SPLF messages include some binary components. This flag enabled correct interpretation of the message data. <\/p>\n\n\n\n
Click OK to save the message selection parameters.<\/p>\n\n\n\n
Select an eFORMz Project to Process the Data<\/h3>\n\n\n\n
With the message selector in place, right click on it and select \u201cAdd Processor\u201d, then \u201ceFORMz\u2026\u201d<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Select an eFORMz project to process the message from the\nData Queue.<\/p>\n\n\n\n
From this point, configuring the Director queue is just like configuring a Director queue to process input from a local directory. After configuration is complete, the Director queue might look like this:<\/p>\n\n\n\n
\"\"<\/figure>\n","protected":false},"excerpt":{"rendered":"
NOTE: For accessing Data Queues from within an eFORMz project, consult the following post: iSeries Data Queue The Director Toolkit can use Data Queues from an iSeries in two ways for processing input. Data Queue Paired with an Input Queue (OUTQ) A Data Queue (DTAQ) can be associated with a Director Input Queue (aka \u201cOUTQ\u201d), so that when a […]<\/p>\n","protected":false},"author":75,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[186],"tags":[596,427],"_links":{"self":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/7824"}],"collection":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/users\/75"}],"replies":[{"embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/comments?post=7824"}],"version-history":[{"count":3,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/7824\/revisions"}],"predecessor-version":[{"id":7834,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/7824\/revisions\/7834"}],"wp:attachment":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/media?parent=7824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/categories?post=7824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/tags?post=7824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}