Co-Deploying Java Applications

Introduction

OpenFin’s Java Adapter embeds the OpenFin Runtime and RVM in the adapter’s .jar file. Download the necessary Java Adapter .jar file from our repository and include it in your build process along with your other Java assets. Once built, you can deploy your applications via the same methods as other Java applications.

Deploying an OpenFin Application with Java Adapter

In this section, we highlight how to deploy an OpenFin application that includes the Java Adapter as an appAssets.

📘

Note

This approach requires that you must launch your OpenFin application first.

Download and Host

Download the necessary Java Adapter .jar file from our repository and host it on your assets server.

Co-Deployment of Assets

Co-deployment of assets allows application developers to deploy external native apps and run them using launchExternalProcess. The OpenFin RVM downloads the zip files and extracts them to:

OpenFin\apps\appid\assets\alias\version

Example

"appAssets": [
     {
      "src": "http://server/hostedApp.zip",
      "alias": "my-app",
      "version": "3.2.50.71",
      "target": "start.bat",
      "args": "--flag=3"
     },
     {
      "src": "http://server/anotherApp.zip",
      "alias": "foo",
      "version": "0.0.0.72",
      "variables": { "abc" : "123", "def" : "456"}
     }
]

Example properties defined

Property

Definition

src

Zip file containing the external native app (should include dependencies such as DLLs, etc).

alias

Unique name for the app. This is used in launchExternalProcess.

version

Version of the package. RVM auto updates the package whenever the version is incremented.

target (optional)

Specified which file should be executed. If it’s not specified, the developer must specify it in the launchExternalProcess call.

args

Command line arguments to send to the app.

variables (optional)

Environment variables to set prior to launching the app.


Did this page help you?