Tactical activation Messaging API request message

Tactical activation is started when a message is placed on the input queue for the Business Rules engine. If table names are passed, only the descriptors that are related to those tables are updated. In addition, if you have a table that is maintained outside of the Business Rules UI that is used in your Business Rules and you would like to be able to view what data was included for a particular release in the Business Rules UI, you can use the copy capability by specifying the destinationSchema and destinationTable attributes. When the destinationSchema and destinationTable attributes are specified, data is copied from the source table to the destination table during tactical activation. The external table should be specified as the data source. The external table cannot contain a column that is named RELID and must be release independent. The destination table must have all of the columns as the source table with the same size and data type. In addition, the destination table must contain a column that is named RELID. Both the source and destination tables are included in the list of tables to tactically activate.

For example, you have a database table that monitors prefunded accounts. This list is maintained externally and is release independent, but it is used to determine whether items need to go to Risk. By specifying a destinationSchema and destinationTable, it is possible to be able to view on the Business Rules UI which accounts are included in a specific rules release.

The default input queue for Business Rules engine is defined as FXH.BUSINESSRULES.INPUT.QUEUE.

This example tactical activation request message notifies the Business Rules engine that the RULES.DEPOSIT_PRODUCT_DEADLINE table has changed and needs to be updated for all of the active releases in the SAMPLE environment.

<?xml version="1.0" encoding="UTF-8"?>
<ibmPaymentsDirectorBridge>
   <header>
      <msgDesc>Service_Request</msgDesc>
      <msgType>activateBusinessRules</msgType>
      <version>1.0.0</version>
      <messageTime>2017-05-03T21:52:46.372Z</messageTime>
      <sourceId>My App</sourceId>
      <destinationId>Business Rules Engine</destinationId>
   </header>
   <contents>
      <rules>
         <environment>SAMPLE</environment>
         <tables>
            <table schema='RULES'>DEPOSIT_PRODUCT_DEADLINE</table>
         </tables>
      </rules>
   </contents>
</ibmPaymentsDirectorBridge>

Table 1 describes the XML elements that can be in the tactical activation request message.

Table 1. Tactical activation request message XML format
Node Name	Parent elements	Node type	Description
ibmPaymentsDirectorBridge	None, this is the root element	ELEMENT	The Messaging API XML root element for the tactical activation request message.
header	ibmPaymentsDirectorBridge	ELEMENT	Contains the Messaging API header information.
msgDesc	header	TEXT	The message description must be set to `Service_Request`.
msgType	header	TEXT	The message type must be set to `activateBusinessRules`.
sourceId	header	TEXT	The ID of the source of this message. It is added to the audit and logging records.
destinationId	header	TEXT	The ID of the recipient of this message. For example, `Business Rules Engine`.
contents	ibmPaymentsDirectorBridge	ELEMENT	This element contains the contents of the message.
rules	contents	ELEMENT	This element contains information about the tables to be updated by tactical activation. If this element does not contain any additional elements, all of the tables for all of the active releases are updated. All of the elements within this element are optional.
effectiveDate	rules	TEXT	The date that tactical activation is to occur. If this element is not specified, tactical activation occurs immediately. When a date is provided, the `type` attribute must be used to indicate the type of date being sent in the message. Valid values for the `type` attribute are: calendar Specify the calendar date in the SQL date format: `YYYY-MM-DD HH:MM:SS.000000000`. business Specify the business date in the following format: `YYYMMDD`. This element is optional.
environment	rules	TEXT	The name of the Business Rules environment to use for tactical activation. If this element is not specified, tactical activation is performed for all of the Business Rules environments. This element is optional.
tables	rules	ELEMENT	This element contains the list of tables to be updated during tactical activation. If this element is not specified, the entire release is activated. This element is optional.
table	tables	TEXT	The name of a database table that was updated. The `schema` attribute must be used to provide the database schema name for the table. This table data can be copied to another similarly defined table for viewing purposes. To copy the table's data, the destinationSchema and destinationTable attributes must be specified. The destination table must contain a column that is called RELID and the source table must not. Both the source and the destination table are tactically activated. This element is optional.