Sh Cache Microservice configuration

The Sh Cache Microservice resource adaptor has configuration properties related to:

  1. The Sh Cache Microservice to connect to — hosts and ports

The Sh Cache Microservice instance to connect to

These configuration options define the host the resource adaptor entity should connect to …​

Name Type Default Description

proxy.enabled

Boolean

False

Whether to use a proxy server. When using a proxy server, all connections are routed through the proxy server. The request URL for messages, as determined by the server URL below, is not affected by this setting.

proxy.host

String

localhost

The hostname of the proxy server.

proxy.port

Integer

4140

The port of the proxy server.

serverURL

String

http://localhost:8088/shcache/v1

The URL for the Sh Cache Microservice.

http.ioThreads

Integer

2

The number of threads to use for processing HTTP requests and responses.

http.connectTimeout

Integer

5s

The connect timeout in seconds.

http.idleTimeout

Integer

0s

The idle timeout in seconds. 0 means no timeout.

http.requestTimeout

Integer

5s

The request timeout in seconds.

http.keepAlive

Boolean

True

Whether to use HTTP keep-alive.

http.keepAliveTimeout

Integer

60s

HTTP keep-alive timeout in seconds.

http.maxPoolSize

Integer

5

HTTP connection pool size. The pool size per thread is this number divided by http.ioThreads, rounded up. Therefore the actual max pool size could be slightly bigger than this configured value.

http.notificationURL

String

http://localhost:8089

The URL that notifications from Sh Cache Microservice will be sent to. This hostname must be able to be resolved by ShCM hosts.

http.notificationPort

Integer

8089

Port to listen on for notifications.

http.notificationPortOffsetEnabled

Boolean

false

Required when running multiple cluster nodes on the same host. If true, the RA will automatically add an offset to the notification port number so that each ShCM RA instance gets a different port number.

http.notificationPortOffsetBase

Integer

101

Required when running multiple cluster nodes on the same host. If http.notificationPortOffsetEnabled is enabled, the ShCM RA’s port will be calculated as Port + (NodeID - PortOffset). Typically the PortOffset value used is the lowest NodeID in the cluster. So if http.notificationPort is 8089, the lowest NodeID is 101, this value is configured to 101, and the cluster has nodes 101, 102 and 103, the SIP ports used will be 8089, 8090 and 8091 respectively.

http.notificationBindAddresses

String

""

Specify notification server bind addresses for each node in the cluster. A comma-separated list of {node}host:port elements, for example "{101}10.0.0.1:8100,{102}10.0.0.2:8100". Overrides the http.notificationPort property. If undefined then the server binds to all interfaces on http.notificationPort.

subscriptionExpiryTime

Integer

3600

Subscription expiry time in seconds.

notificationServerEnabled

Boolean

true

Enable the notification server to receive HTTP notifications for UE Reachability For IP

netty.logging.enabled

Boolean

false

Enables logging in netty used by vert.x. For debugging purposes only, don’t use in production!
Previous page