Administrative (or admin) operations listed in this topic allow you to control the behavior of the MDEX Engine from within the system.
Admin operation | Description |
---|---|
/admin?op=help | Returns the usage page for all of the admin operations. |
/admin?op=ping | Checks the aliveness of an MDEX Engine and returns a lightweight message. |
/admin?op=flush | Specifies when the MDEX Engine should flush its dynamic cache. |
/admin?op=exit | Stops a running MDEX Engine. |
/admin?op=restart | Restarts the MDEX Engine. |
/admin?op=audit | Returns the MDEX Engine Auditing page. |
/admin?op=auditreset | Resets the MDEX Engine Auditing page. |
/admin?op=stats | Returns the MDEX Engine Statistics page. |
/admin?op=statsreset | Resets the MDEX Engine Statistics page. |
/admin?op=logroll | Forces a query log roll, with the side effect of remapping stdout. |
/admin?op=update | Applies any partial update files to the MDEX Engine. |
/admin?op=updateaspell | Rebuilds the aspell dictionary for spelling correction from the data corpus without stopping and restarting the MDEX Engine. |
/admin?op=updatehistory | Shows a list of the update files that the MDEX Engine has processed recently. |
/admin?op=reload-services | A Web services operation that reloads the application's main and library modules. |