To deploy to JBoss

This topic describes how to deploy an application developed using the Interface Mapping Toolkit to JBoss Application Server.

For details of supported versions of this application server and the appropriate JDK to use, see your Readme.

Installing JBoss Application Server

You can download JBoss Application Server from http://www.jboss.com, and install it from there.

To open JBoss Application Server:

Administering JBoss Application Server

JBoss Application Server provides a Web interface for administering the application server. This administration interface is called the JBoss console. To start the console:

Setting up JBoss Application Server

The JBoss Application Server provides deployment descriptors. These are packaged into the application archive (.ear) files when you generate EJBs using the Interface Mapping Toolkit. The deployment descriptors require some changes before generating EJBs.

For JBoss 3.2.7, change the following:

For JBoss 4.x, change the following:

Where:

Starting and Stopping JBoss Application Server

You can start and stop JBoss Application Server from the JBoss console or from the command line, as follows.

Where jboss_home is your JBoss installation directory.

Deploying the Resource Adapter

Resource adapters, named mfcobol*.rar, are supplied together with JBoss-specific deployment descriptors for using the resource adapters with the JBoss Application Server. The descriptors have names corresponding to the resource adapters, as follows:

For the location and details of the resource adapters see the section Resource Adapters in the chapter Deploying Interfaces in your Configuration and Administration Guide for Micro Focus Server.

To deploy a resource adapter:

  1. Copy the appropriate .rar file into your JBoss deployment directory, which is by default jboss_home/server/default/deploy, where jboss_home is your JBoss installation directory.
  2. Copy the corresponding deployment descriptor, *ds.xml, for the resource adapter into the same directory. For example, if you are deploying mfcobol-notx.rar, copy mfcobol-notx-ds.xml.

Deploying the Application .ear File

When you generate an application .ear file

JBoss Application Server requires that the .ear file contains deployment descriptors that specify deployment information about your application. When you use generate a client and EJB using the Interface Mapping Toolkit, these deployment descriptors are automatically created and packaged into the .ear.

For background, see the section Deployment Descriptors in the chapter Mapping a Java Interface and Using Resource Adapters in your Java and COBOL book.

To deploy your application .ear file:

Logging

JBoss stores log files and traces in jboss_home/server/default/log/server.log, by default.

Configuring a JDBC Data Source for XA Transactions

If the application being deployed connects to a third party database, you will need to configure a JDBC data source and specify information such as the JNDI name of the data source. For an Oracle database, you edit the Oracle-supplied deployment descriptor oracle-xa-ds.xml. For full details see the JBoss administration documentation on configuring JDBC data sources.

Further Information

For further information, see the Release Notes for your JBoss Application Server installation and see the JBoss Web site.

Related Topics