HP Web Jetadmin - Using Microsoft SQL Server with HP Web Jetadmin

Windows Authentication

For Windows Authentication, since the Web Jetadmin service is now running under a domain user

account instead of Network Service, crucial Web Jetadmin files must be copied from the old Network

Service location to the new Domain User Account location in order for Web Jetadmin to be able to

use the remote database.

On Windows XP/Server 2003, copy the files and directories from:

DRIVE:\Documents and Settings\NetworkService\Local Settings\Application Data\Hewlett-

Packard\HPWebJetadmin

To:

DRIVE:\Documents and Settings\<Domain User Account>\Local Settings\Application

Data\Hewlett-Packard\HPWebJetadmin

On Windows Vista/Server 2008 R2/Windows 7/Server 2012, copy the files and directories from:

DRIVE:\Windows\ServiceProfiles\NetworkService\AppData\Local\Hewlett-

Packard\HPWebJetadmin

To:

DRIVE:\Users\<Domain User Account>\AppData\Local\Hewlett-

Packard\HPWebJetadmin\WjaService\config\DatabaseSettings.config.xml

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

Network Service, edit the following file on Windows XP/2003:

DRIVE:\Documents and Settings\<Domain User Account>\Local Settings\Application

Data\Hewlett-Packard\HPWebJetadmin\WjaService\config\DatabaseSettings.config.xml

On Windows Vista/2008 R2/Windows 7:

DRIVE:\Users\<Domain User Account>\AppData\Local\Hewlett-

Packard\HPWebJetadmin\WjaService\config\DatabaseSettings.config.xml

Care must be exercised when editing these XML files as extraneous carriage returns can create

problems. Be careful to ensure carriage returns reside as indicated in the examples on the next page.

Typical symptoms that the file has not been edited correctly include the inability to connect to the

HP Web Jetadmin server after restarting the service (since the server cannot connect to the database).

NOTE It is imperative to open the existing file and copy/paste the contents as they are displayed

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

User account in order for HP Web Jetadmin to be able 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 one. Ensure

that the Windows Domain User account has read/write rights. Some older versions of HP

Web Jetadmin may not contain the DatabaseSettings.config.xml file by default, and it must be

created by the user. Just ensure the rights are assigned as mentioned above when creating

the new file. Also, if file extensions are hidden, make sure the file does not have a “.txt”

extension or two “.xml” extensions. 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 need to be defined in the

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

For Windows Authentication, cut and paste the contents of the following examples into the

configuration file if using a named instance instead of a default instance, replacing the instance