# Classical applications

Deploying a JMap application consists of preparing the application and putting it online so it can be accessed by users. You must select the desired options (application type, activated extensions, access controls, etc.) to customize the application according to your needs. To allow a user to open a deployed JMap application, simply give the user the application URL.

Deployed JMap applications are placed online in the web server integrated to JMap Server. They can also be copied manually to other web servers.

The deployment section displays a list of applications that have already been deployed.

## Creating a new deployment

To create a new application deployment, click on the **Create** button in the **Deployed applications** section. Some parameters will be common to all types of applications. The following tables describe these parameters.

<table data-header-hidden><thead><tr><th width="160.5"></th><th></th></tr></thead><tbody><tr><td><strong>Template</strong></td><td> </td></tr><tr><td>Application type</td><td>There are four types of JMap applications. Each type of application has different features that are adapted to different needs. Custom application templates can also be added; these can be variants of the types offered by default.<br><strong>JMap Pro applications</strong>: This type of JMap application offers advanced functionality. It requires more IT resources, and a Java Runtime Environment (JRE) must be installed (Java is no longer required if you use the new deployment mode with an installation program).<br><strong>JMap Web applications</strong>: This type of JMap application is lighter and you can run it from a web browser or a mobile web browser. It doesn’t offer as many advanced features as JMap Pro applications.<br><strong>WFS Service</strong>: This type of application is a vector data web service destined to provide data to third-party applications through the Web Feature Service standard protocol.<br><strong>WMS Service</strong>: This type of application is a web service for the production of map images. It is destined to provide maps to third-party applications using the Web Mapping Service standard protocol.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="159.5"></th><th></th></tr></thead><tbody><tr><td><strong>Identification</strong></td><td> </td></tr><tr><td>Name</td><td>Enter a name for the new deployed application. Names must be unique. The name can contain spaces and any other characters.</td></tr><tr><td>Type</td><td>Select the deployment type, either local or external.<br><strong>Local</strong>: The application service will be deployed directly in JMap Server.<br><strong>External</strong>: Select this option for applications that must be deployed on a web server that is external to JMap Server. The application service will not be deployed in JMap Server. Instead, a <em>.war</em> file will be created. This file must be copied onto the external web server. A Download button in the deployment section allows you to download the <em>.war</em> file.</td></tr><tr><td>Protocol</td><td>The protocol to be used for communication between the JMap application and JMap Server. Select https for secure communication. If the HTTPS protocol is not configured in JMap Server, this option is not available. For more information on using the HTTPS protocol, refer to the <a href="../security/using-https-with-jmap">Using HTTPS with JMap</a> section.</td></tr><tr><td>Application host</td><td>The host name or IP address that will be included in the URL of the deployed application. If your server has several IP addresses, specify the one that must be used. If you have selected the <strong>External</strong> deployment type, make sure you enter the name or address of the external web server where the application will be deployed.</td></tr><tr><td>Application port</td><td>The TCP/IP port used in the URL of the deployed application.</td></tr><tr><td>Relative path</td><td>The path used in the URL of the deployed application, taken from the name given to the application.</td></tr></tbody></table>

The following steps depend on the type of application you selected. Refer to the following sections: [JMap Pro Applications](https://docs.k2geospatial.com/en2/administrator/jmap-server-administrator-manual/jmap-server-applications/classical-applications/jmap-pro-applications), [JMap Web Applications](https://docs.k2geospatial.com/en2/administrator/jmap-server-administrator-manual/jmap-server-applications/classical-applications/jmap-web-applications) and [WFS and WMS Services](https://docs.k2geospatial.com/en2/administrator/jmap-server-administrator-manual/jmap-server-applications/classical-applications/wfs-and-wms-services).

## Managing Deployed Applications

Once you have deployed applications, you can perform certain management tasks on them from the **Deployed Applications** interface of the **Deployed** section.

### **Editing an existing application**

Editing an existing application allows you to go through all configuration sections again and change any options as needed. Double-click on the application’s name and select **Edit**.

### **Clone an existing application**

Select an application to duplicate it.

### **Updating applications**

Updating a deployed application means deploying it again, overwriting the existing version. This is equivalent to editing an existing application and keeping all the same options. Updating applications is useful when you install a new version of JMap to make sure your deployed application uses all the latest library versions. You do not need to update deployed applications when the data or the project changes.

### **Loading and unloading applications**

If you want to temporarily make a deployed application unavailable, you simply need to unload it by selecting it in the list and pressing **Unload**. When an application is unloaded, users can no longer start it using its URL. If you want to make it available again, simply press **Load** to reload it.

### **Downloading applications**

If an application’s type is **External**, you can download that application’s .*war* file in order to deploy it on another web server. Select the application and click on **Download**.

For more information on external applications, see [this section](#creating-a-new-deployment).

### **Deleting applications**

Deleting an existing deployed application deletes all files related to this application. There is no way to undelete an application (you need to redeploy it). Note that when deleting an application, none of your data or configurations (projects, layers, data sources, databases, etc.) are deleted nor affected in any way.

## Other fonctions

Click on this button ![img](https://2098443701-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcA9CuUnY5hTYroiPhD1w%2Fuploads%2Ft5X302jDB81NqsbQyky9%2Fclip0058.png?alt=media\&token=69415620-e93c-4645-aa34-dc7a6dad02d7) to access the following functions:

### **Permissions**

If you select a deployment, you can access the **Permissions** section of the application.

### **Download REST services**

The *service.war* file containing the JMap REST services is downloaded to your computer for deployment on another server.

### **Download report services**

The *report.war* file containing the report service is downloaded to your computer for deployment on another server.

### **Download securityRealm services**

The *securityRealm.war* file is downloaded to your computer. This file is used in single sign-on (SSO) by authentication servers ([OIDC](https://docs.k2geospatial.com/en2/administrator/jmap-server-administrator-manual/security/managing-users/openid-connect-oidc-user-manager), [SAML2](https://docs.k2geospatial.com/en2/administrator/jmap-server-administrator-manual/security/managing-users/saml2-user-manager)) to communicate with JMap.