Unblu 4.1

Unblu Server Network Ports

1. Introduction

This document explains the network ports used by unblu server's when used in on premise integration setups.

2. Network Port Configurations

When installing and running an unblu package (SSO, staticusers, EDBS) on an application server, it may be necessary to configure the various ports used by unblu itself or its components (cassandra, zookeeper). The following sections list these address and ports used by unblu. The proper configuration of server and client parts is explained. Port configuration for the application server itself are not covered here.

2.1. Zookeeper configuration

2.1.1. Zookeeper Server

com.unblu.zookeeper.server.hostname=AAAA (default: localhost)
com.unblu.zookeeper.server.clientPort=xxxx (default: 2181)

2.1.2. Zookeeper Client

com.unblu.zookeeper.client.hosts=AAAA:xxxx (default: 2181)

NOTE: If you change AAAA or xxxx for either server or client part, you must configure the other part correspondingly! Changing AAAA in the zookeeper server part to unbluserver.intra thus must include unbluserver.intra in the client.hosts configuration!

2.2. Cassandra configuration

2.2.1. Cassandra Server

com.unblu.cassandra.server.rpcListenAddress=BBBB (default: localhost)
com.unblu.cassandra.server.rpcPort=yyyy (default: 9160)


Other cassandra server ports (must differ, if multiple unblu instances are started on the same physical machine, but don't have to be considered for the client settings below):

com.unblu.cassandra.server.nodeListenAddress=CCCC (default: localhost)
com.unblu.cassandra.server.storagePort=uuuu (default: 7000)
com.unblu.cassandra.server.sslStoragePort=vvvv (default: 7001)
com.unblu.cassandra.server.nativeTransportPort=wwww (default: 9042) -> available as of 3.4.2 (as of 3.3 included in the product but not configurable)


2.2.2. Cassandra Client

NOTE: If you change BBBB, or yyyy for either server or client part, you must configure the other part correspondingly!