Informatica Corporation Proactive Monitoring for PowerCenter Operations Version 2.1 Release Notes October 2012

Transcription

1 Contents Informatica Corporation Proactive Monitoring for PowerCenter Operations Version 2.1 Release Notes October 2012 Copyright (c) 2012 Informatica Corporation. All rights reserved. Installation... 1 New Features and Enhancements... 1 Version Version 2.0 HotFix Version Fixed Limitations... 3 Known Limitations... 4 Informatica Global Customer Support... 8 This document contains important information about installation, new features and enhancements, fixed limitations, and known limitations of Proactive Monitoring for PowerCenter Operations 2.1. Installation Before you install Proactive Monitoring for PowerCenter Operations 2.1, you must install and configure PowerCenter, Informatica RulePoint, and Informatica Real-Time Alert Manager. You can install Proactive Monitoring for PowerCenter Operations in graphical or console mode on Windows, Linux, or AIX. For detailed installation instructions, see Informatica Proactive Monitoring for PowerCenter Operations 2.1 Solutions Guide. Proactive Monitoring for PowerCenter Operations supports homogenous database environments for an instance of RulePoint, Real-Time Alert Manager, and PowerCenter. Therefore, use the same database type for both PowerCenter and RulePoint for an instance. For example, if you install PowerCenter on Oracle, you must install RulePoint on Oracle. On the other hand, difference in the operating system does not affect the functioning of Proactive Monitoring for PowerCenter Governance. New Features and Enhancements PMPO-RLN

2 Version 2.1 Proactive Monitoring for PowerCenter Operations 2.1 offers the following new and enhanced capabilities: Upgrade from Proactive Monitoring for PowerCenter Operations 2.0 or 2.0 HotFix 1 to 2.1 Effective in 2.1, you can use the installer to upgrade from Proactive Monitoring for PowerCenter Operations 2.0 or 2.0 HotFix 1 to 2.1. Overlay install on Proactive Monitoring for PowerCenter Governance 2.0 Effective in 2.1, you can use the Proactive Monitoring for PowerCenter Operations installer to install on Proactive Monitoring for PowerCenter Governance 2.0. Proactive Monitoring for PowerCenter Governance is a product that monitors PowerCenter repository for best practices violations. Reorganization of the topics in RulePoint Effective in 2.1, the topic trees of Proactive Monitoring for PowerCenter Operations has been reorganized to enhance usability. The rules and templates are renamed to enhance search results. All rules follow standard guidelines and naming conventions. Support for PowerCenter worklets Effective in 2.1, Proactive Monitoring for PowerCenter Operations supports PowerCenter worklets. You can monitor sessions running in PowerCenter worklets. Previously, Proactive Monitoring for PowerCenter Operations did not support PowerCenter worklets. Support for versioned PowerCenter repository Effective in 2.1, Proactive Monitoring for PowerCenter Operations supports versioned PowerCenter repositories. The latest version of PowerCenter objects are considered in rule evaluations in case of versioned repositories. Previously, while using a versioned PowerCenter repository, you found duplicate entries in repository tables. Version 2.0 HotFix 1 Proactive Monitoring for PowerCenter Operations 2.0 HotFix 1 offers the following new and enhanced capabilities: Updates to descriptions of all services of Proactive Monitoring for PowerCenter Operations Effective in 2.0 HotFix 1, the descriptions of all rules, templates, sources, analytics, responders, responses, watchlists, and topics are updated for clarity and readability. Detailed setup instructions to create pc_rp and pcrs_readonly users Effective in 2.0 HotFix 1, you can get detailed instructions to create RulePoint database user and PowerCenter repository read-only database user. The instructions are in the create_pc_user.txt and create_rp_user.txt files. You can get the files in the resources directory of the installer package. Version 2.0 Proactive Monitoring for PowerCenter Operations 2.0 offers the following new and enhanced capabilities: 2 PMPO-RLN

3 IDP/CLU replaced with Web Services Effective in 2.0, you can use the PowerCenter Web Services Hub to access PowerCenter workflows as web services through RulePoint. Previously, you had to install the Informatica Developer Platform (IDP) and PowerCenter Command Line Utility (CLU) on the same host as RulePoint to access PowerCenter. Environment Monitoring Effective in 2.0, you can monitor the operating environment of PowerCenter instance for CPU, memory, tablespace usage, and database status. Rules and analytics for environmental monitoring correlates environmental statistics with PowerCenter aggregates to generate insights into operational performance. Installer Effective in 2.0, you can use the installer to install Proactive Monitoring for PowerCenter Operations in graphical, console, or silent mode. Previously, the installer was a standalone Java application that performed the installation tasks. Operational Pack Effective in 2.0, you can use rules to monitor the PowerCenter operations. Cache Duration Effective in 2.0, the cache duration for pc_get_ and pc_get_rtam analytics is set to 3600 seconds. Previously, the cache duration was set to a sub-optimal value of 0. Fixed Limitations The following table lists the issues that are resolved in Proactive Monitoring for PowerCenter Operations 2.1: CR In a versioned PowerCenter repository, you cannot get appropriate events for disabled sessions In Linux, when you run art.sh or gst.sh on a Microsoft SQL Server database, you get the following error:./art.sh -u rp_ms_ro1 -p rp_ms_ro1 -list Error: String index out of range: -1 Workaround: Change the db.url_base pattern in the jdbc.properties file to the pattern that art.sh and gst.sh tools support. Check the definition of db.url_base in the jdbc.properties file in the rulepoint/web-inf/classes directory. Microsoft SQL Server database supports the following URL pattern: db.url_base=jdbc:jtds:sqlserver://<url:port>/;<properties=xxx> art.sh and gst.sh need the DatabaseName property in the following pattern: DatabaseName=schema_name The DatabaseName is same as db.name property in the jdbc.properties file When you use a versioned PowerCenter repository, you can find duplicate entries in repository tables. If the analytics, get_no_workflows, get_no_mappings, and get_no_sessions use these duplicate tables, you might get wrong data in return. Do not consider the duplicate entries while counting the entries in the tables. PMPO-RLN

4 For IBM DB2 and Microsoft SQL Server databases, the Prev N analytic considers the recently completed run also for calculating the average of the times and records In the Custom Install type, the installation of Proactive Monitoring for PowerCenter Operations 2.1 proceeds even if you do not select any install option. Known Limitations You might encounter the following limitations when you work with Proactive Monitoring for PowerCenter Operations 2.1. If you encounter difficulties or have further questions regarding one of these limitations, contact Informatica Global Customer Support and reference the CR number. CR The timestamp parameter files used by the proactive monitoring SQL sources are stored under the dbenv directory in RulePoint in the following path: $CATALINA_HOME\webapps\rulepoint\WEB-INF\system\dbEnv The parameter files get deleted when Apache Tomcat is shutdown. If the parameter files are missing in the dbenv directory, the timestamp parameter gets reset to the value persisted in the database resulting in duplicate events and alerts when Apache Tomcat is restarted. Workaround: Save a copy of the dbenv directory files before you shutdown Apache Tomcat. Restore the saved files before restarting Apache Tomcat While starting interval based SQL sources, you might see a null pointer exception. Workaround: Restart the Apache Tomcat instance where RulePoint is deployed, and then restart the schedules for the source services During installation, if you do not provide correct inputs for the Web Services Hub WSDL URL in the PowerCenter Services Configuration window, the importing of the XML file fails. Workaround: The installer does not validate the Web Services Hub WSDL URL during installation. Perform a custom installation to provide the correct inputs for Web Services Hub WSDL URL, and then import the XML files using the importcli utility The cleanup utility of the Global Setting Tool does not work with Microsoft SQL Server when you configure the user access using Windows authentication. Workaround: The error occurs when the client and SQL server instances are on separate machines. This could be due to the inability to resolve the Windows account trying to connect to SQL Server. If you see the error message in an application that uses Windows authentication, and if the client and the SQL Server instances are on separate machines, then ensure to use a domain account to access the SQL Server. If the account used is a local account on the client machine, then you see the error message as the SQL Server machine and the domain controller cannot recognize a local account on a different machine. The resolve the error, create a domain account, give it the appropriate access rights to the SQL Server, and then use that domain account to run the client application. This case also includes the special accounts NT AUTHORITY\LOCAL SERVICE and NT AUTHORITY\NETWORK SERVICE trying to connect to a remote SQL Server, when authentication uses NTLM rather than Kerberos When running the importcli utility to import the XML files for Proactive Monitoring for PowerCenter Operations, you might see connection errors from Real-Time Alert Manager in the log. Ignore the errors as they do not affect the import. 4 PMPO-RLN

5 The importcli utility might not complete the task if the PowerCenter Web Services Hub WSDL URL is not accessible during installation. While importing the XML files, the importcli utility might take a long time to complete and would not exit. Ensure that the PowerCenter Web Services Hub WSDL URL provided during installation is correct by connecting to the URL directly using a web browser. During install, the installer parses the URL and waits for the URL to respond before proceeding. Workaround: Stop the java process started by the importcli utility and repeat the installation with a valid PowerCenter Web Services Hub WSDL URL Proactive Monitoring for PowerCenter Operations 2.1 and Proactive Monitoring for PowerCenter Governance 2.0 related topics are created in the topic tree when only Proactive Monitoring for PowerCenter Operations 2.1 is installed on Proactive Monitoring for PowerCenter Operations HotFix 1. When you upgrade from Proactive Monitoring for PowerCenter Operations 2.0 to 2.1, you see the topic tree for both Proactive Monitoring for PowerCenter Governance and Proactive Monitoring for PowerCenter Operations. It is an expected behavior as Proactive Monitoring for PowerCenter Operations 2.0 included topics of Proactive Monitoring for PowerCenter Governance and Proactive Monitoring for PowerCenter Operations PowerCenter Web Service Hub Workflow Control Response returns Workflow run id is null error if you do not specify the RunId. Workaround: Specify WorkflowRunId PowerCenter Web Service Hub Workflow Control Response does not abort the workflow with the following command: stopworkflow with IsAbort=True Workaround: Use the abortworkflow operation During startup, the interval based sources return the following error because SQLIntervalSource stores the parameters on the file system to use in the subsequent call: SQLSourceIntervalBased: Error occurred while writing parameters to file output stream in instance :PowerCenter Completed Sessions exception :invalid stream header: The error occurs if the source is not able to read the file to retrieve the parameters. Workaround: - You must have write permissions to the WEB-INF/system/dbenv directory. - If you see files with the same name as that of SQLIntervalSource in the dbenv directory, delete the files in this directory and restart the source In RulePoint, the topic tree is organized after a complete, upgrade, or overlay installation of Proactive Monitoring for PowerCenter Operations. During custom installation, the topic tree is flattened if you import the XML files manually. Workaround: Use the importcli utility to import the XML files after a custom install The Proactive Monitoring for PowerCenter Operations 2.1 installer does not validate whether the input integration service is present on the environment monitoring node While importing opscommon.xml manually or when running the importcli utility to import the XML files for Proactive Monitoring for PowerCenter Operations 2.1, the following error is thrown: "** Import Failed **com.agentlogic.rulepoint.importexport.importexportconversionexception: An error occurred while saving the service." The import fails if the environment monitoring node properties are not valid as the service gets validated during import. Workaround: Delete the node system and node process sources from RulePoint and then import the XML files again to RulePoint using either the importcli utility or manually. PMPO-RLN

6 On Microsoft SQL Server database, the details of PowerCenter repository user are not updated in the installer.properties file. The Repository Owner field is not required on Microsoft SQL Server The topics for each solution pack are organized in separate directories. Manual import of the XML files for the solution to RulePoint flattens the topic tree organization in RulePoint. All the topics get moved to the main directory after the manual import. Workaround: Use the importcli utility to import the XML files to RulePoint Proactive Monitoring for PowerCenter Operations supports only the runtime statistics for worklets If the process name is too long, you cannot view the complete alerts on the Real-Time Alert Manager dashboard. The process name is truncated, and you cannot view the PID and CPU usage columns as you cannot scroll the screen horizontally. Workaround: Use the Alert Detail > Show > Plain View tab to view details of the message In art.sh or art.bat, the option, -l or -list does not work when added to the end after the parameters of -add. For example, the following command does not work:./art.sh -u RT31_ORA10_UTF8_30 -p RT31_ORA10_UTF8_30 -add -domain Domain_SWG -r repo_swg -folder 'Proactive Monitoring' -wf_name '' -persona itsecurity -rtam 'pcadmin;pcmonitor' - -l Workaround: Use the -l or -list option before the -add option. For example,./art.sh -u RT31_ORA10_UTF8_30 -p RT31_ORA10_UTF8_30 -l -add -domain Domain_SWG -r repo_swg -folder 'Proactive Monitoring' -wf_name '' -persona itsecurity -rtam 'pcadmin;pcmonitor' The art.bat and gst.bat tool returns error if the RulePoint database user password contains special characters such as,!, #, or ^. Workaround: If the database user name or database password of pc_rp contains special characters, the Windows command prompt cannot pass these parameters to the art.bat or gst.bat tools. 1. Create another user for the RulePoint repository database, for example, rp_tool_user with a password that does not contain any special characters. 2. Assign read and write privileges to rp_tool_user to the pc_alert_recipients and pcpm_global_settings tables under the pc_rp user. You can use the tools as usual After a complete installation, while enabling the source services, the node system property source returns the following exception: com.informatica.cep.pcpm.envmonitoring.service.source.nodesystempropertyserviceexcep tion: Unable to connect with Remote System : Please check Host Name, User Name, Password and Domain provided An internal error occurred. [0x8001FFFF] Workaround: Clear the server caches. Delete the following directories: - $CATALINA_HOME/work/Catalina/localhost/rulepoint, where $CATALINA_HOME is the path to the Tomcat installation directory. - $RP_HOME/WEB-INF/lib/cachedir, where $RP_HOME is the path to the RulePoint installation directory After a complete installation, if the installer is run again while enabling the source services, the node process property returns the following exception: com.informatica.cep.pcpm.envmonitoring.service.source.nodesystempropertyserviceexcep tion: Unable to connect with Remote System : Please check Host Name, User Name, Password and Domain provided The object invoked has disconnected from its clients. [0x ] Workaround: Clear the server caches. Delete the following directories: - $CATALINA_HOME/work/Catalina/localhost/rulepoint, where $CATALINA_HOME is the path to the Tomcat installation directory. - $RP_HOME/WEB-INF/lib/cachedir, where $RP_HOME is the path to the RulePoint installation directory. 6 PMPO-RLN

7 While enabling the source services after a complete install, the node process property returns the following incorrect function error: Incorrect function. [0x ] Workaround: Clear the server side caches. Delete the following two directories: - For Tomcat web containers only: $CATALINA_HOME/work/Catalina/localhost/rulepoint, where $CATALINA_HOME is the path to the Tomcat installation directory. - $RP_HOME/WEB-INF/lib/cachedir, where $RP_HOME is the path to the RulePoint installation directory The Proactive Monitoring for PowerCenter Operations installer does not exit the installation process if the Apache Tomcat instance is running. Workaround: Shutdown the instance of Apache Tomcat before installing Proactive Monitoring for PowerCenter Operations No events are published, but the log displays an event queue full message. You see this error if the database connection errors disable the responses and the associated rules. Workaround: Check the database connections, and enable the responses and the associated rules When processing rules, the RulePoint log might display the following log entries: [WARN ] NotEqualsAnalytic: Comparing number to non-number: (1.0 CMP_NEQ ) [WARN ] NotEqualsAnalytic: Comparing number to non-number: (0.0 CMP_NEQ ) [WARN ] NotEqualsAnalytic: Comparing number to non-number: ( CMP_NEQ ) [WARN ] NotEqualsAnalytic: Comparing number to non-number: (436.0 CMP_NEQ ) Workaround: Add the following lines under RP_HOME/WEB-INF/log4j.xml to suppress these logs: <logger name="com.agentlogic.rulepoint.analytic.notequalsanalytic"> <level value="error"/> </logger> When you execute the web service related sources, the RulePoint log might display the following log entries: [WARN : PCWebServiceRuntimeStatistics] operation ======monitordiserver [WARN : PCWebServiceRuntimeStatistics] getparametersformonitoroperation ======{MonitorDIServer.MonitorMode=ALL, MonitorDIServer.DIServiceInfo.ServiceName=aperf, Context.SessionId= b9c31bf bab35} [WARN : PCWebServicesHubSupport] Target: [WARN : PCWebServicesHubSupport] message sent :<?xml version="1.0" encoding="utf-8"?><soap-env:envelope xmlns:soap-env=" xmlns:apachesoap=" xmlns:impl=" xmlns:soapenc=" xmlns:wsdl=" xmlns:wsdlsoap=" xmlns:xsd=" xmlns:xsi=" ENV:Header><impl:Context><SessionId> b9c31bf bab35</SessionId></ impl:context></soap-env:header><soap- ENV:Body><impl:MonitorDIServer><DIServiceInfo><DomainName/><ServiceName>is</ ServiceName></DIServiceInfo><MonitorMode>ALL</MonitorMode></impl:MonitorDIServer></ SOAP-ENV:Body></SOAP-ENV:Envelope> Workaround: Add the following lines under RP_HOME/WEB-INF/log4j.xml to suppress these logs: <logger name="ees.io.services.support.webservicessupport"> <level value="error"/> </logger> PMPO-RLN

8 Proactive Monitoring for PowerCenter Operations 2.0 installation with RulePoint LDAP configuration shows the creator as UNAVAILABLE In Proactive Monitoring for PowerCenter Operations sources, the web services source fills the temp directory with XML files. Workaround: You can delete these files. All these files are of 0 KB size and are not required by the application You cannot monitor temporary and system specific tablespaces and databases as a part of the environment monitoring solution. Do not provide such tablespace and database details to the respective Watchlist. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Europe / Middle East / Africa Asia / Australia Toll Free Brazil: Mexico: North America: Toll Free France: Germany: Italy: Netherlands: Portugal: Spain: Switzerland: United Kingdom: Toll Free Australia: New Zealand: Standard Rate India: Standard Rate Belgium: France: Germany: Netherlands: United Kingdom: PMPO-RLN