此内容没有您所选择的语言版本。
Chapter 13. Example: Scripts to Manage Inventory (All Resource Types)
Servers and services are routinely added or removed from a local machine. While discovery scans are scheduled regularly, actually adding or removing that resource within the JBoss ON inventory is all manual — and administrator must actually choose to import the resource.
An administrator can manage the JBoss ON inventory by automatically adding new resources and automatically deleting other ones based on whatever criteria are defined.
13.1. Automatically Import New Resources: autoimport.js 复制链接链接已复制到粘贴板!
复制链接链接已复制到粘贴板!
As soon as a resource is discovered it is, technically, already in the JBoss ON inventory. It is included with a status of NEW. That's an in-between state, because JBoss ON is aware that the resource exists, but the resource has not been committed so JBoss ON can't manage it.
A script can be created and run regularly so that any newly-discovered resources can be automatically added to the inventory. This script bases its identification on new resources on the inventory state, so ignored or already imported resources aren't included.
The CLI script runs through three steps:
- It identifies new resources using the
findUncommittedResources()
method. - It gets those new resources' IDs.
- It then imports those resources by invoking the discovery system's import operation.
Only one of the operations is already defined in the remote API —
importResources
. The other two functions — findUncommittedResources
and getIds
— have to be defined in the script.
Uncommitted (new) resources can be identified through a
ResourceCriteria
search by adding a search parameter based on the inventory status.
The second function checks that the inventory search actually returned resources and, if so, gets the ID for each resource in the array.