Understanding Application Engine Programs for Responses
After you determine the valid responses for a transaction, code a separate Application Engine program section to handle each response. The program sections require that:
-
The Application Engine program that contains the called sections are tagged as a library.
Each section must have public access.
-
The program includes the WL_RIMRESP_AET and WL_RIMRESP2_AET state records.
-
The called section accesses all of the fields from the WL_RIMRESP2_AET state record:
-
The called section need not perform database commits.
The calling program does this.
The following fields can be included in Blackberry response state records:
| Term | Definition |
|---|---|
|
EMAIL_FROM |
The email address of the person replying to the BlackBerry email message. |
|
WL_SUBJECT |
The email subject. |
|
WL_RESPONSE |
The response from the BlackBerry pager, as it was extracted from the email body. |
|
EMAIL_TEXTLONG |
The complete email body. |
|
WL_PROCESS_FLAG |
This field marks a BlackBerry transaction as having been worked. If the application requires that multiple BlackBerry responses be processed, the called Application Engine user section must set this field to N before ending. The main Application Engine program then updates the appropriate table. |
|
COMPONENT_ID |
The component of the template that was used in the originating email message (if any). |
|
MARKET |
The market of the template that was used in the originating email message (if any). |
|
WL_TEMPLATE_ID |
The template ID. |
|
LANGUAGE_CD |
The language of the original email message. |
|
NOTIFY_TO |
A listing of the user IDs that were used when the original email message was sent. |
|
EMAIL_SENDER2 |
The value of SMTPBlackBerryReplyTo that was used in the application server configuration file when the initial email message was sent to the pager. |