-
MathType
-
WirisQuizzes
-
Nubric
-
CalcMe
-
MathPlayer
-
Store FAQ
-
MathFlow
-
BF FAQ
-
Miscellaneous
-
Wiris Integrations
Configure frontend service endpoints
Reading time: 2minMathType frontend integrations communicate with MathType Integration Services through a configuration endpoint. By default, frontend integrations use the WIRIS-hosted Integration Services. If you deploy your own Integration Services, you must update the frontend configuration so that requests are sent to your deployment instead.
After completing this guide, your frontend integration will communicate with the correct MathType integration services deployment.
Before you begin
Requirements
Make sure you have:
- A working frontend integration.
- Access to the frontend configuration.
- A running MathType integration services deployment if using self-hosted services.
Applies to
All MathType frontend integrations
Steps
Choose your Integration Services deployment
MathType frontend integrations can communicate with either:
- WIRIS-hosted Integration Services, which require no additional configuration.
- Self-hosted Integration Services, deployed on your own infrastructure.
If you're using the WIRIS-hosted services, you can skip this guide. If you're using a self-hosted deployment, continue with the following steps.
Configure the service endpoint
Configure the Integration Services endpoint in your frontend integration. Most integrations use a configuration similar to:
mathTypeParameters: {
serviceProviderProperties: {
URI: 'http://localhost:8080/pluginwiris_engine/app/configurationjs',
server: 'java'
}
}The URI property must point to the configuration endpoint exposed by your MathType Integration Services deployment. The server property identifies the Integration Services implementation. Use the values corresponding to your deployment:
| Deployment | URI | server |
|---|---|---|
| PHP | http://example.com/integration/configurationjs.php |
php |
| Java | http://example.com/pluginwiris_engine/app/configurationjs |
java |
See API services for the endpoint URLs available on your platform.
Verify the configuration
Verify that the configured configuration endpoint is accessible and returns a valid configuration. If the endpoint cannot be reached or does not return valid configuration data:
- Verify that Integration Services are running.
- Verify that the configured
URIis correct. - Verify that your frontend can reach the server.
Verify it worked
Open your editor and perform a complete editing cycle:
- Insert a formula.
- Save the content.
- Reload the page.
- Edit the same formula again.
If the configuration is correct:
- The editor opens successfully.
- Formulas are rendered correctly.
- Requests are sent to your configured Integration Services deployment.
You can use your browser's developer tools to verify that requests are being sent to your own server instead of the WIRIS-hosted services.
Options and variations
Use MathType cloud services
By default, frontend integrations communicate with the WIRIS cloud services. This option requires no server-side deployment and is suitable for evaluation environments or deployments that do not require self-hosted Integration Services.
Use self-hosted PHP Integration Services
If you deploy Integration Services with PHP, configure the frontend endpoints to point to your PHP deployment.
Use self-hosted Java Integration Services
If you deploy Integration Services with Java, configure the frontend endpoints to point to your Java deployment.
Use Docker deployments
When Integration Services run in Docker containers, configure the frontend endpoints to use the published container URLs or the reverse proxy that exposes the services. Verify that the configured endpoints are reachable from the browser.
Common issues
The editor does not open
Verify that:
- the
URIpoints to the correctconfigurationjsendpoint. - Integration Services are running.
- The frontend can reach the configured server.
The endpoint returns an error
Verify that:
- Integration Services have been deployed correctly.
- The web server is exposing the
configurationjsendpoint. - The deployment URL matches the frontend configuration.
Requests are still sent to WIRIS-hosted services
Verify that:
- The frontend configuration has been updated.
- Browser caches have been cleared if necessary.
- All frontend components use the same configuration.