Installing Proactive Monitoring for PowerCenter Operations 2.0 HotFix 1 on Solaris

Transcription

1 Installing Proactive Monitoring for PowerCenter Operations 2.0 HotFix 1 on Solaris Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation.

2 Abstract You can run Proactive Monitoring for PowerCenter Operations on Solaris. This article describes how to install Proactive Monitoring for PowerCenter Operations 2.0 HotFix 1 on Solaris. Install Proactive Monitoring for PowerCenter Operations 2.0 HotFix 1 on Linux and then copy the required files to the Solaris machine. Supported Versions Proactive Monitoring for PowerCenter Operations 2.0.Hot Fix 1 Table of Contents Installation Overview Verify System Requirements Complete the Pre-Installation Tasks Set Up the X Window Server Installing Proactive Monitoring for PowerCenter Operations on Linux Step 1. Install and Configure RulePoint Step 2. Install Real-Time Alert Manager Step 3. Create RulePoint and PowerCenter Users Step 4. Create PowerCenter Web Services Hub Step 5. Install Proactive Monitoring for PowerCenter Operations Step 6. Complete the Post-Installation Tasks Step 7: Configure the RulePoint Components Configure Proactive Monitoring for PowerCenter Operations on Solaris Install and Set Up Apache Tomcat Enable Proactive Monitoring on Solaris Installation Overview To install Proactive Monitoring for PowerCenter Operations on Solaris, install the solution on a Linux machine and then copy the required files to the Solaris machine. Complete the pre-installation tasks to prepare for the installation. Important: While installing Proactive Monitoring for PowerCenter Operations on Linux, provide the RulePoint and PowerCenter database configuration information for the Solaris environment. The environment monitoring feature of proactive monitoring is not supported on Solaris. After you install Proactive Monitoring for PowerCenter Operations on Linux, you must disable the unsupported rules, templates, template rules, and source services related to environment monitoring and enable the supported rules and templates. You must configure the proactive monitoring solution on Linux before you deploy it on Solaris as configuring options are not available on Solaris. 2

3 Verify System Requirements Before you install Proactive Monitoring for PowerCenter Operations, verify that the environment meets the following software and hardware requirements: Component Description Operating Systems - Windows - Linux - AIX - Solaris Application Servers Apache Tomcat Database Servers - Oracle - IBM DB2 Hardware Requirements (Recommended) - 64-bit (Intel, AMD-compatible) Xeon equivalent or better, 1.7- Ghz minimum CPU GB RAM GB application disk space - 1 GB (preferred) Ethernet network connection Informatica RulePoint RulePoint 5.2 HotFix 3 Informatica Real-Time Alert Manager Real-Time Alert Manager 3.1 HotFix 1 Informatica PowerCenter - Informatica PowerCenter Informatica PowerCenter Informatica PowerCenter For more information about Proactive Monitoring for PowerCenter Operations support, see the Product Availability Matrix at Complete the Pre-Installation Tasks Before you install, set up the machine to meet the requirements to install and run Proactive Monitoring for PowerCenter Operations. The installer requires information about the database, the application server, and the authentication mode. 1. On Linux, the user who runs the installer must have read, write, and execute permissions on the installer and the installer files directory. The user must have write access to the /tmp directory. The /tmp directory must have sufficient space for the installer to perform the installation. 2. Enable SSHD on Linux. 3. Install JDK 1.6 on the Linux machine where you want to install Proactive Monitoring for PowerCenter Operations. Set the JAVA_HOME/bin PATH environment variable on the Linux machine. 4. Set up Apache Tomcat application server on both the Linux and Solaris machines. Set the operating system environment variable $CATALINA_HOME to the installation location of the Tomcat server. Set the environment variable for the entire system. For example, $CATALINA_HOME="/home/tomcat/apache-tomcat " Note: The directory names in the Tomcat installation path must not contain spaces. 5. Install JDK 1.6 on Solaris. Add JAVA_HOME or JRE_HOME to.profile file of the Solaris machine. 3

4 6. Install database client on Solaris. Add Oracle PATH and ORACLE_HOME to.profile file of the Solaris machine. 7. Install PowerCenter on Solaris. Create the Informatica domain, the PowerCenter Web Services Hub, the PowerCenter Integration Service, and the PowerCenter Repository Service on Solaris. Set Up the X Window Server When you run the installer in graphical mode on UNIX or Linux, you must use a graphics display server. On UNIX, the graphics display server is typically an X Window server. If you do not have the X Window server installed on the machine where you want to install the product, you can run the installer with an X Window server installed on another machine. Use the DISPLAY variable to redirect output of the X Window server to another UNIX machine. The following table lists the commands to set the DISPLAY environment variable: Shell Command Example C setenv DISPLAY <TCP/IP node of XWindow server>:0 setenv DISPLAY :0 Bash/Korn export DISPLAY= <TCP/IP node of XWindow server>:0 export DISPLAY= :0 Bourne DISPLAY= <TCP/IP node of XWindow server>:0 export display DISPLAY= :0 export display If you do not know the IP address of a UNIX machine where the X Window server is installed, ask your network administrator. For more information about redirecting the DISPLAY variable, see the documentation from the UNIX vendor. If the X Window server does not support the font that the installer uses, the installer can display incorrect labels on the buttons. Installing Proactive Monitoring for PowerCenter Operations on Linux Install and configure Proactive Monitoring for PowerCenter Operations on Linux. Complete all the post-installation tasks and the required configuration for the proactive monitoring solution on Linux before you deploy the solution on Solaris. This article provides overview of steps required to install Proactive Monitoring for PowerCenter Operations on Linux with detailed information about how to configure the installation to migrate it to Solaris. For step-by-step instructions to install Proactive Monitoring for PowerCenter Operations on Linux, see the Proactive Monitoring for PowerCenter Operations 2.0 HotFix 1 Solutions Guide. Step 1. Install and Configure RulePoint When you install RulePoint on Linux, ensure that RulePoint uses the database configured for the Solaris environment. The database user for RulePoint operations must have permissions to create, delete, select, and update tables on the database configured for the Solaris environment. Note: When you run the RulePoint installer, ensure that you provide the database configuration details of the Solaris environment in the following windows: In the Database Configuration window, provide the details of the database configured for Solaris. In the Database Configuration - Repository User Account window, enter the account information for the RulePoint repository user of the database configured for Solaris. 4

5 In the Authentication Configuration window, provide the authentication details of the database configured for Solaris. For Microsoft Active Directory or LDAP authentication, ensure that you configure and provide the authentication details of the Solaris machine. Step 2. Install Real-Time Alert Manager When you install Real-Time Alert Manager on Linux, ensure that Real-Time Alert Manager uses the database configured for the Solaris machine. The database user for Real-Time Alert Manager must have permissions to create, delete, select, and update tables on the database configured for Solaris. Note: The database user for Real-Time Alert Manager can be the same database user created for RulePoint. If not, you can create another database user for Real-Time Alert Manager with the required privileges. Step 3. Create RulePoint and PowerCenter Users Create a database user for RulePoint repository and a database user with read-only privileges for PowerCenter repository. Create a database user, pc_rp, to host alerts in the RulePoint database. Create a database user, pcrs_readonly, with read-only permissions to access PowerCenter repository. Step 4. Create PowerCenter Web Services Hub Create and enable a PowerCenter Web Services Hub so that RulePoint can access PowerCenter workflows as web services. Enable the Web Services Hub in the PowerCenter domain on the Solaris machine. Step 5. Install Proactive Monitoring for PowerCenter Operations Install and configure Proactive Monitoring for PowerCenter Operations on Linux. While installing Proactive Monitoring for PowerCenter Operations on Linux, provide information about the Informatica domain, the PowerCenter Web Services Hub, the PowerCenter Integration Service, and the PowerCenter Repository Service configured for Solaris. Install Proactive Monitoring for PowerCenter Operations on Linux. - In the Installation Mode window, select Complete Install. - In the PowerCenter Services Configuration window, enter details of PowerCenter node on Solaris. - In the Configuration for Integration Service Monitoring window, enter dummy values for the parameters of environment monitoring. Each field must contain a value. Environment monitoring functionality to fetch CPU, memory, database, and tablespace usage is not supported for Solaris. Step 6. Complete the Post-Installation Tasks After installation, configure the environment for the Solaris installation. Perform the post-installation tasks to ensure that the domain and services for Proactive Monitoring for PowerCenter Operations run properly. Step 7: Configure the RulePoint Components Log in to RulePoint to enable the supported components and disable the unsupported components. You must configure the RulePoint components before you copy the solution to Solaris. You cannot configure the RulePoint components directly on Solaris. After you enable the supported components and disable the unsupported components, export all the contents and save the exported data to disk. To export the contents, click Administration > Export in the RulePoint window. 5

6 For details on using RulePoint, see RulePoint 5.2 HotFix 3 User Guide. Disable Unsupported Templates, Template Rules, and Source Services Disable the templates, template rules, and source services that are not supported by Proactive Monitoring for PowerCenter Operations on Solaris. You can delete the disabled rules, template rules, and source services manually. Templates Disable the following environment monitoring related templates: Template Rules PowerCenter Workflow Running Time greater than Proactive Monitoring SLA 5 minutes Environment Monitoring PowerCenter Workflow Running Time greater than Repository SLA 10 minutes Environment Monitoring PowerCenter Workflow Running Time greater by 25 percent than recent 3 Average Environment Monitoring PowerCenter Scheduled Workflow did not start 3 minutes after scheduled time Environment Monitoring PowerCenter Session Elapsed Time 25 pc greater than recent Average Environment Monitoring PowerCenter Workflow Elapsed Time greater than 25pc of recent Average of 3 runs Environment Monitoring PowerCenter Workflow Load Mobile records running more than 2 minutes Environment Monitoring PowerCenter Session Running Time greater than 25 percent of Average of previous 3 runs Environment Monitoring PowerCenter Session Exceeds Proactive Monitoring SLA 6 minutes Environment Monitoring PowerCenter Session Exceeds Repository SLA 10 minutes Environment Monitoring PowerCenter Session s_m_load_sports_events SLA 4 minutes Environment Monitoring PowerCenter Session Loaded Rows 25 percent lesser than recent Average Environment Monitoring PowerCenter Scheduled Workflow missed schedule by 3 minutes due to running status Environment Monitoring PowerCenter Skewed Session to Workflow elapsed time ratio less than 0.6 Environment Monitoring Disable the following environment monitoring related template rules: Source Services PowerCenter Workflow Elapsed Time greater than recent Average Environment Monitoring Template PowerCenter Scheduled Workflow did not start N minutes after scheduled time Environment Monitoring Template PowerCenter Session Elapsed Time greater than recent Average Environment Monitoring Template PowerCenter Workflow Running Time greater than Repository SLA Environment Monitoring Template PowerCenter Workflow Running Time greater than recent Average Environment Monitoring Template PowerCenter Workflow Running Time Exceeds Workflow SLA Environment Monitoring Template PowerCenter Workflow Running Time greater than Folder SLA Environment Monitoring Template PowerCenter Session Running Time greater than recent Average Environment Monitoring Template PowerCenter Session Running Time greater than Folder SLA Environment Monitoring Template PowerCenter Session Running Time greater than Repository SLA Environment Monitoring Template PowerCenter Session Running Time Exceeds Session SLA Environment Monitoring Template PowerCenter Session Loaded Rows lesser than recent Average Environment Monitoring Template PowerCenter Scheduled Workflow missed schedule due to running status Environment Monitoring Template PowerCenter Skewed Session to Workflow elapsed time ratio Environment Monitoring Template Disable the following environment monitoring related source services: 6

7 Node Database Monitor Node Process Monitor Node System Monitor Node Process Property Table Purge Enable Supported Templates and Template Rules Enable the templates and template rules that are supported by Proactive Monitoring for PowerCenter Operations on Solaris. Templates Enable the following templates that are not related to environment monitoring: Template Rules PowerCenter Scheduled Workflow did not start N minutes after scheduled time Template PowerCenter Skewed Session to Workflow elapsed time ratio Template PowerCenter Session Running Time greater than recent Average Template PowerCenter Session Running Time greater than Folder SLA Template PowerCenter Session Running Time greater than Repository SLA Template PowerCenter Session Running Time Exceeds Session SLA Template PowerCenter Workflow Running Time greater than recent Average Template PowerCenter Workflow Running Time greater than Repository SLA Template PowerCenter Workflow Running Time greater than Folder SLA Template PowerCenter Session Elapsed Time greater than recent Average Template PowerCenter Workflow Elapsed Time greater than recent Average Template PowerCenter Workflow Running Time Exceeds Workflow SLA Template PowerCenter Session Loaded Rows lesser than recent Average Template PowerCenter Scheduled Workflow missed schedule due to running status Template Enable the following template rules that are not related to environment monitoring: PowerCenter Workflow Running Time greater than Proactive Monitoring SLA 5 minutes PowerCenter Workflow Running Time greater than Repository SLA 10 minutes PowerCenter Workflow Load Mobile records running more than 2 minutes PowerCenter Scheduled Workflow missed schedule by 3 minutes due to running status PowerCenter Scheduled Workflow did not start 3 minutes after scheduled time PowerCenter Skewed Session to Workflow elapsed time ratio less than 0.6 PowerCenter Session Loaded Rows 25 percent lesser than recent Average PowerCenter Workflow Elapsed Time greater than 25pc of recent Average of 3 runs PowerCenter Session Elapsed Time 25 pc greater than recent Average PowerCenter Workflow Running Time greater by 25 percent than recent 3 Average PowerCenter Session Running Time greater than 25 percent of Average of previous 3 runs PowerCenter Session Exceeds Proactive Monitoring SLA 6 minutes PowerCenter Session Exceeds Repository SLA 10 minutes PowerCenter Session s_m_load_sports_events SLA 4 minutes 7

8 Configure Proactive Monitoring for PowerCenter Operations on Solaris To configure Proactive Monitoring for PowerCenter Operations on Solaris, transfer the required installation files to the Solaris machine. Install Apache Tomcat on Solaris and then enable the proactive monitoring solution. Install and Set Up Apache Tomcat Set up Apache Tomcat application server on the Solaris machine. 1. Download apache-tomcat tar.gz file from the following location: 2. Untar it to the same directory path on Solaris that you selected on the Linux host where you installed RulePoint and Real-Time Alert Manager. Use the following command to untar: # tar xvzf apache-tomcat tar.gz 3. Set the operating system environment variable $CATALINA_HOME to the installation directory of the Apache Tomcat application server. Set the environment variable for the entire system. For example, $CATALINA_HOME="/home/tomcat/apache-tomcat " Note: The directory names in the Tomcat installation path must not contain spaces. 4. Change the port numbers in $CATALINA_HOME/conf/server.xml as follows: Listener Port. Change to AJP Connector Port. Change to Server Admin Port. Change to Copy the rulepoint and RTAM directory from the $CATALINA_HOME/webapps/ of the Linux machine to the $CATALINA_HOME/webapps/ directory configured on the Solaris machine. Enable Proactive Monitoring on Solaris 1. Start the Apache Tomcat application server instance on Solaris where you deployed RulePoint and Real-Time Alert Manager. Restarting the Tomcat application server instance restarts RulePoint and Real-Time Alert Manager. 2. Log in to RulePoint to ensure that the solution is correctly installed on Solaris. Author Pubali Dekaphukan Senior Technical Writer Acknowledgements The author would like to acknowledge Indu Thomas, Sunaina Awadhiya, and Mandar A Mathure for their help with this article. 8