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)`

Server Automation10.60

Use > Server Automation > Run SA extensions > Add scripts to extensible discovery > Upgrade your scripts in extensible discovery

Upgrade your scripts in extensible discovery

This section describes how to upgrade your scripts that are used with Extensible Discovery. The following steps presume you have already created and installed a script called get_mysysdata.sh and wrapped it in the file get_windows_data_v1.0.zip and imported it into Extensible Discovery as described in Add your own scripts to extensible discovery. To upgrade this script:

Create the new version of your script and give it the same name as the original script file. For example, use get_mysysdata.sh. Follow the instructions in Write your own scripts for extensible discovery.
Wrap your script in a .zip file and increment the version string of the .zip file. For example, you could use get_windows_data_v1.1.zip.
Import your .zip file into a package in SA.

For convenience, you can place your packages in /Opsware/Tools/Extensible Discovery/Customer Provided Components. Make sure your imported package specifies the proper target operating system.

For instructions on importing packages, see "Software management" in the SA Use section.
Open your package in the SA Client and set the Default Install Path property to one of the following and save your changes.
- UNIX: /var/opt/opsware/extensible_discovery/scripts
- Windows: %ProgramFiles%\Common Files\Opsware\extensible_discovery\scripts\. SA replaces %ProgramFiles% with the appropriate system Program Files directory.
Open the software policy “Customer Provided Scripts”. If you have used another software policy, open that policy.

Note
Make sure the respective software policy has the proper target operating system(s).
Remove the old .zip file from the policy, get_windows_data_v1.0.zip in this example.
Add your new .zip file to the policy, get_windows_data_v1.1.zip in this example.
If you are using the “Customer Provided Scripts” policy, run Extensible Discovery as described in Running extensible discovery on managed servers. This remediates your new script on the managed servers.

If you are using another policy, remediate the servers with that policy. This remediates your new script on the managed servers so Extensible Discovery can be run.

Send Help Center feedback