Deploy MathType services with .NET

Use this guide when you want to deploy MathType Services on your own .NET infrastructure instead of using the WIRIS-hosted services. This deployment model is suitable for organizations that require self-hosted services because of security, compliance, network isolation, or infrastructure requirements.

After completing this guide, you will have a self-hosted .NET deployment that includes:

• MathType Editor Services.
• MathType Hand Services.

These services will be available for use by your MathType Integration Services or by applications that communicate directly with MathType Services.

Before you begin

Requirements

Make sure you have:

• Access to a Windows server with IIS.
• IIS Application Development Features enabled, including:
  • ASP.NET 4.x
  • .NET Extensibility 4.x
  • ISAPI Extensions
  • ISAPI Filters
• The licensed MathType Services package for .NET.
• A valid MathType server license.
• Basic understanding of the MathType integrations architecture.

Applies to

Self-hosted MathType Services · .NET · IIS

Steps

Extract the deployment packages

Extract both deployment packages into your IIS web root. For example:

C:\inetpub\wwwroot\WIRISeditor
C:\inetpub\wwwroot\hand

Configure IIS applications

Create an IIS Application for each extracted package. For example:

Configure the product keys

Configure the product key for each service.

Editor Services

Use the Web.config.4.0 file provided with the package as the application Web.config, then configure:

<add key="com.wiris.editor.license.product.key" value="YOUR_PRODUCT_KEY"/>

Hand Services

Configure the product key in:

Web.config

using:

<add key="com.wiris.hand.license.product.key" value="YOUR_PRODUCT_KEY"/>

Restart IIS after updating the configuration.

Verify the deployment

Verify Editor Services

Open the Editor Services render endpoint:

http://<your-domain>/<editor-app-path>/editorservice.aspx/render?mml=<mi>x</mi>

A successful deployment returns the rendered formula. If the request returns an error, restart or recycle the IIS application pool and review the application logs.

Verify Hand Services

Open the Hand Services application URL:

http://<your-domain>/<hand-app-path>

Use the diagnosis or test page included in the application to verify that handwriting recognition is working correctly.

Migration considerations

If you are migrating an existing deployment:

• Copy the configuration.ini file (or equivalent configuration).
• Preserve the formula storage directory if your deployment uses image save mode.
• The cache directory does not need to be migrated because it is regenerated automatically.
• Verify that the migrated storage directories remain writable by the web server.

Verify it worked

A successful deployment should meet all of the following conditions:

• The IIS applications load without server errors.
• Product keys are accepted.
• Editor Services can render a simple formula.
• Hand Services test or diagnosis page loads correctly.
• Integration Services can connect to the deployed MathType Services.

Common issues

Requests to editorservice.aspx return HTTP 404

Verify that:

• IIS Application Development Features are enabled.
• ASP.NET 4.x is installed.
• The deployment has been configured as an IIS Application.

Formula rendering fails with request validation errors

Verify that Editor Services are using the Web.config.4.0 configuration file.

Hand Services do not load

Verify that:

• The application is deployed using the /hand application path (or the corresponding application path configured by your deployment).
• The Hand Services product key is configured correctly.
• The IIS application has been restarted after the configuration update.

Related articles

• MathType integrations architecture.
• MathType integrations deployment models.
• Test Integration Services.
• Configure MathType Integration Services.