This topic describes how to deploy an application developed using the Interface Mapping Toolkit to JBoss Application Server.
You can download JBoss Application Server from the JBoss official website, 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 administration console. To start the console:
You can start and stop JBoss Application Server from the JBoss console or from the command line, as follows.
To deploy a resource adapter for JBoss EAP 7.x, update the standalone.xml file, located in your JBoss installation's standalone\configuration directory, as follows:
<archive-validation enabled="false" fail-on-error="true" fail-on-warn="false"/>
<subsystem xmlns="urn:jboss:domain:resource-adapters:5.0"> <resource-adapters> <resource-adapter> <archive>mfcobol-notx.rar</archive> <transaction-support>NoTransaction</transaction-support> <connection-definitions> <connection-definition class-name="com.microfocus.cobol.connector.spi.CobolNoTxManagedConnectionFactory" jndi-name="java:/eis/MFCobol_v1.5" pool-name="CobolConnectionFactory"> <pool> <min-pool-size>2</min-pool-size> <max-pool-size>10</max-pool-size> </pool> <security> <application/> </security> </connection-definition> </connection-definitions> </resource-adapter> </resource-adapters> </subsystem>
<resource-adapter> <archive>mfcobol-localtx.rar</archive> <transaction-support>LocalTransaction</transaction-support> <connection-definitions> <connection-definition class-name="com.microfocus.cobol.connector.spi.CobolLocalTxManagedConnectionFactory" jndi-name="java:/eis/MFCobol_v1.5" pool-name="CobolConnectionFactory"> <pool> <min-pool-size>2</min-pool-size> <max-pool-size>10</max-pool-size> </pool> <security> <application/> </security> </connection-definition> </connection-definitions> </resource-adapter>
<resource-adapter> <archive>mfcobol-xa.rar</archive> <transaction-support>XATransaction</transaction-support> <connection-definitions> <connection-definition class-name="com.microfocus.cobol.connector.spi.CobolManagedConnectionFactory" jndi-name="java:/eis/MFCobol_v1.5" pool-name="CobolConnectionFactory"> <xa-pool> <min-pool-size>2</min-pool-size> <max-pool-size>10</max-pool-size> </xa-pool> <security> <application/> </security> </connection-definition> </connection-definitions> </resource-adapter>
When you generate an application .ear file the 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.
Copy the application .ear file from the directory my-project\repos\my-service.deploy\my-service.ear into your JBoss deployment directory which is, by default, jboss_home\standalone\deployments.
If the application being deployed connects to a third-party database, you need to configure a JDBC data source and specify information such as the JNDI name of the data source.
Add a data source to the standalone.xml file.
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 the JBoss Web site.