Getting started for Node.js

Javonet allows you to reference and use modules or packages written in (Java/Kotlin/Groovy/Clojure, C#/VB.NET, Ruby, Perl, Python) like they were created in your technology.

To use the guides both interacting technologies needs to be selected from left-side dropdown lists. Developer's technology is named "I code in" and technology to be called is named "I want to use".

Prerequisites

To call library/package/module from another technology, corresponding runtime has to be installed. See Prerequisites for details about installing called technology runtime.
Javonet is available as javonet-nodejs-sdk package which can be downloaded from NPM public repository or from My Javonet Portal.
Package can be installed with CLI:

npm i javonet-nodejs-sdk

Get activation key

Use register or log in page to get license key, which is necessary to activate Javonet.

First sample application

Javonet needs to be imported as any other dependency.

const { Javonet } = require('javonet-nodejs-sdk/lib/sdk/Javonet')

Javonet needs to be activated first. Activation must be called only once at the start-up of an application. More about activation in Activating Javonet section.

Javonet.activate("your-license-key")

As a second step, Runtime Context of the called technology needs to be created. RuntimeContext refers to single instance of the called runtime. Once it is created it is used to interact with called runtime.

let pythonRuntime = Javonet.inMemory().python()

The simplest use case is to get from target technology a type from a built-in library:

let pythonType = pythonRuntime.getType('math').execute()

And then get static field from the type:

let response = pythonType.getStaticField("pi").execute()

The returned value needs to be cast to calling technology type and can be used as any other variable:

let result = response.getValue()
console.log(result)

To sum up, the whole code snippet looks like:

// <Import>
const { Javonet } = require('javonet-nodejs-sdk/lib/sdk/Javonet')
// </Import>

// <Activation>
Javonet.activate("your-license-key")
// </Activation>

// <RuntimeContextCreation>
let pythonRuntime = Javonet.inMemory().python()
// </RuntimeContextCreation>

// <GetType>
let pythonType = pythonRuntime.getType('math').execute()
// </GetType>

// <GetStaticField>
let response = pythonType.getStaticField("pi").execute()
// </GetStaticField>

// <GetValue>
let result = response.getValue()
console.log(result)
// </GetValue>

The same operation can be performed remotely by just changing the new Runtime Context invocation from in memory to tcp that will create and interact with your .NET DLL objects on any remote node, container or service that hosts Javonet Code Gateway. This way you can preserve the same logic in your application and instantly switch between monolithic and microservices architecture without the need to implement the integration layer based on web services or other remote invocation methods.

Read more about use cases and software architecture scenarios where Javonet runtime bridging technology can support your development process.

Additional references