View Source

This section discusses how to enable remote connection to the server, using Java Remote Method Invocation (RMI).

h2. Connectivity options

To set up the connectivity options edit *<KIM_HOME>/config/install.properties* and set the following parameters:

{code}com.ontotext.kim.KIMConstants.RMI_HOST=localhost{code}

This specifies a visible/outer IP for the server. Replace {{localhost}} with the externally visible IP of the server. The client application needs to specify the configured host in its connection properties. When creating Java client applications, use this host as a parameter to the {{GetService.from (host, port)}}.

{code}com.ontotext.kim.KIMConstants.RMI_PORT=1099{code}

This is the port of the KIM Server RMI registry. The client application needs to specify this port in its connection properties. When creating Java client applications, use this port as a parameter to the {{GetService.from(host, port)}}. method.
See [the relevant Java documentation|http://java.sun.com/javase/6/docs/api/java/rmi/registry/LocateRegistry.html#createRegistry%28int%29] for details.

{note}Please update all clients configuration ([Web UI, Web Service API|Web Applications] , [Populater|Population]) if you change the above options. However, all local tools in */bin/tools*, except the Populater, use this configuration file and don't need to be configured separately.{note}

{code}com.ontotext.kim.KIMConstants.RMI_DATA_PORT=10990{code}

This is the port for Java RMI data connections. You don't need to specify this port in the client configuration. The client is automatically informed about it by the server registry. The KIM Server will be exported as a Java remote object on this port. See [the relevant Java documentation|http://java.sun.com/javase/6/docs/api/java/rmi/server/UnicastRemoteObject.html#exportObject%28java.rmi.Remote,%20int%29] for details.

When a firewall is present on the server or on the client machine, make sure that a two-way communication is allowed for both configured ports through firewall added exceptions.

{note}*On Windows XP Home* the Java RMI sub-system will not start, because some system environment variables are named incorrectly, i.e. {{SYSTEMROOT}} instead of {{$SystemRoot}}. If you want to work around the problem, you can find more information in [this java RMI bug report|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6256268] . (This applies only to Windows XP Home systems. There are no such issues in other versions or editions of Windows.)

You can find more information about connectivity problems on our [Frequently Asked Questions (FAQ)] page.{note}