The installation of the JSON-RPC module on the gateway server can be done automatically via script or manually.

Automated Installation

At runtime you can execute the module's install script through the Kit Manager, deployed in advance on the OSGi service platform. In general, the Kit Manager can be used from a text console to the runtime:

• from the local console,
• from a Telnet client,
• from a Remote Console, available as a standalone tool or as a part of the Web Admin Console.

To execute the install script, which in terms of the Kit Manager is to "install a kit", go to the kitman command group and use the install console command. The set of bundles for the JSON RPC module, that you can find in the bin/pscripts/webservices.jsonrpc.txt, is automatically available under the "Web Services JSON RPC Provider Bundles" kit name. To install it, pass the name or the ID of the kit as an argument to the install Kit Manager console command:

kitman.install "Web Services JSON RPC Provider Bundles"

The kitman command group is exported by the Kit Manager bundle – com.prosyst.mbs.util.kitman.jar, located in the /bundles directory.

You may also write your own install scripts for easier installation (and start) of a certain set of bundles. The required bundles for the JSON-RPC module are listed in the Manual Installation section below.

Manual Installation

You can install only the needed bundles from the module taking into account their dependencies.

Install and start the following bundles:

• fw.i -f -s com.prosyst.mbs.websockets.api.jar
• fw.i -f -s com.prosyst.mbs.websockets.core.jar
• fw.i -f -s com.prosyst.mbs.websockets.commands.jar

• fw.i -s -f com.prosyst.mbs.policyadmin.api.jar
• fw.i -s -f com.prosyst.mbs.policyadmin.commands.jar
• fw.i -s -f com.prosyst.mbs.policyadmin.identity.condition.jar
• fw.i -s -f com.prosyst.mbs.policyadmin.identity.useradmin.jar
• fw.i -s -f com.prosyst.mbs.policyadmin.policy.jar
• fw.i -s -f com.prosyst.mbs.policyadmin.core.jar
• fw.i -s -f com.prosyst.mbs.policyadmin.http.websockets.jar

• fw.i -f -s com.prosyst.mbs.websockets.wa.events.handler.jar
• fw.i -s -l -f com.prosyst.mbs.webservices.jsonrpc.api.jar
• fw.i -s -l -f com.prosyst.mbs.webservices.jsonrpc.core.jar
• fw.i -s -l -f com.prosyst.mbs.webservices.jsonrpc.handler.backup.jar
• fw.i -s -l -f com.prosyst.mbs.webservices.jsonrpc.handler.config.jar
• fw.i -s -l -f com.prosyst.mbs.webservices.jsonrpc.handler.event.jar
• fw.i -s -l -f com.prosyst.mbs.webservices.jsonrpc.handler.platformstate.jar
• fw.i -s -l -f com.prosyst.mbs.webservices.jsonrpc.handler.resourceprovider.jar
• fw.i -s -l -f com.prosyst.mbs.webservices.jsonrpc.handler.useradmin.jar
• fw.i -s -l -f com.prosyst.mbs.webservices.jsonrpc.invoker.policy.jar
• fw.i -s -l -f com.prosyst.mbs.webservices.jsonrpc.event.websocket.jar

To install and start a bundle execute the console command from the fw command group:

install -s <bundle_name>.jar

Target URL

In a Web application all JSON-RPC requests should be sent over Ajax, to the common URL that the distribution provider handles, that is, to:

• Plain HTTP connection:

  http://<osgi_host>/remote/json-rpc

• Secure HTTP connection over SSL or TLS:

  https://<osgi_host>/remote/json-rpc