+

Search Tips   |   Advanced Search

Deploy a project WAR file manually.

The procedure to manually deploy the app to an application server depends on the type of application server being configured, as detailed here. Depending on the version of the product that was used to build the project WAR file and the version of MobileFirst Server, we might need to migrate the WAR file first.

When the version of MPF produces a WAR file that is not compatible with the version of MobileFirst Server, we must migrate the project WAR file to the current MobileFirst Server version to ensure a successful manual deployment. All fix packs of a product version are compatible in that sense, and so you do not need to migrate associated project WAR files. For example, if you build a project WAR file using MobileFirst Studio v6.0.0 and want to deploy it manually to MobileFirst Server v6.0.0.1, you do not need to migrate the WAR file. WAR file migration is necessary if MobileFirst Studio and MobileFirst Server are of different versions. For example, if you build a project WAR file using MobileFirst Studio v6.0.0 and want to deploy it to MobileFirst Server v6.1.0, we must migrate the WAR file before you deploy it manually. Project WAR files need to be migrated because they contain information specific to the MobileFirst Server version. The migration updates the version-specific information in the WAR file, thus making it suitable to run on the new version of MobileFirst Server.

Only WAR files produced by MobileFirst Studio from V5.0.6 and later can be migrated: earlier versions are not supported.

These manual configuration instructions assume that you are familiar with the application server.

Use the Ant task to deploy the project WAR file and configure the application server is more reliable than installing and configuring manually, and should be used whenever possible.


Parent topic: Deploy the project WAR file manually