-
MathType
-
WirisQuizzes
-
Nubric
-
CalcMe
-
MathPlayer
-
Store FAQ
-
MathFlow
-
BF FAQ
-
Miscellaneous
-
Wiris Integrations
Configure MathType Integration Services
Reading time: 2minMathType Integration Services are configured through a deployment-specific configuration file. This guide explains where to find it, how to modify it, and how to verify your changes. Most deployments work with the default configuration. You only need to modify the configuration when adapting MathType to your infrastructure or application requirements.
After completing this guide, you'll know how to:
- Locate the Integration Services configuration file.
- Understand how configuration is applied.
- Modify the server configuration safely.
- Verify that your changes have been applied.
Before you begin
Requirements
Make sure you have:
- A working MathType Integration Services deployment.
- Access to the MathType Integration Services configuration file.
- Permission to restart your web server or application server if required.
Applies to
Self-hosted MathType Integration Services
Steps
Locate the configuration file
MathType Integration Services store their configuration in a deployment-specific configuration file.
| Deployment | Configuration file |
|---|---|
| PHP | <integration>/configuration.ini |
| Java | <webapp>/WEB-INF/configuration.ini |
| .NET | Web.config |
| Docker | A mounted configuration.ini file |
If the file does not exist, copy the provided configuration.ini.dist file and rename it to configuration.ini.
Understand the configuration format
PHP, Java, and Docker deployments use an INI-style configuration file. Lines beginning with # are treated as comments and ignored by Integration Services. Each setting consists of a key-value pair:
parameter = valueFor .NET deployments, the configuration is stored in the standard Web.config file.
Understand configuration precedence
The Integration Services configuration file defines the default behaviour for every frontend integration connected to the same deployment.
Some settings can also be configured by the frontend integration or by editor-specific parameters. When both server-side and frontend configuration are available, the frontend configuration takes precedence for that integration, while the Integration Services configuration remains the global default.
This allows multiple integrations to share the same Integration Services deployment while applying different frontend settings when needed.
Edit the configuration
Open the configuration file and modify the parameters required for your deployment. Depending on what you want to configure, continue with one of the following guides:
- Configure frontend service endpoints.
- Configure rendering output.
- Configure formula storage and cache.
- Configure proxy and network settings.
- Configure cross-domain requests.
For a complete description of every supported parameter, see MathType Integration Services parameters.
Apply the changes
Save the configuration file. Depending on your deployment, configuration changes may require restarting the service.
| Deployment | Action |
|---|---|
| PHP | Changes are typically applied immediately. |
| Java | Restart the application server. |
| Docker | Restart the container if the configuration file is mounted during startup. |
| .NET | Restart the web application if required by your hosting environment. |
Verify the configuration
Verify that the configuration endpoint returns the expected configuration.
See API services for the endpoint URLs available on your platform.
Verify it worked
If you modified rendering, storage, networking, or other processing options, perform a complete integration test:
- Open your HTML editor.
- Insert a formula.
- Save the content.
- Reload the page.
- Reopen the formula for editing.
- Verify that the expected behaviour is applied.
Common issues
Configuration changes are not applied
Verify that:
- You edited the correct configuration file for your deployment.
- The configuration file contains valid syntax.
- The service has been restarted if required by your deployment.
The configuration file cannot be found
Verify that:
- You're looking in the correct location for your deployment.
- The
configuration.inifile has been created fromconfiguration.ini.dist, if required. - Your deployment was installed correctly.