Overview of .NET and Java integration

Today's financial desktop is made up an assortment of mission critical applications written in C# and Java. OpenFin's native language adapters for .NET and Java provide a path for seamless integrations with your existing applications and your new web applications.

With OpenFin, web apps and native apps can easily

  • Share data and context with one another across process boundaries to deliver powerful automated workflows
  • Embed web content inside a native application
  • Generate Notifications for a seamless and unified experience
  • Expose bespoke APIs from native applications to your OpenFin powered web apps

In addition to the above, our native language adapters can solve for much more. Depending on your use case, we suggest walking through these steps to identify how to scope your native integration.

Step 1 | Identify existing native widget/screen to migrate

To begin the migration, consider choosing a feature/widget/screen that;

  • Is self contained
  • Is well understood
  • Offers quick wins (simple but useful)
  • Has a reusable backend
  • Requires future development goals (aside from the migration)

Once you have your first migration candidate agreed by the relevant stakeholders we can move on to Step 2.

We recommend that Steps 2 and 3 below are done in parallel.

Step 2 | Build MVP

  • Create a simple web application representing some basic feature set of the intended widget/feature that you’re migrating.
  • Re-use any existing backend services that currently feed into your native application. Adapters may need to be built, but having one backend for both has obvious high potential to save effort in the future.
  • Consider adding a button to launch the new feature from the existing native application but put access to the button behind a security role or permission, granting access to only a handful of “friendly faces”.

Step 3 (optional) | Embed MVP Web App inside existing native app

  • Use the OpenFinEmbedded view to embed the new version of your application widget within the exisitng native application. Details to do this can be found in “Embed Web Content In a Native App” recipe.
  • If you choose to embed your new view in the native app, consider obscuring the new view behind a security role or permission, again, granting access to only a handful of “friendly faces”.

Step 4 | Release to UAT group

  • Release to engaged and enthusiastic stakeholders via a dedicated UAT environment.
  • This will not only help with feedback, it will also flush out any environmental issues with deployment such as firewall access, authentication etc…
  • Once the existing functionality has been migrated fully to the new, web based, version, you should consider removing or decommissioning the old functionality in the existing native application.
  • At this point it is recommended to add progressive enhancements to your new web application to take advantage of the wealth of API’s that OpenFin has on offer.
  • Notifications and inter-application-communication are 2 good places to start.

Step 5 | Progressively enhance new Web App

  • Once the web version of your application is fully operational, then it maybe be time to consider disabling the native feature.
  • Remember that now you’ve encapsulated this feature as a web component, it can be easily re-used in other Native applications throughout the organization. Simply drop it in with an EmbeddedView.