FAS Installation Guide

YRP1-508, 3-4 Hikari-no-Oka Yokosuka-Shi, Kanagawa, 239-0847, Japan

tel.: + 81-(0) 46-821-3362 | cba-japan.com
This document contains confidential information that is proprietary to CBA. No part of its contents
may be used, disclosed or conveyed to any party, in any manner whatsoever, without prior
written permission from CBA.
© Copyright 2023 CBA.

All rights reserved.

Updated: 2022-06-22

Document version: 2.6

Java is a registered trademark of Oracle and/or its affiliates.

Linux is the registered trademark of Linis Torvalds, owner of the mark on a world-wide basis.

All other trademarks are property of their respective owners.

Contact Information

For technical support or other queries, contact CBA Support at:

[email protected]

For our worldwide corporate office address, see:

https://www.cba-japan.com (Japanese) https://www.cba-gbl.com (English)

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 2

Documentation in this Release
The following user documentation is provided in this release

Fusion Application Server Architecture Guide

Fusion Application Server Installation Guide

Fusion Application Server Administration Guide

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 3

Contents
Introduction
Prerequisites
Planning for Installation
Planning DNS and IP Addresses
Time Server
Quick Installation
Post Installation Tasks
Installing the Fusion Application Server
Users and Security
Application Users
Installing as a Non-Root User
Operating System User Groups
Installation Mode
Silent Installation
Installer Properties
Post Installation
Upgrade
Upgrade Rollback
Uninstalling FAS
Testing the Installation
Starting Fusion Application Server
Checking the State of Fusion Application Server
Using the Management Console
Starting and Stopping Individual Components
Glossary

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 4

Introduction
The CBA Fusion Application Server (FAS) is a Java EE 6 Application Server with additional
support for JSR 289. It incorporates JBoss AS 7 and Mobicents SIP Servlets, hardened with a
large number of improvements, and packaged in a tried and tested configuration to support the
suite of CBA Fusion products, such as Fusion Client SDK and Fusion Live Assist.

A platform is also provided for customers to develop their own applications using Fusion Client
SDK.

A cluster consists of one or more Fusion Application Server host machines.

Each FAS host in a cluster runs one or both of two main classes of server process:

Application Server (AS)

The AS is where the application runs. Each cluster must contain at least one AS node (a FAS
node running an AS server process), and one AS node in a cluster must be the master node,
from where all changes to the configuration for the cluster are performed.

Note: Ensure that multicast is enabled between master and slave nodes.

Load Balancer (LB)

The LB is the outward-facing component of a cluster. It receives SIP and HTTP messages and
sends them to the correct AS for processing.

New SIP and HTTP requests will be balanced across the ASs.

Each host or virtual machine can run no more than one of each type of server process; however,
you can run both an AS and an LB on a single FAS host.

For more details about each of these component types, see the Fusion Application Server
Architecture Guide.

Note: Since the term Application Server is ambiguous, and the term Load Balancer could refer to
an external load balancer, this documentation generally refers to the FAS server processes
detailed above as ASs and LBs.

Prerequisites

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 5

Before you start the installation of Fusion Application Server, ensure that you are running on a
compatible Operating System, and that you have a supported JDK installed. See the Fusion
Application Server Release Notes for details of the supported operating systems and JDK
versions.

It is important to read the Fusion Application Server Architecture Guide, which introduces the
core concepts, terminology, and the different options for FAS deployment topologies, before you
start installation; this guide assumes that you are already familiar with these options.

Planning for Installation

If you want to deploy large or complex installations of Fusion Application Server and other CBA
products, we recommend that you work with your CBA Sales or Support teams to help you plan
the deployment. Before installing, consider the following:

Topology

How many servers (or virtual machines) will you use for this 10.1.2.20 cluster?

Which processes will run on which hosts?

What do you require in terms of High Availability (HA)? What failures do you need the
cluster to survive?

DNS

If you are installing more than one LB, how will other entities route messages to these LBs?
Will they route directly to the individual hosts, will they use multiple trunks to access each
LB, or will they use DNS to resolve an address to any one of the LBs?

Can the products routing to this cluster use DNS?

Is it important to support call continuity in the event of an LB failure? If so, products routing
through the FAS must be able to route to an alternative LB if one becomes unresponsive; it
can do this either using multiple trunks or DNS.

If the cluster domain is an FQDN, it must use DNS, because the FQDN will appear in Record-
Route headers and must be resolvable for routing subsequent messages.

Traffic Segregation

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 6

 FAS allows you to separate management and service traffic, with each using a separate
network interface. You can set this up during installation, or configure it later.

Planning DNS and IP Addresses

During installation, the installer requests the following IP addresses or FQDNs:

Service Traffic IP Address

This is the IP address that the AS and LB server processes bind to for HTTP, HTTPS, SIP, and
SIPS traffic.

Management Traffic IP Address

This is the IP that the Management Traffic binds to. This is used by the CLI and Management
Console, and for communication between master and slave host controllers.

Cluster Address

This is the FQDN that the cluster as a whole is contactable on. This is the domain name that
external User Agents should use to address the HA cluster.

In many deployments where an LB and an AS are deployed on the same host, the IP address for
Service and Management traffic is the same; however, this is not necessarily always the case.

The IP addresses are typically external addresses on a private network. We do not recommend
using the loopback address for anything other than testing. For each external IP that is used, we
recommend that a forward and reverse DNS entry is set up. For example, if the Service Traffic IP
address selected is 10.1.2.20, performing nslookup 10.1.2.20 should resolve to a domain name
(for example, sipserver1.mycompany.com) and performing nslookup sipserver1.mycompany.com
should resolve to 10.1.2.20. We do not recommend relying on other operating system-specific
resolution mechanisms, such as the hostname command or the hosts file.

The Cluster Address should be an FQDN; only use an IP address for testing or single-box
deployments. In an HA environment the cluster FQDN should resolve to one of the following:

A set of A-Records (and optional SRV-Records).

A-records can be used for SIP and HTTP resolution, whereas SRV-records should only be used
for SIP, as most HTTP clients do not support SRV. Typically, there is a single A-Record entry per
LB IP address. Configuring a reverse lookup from LB IP address to cluster address is optional.

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 7

 A single A-Record that resolves to a virtual IP address.

The virtual IP address does not point directly to the LBs; instead it targets a hardware or
software external Load Balancer cluster (for example, Linux Virtual Server) which would
distribute traffic to the LBs.

Note: Do not confuse the external Load Balancer with the FAS LB server process.

Note: These IP addresses or FQDNs can be changed following installation. See the Fusion
Application Server Administration Guide for details.

Time Server
In an HA environment, each node must have its system clock synchronized with all the others.
You can do this easily by synchronizing all of them to the same external Time Server, using NTP
(Network Time Protocol). It is especially important to be careful to do this when adding nodes to
an existing installation.

If the nodes are not time-synchronized in an HA environment, the Infinispan cache may become
corrupted, and the cluster may become unusable; this can be seen in issues with the web plug-in
framework not working, and showing Infinispan-related errors in the logs. Deleting the cache and
restarting the service usually fixes the problem temporarily, but to avoid the problem, ensure that
the time is synchronized across all nodes in the cluster.

Quick Installation
For development systems where you do not need High Availability, and the load on the server
will be light, the installer offers a quick install mode, which uses defaults for almost all the
installation options; you should only need to provide the installation path.

Post Installation Tasks

After you have completed the installation, there are a number of configuration tasks that you
might need to perform before you use Fusion Application Server:

configure system properties

configure logging

manage certificates for TLS

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 8

See the Fusion Application Server Administration Guide.

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 9

Installing the Fusion Application Server
You can install FAS by a silent installation on the command line using a properties file.

You can deploy a non-HA (high availability) installation of FAS either on a single box or across
multiple boxes. Installing FAS across multiple boxes offers the option of installing it in a high-
availability architecture.

For single-box installations, all components are installed on the same host, and the installer only
needs to be run once. For multi-box installations, you must run the installer on each host on
which you want to install a cluster component, and you can choose whether to install an AS, LB,
or both, on each FAS node.

An AS node (a FAS node running an AS) in a cluster can either be a master or a slave node.
Each cluster must have one master node. In a multi-box installation, the master node acts as the
Domain Host Controller, and hosts the Management Console and the License Manager, which
are installed when you select a node type of Master (or when you select a single-box
installation).

The master node must be installed first, as the installation of slave nodes requires that you
specify the connection details for the master. All clusters must contain at least one AS and at
least one LB.

The master node must be up and running before you install any FAS components on another
host.

Users and Security

Application Users

FAS uses two sets of administration credentials, one for the administrator to log in to the
administration interface, and another for communication between slave and master nodes within
the cluster.

The user logs in to the administration interfaces (CLI, and Web UI) using the LOCAL credentials.
The defaults are:

User name administrator

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 10

 Password administrator

Note: This is the same local account that is used by FCSDK.

The slave to master node communications use a specific set of credentials. The defaults are:

User name master

Password master

Note: These credentials are stored in the file <install dir>/domain/configuration/mgmt-

users.properties.

Installing as a Non-Root User

When you install FAS as a non-root user, you have to specify at least one of two non-root OS-
level users in the installation properties file:

os.user is the user which the FAS will be running as.

This user is able to read and write log files, and start and stop the services (FAS and media
broker)

os.admin is the user which the administrative tools run as.

This user is able to run the CLI and logcapture, view the audit logs, and perform administration
duties (for example, deploy files or make administration changes).

The first user (os.user) is mandatory, but is set to root in the FAS installation properties file by
default. If the installation properties file does not specify the second user (os.admin), the installer
assigns os.admin’s responsibilities to os.user. Therefore, if you did not change the defaults when
you installed FAS, both the administration tools and the system itself will be running as root.

Operating System User Groups

By default, the installers install FAS to run as the root user. When installing as a non-root user
(see the Installing as a Non-Root User section), you can define two OS user groups in the
advanced-install.properties file:

FAS OS Users

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 11

Members of this group can operate FAS by starting and stopping the FAS services. They need to
have write and execute permissions for the files and directories which will start and stop the
services.

The default value in the advanced-install.properties file is cba-users.

FAS OS Admins

Members of this group perform upgrades and any other administrative tasks, such as running
logcapture.sh and viewing the audit logs. In addition to the permissions associated with the FAS
OS Users, they need to be able to:

Execute the FAS upgrade procedure and the log capture scripts

Execute any FAS-related scripts in <install dir>/bin and <install dir>/resources

The default value in the advanced-install.properties file is cba-admins.

Note: The groups need to be created before installing FAS. The installer only adds the groups to
the os.user and admin.user users, and sets permissions on the appropriate files.

Installation Mode

The silent installers can be run in one of the following modes:

Quick

Installs on a single box, defaulting most of the options. It is suitable for development systems
where High Availability is not required and the system load is light.

Advanced

Allows for specifying all the possible options.

Upgrade

Upgrades an existing installation, taking options from the existing installation where it can.

Silent Installation

Fusion Application Server can be installed silently from the command-line by specifying the
required installation configuration in a properties file. See the Installer Properties section for

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 12

details of how to complete the properties fields. Template property files for quick, advanced, and
upgrade installations are provided with the installer.

1. Extract the fas-core-installer-x.x.x.zip file.

2. Edit the properties file as required. Three files are provided:

quick-install.properties

advanced-install.properties

upgrade-install.properties

The quick version only has those properties needed by a quick install.

3. Run the installer:

java -jar fas-core-installer-x.x.x.jar ‑options <properties file>

where <properties file> is the file you edited in step 2.

Installer Properties
Note: Do not change the installation.mode.* property in the file. This is set to the correct value
(quick, advanced, or upgrade) in each of the properties files.

Property Description

Set to accept, yes, or true to indicate that you accept the

End User License Agreement. This value is not set in any
accept.eula
of the properties files, and must be set by the user to
indicate acceptance.

INSTALL_PATH The directory to which FAS will be installed.

JDKPath The path to your JDK.

topology.type Set to singlebox or multibox. Default is singlebox.

Set to master (the default) or slave. For single box

node.type
installations, this value is ignored.

install.appserver Set to y to install an AS, or n to not do so. y is the default.

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 13

 install.loadbalancer Set to y to install an LB, or n to not do so. y is the default.

The user name of the user that owns and runs the AS files
os.user
and processes.

Keystore password for identity certificates. The default is

keystore.password
changeit.

Specifies whether services should be created during

installation. The default is true; set to false to not create a
services.create
service during installation. You can still create a service
after installation; see the Post Installation section.

Specifies whether the installed components should start

services.start immediately after installation. The default is true. Set to
false to not start the components.

The installer will not continue if existing running FAS

processes are found. Set this to yes or true to proceed
with the installation even if running processes are found.
running.processes.ignore The default is no. Note: If you enable this, and there are
any processes still running, you may be installing to an
unsupported configuration, or to one which causes
problems later.

Specifies the address to bind to for service and internal

bind.address.service
traffic.

bind.address.management Specify the address to bind to for management traffic.

The user name to use to log in to the Management

admin.user
Console. The default is administrator.

The password for the above user when logging in to the

admin.password
Management Console. The default is administrator.

The user name for authentication of internal traffic

masterslave.auth.user
between master and slave. The default is master.

masterslave.auth.password The password for the above user. The default is master.

snmp.protocol Protocol to use for SNMP traps. The default is SNMPv2c.

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 14

 The address of the SNMP client which SNMP traps
snmp.target.address
should be sent to.

The port the SNMP client is listening on. The default is

snmp.target.port
162.

Specifies the polling period for the SNMP Agent (see the
snmp.pollperiod
Fusion Application Server Architecture Guide).

If you are installing a master AS or an LB in a multi-box

installation, you must provide an address for the cluster.
This must be an FQDN that resolves with DNS to all of
cluster.address the LB nodes in the cluster; if you only have one LB node
you can provide the FQDN or IP address for that host. If
you are installing on a single box you can use the IP
address of the FAS.

Set to yes or true to bypass the checks on the cluster

address. These checks try to resolve the cluster address,
to ensure that it is valid, and the installer will not proceed
cluster.address.bypassChecks with the installation unless they pass. The default is false.
Note: If you enable this, and the cluster address cannot
be resolved, the installation will probably not work until the
problem is corrected.

To ensure that the replicated data from each cluster is

kept separate, a unique Cluster ID is used in the
replication layer. If you are installing a master AS node or
cluster.id an LB node, enter the cluster ID or leave it blank to use
the default value of:ClusterID-<cluster.address> where
<cluster.address> is the value entered for the
cluster.address.

An AS or LB on a slave node needs to connect to the

master node. Enter the address of the master node here.
master.address
These details are not required if you are installing the
master node.

master.port Enter the port of the master node. The default is 9999.

For an upgrade, enter the user name you provided when

master.user
installing the master node. The default is administrator.

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 15

 The password for the above user. The default is
master.password
administrator.

Post Installation

If you chose not to install the service during installation, you can manually add the service:

1. Log on to the OS as a user with administrative privileges.

2. Execute the add-service.sh script in the FAS resources directory:

<install dir>/resources/add-service.sh

You should now be able to invoke the service script in the normal way (see the Starting Fusion
Application Server section).

Upgrade

An upgrade installs the latest FAS into the specified directory (which cannot be the same as the
current installation directory), and copies the existing configuration and applications to the new
installation. Note that the current FAS must be shut down during upgrade, and the new one must
be started manually after the upgrade has completed. When upgrading a multi-box cluster, start
the master node before the slave nodes.

Upgrade Rollback
If you need to roll back the upgrade to the previous installation:

1. Shut down the upgraded FAS

2. Edit the /etc/fas.conf file, and change the JBOSS_HOME value to point to the previous
installation directory

3. Restart FAS.

Once restarted, you can delete the new FAS directory.

Uninstalling FAS

You can uninstall Fusion Application Server using the supplied uninstaller.jar executable:

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 16

 1. Stop all FAS processes running on the host or VM:

service fas stop

Note: Perform this step on all nodes of the cluster before running the uninstaller on any of them.

2. Change to the <install dir>/Uninstaller directory

3. Run the uninstaller.jar executable:

java -jar uninstaller.jar

4. If you want to delete the FAS directory, check the Force the deletion of… checkbox.

5. Click Uninstall.

6. The uninstaller displays a prompt, asking you to ensure that the server processes are
stopped before running the uninstaller. Ensure that these have stopped (see step 1), and
click OK.

7. You will see a second prompt, asking whether to uninstall the FAS services. Select Yes.

8. When the process has finished, click Quit.

Repeat the procedure on all FAS nodes in the cluster.

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 17

Testing the Installation
This chapter describes how to test your installation by starting each of the Fusion Application
Server processes and then launching the Management Console.

All of the nodes in a FAS cluster, and all of the server processes in a FAS node (that is, AS, LB,
and SNMP Agent) can be run independently of each other; however, the master node plays the
most important role. Specifically:

Configuration changes such as application deployment or un-deployment require that the

master node is running, since only the master node runs the management server process.

Slave nodes receive updated configuration from the master. If the master node is not
running, the slaves will use cached configuration and then periodically make attempts to
connect to the master to get configuration updates.

We therefore recommend that you start the master node before the slaves or the other
processes. The start-up order of these other processes is unimportant.

Starting Fusion Application Server

Using the Service

If you selected the Start services after install option during installation, the AS and LB should
have started automatically. If you created the services but did not start them automatically, you
can start FAS manually using the service:

service fas start

Note: The startup type of the services is set to automatic on installation.

Using the Script

You can also use the script provided to start FAS:

\<install dir\>/bin/fas.sh

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 18

When FAS starts, it starts every component on the host; if both an LB and an AS server process
are present, it starts both of them.

Checking the State of Fusion Application Server

If it has been installed as a service, the running status of FAS can be checked from the
command line:

# service fas status

Fusion Application Server is running (pid 20986)

You can also stop or restart (stop and immediately start again) the service using:

service fas stop

or

service fas restart

Using the Management Console

You can check if FAS has installed and started by launching the Management Console at:

https://<fas address>:9990

where <fas address> is the IP address of the master AS, or of the machine hosting a single box
installation.

If the FAS has started, you will be asked to supply the administrator credentials you supplied
during installation. Once you have entered them, you will see the main Fusion Application
Server window:

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 19

This example (for a single box installation) shows three server processes running:

appserver-localhost

The AS server process (JEE / JSR 289 container).

loadbalancer-localhost

The LB server process.

management

This is only present on the master node. It hosts the licensing application and the Management
Console.

If the FAS is running correctly, all server processes present should show a tick in the Active
column.

Note: If you are checking the status of a multibox cluster, you can choose a different host from
the Server dropdown in the top left of the screen (which will show all the nodes in the cluster in
the Host column). When you have chosen a host and clicked the Done button, you will see in
the Server Status page, those server processes (AS, LB, and Management if applicable), and
only those server processes, which are on that on that host.

Starting and Stopping Individual Components

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 20

From the Management Console, you can stop and start individual services (AS or LB server
processes) on a node. To stop a service:

1. Select the service you want to stop in the Server Status page (you can only select one
service at a time).

2. Click the Stop button at the top right of the page.

When the service has stopped, the tick will be replaced by a circle with a line:

The Stop button has now changed to Start. You can start a stopped service by clicking the Start
button.

Note: Because the service does not stop immediately upon clicking the Stop button, it is
possible to try to start a service while it is still stopping, which will result in an error. It is advisable
to wait for the service to stop (up to a minute) before trying to start it again.

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 21

Glossary
Term Description

This is a framework offered by applications to manage their

configuration. Unlike managing application configurations
Application
using standard system properties, this framework offers
Configuration
validation and publishing hooks that allow the application to
Framework (ACF)
check that configuration settings are valid, and to be informed
when configuration settings have changed.

Used for co-hosting multiple products on the same FAS

Application Router cluster. Where each product has its own application router
Registry and set of applications, the application router registry
determines which application router a request is sent to.

Server process running in FAS to which applications are

Application Server
deployed, and which executes the application logic. It is a
(AS)
JSR 289-compliant application server.

Application Server
FAS node running at least an AS server process.
node (AS node)

Group of FAS nodes, of which one is the master and the

Cluster
others are slave nodes.

A unique name within the enterprise that a cluster is known

Cluster name by. Specifying the cluster name when adding a new AS or LB
adds that component to the specified cluster.

Datasource The connection set up to a database from a server.

A set of Server Groups that can be managed from a single

point. Essentially equivalent to a cluster, though a cluster is
Domain
more physical (a set of host machines or virtual servers),
while a domain is more logical (a set of Server Groups).

A Host Controller that is in charge of all the others in a cluster,

Domain Host
and the point from which the Server Groups in a domain are
Controller
managed.

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 22

 Dynamic Model
A tree-structure representation of the FAS attributes that can
Representation
be configured.
(DMR)

A combined SIP and HTTP application development and

delivery platform that can be used in multiple network
Fusion Application
architectures, ranging from the smallest enterprise
Server (FAS)
applications to carrier-scale IMS environments using SIP and
HTTP.

Host or virtual server running FAS, and which is part of a FAS

FAS node
cluster.

Host Controller The FAS process that provides the management interfaces.

A certificate that proves a resource’s identity, usually signed

Identity Certificate
by a Certification Authority. Used in TLS.

A scalable, highly available data store and distributed data

Infinispan grid platform that provides distributed cache capabilities and
state replication.

The Java API for XML Web Services. It is a Java

JAX-WS programming language API for creating web services, and is
part of the Java EE platform.

A graphical monitoring tool to monitor Java Virtual Machine

JConsole (JVM) and java applications both on a local or remote
machine.

A toolkit for reliable messaging. It can be used to create

JGroups groups of processes whose members can send messages to
each other.

A server process running within FAS. It is a largely stateless

Load Balancer
proxy for both SIP and HTTP that routes new requests to an
(LB)
AS server process.

Load Balancer
A FAS node running at least an LB server process.
node (LB node)

Managed domain In a managed domain each application server instance is a

member of a server group. You can manage multiple server

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 23

 groups within a domain.

Management A server process running on the FAS master node in a cluster

Server (and only on the FAS master node).

The traffic from the CLI, Management Console and from

Management traffic
communication between master and slave host controllers.

The FAS node that hosts the Domain Host Controller, which
Master node the CLI and Management Console connect to to manage the
cluster.

Java Management Extensions (JMX) is a Java technology

that supplies tools for managing and monitoring applications,
MBeans system objects, devices and service oriented networks. Those
resources are represented by objects called MBeans (for
Managed Bean).

The reference implementation of the JAIN-SIP API. JAIN-SIP

is a low level protocol API for SIP. NIST stands for National
NIST SIP stack
Institute of Standards and Technology. JAIN stands for Java
APIs for Intelligent Networks.

The FAS process that manages the lifecycle of the other

Process Controller
processes - starting, stopping, and restarting as appropriate.

A profile is a set of subsystems (for example, logging, web,

Profile
SIP, Infinispan) together with their configuration.

A logical construct used by the AS to group sessions. Each

AS creates a fixed number of segments when it starts. The
Segments
assignment of Segment ID to AS is shared via Infinispan and
known to all FAS nodes.

Server processes across one or more hosts are grouped into

Server Groups. Applications are deployed to Server Groups,
Server Group
so all hosts in a Server Group will have the same set of
applications deployed.

A process running in FAS (AS, LB, or Management).

Server Process Unfortunately referred to as a server in the Management
Console.

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 24

 Service traffic HTTP, HTTPS, SIP, and SIPS traffic.

The FAS nodes within a cluster that are not the Master are
Slave slaves, which receive their configuration changes from the
Domain Host Controller running on the Master node.

A process integrated with each Domain Host Controller and

Host Controller that collects information from the FAS
SNMP Agent platform, and applications hosted on FAS, and exposes this to
the external Network Management System. SNMP stands for
Simple Network Management Protocol.

A state resulting from network issues that prevent some AS

Split brain nodes from communicating with other AS nodes in the cluster,
forming separate subgroups.

A certificate from an external host that enables secure

Trust certificate
communication with that host. Used in TLS.

An abstraction layer on top of a more concrete file system that

Virtual File System
allows client applications to access different types of file
(VFS)
systems in a uniform way.

The Web Services Description Language is an XML-based

WSDL interface description language that is used for describing the
functionality offered by a web service.

© 2023 CBA | All Rights Reserved | Unauthorized use prohibited. Page 25