Namespace jabberwerx.cisco.cupha
All constants, functions and classes required for Cisco Unified Presence High Availability CAXL. CUP HA CAXL 8.6.1 is fully implemented within this namespace. Several CAXL classes and configuration options are overriden to provide functionality.
Cisco Unified Presence High Availability
See CUP CAXL 8.x Integration Guide for detailed information on CUP HA deployment and configuration. It is highly recommended CUP HA CAXL developers carefully study the integration guide. All HA functionality and protocols are defined therein. CUP HA CAXL supports the Cisco Unified Presence multi-node/multi-cluster deployment model. This support includes high-availability failover protection provided by an enabled dual-node deployment within a subcluster. CUP CAXL internally determines the best connection for a user using two specifically configured "Service Discovery (SD)" CUP servers. Service Discovery requires that CAXL is configured with two SD nodes: Primary SD Node: This is a Cisco Unified Presence server to which CAXL can connect to determine the home & backup node information for a given user. The primary node is the Cisco Unified Presence server used by CAXL under normal conditions. Secondary SD Node: This is an alternative Cisco Unified Presence server to which CAXL can connect to determine the home & backup node information for a given user. The secondary node is used by CAXL if for some reason the primary node is unavailable. In a high-availability deployment a user may have two associated Cisco Unified Presence nodes: home node: This is the Cisco Unified Presence server to which a user would normally connect. backup node: This is the Cisco Unified Presence server to which a user would connect if their home node is unavailable. CAXL internally determines both home & backup nodes from Service Discovery.Configuration
See CUP CAXL 8.x Integration Guide for detailed description of CUP HA configuration options. For complete API compatablility with core CAXL, CUP HA CAXL leverages the existing httpBindingURL configuration option. In addition to the HA discovery options users may specify a connection timeout. CUP HA CAXL adds the following configuration options:| Name | Default | Description |
|---|---|---|
| serviceDiscoveryEnabled | false | |
| httpBindingURL_secondary | /httpbinding | Description goes here |
| bindRetryCountdown | 30 | Number of seconds timeout between sending a bind resource request and receiving the response from server. If no response from server after this timeout period, a reconnect operation will be processed. If {bindRetryCountdown} is less than or equal 0, the default value jabberwerx.cisco.cupha.DEFAULT_CONNECTION_TIMEOUT will be used. |
| Constructor Attributes | Constructor Name and Description |
|---|---|
| Field Attributes | Field Name and Description |
|---|---|
| <static> |
jabberwerx.cisco.cupha.DNS_HOST_PATTERN
DNS Hostname validation regex patern.
|
| <static> |
jabberwerx.cisco.cupha.IPv4_PATTERN
IPv4 validation regex patern.
|
Field Detail
<static>
jabberwerx.cisco.cupha.DNS_HOST_PATTERN
DNS Hostname validation regex patern.
public domain via stackoverflow:
http://stackoverflow.com/questions/106179/regular-expression-to-match-hostname-or-ip-address
<static>
jabberwerx.cisco.cupha.IPv4_PATTERN
IPv4 validation regex patern.
public domain via stackoverflow:
http://stackoverflow.com/questions/106179/regular-expression-to-match-hostname-or-ip-address