Using modules

Modules contain processes and the related schedules, configurations, and rules. Modules can be independent or they can depend on processes and configuration items in other modules. You can use the  Development Studio application to create new or customized processes.

Generally, modules reside in the repository, which stores all content for the  application. Modules can also reside in module archive files (.roar files) in the  Development Studio workspace, particularly if they are new or have been imported from the repository for editing or testing. You can create new modules in  Development Studio. To use new or revised modules, you export them to the repository and activate them on a grid.

Some of the modules in the repository contain prebuilt processes that automate tasks. For example, Operations Actions utilities provide many out-of-the-box processes that perform server tasks. You can use imported modules as a basis for customized processes. To use or edit those processes, you must import the modules from the repository or a disk and unbundle them in the Library Manager. The Import Modules tab displays the latest version of the module, but you can import any version that is available in the repository. To see all versions for a module, click the version number for that module.

You can use software configuration management (SCM) systems to help manage versioning of modules and their components.

This section contains the following topics:

• Library Manager
• Creating modules
• Using process directories
• Creating rules
• Creating schedules
• Configuration items