サポートと今すぐチャット
サポートとのチャット

Enterprise Reporter 3.5 - Installation and Deployment Guide

Product Overview Installation Considerations for Enterprise Reporter Installing and Configuring Enterprise Reporter Managing Your Enterprise Reporter Deployment Troubleshooting Issues with Enterprise Reporter Appendix: Database Content Wizard Appendix: Encryption Key Manager Appendix: Log Viewer

Enterprise Reporter Architecture

Figure 1 outlines the relationship between the components.

Figure 1. Enterprise Reporter Architecture

 

Installation Considerations for Enterprise Reporter

•
Before You Install Enterprise Reporter
•
Reporter server and database considerations
•
System Requirements
•
Overview of Enterprise Reporter communications and required credentials
•
Database Requirements

Before You Install Enterprise Reporter

The system requirements are the same for all components of Enterprise Reporter. Ensure that the minimum requirements are met and all necessary software is installed before installing any of the components.

See also:

•
Reporter server and database considerations
•
System Requirements
•
Minimum permissions for installing Enterprise Reporter
•
Port Requirements
•
Firewall Requirements
•
Configuring the Database and Security Groups
•
Database Requirements

Reporter server and database considerations

You must choose a host computer for Enterprise Reporter server and a SQL Server to host the Enterprise Reporter database. Your decision affects the performance of the product.

The Enterprise Reporter server communicates directly with the database frequently. For best results, locate the Enterprise Reporter server physically close to the SQL Server.

The nodes also regularly connect to the database. The more nodes you have in your deployment, and the more discoveries you run, the greater the impact on the SQL Server. Choose a SQL Server with enough power to manage the connections and data transfer from the nodes. Check your Microsoft SQL Server documentation for more information on system requirements.

Reporter supports a variety of SQL configurations. You can use a regular SQL instance, a SQL cluster, or a mirrored database. If your SQL deployment supports it, using clusters or mirrors allows for automatic failover recovery in the event that a SQL Server is down.

See also:

•
Failover recovery using SQL clusters
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択