HP Web Jetadmin - Columns and Filters Detail

Now two filter items are created with an AND joining them. Figure 25 shows these filters along with

an advanced representation shown in Notepad editor.

Gotchas

We will take a moment to consider the

complexity of this area of HP Web Jetadmin.

This portion of the HP Web Jetadmin interface

provides a literal logic interface that can be

used to build pretty much any test for detecting

devices and populating lists and groups. Here

are a few tips about creating filtering around

complex device details:

NOT – Putting NOT at the secondary filter level.

It is very important to remember that you can put

NOT at the primary level, but this creates a

different logical test that operates on the overall

table values rather than the targeted elements

such as IP Address and Community Name.

Adding Multiple Secondary Filters – This is possible if tests are to be performed on multiple targets.

For instance, if a statement such as IP Address = xxx.xxx.xxx.xxx AND Community = YYYY are

desired, then adding multiple filters at the secondary filtering level is okay. In our example, adding

both IP Address tests is not logical because the secondary filter will ask for an entry to equal

xxx.xxx.xxx.xxx AND yyy.yyy.yyy.yyy. Since this is not possible, the resulting list will be blank. Both

All Item Matches and Any Items Match have this logical characteristic.

All Item Matches vs. Any Items Match – Both items provide different views into complex details. These

should be taken literally when forming filter logic. All Item Matches means just that, all the items in

the selection will be tested to see if they match the filter criteria. Similarly, Any Items Match means the

test will detect single or multiple items that match the criteria. In our example filter where we used

NOT equals a specific IP Address entry, the test was set up to detect a table where none of the entries

had that specific IP address value.

Complex within Complex – Sometimes a complex device detail can contain other complex details.

And, sometimes these can contain further complex details. In these cases, we can not only create

secondary layers of filtering, but also create tertiary layers of filtering and so on. At this point, it is

easy to analyze filtering using the Advanced filter editor that we see being used in Figure 25.

SUMMARY

HP Web Jetadmin contains an effective and powerful set of tools in columns and filtering features.

This document should serve as a reference for understanding these changes and continued successful

use of the HP Web Jetadmin software. Watch for updates to this document in the future.

Figure 25 – Resulting Filters