Provides step-by-step instructions that start with defining an Enterprise Java Bean (EJB) service interface using the Interface
Mapping Toolkit (IMTK), take you through the process of deploying it to an
enterprise server instance, and generating and running a client to access it.
Restriction: This topic applies only when the Enterprise Server feature is enabled.
Restriction: This topic applies to Windows environments only.
- Review the
Before you begin a tutorial sections in the
Tutorials: Interface Mapping Toolkit topic to ensure that your
Visual COBOL environment is set up properly.
- The following prerequisite software must be installed and configured before proceeding:
- Before you can successfully deploy a Java service, you must have the
Java Development Kit (JDK), version 1.8 installed. This version is installed automatically with
Visual COBOL. Following installation, edit your Windows environment variables as follows:
- Set the JAVA_HOME system environment variable to your Java installation directory
- Add the path to the
JAVA_HOME\bin directory to your system PATH environment variable
- JBoss EAP 7.1
- Before you can successfully access a Java service, you must install a Java application server. This tutorial provides instructions
for using JBoss Application Server version EAP 7.1 with cumulative patch 4, available for download from the Red Hat Web site.
Following installation, continue with configuration:
- Ensure that the JBOSS_HOME system environment variable is set to your JBoss installation directory.
- Using any text editor, edit the
standalone.xml file, located in your JBoss installation's
standalone\configuration (Windows) or
(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:
<connection-definition class-name="com.microfocus.cobol.connector.spi.CobolNoTxManagedConnectionFactory" jndi-name="java:/eis/MFCobol_v1.5" pool-name="CobolConnectionFactory">
Demonstration application - BookDemo
The BookDemo demonstration application represents a legacy COBOL application, meaning that this application is understood
to have been in production use for some time. The application source code and project files are installed with
Visual COBOL in the
%PUBLIC%\Documents\Micro Focus\Visual COBOL\Samples\Interface Mapping Toolkit\ServiceInterfaces\BookDemo (Windows) or
$COBDIR/demo/Interface Mapping Toolkit/ServiceInterfaces/BookDemo (UNIX) directory by default.
The BookDemo application is an online data application that uses an indexed file to maintain stock and inventory data such
as might be in use at a book retailer. The application enables you to read, add, and delete records, and to progress from
the current record to the next record. It uses the following source and data members:
- Performs the four main functions of the application by receiving a user-supplied value via a linkage section, accessing or
modifying the data based on the request received, and sending output data back to the user.
- Called by
book-rec.cpy contains linkage section data structures.
- The data file maintained by the
- The data index file.
To complete this tutorial, progress through these topics in the order presented here. The bottom of each topic provides
Next topic and
Previous topic navigational links to help you proceed in the proper sequence: