Script Modules

This chapter contains the following sections:

Script Modules

Script modules are used to integrate third-party jars and custom libraries with Cisco UCS Director to perform specific operations. Some script module operations are already defined in Cisco UCS Director, including:

  • Creating advanced controls to collect user input in workflows, including tabular reports and lists of values (LOVs).

  • Context workflow mapping, which enables you to attach workflows to custom actions in a report in Cisco UCS Director.

For more examples of script module use, see the Cisco UCS Director Orchestration Guide.

When to Use Script Modules

Use a script module when you want to create custom functionality that can be used in custom workflow tasks or added to Cisco UCS Director. Script modules can be exported and re-used in different instances of Cisco UCS Director.

Using Script Modules

You create script modules in Cisco UCS Director. You can then call the script module's libraries and methods from custom tasks.

You can import and export script modules along with worflows, custom tasks, and activities in Cisco UCS Director using the Import and Export actions respectively in the Policies > Orchestration > Workflows tab.

See the Cisco UCS Director Orchestration Guide for how to create a script module and add libraries and jar files to the script module.

See the Cisco UCS Director Custom Task Getting Started Guide for information about using script modules in custom tasks.


Note

Despite similar names, script modules and script bundles are very different things. Script bundles are packaged collections of workflow tasks that are released with Cisco UCS Director. Script modules are a mechanism for you to add custom functionality to the Cisco UCS Director UI.