System::Session::set_active_folder¶
Introduced : BIG-IP_v11.0.0
Sets the active folder. Most configuration objects reside in folders
(see the Management::Folder interface), but continually specifying the
full path to name an object can be wearing. For ease, an “active
folder” can be specified. When creating or accessing objects and a
full object path is not specified (i.e., the object path does not
begin with a slash (/)), the active folder is prepended to the object
name. Thus if the name for an object to be created is specified as
“repository-a” and the active folder is /george/server, the full path
for the created object is /george/server/repository-a. Note that
relative paths are also allowed in the object identifier, so that if
the active folder is /george/server and the given object identifier is
virtual/repository-a, then the full object path is
/george/server/virtual/repository-a. The active folder may be the root
folder (/), but that is only usable when querying. If for some reason,
neither the currently active folder nor the newly requested active
folder exist, the currently active folder will be set to the
user&aposs default folder.
Parameters¶
Parameter | Type | Description |
folder | String | Active folder. The default is the folder in which the user is defined to have a role. If the role is valid in all folders, it defaults to /Common. |
Exceptions¶
Exception | Description |
Common::AccessDenied | Raised if the client credentials are not valid. |
Common::InvalidArgument | Raised if one of the arguments is invalid. |
Common::OperationFailed | Raised if an operation error occurs. |
See Also¶
Warning
The links to the sample code below are remnants of the old DevCentral wiki and will result in a 404 error. For best results, please copy the link text and search the codeshare directly on DevCentral.
Sample Code¶
- PowerShell Management Folder - This example illustrates how to use the Folder methods to build a console shell allowing you to navigate and manage system Folders on BIG-IP v11 and above.
The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.