iWD Runtime Node Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
- Message Server Configuration—Connections to Message Server must now be configured via a Message Server DAP rather than a direct connection to Message Server. This makes it possible for the Load Config job to read configuration data directly from Configuration Server without defining the connection to Message Server and the Message Server database.
- Message Server Connection Now Optional—Connection to Message Server is also made optional (though strongly recommended) in this release, rather than obligatory. The previous implementation of iWD 8.5.x iWD required a connection to Message Server and Message Server database in order to bring up Data Mart to Service. With this release it is possible for the Load Config job to read configuration data directly from Configuration Server without defining the connection to Message Server and Message Server database. The fact that the Load Config job does not have audit logs (stored in Message Server) might result in some changes to Business Structure not being reflected in Data Mart. For example, for a Data Mart running in a 15-minute interval, if configuration data is renamed twice during one interval, only the last change will be reflected in Data Mart. Data Mart will rely on the configuration snapshots that it makes every 15 minutes.
- Support for Multiple Rule Packages in a Single ESP Call—The ESP interface with Genesys Rules Engines has been extended to allow a rules package to specify multiple rule package names in a single ESP call. Only the rule evaluation metrics for the last rule package will be returned. On an incoming request when the Service parameter is set to BusinessContextManagement and the Method parameter equals either SetBusinessContext, Prioritize, or Archive, the interface will accept multiple rule packages specified in the following format: rule.package1, rule.package2, rule.package3…… Task History for all rule packages has also been implemented.
This release contains the following resolved issues:
Problems with the Load Config job being unable connect to Message Server have been resolved by configuring the connection by means of a Message Server DAP. (IWD-4675)
The su option in the iWD_Data_Mart_Service_Script.sh no longer needs to be enclosed in quotation marks in that script. (IWD-4486)
iWD Runtime Node now respects the path option configured in the logging section. (IWD-4671)
No special procedure is required to upgrade to release 8.5.101.03.