Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

CMS UI2018.08

Use > CMS Modules > Package Manager > Package Administration > Package Administration Overview

Package Administration Overview

Note The Package Manager module is available for users with the following permissions:

A package contains resources that are grouped together by defined criteria. For a list of the default resource types, see Resource Types.

Package Manager fulfills several functions:

Enables the discovery of specific IT infrastructure assets. For example, deploys the SQL_Server package to discover Microsoft SQL servers.
Enables you to define the CI Type model through the CI types that are included in the packages. For example, some of the CI types included in the Host_Resources_Basic package are File System, CPU, Process, and Print Queue.
Enables you to move groups of resources from one system to another, for example, from a test to a production environment.

There are two types of packages:

Factory package. Contains resources that are deployed with the installation and are used to initialize .

By default, factory packages are located in the <UCMDB_installation_folder>\content\basic_packages folder.
Custom package. A package that is user created. You may want to create a custom package if the factory packages do not contain the resources needed for the tool you are developing, or if you want to export resources from system to system. For details, see How to Create a Custom Package.

Caution If you create custom packages for the resources or tools you develop, do not place them in the <UCMDB_installation_folder>\content\basic_packages folder. This folder is only for factory packages.

Export and deployment of packages from system to system is performed through the Package Manager interface.

You can:

Export some or all of a package's resources to your local directory. For details, see How to Export a Package.
Deploy some or all of a package's resources to the from your local directory. For details, see How to Deploy a Package.

Package Locations

There are three pre-defined folders with out-of-the-box, automatically deployed packages under <UCMDB_installation_folder>\content:

Each package in the Package Manager User Interface includes the following:

A Package Name representing the name of the .zip file (optional)
The Category as allocated in the descriptor.xml file (optional)
A Readme file that corresponds to the package (optional)
The Version number
The Build number
Factory identifying the package as factory or custom. A check mark represents the factory packages.
A Description that corresponds to the description located in the descriptor.xml file