|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// applications/application_life_cycle_management/odc-deploying-java-applications.adoc |
| 4 | + |
| 5 | +[id="odc-deploying-java-applications_{context}"] |
| 6 | += Upload JAR files for easy deployment of Java applications |
| 7 | + |
| 8 | +You can use the JAR files in the *Topology* view of the *Developer* perspective to deploy your Java applications. You can upload a JAR file using the following options: |
| 9 | + |
| 10 | +* Navigate to the *+Add* view of the *Developer* perspective, click the *Upload JAR file* tile through the *From Local Machine* option. Browse and select your JAR file, or drag and drop a JAR file to deploy your application. |
| 11 | + |
| 12 | +* Navigate to the *Topology* view and use the *Upload JAR file* option, or drag and drop a JAR file to deploy your application. |
| 13 | + |
| 14 | +* Navigate to the Context Menu in the *Topology* view and use the *Upload JAR file* option to upload your JAR file to deploy your application. |
| 15 | + |
| 16 | +Use the following instructions to upload a JAR file in the *Topology* view to deploy a Java application: |
| 17 | + |
| 18 | +.Procedure |
| 19 | + |
| 20 | +. In the *Topology* view, right-click anywhere in the *Topology* view to see the *Add to Project* menu. |
| 21 | + |
| 22 | +. Hover over the *Add to Project* menu to see the menu options, and then select the *Upload JAR file* option to see the *Upload JAR file* form . Alternatively, you can drag and drop the JAR file in the *Topology* view. |
| 23 | + |
| 24 | +. In the *JAR file* field, browse for the required JAR file on your local machine and upload it. Alternatively, you can drag and drop the JAR file on the field. A toast alert is displayed at the top right if an incompatible file type is dragged and dropped on the *Topology* view. A field error is displayed if an incompatible file type is dropped on the field in the upload form. |
| 25 | + |
| 26 | +. You can further specify optional Java commands to customize your deployed application. The Runtime Icon and Builder Image is selected by default. If a Builder Image is not auto-detected, select a Builder Image. If required, you can change the version using the *Builder Image Version* drop-down list. |
| 27 | + |
| 28 | +. In the optional *Application Name* field, enter a unique name for your application for the resource labelling. |
| 29 | + |
| 30 | +. In the *Name* field, enter a unique component name to name the associated resources. |
| 31 | + |
| 32 | +. In the *Resources* field, choose the resource type for your application. |
| 33 | + |
| 34 | +. In the *Advanced options*, click on *Create a Route to the Application* to configure a public URL for your deployed application. |
| 35 | + |
| 36 | +. Click *Create* to deploy the application. The user sees a toast notification notifying that the JAR file is being uploaded and takes a while. The toast notification also includes a link to view the build logs. |
| 37 | + |
| 38 | ++ |
| 39 | +[NOTE] |
| 40 | +==== |
| 41 | +If the user attempts to close the browser tab while the build is running, a web alert would be displayed asking the user if they actually want to leave the page. |
| 42 | +==== |
| 43 | + |
| 44 | +After the JAR file is uploaded and the application is deployed, you can see the deployment in the *Topology* view. |
0 commit comments