SDX 6.4.x Application Library Guide > Providing Threat Mitigation Services with the Threat Mitigation Application > Installing and Initially Configuring the Threat Mitigation Application

Installing and Initially Configuring the Threat Mitigation Application

Because the Threat Mitigation Application relies on other components in the SDX network, you must complete several tasks before you install the Threat Mitigation Application software. After you install the software, you must also complete several configuration tasks before the application can function correctly.

For information about the location of the Threat Mitigation Application software on the application library CD, see Chapter 1, Installing the SDX Applications.

Before You Start

Before you install and configure the Threat Mitigation Application, you must:

1. Deploy a working SDX network.

To support the Threat Mitigation Application, you must install SAEs to manage the routers or other devices through which subscribers connect to the network. You must also install and configure the directory in which you will store the SDX data.

2. Install a J2EE application server on the host that supports the Threat Mitigation Application.

For information about installing JBoss (the J2EE application server provided with the SDX software), see SDX Getting Started Guide, Chapter 5, Installing the SDX-300 Software.

3. On the host that supports the Threat Mitigation Application, install a transactional database to store the data for the Threat Mitigation Application.

Installing and Initially Configuring the Threat Mitigation Application Software

To install the Threat Mitigation Application:

1. Install the Solaris package for the Threat Mitigation Application (see Chapter 1, Installing the SDX Applications) on the hosts that support the following components:

• SAEs
• Directory
• JBoss

2. Run the configuration script to configure the Threat Mitigation Application. See Configuring the Threat Mitigation Application.
3. Run the load script to complete the configuration tasks for deploying the Threat Mitigation Application. See Deploying the Threat Mitigation Application.
4. On each host, restart JBoss.

You must restart JBoss when you have configured the Threat Mitigation Portal for the first time or you have changed the database type.