Instant Server

iKnowBase comes with client and server side support for creating applications with real time asynchronous messaging support. The Instant server is implemented as a java web application and is typically installed as /ikbInstant.

See the Development Guide#Using Instant for concept and examples.

Installation

The Instant Server is installed the same way as all other iKnowBase web applications, but make sure you also configure the SecureTokenEngine InstallationGuide#SecureTokenEngine to enable web client single sign on between ikbViewer and ikbInstant. An alternative without single sign on between ikbViewer and ikbInstant is to use explicit login – see Authenticating with direct application container authentication .

Special requirements

The connected web-clients will be “always connected” using asycnchronous HTTP transport mechanisms and will, compared to traditional HTTP clients, need infrastructure with support for non-blocking I/O or a sufficient high number of supported concurrent connections. One Instant client subscription means one network connection. ikbInstant may be deployed on an application server separate from where the other iKnowBase applications are deployed, as long as it’s connected to the same iKnowBase database repository.

If Cross Origin Resource Sharing (CORS) is in use, the CORS address MUST use the same protocol as the webpage containing the JavaScript client. If the web page uses HTTPS, then the CORS address must also be HTTPS.

The Instant Server

Enable or disable the Instant Server

Disable the Instant server by stopping the Web application.

Configuring the Instant Server

See the Installation Guide#Configuring the ikbInstant application for configuration options.

Testing and troubleshooting

For developers, the console available at /ikbInstant/ikb$console provides