*Back to [[Book|Administrator's Configuration File Reference#cfr]] [[Topic|Administrator's Configuration File Reference#chap4]]*
h2. Editing {{magnus.conf}}
You can add directives or edit existing directives in {{magnus.conf}}. Be very careful when editing this file. Simple mistakes can make the server fail to operate correctly. When editing {{magnus.conf}}, use the {{wadm}} command {{get-config-file}} to pull a copy of the file, edit the file locally, then use {{set-config-file}} to put the edited file back. You must restart the server after editing {{magnus.conf}}.
Directives in {{magnus.conf}} either set a value or invoke a Server Application Function (SAF).
h3. Parameters
For pre-defined SAFs, the number and names of parameters depend on the function. The order of parameters on the line is not important.
h3. Case Sensitivity
Items in the {{magnus.conf}} file are case-sensitive including function names, parameter names, parameter values, and path names.
h3. Separators
The C language allows function names to be composed only of letters, digits, and underscores. You may use the hyphen ( - ) character in the configuration file in place of underscore ( _ ) for your C code function names. This is only true for function names.
h3. Quotation Marks
Quotation marks ( '' ) are only required around the value strings when there is a space in the string. Otherwise, they are optional. Each open quotation mark must be matched by a closed quotation mark.
h3. Spaces
* Spaces are not allowed at the beginning of a line except when continuing the previous line.
* Spaces are not allowed before or after the equal ( = ) sign that separates the name and value.
* Spaces are not allowed at the end of a line or on a blank line.
h3. Line Continuation
A long line may be continued on the next line by beginning the next line with a space or tab.
h3. Path Names
Always use forward slashes ( / ) rather than backslashes ( \ ) in path names on the Windows platform. A backslash escapes the next character.
h3. Comments
Comments begin with a pound ( # ) sign. If you manually add comments to {{obj.conf}}, then use the Admin Console or CLI to make changes to your server, your comments are overwritten when {{obj.conf}} is updated.
h2. Editing {{magnus.conf}}
You can add directives or edit existing directives in {{magnus.conf}}. Be very careful when editing this file. Simple mistakes can make the server fail to operate correctly. When editing {{magnus.conf}}, use the {{wadm}} command {{get-config-file}} to pull a copy of the file, edit the file locally, then use {{set-config-file}} to put the edited file back. You must restart the server after editing {{magnus.conf}}.
Directives in {{magnus.conf}} either set a value or invoke a Server Application Function (SAF).
h3. Parameters
For pre-defined SAFs, the number and names of parameters depend on the function. The order of parameters on the line is not important.
h3. Case Sensitivity
Items in the {{magnus.conf}} file are case-sensitive including function names, parameter names, parameter values, and path names.
h3. Separators
The C language allows function names to be composed only of letters, digits, and underscores. You may use the hyphen ( - ) character in the configuration file in place of underscore ( _ ) for your C code function names. This is only true for function names.
h3. Quotation Marks
Quotation marks ( '' ) are only required around the value strings when there is a space in the string. Otherwise, they are optional. Each open quotation mark must be matched by a closed quotation mark.
h3. Spaces
* Spaces are not allowed at the beginning of a line except when continuing the previous line.
* Spaces are not allowed before or after the equal ( = ) sign that separates the name and value.
* Spaces are not allowed at the end of a line or on a blank line.
h3. Line Continuation
A long line may be continued on the next line by beginning the next line with a space or tab.
h3. Path Names
Always use forward slashes ( / ) rather than backslashes ( \ ) in path names on the Windows platform. A backslash escapes the next character.
h3. Comments
Comments begin with a pound ( # ) sign. If you manually add comments to {{obj.conf}}, then use the Admin Console or CLI to make changes to your server, your comments are overwritten when {{obj.conf}} is updated.