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.50

Develop > Automation Platform Extensions (APX)

Automation Platform Extensions (APX)

This topic describes how to create and manage Automation Platform Extensions (APX), commonly just called extensions. APXs provide a framework that allows anyone familiar with script‑based programming tools such as shell scripts, Python, Perl, and PHP, to extend the functionality of SA and create applications that are tightly integrated into SA. SA provides two types of APXs:

Program APXs (also called Script APXs) run in the Global File System (OGFS) and can use all of the OGFS functionality. You can use typical programming practices to leverage the SA API and access a core’s Managed Servers to implement new custom functionality. For example, you could write an APX that gathers BIOS information from managed servers and populates custom fields using shell commands. See Program APXs.
Web APXs allow you to create a web-based application, where either an Apache 2.x process or a CGI/PHP script is called using GET or POST URL. Web APXs can contain static web resources such as images, and can employ CGI or PHP for dynamic content generation. See Web APXs.

APXs allow you to access data about your managed environment and share and process that data with web applications, scripts, programs and other applications. Below are some of the benefits of APXs:

Listed in the SA Library and can be used from the SA Client.
Uniquely identified and managed through versioning.
Secure because they take full advantage of SA’s security model. When needed, APXs can securely and temporarily escalate a user’s permissions beyond the normal defaults during the APX session.
Scalable within and across SA cores.
You can schedule them to be pushed automatically to servers.
Auditable.
Able to persist through an upgrade of the SA platform. APXs do not have to be rewritten after an upgrade.

For information on using APX extensions, see the Running Extensions to SA section in the SA 10.50 User GuideOverview See also the SA Global Shell section in the SA 10.50 User Guide because you can also run APX extensions from the SA Global Shell.

Send Help Center feedback