* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Connecting to a Named Instance of Microsoft SQL Server from
Survey
Document related concepts
Concurrency control wikipedia , lookup
Oracle Database wikipedia , lookup
Extensible Storage Engine wikipedia , lookup
Microsoft Access wikipedia , lookup
Ingres (database) wikipedia , lookup
Team Foundation Server wikipedia , lookup
Database model wikipedia , lookup
Relational model wikipedia , lookup
Clusterpoint wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Transcript
Connecting to a Named Instance of Microsoft SQL Server from Proactive Monitoring for PowerCenter 3.0 © 2014 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. All other company and product names may be trade names or trademarks of their respective owners and/or copyrighted materials of such owners. Abstract You can use a named instance of Microsoft SQL Server to configure Proactive Monitoring for PowerCenter, version 3.0. This article provides the format of the URL that you must use to connect to the named instance of the SQL server. The article also provides the name and location of the properties files whose URL format you must update. Supported Versions • Proactive Monitoring for PowerCenter Operations 3.0 • Proactive Monitoring for PowerCenter Governance 3.0 Table of Contents Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Provide the JDBC URL in Proactive Monitoring for PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Update the Properties Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Overview If you choose a named instance of Microsoft SQL Server as the database to configure Proactive Monitoring for PowerCenter, you must specify the custom JDBC parameters during installation. Proactive Monitoring for PowerCenter uses the JDBC drivers to connect to the Microsoft SQL Server database. If the Microsoft SQL Server database is a named instance, you must specify the instance name assigned to the TCP/IP port. Specify the JDBC connection string for the database driver during the installation. Provide the JDBC URL in Proactive Monitoring for PowerCenter When you install Proactive Monitoring for PowerCenter, specify the JDBC connection string for the database driver in the Database Configuration page. Proactive Monitoring for PowerCenter requires the JDBC connection URL when it verifies the connection information for an object. 1. Run the Proactive Monitoring for PowerCenter Operations installer. 2. Specify the database type as Microsoft SQL Server. 3. Enter the database information where you want to configure Proactive Monitoring for PowerCenter. 4. Provide the JDBC parameters to include in the JDBC URL and the connection string for the DataDirect driver in the following format: jdbc:informatica:sqlserver://<HOST_NAME>\<NAMED_INSTANCE_NAME>;databaseName=<DB_NAME> In the JDBC URL, <HOST_NAME> is the hostname of Microsoft SQL Server database, <NAMED_INSTANCE_NAME> is the named instance of Microsoft SQL Server, and <DB_NAME> is the name of the Microsoft SQL Server database. Note: You must use a single slash "\" after <HOST_NAME> in the URL. You must update the URL in the property files after the installation. The installer fails to start the node if you do not update the properties files. 5. 2 Click Test Connection to verify that you can connect to the database, and then continue with the installation. Update the Properties Files After you complete the installation, update the format of the JDBC URL in the properties files. 1. Update the URL in the properties files. Add a slash after the host name. For example, jdbc:informatica:sqlserver://10.65.12.93\\pmpcdb;databaseName=samplename. The following table lists the name and location of the properties files that you must update: File Name Location - cs.properties - rpagent.properties <PROACTIVE_MONITORING_HOME>\rulepoint\conf - cs.properties - jdbc.dashboard.properties - jdbc.properties <PROACTIVE_MONITORING_HOME>\rulepoint \design\webapps\rulepoint\WEB-INF\classes - cs.properties - rtam-config.properties <PROACTIVE_MONITORING_HOME>\rulepoint \design\webapps\RTAM\WEB-INF\classes jdbc.properties <PROACTIVE_MONITORING_HOME>\rulepoint \design\webapps\pmpc\WEB-INF\classes nodeagent.properties <PROACTIVE_MONITORING_HOME>\nodeagent\conf \nodeagent.properties Note: You must first unzip nodeagent.zip from the <PROACTIVE_MONITORING_HOME> location. 2. Verify that the existing Proactive Monitoring for PowerCenter processes, such as the java process for host agent, node, design time, grid manager, lbmrd, and umestored are not running. 3. Start the Proactive Monitoring for PowerCenter instance. At the command prompt, enter the following command to start the instance on Windows or Linux: • For Windows: <PROACTIVE_MONITORING_HOME>\bin solution.bat start • For Linux: <PROACTIVE_MONITORING_HOME>/bin solution.sh start Author Dimple Rai Senior Technical Writer Acknowledgements Thanks to Shilpa and the QA team for their help in completing this article. 3