Cisco Cisco Firepower Management Center 2000 Entwickleranleitung

Some XML editors can read the 

module.template

 schema and automatically generate a 

module.template

 file with a namespace and schema declaration, with the top level element and child 

elements and attributes. If you choose not to use such an editor, you must include the child elements 
manually. 

If you set your XML editor to auto-generate the namespace and schema location, you must delete those 
lines before including the final version of 

module.template

 in your installation package.

The following example illustrates the 

module

 element with only the 

name

 attribute defined.

<module name="example_module">

<global_config>

<display_name/>

<version/>

<binary/>

</global_config>

<remediation_type name="">

<display_name/>

</remediation_type>

</module>

See the following sections for details about writing the rest of 

module.template

:

 explains how to use the 

global_config

 element to 

define the name that appears for your module on the Modules page, as well as the module’s version, 
binary location, and its description.

 explains how to use the 

config_template

 element 

to define the configuration information that your module requires the user to specify from the web 
interface.

 explains how to use the 

remediation_type

 element to 

define the remediations the module can launch and the correlation event data that each remediation 
requires.

 explains how to use the 

exit_status

 element define the custom 

exit statuses your module returns to the remediation subsystem.