...
- Stop the server.
- Back up the current config.xml file and open the file in an editor.
- Review the current config.xml file. You can find <module> elements with the following form. Each module contains 0, 1, or more <gbean> elements which, in turn, contain 0, 1, or more <attribute> elements.
whereCode Block XML XML borderStyle solid XML <module name="moduleName"> <gbean name="beanName"> <attribute name="name">value</attribute> . . . </gbean> . . . </module>
indent 0 0 _moduleName_
indent 1 1 The module name of the component that contains the GBeans that have attributes to be configured. The value specified must match the value specified when the component was deployed. Use the deployer's [list-modules|deploy#deploy-Listmodulescommandandoptions] command to obtain the list of module names deployed in your server. Note that you can use *load="false"* attribute in <module ...> element to prevent the module from starting up.
indent 0 0 _beanName_
indent 1 1 The name of the GBean in the current configuration that contains the attribute to be configured.
indent 0 0 _name_
indent 1 1 The name of the attribute with a value that is to be configured.
indent 0 0 _value_
indent 1 1 The current configuration value that overrides the default attribute value in the current configuration.
- Change the attribute values as necessary to customize your configuration.
- Save and close config.xml.
- Restart the server and test your configuration changes.
...