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

database. For example, the HP Web Jetadmin backup.bat file runs a SQL script on the same

machine to back up the database as such:

%OSQL% -S localhost\HPWJA -E -i osql_backup.sql > osql_backup.log

This line could easily be changed to run the script on the remote SQL server:

%OSQL% -H wksta_server -S SQL_server\Instance -U user -P password -i osql_backup.sql >

osql_backup.log

The SQL script backs up a database named HPWJA to DRIVE:\

BACKUP DATABASE HPWJA TO DISK =

'DRIVE:\HPWJA_DB_BACKUP\HPWJA_DB_BACKUP.dat'

This script could be changed to backup any database name to a shared UNC path:

BACKUP DATABASE database_name TO DISK = '\\WJA

_server\shared_directory\HPWJA_DB_BACKUP\HPWJA_DB_BACKUP.dat'

The backup.bat file creates a temporary directory to write the .dat file then removes it once the .dat

file is copied to the Program Files location. Since the backup.bat file looks for the .dat file under this

temporary directory, and it is impossible to share out this temporary directory since it doesn’t always

exist, an additional permanent directory could be created and shared. The SQL script could be

modified by adding an additional line to the backup.bat file to copy the .dat file from this shared

directory to the HP Web Jetadmin temporary directory. Now, the backup.bat script is never disrupted

and can continue from that point.

SUMMARY

An existing installation of Web Jetadmin can be configured to use SQL Server instead of SQL Express

for its database. For example, it may be more convenient for HP Web Jetadmin to use SQL Server

since it may already be installed, or to avoid the SQL Express 4 GB database limitation.