You are here: Administrator's Guide > Optimizing FME Server > Moving the Web Applications Server to Another Machine

Moving the Web Applications Server to Another Machine

To improve performance and free up resources, you may wish to move the web applications server, which runs the FME Server Web Services, to another machine. This move requires the following steps:

  1. Install a web applications server on the new host machine (optional)
  2. Install the FME Server Web Services on the new host
  3. Update services URLs
  4. Configure CORS filters (optional)

Install a web applications server on the new host machine (optional)

To run the FME Server Web Services, you can use the Apache Tomcat web application server that is automatically provided when you install the services. In this case, skip this step and proceed to the next step.

Alternatively, you can install and use your own web application server for running the FME Server Web Services. Supported web applications servers include Apache Tomcat and Oracle WebLogic.

You must know the port number on which your web application server receives incoming requests and the path to the directory where your web application server stores web application .war files. (This directory is sometimes called webapps.)

Install the FME Server Web Services on the new host

On the new web applications server host, follow the instructions under Install the FME Server Web Services, for either Windows or Linux.

Update services URLs

On the machine hosting the FME Server core:

  1. Open the fmeServerConfig.txt file, located at <FMEServerDir>/Server.

    2. Locate the FME_SERVER_WEB_URL directive and update the URL value to the new web applications server host. For example:

    FME_SERVER_WEB_URL=http://MY_WEBAPP_HOST:80

  2. Log in to the FME Server Web User Interface (http://<host>/fmeserver).
    1. Click Services.
    2. Click on each service to open the Editing Service page.
    3. In the URL Pattern field, update the URL value to the new web applications server host, and click OK when done.

      4. For example, to update the Data Download Service:

      http://MY_WEBAPP_HOST/fmedatadownload

Configure CORS filters (optional)

If you are a web application developer, you may want to configure Cross-Origin Resource Sharing (CORS) filters, so that your application can bypass manual authentication when accessing the FME Server Web Services on another domain.