Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Transferring an Enterprise Reporter Database

This section provides details about the Transfer task.

Syntax

Start-ERTransfer [-SourceSqlHost] <string> [[-SourceDatabaseName] <string>]
[[-SourceUserID] <string>][[-SourcePassword] <string>] [-TargetSqlHost] <string>
[-TargetDatabaseName] <string> [[-TargetUserID] <string>] [[-TargetPassword] <string>] [-SelectedOptions] <TransferDataSelectionEnum>
{None | ClustersAndNodes | Discoveries | Reports} [<CommonParameters>]

Parameters

•
[-SourceSqlHost] is the name of the SQL Server that holds the source database.
•
[-SourceDatabaseName] is the name of the database containing the data that will be transferred into a clean target database.
•
[-SourceUserID] (optional) is the SQL Server user ID used to connect to the source database. If not provided, Windows credentials are used.
•
[-SourcePassword] (optional) is the SQL Server password to the source database. If not provided, Windows credentials are used.
•
[-TargetSqlHost] is the name of the SQL Server that holds the target database.
•
[-TargetDatabaseName] is the name of the database that the data will contain the transferred data.
•
[-TargetUserID] (optional) is the SQL Server user ID used to connect to the target database. If not provided, Windows credentials are used.
•
[-TargetPassword] (optional) is the SQL Server password to the target database. If not provided, Windows credentials are used.
•
[-SelectedOptions] are the three choices of data to transfer in any combination. You may specify each data type using its name or numerical equivalent. ClustersAndNodes (or 1), Discoveries (or 2), and Reports (or 4).
To transfer clusters and nodes, discoveries and reports using Windows authentication
•
Provide values for SourceSqlHost, SourceDatabaseName, TargetSqlHost, TargetDatabaseName. and SelectedOptions.
Start-ERTransfer –SourceSqlHost Sample.Sql.Server –SourceDatabaseName SourceDatabase –TargetSqlHost TargetSample.Sql.Server –TargetDatabaseName TargetDatabase –SelectedOptions 1, 2, 4
To transfer clusters and nodes, discoveries and reports using SQL server authentication
•
Provide values for SourceSqlHost, SourceDatabaseName, SourceUserID, SourcePassword, TargetSqlHost, TargetDatabaseName, TargetUserID and TargetPassword.

Start-ERMerge –SourceSqlHost Sample.Sql.Server –SourceDatabaseName SourceDatabase –SourceUserID TestUser –SourcePassword fee3td
–TargetSqlHost TargetSample.Sql.Server –TargetDatabaseName TargetDatabase –TargetUserId TargetUser –TargetPassword fhfsk8 –SelectedOptions ClustersAndNodes, Discoveries, Reports

Appendix: Encryption Key Manager

•
Starting the Encryption Key Manager
•
Generating a key file
•
Importing a key file
•
Exporting a key file
•
Resetting credentials

Enterprise Reporter makes use of FIPS 140-2 compliant encryption to secure user credentials and includes an encryption key management tool. The Enterprise Reporter Encryption Key Manager can be started from the Windows Start menu. This tool allows you to perform the following tasks related to the Enterprise Reporter encryption key.

•
Generating an encryption key
•
Importing an encryption key from a backup file
•
Exporting an encryption key to a backup file
•
Resetting Enterprise Reporter user credentials

Starting the Encryption Key Manager

To start the Encryption Key Manager from the Windows Start menu
1
Click Programs | Quest | Enterprise Reporter | Encryption Key Manager.

Generating a key file

The Encryption Key Manager can be used to generate a new encryption key. If Enterprise Reporter contains credentials with passwords, selecting this option will force the decryption and re-encryption of all Enterprise Reporter user credentials. If the decryption of the existing passwords fails, the procedure is unsuccessful, errors are returned, and no key file is generated. If the decryption and re-encryption is successful, the procedure continues and the new encryption key is written to the secure Windows Credential Manager (not to be confused with the Enterprise Reporter Credential Manager). The user is prompted to export the new key to a backup file.

To generate a key file
1
Stop all Enterprise Reporter nodes.
2
Start the Enterprise Reporter Encryption Key Manager.
3
Click the Generate Key button.
4
Read and accept the warning.
5
Click OK to generate a new key file.
6
Click OK to continue to export the key file to a backup file.
For more information, see Exporting a key file .
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation