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.
You can download JBoss Application Server from http://www.jboss.com, and install it from there.
To open 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:
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:
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.
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:
To deploy a resource adapter:
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:
JBoss stores log files and traces in jboss_home/server/default/log/server.log, by default.
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.
For further information, see the Release Notes for your JBoss Application Server installation and see the JBoss Web site.