INSTANT TEAM SESSIONS / BROWSER CLIENT BETA

Server & setup resources

Plan your evaluation of browser-based access to persistent Team Sessions rooms.

Documentation preview · server download not yet available

The browser client is running in a Sametime 11 development pilot. A public server package is not available here yet. Sametime 12 qualification is pending; the desktop plug-in's compatibility statement does not apply to this browser bridge.

Ask about beta evaluation →Explore product screenshots

THE CURRENT PILOT DESIGN

One browser experience. A connected server stack.

Live conversation, authenticated room access and persistent capture each have a clear role. The browser bridge is managed separately from the existing ITS server.

01 / CLIENTYour browser
Rooms, chat and unread previews over HTTPS.
02 / EDGEHTTPS gateway
One public origin; route bridge traffic and Domino web requests to their intended services.
03 / BROWSER SERVERRoom bridge
Qualified Java 8 and the native Sametime SDK maintain room sessions on behalf of signed-in users.
04 / SIGN-IN ONLYJava 21 helper
The installed HCL provider and protected signing source issue short-lived sign-in tokens.
05 / ACCESS POLICYDomino HTTP application
Authenticates users and provides authorized rooms, visibility and password checks over loopback HTTP.
06 / LIVE CHATSametime 11
Native room messaging and participant presence.
07 / PERSISTENCEExisting ITS archive
Captures chat and stores history in Domino, independently of the bridge.

Current pilot topology. The bridge and Domino HTTP must share a host: trusted backchannels use loopback port 80. Diagram lines summarize responsibilities, not every protocol exchange. Other service placement and runtime combinations require deployment review.

What runs where

Browser client: Room discovery, live chat, unread previews, search, user filters and display preferences. No applet or desktop plug-in is installed in the browser.
Browser server bridge: A separate server application serves the UI and maintains native Sametime sessions on behalf of authenticated users. It has its own configuration, logs and operational metrics.
Domino HTTP application: Authenticates the user and provides the authorized room catalog and entry flow. Hidden rooms are omitted; visible password-protected rooms require entry authorization.
ITS server & archive: The existing ITS server and archive logger remain responsible for persistent capture. The bridge retrieves available room history through the existing integration.

The selected HTTP room provider opens no Notes sessions or Notes threads in the bridge. Domino HTTP still performs authenticated database work inside Domino. Legacy Notes-native directory modes are outside this installation plan; the bridge does not replace the ITS archive server.

BEFORE INSTALLATION

Dependencies, with the boundaries made clear.

The two Java runtimes serve different purposes. The Java 21 helper does not replace the JVM used by the legacy native Sametime toolkit.

Current pilot dependencies · target-host qualification required
Component	Current requirement	Provisioning
Host & gateway	Windows; the bridge and Domino HTTP share the host. HTTPS ingress serves one public origin.	Existing environment
Bridge JVM	Qualified Java 8 runtime matching the native toolkit and library architecture.	Operator supplied
Native Sametime SDK	`CommRes.jar`, `STComm.jar`, `stcommsrvrtk.jar`, `stjavatk.jar`; matching native dependencies as required by the installation.	Licensed HCL installation
Sign-in helper	Java 21 plus the installed HCL JWT provider classes and their complete dependency set. Reviewed access to the existing protected signing source.	Licensed installation; assisted setup
Domino application	Authenticated room-catalog and identity/entry endpoints, correct database replica, ACL/Readers policy and signed run-as-web-user designs.	Separate controlled design deployment
Sametime & ITS archive	Current native pilot: Sametime 11. Existing ITS archive capture and history retrieval remain active.	Existing services
Bridge transport & service tools	Pinned Netty 4.2.19.Final libraries and WinSW 2.12.0 x64 are used by the current packaging candidate, with dependency hashes and notices.	Planned application package; not yet published

Installation planning

This is a preparation guide. The dependencies above describe the current pilot. Package-specific commands and a finalized supported-runtime matrix will accompany a released distribution.

Choose an isolated evaluation environment. Identify the Sametime service, Domino application database, ITS archive service and test users. Confirm room visibility, password rules and archive operation before adding the browser bridge.
Qualify the server runtime. The native bridge uses a qualified Java 8 runtime and licensed Sametime toolkit; a separately configured Java 21 helper uses the installed HCL token provider. The HTTP room provider does not initialize the Notes API in the bridge. Confirm supported runtime versions and matching native-library architecture with support.
Plan HTTPS and service access. Choose an exact public HTTPS origin, a restricted service identity and a reviewed same-host gateway topology. The trusted Domino backchannels currently require loopback HTTP on port 80. Keep the bridge backend protected; expose only the intended browser endpoint.
Separate releases from configuration. Keep versioned application files distinct from protected configuration, credentials, service definitions and rotating logs. Retain the previous release and configuration for rollback.
Coordinate the Domino HTTP integration. The shared catalog and password-entry endpoints must be installed and verified for the selected database. Database design updates need their own controlled deployment and backup; installing the bridge alone does not supply them.
Complete preflight before opening access. Verify package checksums when supplied, service identity, certificate trust, connectivity, room authorization and archive retrieval. Expand access after evaluation checks pass.

Start with a neutral configuration.

The annotated template documents the actual setting names used by the bridge. It contains reserved hostnames, an all-zero replica marker and REPLACE_ME paths. It is a planning reference and cannot establish a working installation unchanged.

Download annotated configuration template ↓

See the core HTTP room-access settings

transport.mode=sametime
http.proxyEnabled=true
http.publicOrigin=https://chat.example.invalid
directory.provider=http
domino.database=team-sessions.nsf
domino.expectedReplicaId=0000000000000000
directory.http.url=http://127.0.0.1/team-sessions.nsf/ITS2026Rooms
domino.handoff.enabled=true
domino.handoff.identityUrl=http://127.0.0.1/team-sessions.nsf/ITS2026BrowserRoomAccess
domino.handoff.loginPath=/team-sessions.nsf/xpLandingMain.xsp

Configuration areas

Use the version-matched configuration examples supplied with the beta package. Keep passwords, IDs and tokens out of source control, command lines, URLs and diagnostic screenshots.

Public origin & gateway: Set the exact HTTPS browser origin, gateway routing, private backend binding and cookie/CSRF protection. The same-host pilot uses a loopback bridge backend behind its HTTPS gateway.
Sametime connection: Configure the community host and port, qualified SDK libraries, native-session admission limits, request timeouts and orderly session cleanup.
Domino HTTP access: Configure the trusted application URL and database/replica identity. Bind authorization to the signed-in user and keep refreshes bounded. Never use a privileged all-room list as a fallback.
Sign-in helper: Configure the Java 21 executable and installed HCL provider classpath separately from the native bridge JVM. Review service-identity access to the existing protected signing source.
Archive integration: Identify the existing ITS archive service and expected archive senders. Verify that history is captured and returned after a fresh sign-in.
Operations & access: Restrict Admin access. Configure log rotation, resource sampling, queue limits, session expiry and recovery monitoring; size these from measured evaluation results.

Evaluate the complete system

Sign in as ordinary users with different permissions. Compare both room lists, check hidden-room exclusion, and test correct, wrong and cancelled room passwords.
Join, send and receive, leave and re-enter. Check rosters, unread previews, search, user filters and display preferences.
Confirm new messages appear in the existing ITS archive, then reload them from a fresh session. Sending acceptance alone is not proof of archival.
Run load generators on client machines while the bridge, Sametime, Domino HTTP and ITS archiving remain active. Record user and room counts, delivered messages, archive verification, latency, errors and recovery.
Capture host CPU and process CPU separately, process working/private memory, Java heap use and allocation/GC, thread counts, queue depth and admission rejections. Compare equivalent loads and post-test recovery rather than a single heap snapshot.

Beta package & documentation

Server application download: not yet available. The server code and package remain under development; documentation here describes what is known today. This area is reserved for the versioned bridge package, checksums, release notes, supported runtime matrix and version-specific installation and configuration instructions.

The browser bridge is separate from the existing ITS server JAR and desktop plug-in. Their downloads remain on the main downloads page.

Contact support about deployment prerequisites or request a demonstration.