HP Web Jetadmin Software Manuel d'utilisateur télécharger pdf (Page 14)

Now that the necessary HP Web Jetadmin files reside under the correct Domain User Account instead

of Network Service, edit the following file on Windows Vista, 2008 R2, Windows 7, and

Windows 8:

C:\Users\domain_user_account\AppData\Local\HP Inc\HPWebJetadmin\

WjaService\config\DatabaseSettings.config.xml

Be careful when editing XML files. Extraneous carriage returns can create problems. Make sure that

the carriage returns reside as indicated in the following examples. Typical symptoms that indicate the

file has not been edited correctly include the inability to connect to the HP Web Jetadmin server after

restarting the service, which occurs because the server cannot connect to the database.

CAUTION It is imperative that you open the existing file and copy and paste the content as it is

displayed here to maintain the user rights. The file must have read/write rights for

Network Service in order for HP Web Jetadmin to use it. If a new file is created

instead of opening the existing file, the new file assumes the user’s rights. If this

happens, HP Web Jetadmin does not attempt to use the new database and defaults

to the old database. Make sure that Network Service has read/write rights. Some

older versions of HP Web Jetadmin might not contain the

DatabaseSettings.config.xml file by default. In this case, you must create the file.

Make sure that the rights are assigned as mentioned previously when creating the

new file. Also, if file extensions are hidden in Windows Explorer, make sure that the

file does not have a .txt or .xml.xml extension. This is a common mistake when using

a text editor to create this file.

For a remote instance of SQL Server, there are several items that must be defined in the configuration

file, such as the remote machine name, database name, and named instance.

For Windows Authentication, if you are using a named instance instead of a default instance, copy

the content of the following examples and paste it into the configuration file. Replace the instance

configuration file with either a named instance or a default instance. Replace the machine name,

instance name, and database (catalog). The sections containing the user name and password are not

required as is the case when using SQL Authentication. Without a user name and password in the

file, HP Web Jetadmin knows to use Integrated Security (Windows Authentication) in the connection

string to SQL Server. Remember that HP Web Jetadmin identifies itself remotely as Domain\Machine$

when Windows Authentication (Integrated Security) is used. In this case, make sure that the

Domain\Machine$ account has DBO rights (or read/write/execute at a minimum, see the Database

rights section) on the database. To use a Windows User account instead of a Windows Machine

account, the properties for the HP Web Jetadmin service must be changed from Network Service to

the Windows User account. After this is done, HP Web Jetadmin identifies itself to the remote SQL

Server as the Windows User account. Therefore, make sure that the Windows User account has DBO

rights (or read/write/execute at a minimum, see the Database rights section) on the database.

Remember, encrypted data, such as global credentials, are locked to the user/machine account and

must be re-entered.

For HP Web Jetadmin 10.4 and earlier, the folder name in the installation directory path is Hewlett Packard. For HP Web

Jetadmin 10.4 SR1 and later, the folder name in the installation directory path has been changed from Hewlett Packard to HP

Inc.

1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 29 30

Pas de commentaire

HP Web Jetadmin Software Manuel d'utilisateur Page 14