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

While HP Web Jetadmin supports database mirroring, the behavior of the HP Web Jetadmin service

and connected clients may vary when a failover occurs on the database. The HP Web Jetadmin

service may sometimes stop as Microsoft fails over to the alternate database. When a failure occurs

with the database connection, Microsoft switches the HP Web Jetadmin database connection to the

alternate database and reports the failed database transaction to HP Web Jetadmin with an

exception. Depending upon where HP Web Jetadmin accesses the database, the exception may

cause the HP Web Jetadmin service and attached clients to fail.

It is recommended to configure the HP Web Jetadmin service to automatically restart after an

abnormal termination (such as a failover) so that there is no manual intervention required to get the

service back up and running again on the new primary database. The service and clients still fail, but

only temporarily as the service should be up and running again on its own, and the clients can be

restarted.

When a failover happens, further connection attempts go to the failover partner. If those are

successful the service continues to run. If they are not successful the service shuts down. On restart, the

service should function normally if the failover partner node is available. Otherwise it waits for a

database connection to succeed before the service comes up all the way.

PERFORMANCE SETTINGS

Other properties that can be set in the DatabaseSettings.config.xml file include:

 DatabaseConnectionFactory.MinimumPoolSize—Sets the minimum number of connections to keep

open to the database. Default is 0.

 DatabaseConnectionFactory.MaximumPoolSize—Sets the maximum number of connections to

allow to be opened to the database. Default is 100.

 DatabaseConnectionFactory.CommandTimeoutInSeconds—How long to wait for results to start

being returned in a query. Default is 120.

These settings can be used to improve performance when reading from and writing to the database.

BACKUP OF HP WEB JETADMIN CONFIGURED FOR A

REMOTE DATABASE

Administrators may want to run scheduled backups of the HP Web Jetadmin installation that points to

a remote SQL database. HP Web Jetadmin provides scripts to back up the default SQL Server Express

database instance that is installed with the base product. It also backs up the HP Web Jetadmin

configuration settings. If the backup and restore scripts from the HP Web Jetadmin install directory

(WJABackupRestore directory) have been used previously to back up the local HP Web Jetadmin

installation, the following options may need to be considered to ensure backing up the remote

database:

 Option 1: Backup and restore of the remote database is not done by HP Web Jetadmin. There

may already be other processes in place for backing up the remote SQL database and the

HP Web Jetadmin settings directory so the HP Web Jetadmin script is not required.

 Option 2: Continue to use the HP Web Jetadmin backup script, but remove or comment out the

lines in the script that back up the database. This allows the script to continue backing up the

HP Web Jetadmin settings directory. There may already be other processes in place for backing

up the remote SQL database so backup of the remote database is not performed by HP Web

Jetadmin.

 Option 3: Modify the HP Web Jetadmin script to back up the remote database as well as the

HP Web Jetadmin settings directory. The lines in the scripts that back up the default SQL Server

Express database instance can be replaced with custom commands that will back up the remote