Fusion Web App Deployment

UI deployment overview
Publishing a search interface to Fusion Server
Migrating a search interface to other Fusion hosts
- Download or build a .war file
  - Downloading a .war file
  - Building a .war file
- Upload the .war file
  - Uploading with the Fusion UI
  - Uploading with the REST API
Running a dedicated node for a search interface

To deploy App Studio in Fusion Server, you develop your search interface, then publish it to Fusion’s Webapps service. This deployment type leverages your existing production environment, requiring no dedicated nodes for App Studio. However, you may need to deploy additional Fusion nodes if you anticipate significant traffic to your search interface.

UI deployment overview

Fusion Web app deployment

Here’s an overview of the steps:

Develop your search interface.
Publish your UI to Fusion Server using the instructions below.

Your Web app then becomes accessible at http://localhost:8764/webapps/<project-name>.

Publishing a search interface to Fusion Server

These steps publish your search interface to a Fusion instance (and its cluster) where the App Studio project already exists.

In the Fusion workspace, navigate to App Studio and select your search interface.

The configuration panel appears.
Next to Publish Status, click the toggle:
Click Save.

The interface is only published after you click Save, which also enables the View Published UI button.
Click View Published UI to launch a new window where you can view the interface as an end user.

Your published interface is available at http://localhost:8764/webapps/<project-name>.

Migrating a search interface to other Fusion hosts

If you’ve published your search interface on one Fusion Host in a cluster, then it is published throughout the cluster.

There are two ways to migrate a search interface to another Fusion cluster:

Export and import the Fusion app Download and upload the .war file

Export and import the Fusion app	Download and upload the .war file
This migrates all objects in the Fusion app, such as datasources, query profiles, schedules, and so on, in addition to the search interface. The search interface will be editable on the target hosts. For instructions, see Working With Apps in Fusion Server’s Getting Started guide.	This migrates only the search interface. The search interface will not be editable on the target hosts. If you are uploading the file into a Fusion app other than the one in which it was created, the new Fusion app must include a query profile and data fields whose names are identical to the ones already configured in the search interface. For instructions on download or building a `.war` file and uploading it to Fusion, see below.

This migrates all objects in the Fusion app, such as datasources, query profiles, schedules, and so on, in addition to the search interface.

The search interface will be editable on the target hosts.

For instructions, see Working With Apps in Fusion Server’s Getting Started guide.

This migrates only the search interface. The search interface will not be editable on the target hosts.

If you are uploading the file into a Fusion app other than the one in which it was created, the new Fusion app must include a query profile and data fields whose names are identical to the ones already configured in the search interface.

For instructions on download or building a .war file and uploading it to Fusion, see below.

Download or build a `.war` file

You distribute a search interface as a .war file.

You can download a .war file from the Fusion UI or create one from a downloaded project.

Downloading a .war file

In the Fusion workspace, navigate to App Studio and select your search interface.

The configuration panel appears.
Click Download war:

Building a .war file

A downloaded project comes with an app-studio script that creates a .war file.

In a shell window, switch to your project directory:
```
cd /path/to/Project_Directory
```
Run the following command:
```
./app-studio package
```

The script creates the following files in the dist directory of your project:

search-app-4.1.x.jar

This is a self-executing application file.
search-app-project.zip

Use this file to share your project with other search interface developers.
search-app.war

You can upload this file to Fusion to deploy it. See the Deployment Guide.

Upload the .war file

You can upload the .war file through the Fusion UI or the REST API.

Uploading with the Fusion UI

You can upload your project (as a .war file) in the App Studio configuration panel.

Note	If you are uploading the file into a Fusion app other than the one in which it was created, the new Fusion app must include a query profile and data fields whose names are identical to the ones already configured in the search interface.

From the App Studio menu, select your project:

The project configuration panel appears.
Click Upload.

Fusion prompts you to confirm that you want to upload a project that will delete the existing one.
Click Yes, continue.
Navigate to your .war file and select it.

Once the upload is complete, you can edit or publish the uploaded project.

Uploading with the REST API

Use the webapps/{id}/war endpoint of the Webapps API to upload a .war file, as in this example:

curl -u admin:password123 -X PUT http://localhost:8764/api/webapps/Movie_Search/war -F 'file=@movies.war'

Running a dedicated node for a search interface

When deploying Fusion nodes dedicated to serving one or more search interfaces, only the following Fusion services need to run:

agent
api
log-shipper
webapps

When starting a dedicated node, you can minimize the number of running services by starting it like this:

fusion/4.1.x/bin/agent start
fusion/4.1.x/bin/api start
fusion/4.1.x/bin/log-shipping start
fusion/4.1.x/bin/webapps start