/**
 * API action for admin general settings management.
 * Provides RESTful API endpoints for managing general system configuration settings in the Fess search engine.
 * General settings include system-wide parameters, LDAP configuration, and core application settings.
 *
 */
public class ApiAdminGeneralAction extends FessApiAdminAction {

    // ===================================================================================

# Using the Request Directly { #using-the-request-directly }

Up to now, you have been declaring the parts of the request that you need with their types.

Taking data from:

* The path as parameters.
* Headers.
* Cookies.
* etc.

And by doing so, **FastAPI** is validating that data, converting it and generating documentation for your API automatically.

But there are situations where you might need to access the `Request` object directly.

        }
    }

    /**
     * Converts this access result data to XContent format for OpenSearch indexing.
     *
     * @param builder The XContentBuilder to write to.
     * @param params Additional parameters for the conversion.
     * @return The XContentBuilder with the access result data.
     * @throws IOException if the conversion fails.
     */
    @Override

    /**
     * Converts this URL queue entry to XContent format for OpenSearch indexing.
     *
     * @param builder The XContentBuilder to write to.
     * @param params Additional parameters for the conversion.
     * @return The XContentBuilder with the URL queue data.
     * @throws IOException if the conversion fails.
     */
    @Override

    * This includes a file-like interface.
    * Here's the updated documentation for declaring [`File` parameters with `UploadFile`](https://fastapi.tiangolo.com/tutorial/request-files/#file-parameters-with-uploadfile).
    * And here's the updated documentation for using [`Form` parameters mixed with `File` parameters, supporting `bytes` and `UploadFile`](https://fastapi.tiangolo.com/tutorial/request-forms-and-files/) at the same time.

            doColumn("createdTime");
        }

        public void columnHostname() {
            doColumn("hostname");
        }

        public void columnParameters() {
            doColumn("parameters");
        }

        public void columnPassword() {
            doColumn("password");
        }

        public void columnPort() {
            doColumn("port");
        }

The AMQP configuration is located under the sub-system `notify_amqp` top-level key. Create a configuration key-value pair here for your AMQP instance. The key is a name for your AMQP endpoint, and the value is a collection of key-value parameters described in the table below.

```
KEY:
notify_amqp[:name]  publish bucket notifications to AMQP endpoints

ARGS:
url*           (url)       AMQP server endpoint e.g. `amqp://myuser:mypassword@localhost:5672`

    protected String path;

    /** The timestamp when this dictionary file was created or last modified. */
    protected Date timestamp;

    /**
     * Creates a new DictionaryFile with the specified parameters.
     *
     * @param id the unique identifier for this dictionary file
     * @param path the file path of this dictionary
     * @param timestamp the timestamp of the dictionary file
     */

            assertEquals(8, entries[i].getType());
        }
    }

    @Test
    @DisplayName("Constructor should use default DCE/RPC parameters")
    void testConstructorDefaults() {
        // Verify default parameters are set correctly
        assertEquals(0, dfsRootEnum.getPtype());
        assertEquals(0xFFFF, dfsRootEnum.prefmaxlen);
        assertEquals(0, dfsRootEnum.totalentries.value);

        super.setUp();
        // Create a test implementation of ScriptEngine
        scriptEngine = new TestScriptEngine();
    }

    // Test evaluate method with valid template and parameters
    public void test_evaluate_withValidTemplateAndParams() {
        String template = "Hello ${name}";
        Map<String, Object> paramMap = new HashMap<>();
        paramMap.put("name", "World");