SQL Scripts for Automating HP Web JetAdmin Configuration

[blair19]

The overall goal would be to deploy a Server Core instance with WJA at each site and run SQL scripts to configure the basic items mentioned below. All site WJAs would then be configured to sync to a centralized WJA, which I refer to as WJAM, aka Web Jetadmin Manager, for that 'single pane of glass' that everyone loves to have.

To help accomplish automating the site WJA side of things, I've just started digging into seeing how to automate the configuration of various Web Jetadmin items post installation. Such items of interest include the creation of device groups (based on model, NIC, etc.), discovery scans, group policies, and credentials. With these four specific items configured, a WJA deployment at a local site should then be fully ready to discovery and start managing printers.

Currently, my best guess is to use INVOKE-SQLCMD on one of our existing WJA instances to gain insight on configuration I've previously completed manually through the WJA GUI. I know nothing about databases, but I've been able to query and list all WJA tables, and from that list I've started poking around further. While I do see 'stuff,' I'm not seeing anything that currently makes much sense, such as the names of my current device groups; every result seems to contain some sort of GUID/UUID.

Sample Cmd; Invoke-Sqlcmd -ServerInstance .\HPWJA -Query "USE HPWJA; SELECT TOP 20 * FROM DAV_GROUP_POLICY;"

So, I haven't even gotten around to trying to create any sort of configuration, as I'm currently sort of stuck in trying to 'see' the things I've already configured in the current WJA instance and make sense of them.

If any of what I mentioned is not the 'best' way to accomplish this, I'm all ears.

[PaulGasper]

Just providing my insight here from a recent service call with HP.

They actually recommended to not set up multiple WJA instances due to synchronization of data.  I know this is a feature that is available and I was shocked to hear it was not recommended by their staff.  Your best bet would be to submit a support request for best practices if it must be set up this way.

[blair19]

That is rather interesting, though I've gone ahead and configured sync anyways. It's a one-way sync, not sure if that makes a difference or not as far as their recommendations.

As far as automating the configuration, it's gone back burner for now, though I was able to create a device group using SQL CMDs. This group did not 'show' until I restarted the server for an unrelated reason. and all of a sudden it was there.

I believe this was the command (I thought I kept better notes on this), which required at least these three values before working.

Invoke-Sqlcmd -ServerInstance .\HPWJA -Query `
"USE HPWJA; INSERT INTO IPMC_GROUP (GroupGUID, GroupType, NameID) VALUES ('ffe2404a-2645-4b02-a284-af99fdaecef6','Device', 'TESTING');"