This article provides an overview of each of the subject areas covered in this guide, which includes the concepts involved in administering a Fusion Application Server cluster, and the main areas of administration.
Domains, Server Groups, Server Processes, and Profiles
You can manage Fusion Application Server configuration at a number of different levels: the domain level, server group level, server process level, or by way of profiles. See the Domains, Server Groups, Server Processes, and Profiles article.
Management Interfaces
You can perform much of the configuration and management of Fusion Application Server clusters using the Management Console. You can also perform the same configuration tasks, and some additional tasks, using the CLI. For more info, see this article.
File System
FAS stores its configuration options in a number of property files. You do not normally need to edit these files directly; in most cases you can use the Management Console or CLI. See the File System article.
Managing Cluster Components
A FAS cluster consists of FAS nodes running Load Balancers (LBs) and Application Servers (ASs), which are server processes. See the Managing Cluster Components article.
Managing Applications
FAS is the platform on which CBA applications and other applications run. Several types of application can run on FAS. See the Managing Applications article.
Licensing
Some CBA applications require a license to enable subscribers to use them. Licenses are available from CBA Support, and are applied to the application using FAS’s License Server. See the Licensing article.
SNMP Traps
Each Host Controller process contains an SNMP Agent, which provides a means by which applications deployed on FAS can raise traps. There are also a number of SNMP traps that the FAS cluster itself may raise when significant events occur. See the Configuring SNMP article.
Logging
FAS uses Log4J to log events to the console, and to various files in the system. You can change logging levels and logging destinations using the Management Console. See the Logging article.
Security
By default, local access (that is, from the node itself) is not restricted, but remote access is restricted by credentials specified during installation. These credentials are also used by slave application servers to communicate with the master application server. See the Security article.
Trust Management
By default, FAS is configured to use Transport Layer Security (TLS).
The components within a FAS cluster must trust each other, so you must provision all of them with identity certificates signed by a trusted CA. As the LBs send and receive external data, you should provision them with trust certificates which will let them know which external hosts to trust. See the Trust Management article.
Ports
Fusion Application Server uses a number of ports for communication between cluster components and external SIP or HTTP devices. These ports are listed in the Ports article.
Performance
There are a number of properties on Fusion Application Server cluster components, and on the SIP stack, which you can change to improve performance. See the Performance article.
Monitoring
The operational status of FAS components is exposed using JMX MBeans.
This data can be viewed using JConsole, which is supplied with your JDK. FAS also provides a script for collecting diagnostic information from a server for further offline investigation. See the Monitoring article.
Comments
0 comments
Please sign in to leave a comment.