To Deploy to JBoss

Restriction: This topic applies only when the Enterprise Server feature is enabled.

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

Important: For a current list of supported JBoss application server versions, see the Application Server JCA support for Enterprise Server topic under Additional Software Requirements.

Installing JBoss Application Server

You can download JBoss Application Server from the JBoss official website, and install it from there.

To open JBoss Application Server:

Enter the URL http://localhost:8080 in your Web browser, where 8080 is the default port.

Administering 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:

Enter http://localhost:9990/console/App.html in your Web browser. Port 9990 is predefined as the Management Console socket binding.

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.

For Windows environments :

Run jboss_home\bin\standalone.bat to start it.
Run jboss_home\bin\jboss-cli --connect command=:shutdown to stop it.

For UNIX environments :

Run jboss_home/bin/standalone.bat to start it.
Run jboss_home/bin/jboss-cli --connect command="shutdown to stop it.

Deploying the Resource Adapter

To deploy a resource adapter for JBoss EAP 7.x, update the standalone.xml file, located in your JBoss installation's standalone\configuration (Windows) or standalone/configuration (UNIX) directory, as follows:

Disable the jca subsystem

Edit the <archive-validation> child of the <subsystem xmlns="urn:jboss:domain:jca:5.0"> element to read as follows:

<archive-validation enabled="false" fail-on-error="true" fail-on-warn="false"/>

Add the mfcobol-notx.rar resource adapter

Replace the existing resource-adapters subsystem element in its entirety with the following subsystem definition:

<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>

Add the mfcobol-localtx.rar resource adapter

Within the <subsystem xmlns="urn:jboss:domain:resource-adapters:5.0"> tag, add the following <resource-adapter> definition as a child of <resource-adapters>:

<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>

Add the mfcobol-xa.rar resource adapter

Within the <subsystem xmlns="urn:jboss:domain:resource-adapters:5.0"> tag, add the following <resource-adapter> definition as a child of <resource-adapters>:

<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>

Deploying the Application .ear File

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 (Windows) or my-project/repos/my-service.deploy/my-service.ear (UNIX) into your JBoss deployment directory which is, by default, jboss_home\standalone\deployments (Windows) or jboss_home/standalone/deployments (UNIX).

Logging

JBoss stores log files and traces by default in jboss_home\standalone\log\server.log (Windows) or jboss_home\standalone\log\server.log (UNIX).

Configuring a JDBC Data Source for XA Transactions

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.

Further Information

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