• Download PDFs
• Configuring the J2EE Application Server  

• Related Topics
• Accessing the J2EE Application Server’s Client Libraries
• SRC-VTA Architecture and Connections to SRC Components
• Using SRC-VTA Keys to Manage Subscriber and Server Sessions

Configuring the J2EE Application Server

Before configuring the J2EE application server, install the JDBC driver that allows your database to connect to the J2EE application server, and restart the J2EE application server. See the documentation for the database to determine the required JDBC driver. For example, for JBoss, copy the driver to /opt/UMC/jboss/server/default/lib.

Note: If you use JBoss, the VTA configuration script configures the J2EE application server, and you do not need to complete these tasks.

To configure the J2EE application server to support the SRC-VTA:

1. For each VTA, create a data source with a Java Naming and Directory Interface (JNDI) name that matches the name of the data source (see Table 1 for the default names).

   The load script copies default data-source deployment descriptors. These descriptors are appropriate for an environment in which you use JBoss with the MySQL database and have both of these applications running on the same host. The descriptor files begin with mysql-. For more information about these files, see the documentation for the version of JBoss included with the SRC software.

   To modify the names of the VTA deployment descriptors, see Creating Deployment Descriptors.

2. Set up a Java Message Service (JMS) connection factory, and link it to the resource environment reference jms/QueueConnectionFactory.

   The way you link the JMS connection factory to the resource environment reference depends on the J2EE application server. See the documentation for the J2EE application.

3. For each VTA, create a JMS queue for the ConnectionFactory class with the appropriate name for the SRC-VTA (see Table 1).
4. Create a role called VTA-Admin, and configure the administrator profiles so that administrators can access the VTA administration portal with this role.
5. Specify an authentication mechanism, and access parameters (such as a username and password) by which administrators can access the data source through the portals.

   The access parameters that you configure must match the access parameters that you configure for the database (see Configuring a Database to Store Account and Session Data).

Table 1: Names for Data Sources and JMS Queues