RulePoint Proactive PowerCenter Monitoring

Transcription

1 Contents Informatica Corporation RulePoint Release Notes June 27, 2011 Copyright Informatica Corporation Abstract... 1 RulePoint Proactive PowerCenter Monitoring... 1 Installation... 1 Enhancements... 1 Fixed Limitations... 2 Known Limitations... 2 Summary of Third-party License Information... 7 Contact Information... 7 Abstract This document contains information about the installation, enhancements, fixes, and limitations of Informatica RulePoint 5.2 HF1. RulePoint Proactive PowerCenter Monitoring A Starter Kit consisting of twenty commonly encountered scenarios is available for download at the Informatica Marketplace. The kit will get you started right away with the Proactive Monitoring for PowerCenter Option. The Starter Kit consists of the required software components and a documentation to install and configure the solution. Download link: Installation RulePoint 5.2 HF1is an upgrade to RulePoint 5.2, not a full release of the product. Refer to the RulePoint 5.2 HF1 Administrator Guide for detailed instructions to install RulePoint 5.2 HF1. The RulePoint Administrator Guide also provides instructions for upgrading RulePoint to RulePoint 5.2 HF1. The RulePoint 5.2 HF1 Administrator Guide file is named RulePoint_5.2HF1_AdminGuide_en.pdf and is provided separately. Enhancements RPPD-3732 RPPD-4103 The RulePoint 5.2 REST API is now available. French Canadian characters are now supported in both the database and REST API. RPPD-4185 RulePoint 5.2 now supports Oracle RPPD-4220 RulePoint 5.2 now supports SQL Server 2008 R2. RulePoint 5.2 HF1 Release Notes -1-

2 Fixed Limitations Fix RPPD-3018 RPPD-3672 RPPD-3673 RPPD-3778 RPPD-3979 [RPPD-4074 RPPD-4105 RPPD-4124 RPPD-4159 RPPD-4163 RPPD-4177 RPPD-4183 RPPD-4203 In Oracle, rules now correctly evaluate for mixed case topics. Previously, lower case topics needed to be used. Executing the migrate-policy.bat script no longer causes a null pointer exception. When migrating user policies from RulePoint 5.1 to 5.2 using local authentication, changes to the user policy will be saved to the Policy text file. Full exports no longer fail for large configurations that previously resulted in out of memory errors. If you use the regex analytic, simple regex is now supported. Previously, you had to use a regular expression that contained at least two capture groups; otherwise, the match was never returned. The Recent Rules Activations pages correctly show those rules which have recently been activated in local database authentication. The DB2 migration scripts now work if a different option than currentschema option is used. Templates that were created with invalid DRQL and saved in "disabled" state are now listed with Show Templates using Show All and Show Disabled. The administrator account password can now be changed when using local authentication. The last error for JMS Services on a connection failure can now be found in the log file. Event Subscriber now publishes events when the response overrides existing topic properties. The SQL analytic now works properly with Oracle when the result set contains NULL columns. The status of entities in an export file will now be preserved on import when using overwrite option. Known Limitations The following issues are known limitations within RulePoint 5.2. The limitations are grouped by key features of the product. Analytics RPPD-2197, RPPD-4140 The match, notmatch, and unique analytics cannot be used with the OR, AND NOT operators. They are always treated as if they are included in the rule using AND. RPPD-2220 Search analytic and multiple conditions. If you use the search() analytic with multiple parameters separated by AND or, you must use parenthesis to group the conditions in the precedence you want the rule to use. RPPD-2616, RPPD-2336 RPPD-3998 Match/notmatch/unique. When using the match, notmatch, or unique analytics with a topic for which no count is specified and the rule contains no complex conditions (conditions involving analytics or second topics), the rule will be evaluated for the largest set of events for the specified topic which meet the criteria specified for that topic. If these analytics are not being used for a particular topic for which no count is specified (and the rule contains no complex conditions), all current events for the topic must meet the conditions of the rule for it to fire. Rules using nested analytics always evaluate to true and fire if the inner analytic returns a list. The results of the outer analytic do not have any bearing on whether the rule fires or not. -2- Release Notes

3 Authentication RPPD-1448 [RPPD-3435 Login screen does not support domain names as part of the username when configured with external authentication. To support domain names, configure the "securityprovider.ldapuserdnformat=" value in the rulepoint- config.properties file. The first time a user logs in to RulePoint, the following message is placed in the audit log and can be ignored: [AUDIT"Audit Log Record" VAX "" failed to login from Import/Export Import/Export RPPD-2940 RPPD-4199 RPPD-4344 On WebLogic and Internet Explorer, if you attempt to load an import file that is larger than the limit specified, the browser will hang. Either increase the size of the "upload.maxuploadsize" property or give the upload file to your administrator to place it in the upload directory on the RulePoint server. When doing an Export All operation, the back button is enabled but should not be utilized. A large number of input files can cause errors when navigating the list. The work-around is to prune the number of import files being persisted below 3 pages. Engine RPPD-2935 RPPD-3421 Condition 'OR" operator does not work as expected when used within a multi-topic rule in conjunction with cross-referenced event properties. The following rule will not operate as expected: when 1 stock s, 1 news n with s.symb="infa" OR n.price=10 then... When either the past() or current() analytics are used in certain combinations with the contains() analytic, the contains() analytic does not operate as expected Installer RPPD-4284 When choosing the staging folder for the RulePoint Installer, some of the icons (e.g., moving up a level) are not being displayed. The workaround is to hover your mouse over these areas and read the tooltip to determine the actions available. Rules RPPD-1851 RPPD-3776 RPPD-3121 RPPD-4064 RPPD-1937 RPPD-2614 RPPD-2807 RPPD-2808 Using a Topic alias of "w" causes an error when saving the rule. Do not use "w" as a topic alias name. Creating a rule using double quotes within a single quote when testing for equality (e.g., price = '"3"') can cause auto-completion to break. The use of the DRQL system property keywords are only supported for use within the response and may not be used within a rule condition. Trace Report shows incorrect rule name, rule and events information. New line and escape characters may not be used within response properties of a Wizard rule. OR limitations with combinations of events. When using OR between conditions in a rule where the topic referenced has multiple values (for instance, "when 2 stock s with s.price > 10 or s.price < 1 ""), all of the events being evaluated must meet the same one of the conditions. In this case, both of the stock events must have a price greater than 10, or both of them must have a price less than one. Saving a wizard rule that uses the SQL or geoinsidearea analytic to an advanced rule does not result in a correct advanced rule. You may not use special characters in the wizard conditions after selecting "Input a Value". RulePoint 5.2 HF1 Release Notes -3-

4 RPPD-2825 RPPD-3483 RPPD-3627 RPPD-3952 RPPD-4175 RPPD-4288 It is possible to select the same topic multiple times when creating a wizard rule. This causes inconsistent behavior in the conditions and responses section of the rule since you cannot differentiate in those pages between the multiple occurrences of the same topic. If you want to create a rule using multiple instances of the same topic, use Advanced mode instead of wizard mode. If you reference a non-existent temporary variable in a wizard rule, you'll get a NullPointerException error displayed in the UI when you try to save the rule. WebService parameters cannot be overwritten in a rule. The work-around is to change them in the WSDL Response itself. Using the List2vars analytic in a wizard rule is not supported. A wizard rule with a removeoldest clause and OR conditions will be converted improperly into an advanced rule. The work around is to convert the "OR removeoldest" clause into an "AND removeoldest" clause. Sometimes when viewing profiles for rule activation, the profile information will not be displayed. The work-around is to try again as this issue is intermittent. Services RPPD-1802 RPPD-2104 RPPD-2570 RPPD-2932 RPPD-2986 RPPD-3451 RPPD-3538 RPPD-3562 RPPD-3940 RPPD-4092 RPPD-4167 RPPD-4340 RPPD-4343 RPPD-4346 In the HTTP Response, it is not possible to use a parameter with the name "target", since this is a system reserved keyword. Additionally, when using the "body" parameter, all other parameters are ignored since the HTTP Response will send the entire response as an MIME-encoded format within the "body" parameter. SQL source service cannot process data from tables which include columns with a data type of "XMLTYPE". When creating source services, connection status always shows "NotStarted" instead of "Connected". File input source service. If you input meta-data which does not validate, you will not receive any error message but will be returned to the service configuration page with the values emptied out. Check the log file for errors and re-enter the configuration data. HttpMonitor loops or hangs indefinitely and consumes a large percentage of CPU resources. The syntax for dynamically passing topic property values requires square brackets (e.g., when 3 stock5 s then updateresult with names="[${s.symbol(*,comma)} "). If parentheses are used instead, it will appear to fail silently but actually creates a valid but different SQL expression from what was intended. Even though the source file may not have changed, restarting RulePoint will cause the File Input Source service to fire an event on its first run. JMS Source Service's connection status is not reliable. Use the RulePoint log to verify connection status. If you edit a WSDL analytic and change the URL, hit cancel, and then confirm with the Yes button, you will be taken to the next page to choose the WSDL operation. For a JMS Source service, if you change the startup type from automatic to manual, the currently executing instance will be stopped. When using the URL/Web page monitor in WebSphere, some URLs will not work with this service. For the Instant Message service, the connection always indicates "Not Connected". The "last error" field for all services may not be formatted correctly. Migrating JMS services from 5.1 to 5.2 causes XML errors during RulePoint startup. The work-around is to open and re-save the affected services to restore normal operation. -4- Release Notes

5 RPPD-4347 RPPD-4359 RPPD-4148 When trying to create new source web services, input fields are not being displayed, preventing proper configuration. If RulePoint is shut down, instant messages (tied to the IM service) are fired, then RulePoint is started up, the IM Service will generate the events but the associated rules will not be activated. The work-around is to resend the events after RulePoint has started up. When creating a web page monitor, the first time it runs it will run an exception to the log. However, it and the remaining changes will be processed successfully. Responses RPPD-2734 RPPD-2910 RPPD-3663 RPPD-3930 RPPD-4180 SQL responses. If you create a rule which references a SQL response, then change the parameters to the SQL response, the rule will not be updated to use the new parameters until you edit and save the rule. Default values in responses. If you have a response with double quote characters in the default values, the response values will not be validated when used in the wizard. In the response, if you enter the date using the DD/MM/YYYY format instead of MM/DD/YYYY format, the date will not be saved correctly. This field has been deprecated. Response parameters are case sensitive in advanced rules. Be sure to match the case as shown in the autocomplete when overriding the parameter values in advanced rules; otherwise, they will be ignored. Referenced topic properties in the Event Recorder response must be in all lower case to work or they will be missed. REST API RPPD-4130 RPPD-4219 RPPD-4353 When using the RulePointAPI class methods getresponseinstancelist() and gettopiclist() without the PaginatedQuery parameter, null lists will be returned. The workaround is to pass in a parameter of the following form: new PaginatedQuery(1,-1). In the REST API, using GET /api/wizardrules responds with HTTP status The requested resource (/rulepoint/api/wizardrules) is not available. This issue also occurs with wizardrules.xml, wizardrules/ and POST /api/wizardrules. When doing a PUT for a response with an invalid key, instead of an error message indicating the response does not exist, it returns an invalid error message and stack trace. Templates RPPD-3003 RPPD-3413 RPPD-3985, RPPD-4293 RPPD-4002 RPPD-4010 A user who has User Policy MC* access to Template rules and read ACL access to a template cannot create a template rule. They receive the following error: "Error saving rule: An attempt was made to reference a non-existent, or disabled service or response: Resp_000." Entities referred to by templates can be deleted even though they are being used by the template. These deletions can also result in the template not showing up even though the user has Write ACL access to it. When upgrading a template and editing the validation for a parameter such that an existing child rule does not conform to the new validation, the upgrade can sometimes fail. When specifying custom validations for template fields, configuration errors will cause an error message to display and disable the save button. When unchecking the custom validation, the save button should be enabled; however, it is not. The work-around is to reselect Custom Validation, then delete or fix the custom validation with errors. This will enable the save button. If a template has parameters with custom validation and then is upgraded to remove that validation, it is no longer possible to revert back to the state where the parameters had custom validation. RulePoint 5.2 HF1 Release Notes -5-

6 RPPD-4071 RPPD-4319 When editing custom validation for a template parameter, there are edge cases where the option to select a canned validation is no longer available. The workaround is to delete the current custom validation and then add a new one. In some cases, changing a template parameter's validation from one of the standard ones to a custom one can throw an exception and prevent saving. Topics RPPD-2246 RPPD-3962 Topic processing. If a topic is persisted in the database, and is referenced by a rule including a call to "removenone" for that topic, then events which have not yet expired will be reprocessed if the topic is reprocessed. If you create a new source service and define the topic name with a particular case (e.g., sometopic) where that topic has not yet been created, when you first run the service the specified case will be ignored and a new topic will be created in all lower case (e.g., sometopic)." User Interface RPPD-3170 RPPD-3420 RPPD-3546 RPPD-4176 RPPD-4313 RPPD-4317 RPPD-4354 RPPD-4356 IE 6 and 7 can sometimes display "Failed to load dependencies: JavaScript SyntaxError exception: Out of memory" when trying to Export All where a large dataset exists (500+ rules). Use another browser if you need to export a large number of rules. The Remove Inactive Events button is not removing expired events. RulePoint does not allow rule, response, wizard, event, topic or service names to use accented (i.e., upper ASCII) characters. However, UTF-8 characters beyond normal ASCII may be used. The topic tree does not properly filter the list of topics. When using database authentication, RulePoint allows the creation of user names containing spaces. This should not be possible and must be avoided. When using RulePoint on IE8, selecting the Plain Text View link on the System Information Page will not work. The workaround is to not use a different browser. The WebService.maxWSDLcache property setting is ignored for Web Service WSDL Cache. With a larger mixture of database and memory events, attempting to view the last page causes an exception. When the events are all database events, the "Next" button may be greyed out. Watchlist RPPD-3327 The UI allows watchlists with periods in their names to be created, which should not be allowed. This can cause rule auto-completion problems. -6- Release Notes

7 Summary of Third-party License Information This software uses some third-party and open source components. Many open source license agreements require user documentation to contain notification that the open source software is included in the product. Contact Information RulePoint 5.2 HF1 Release Notes -7-