Restriction: This topic applies only when the Enterprise Server feature is enabled.
- Start your Java application server and its administration console, and navigate to where you add resource adapters.
The resource adapter must be deployed on a machine where a COBOL system such as
COBOL Server or
Visual COBOL is installed.
- Specify the resource adapter to deploy. These can be one of the following:
- mfcobol-notx.rar - does not support transactions
- mfcobol-localtx.rar - supports local transactions
- mfcobol-xa.rar - supports XA transactions
Specific versions of these files are supplied for each supported application server and Java version. They are available in
the application server subdirectories
under
%ProgramFiles(x86)%\Micro Focus\Visual COBOL for Visual Studio 2013\javaee in your COBOL development system, as follows:
-
javaee5/ibmwebsphere7
- javaee5/jboss5
- javaee5/oracleweblogic10
- javaee6/ibmwebsphere8
- javaee6/ibmwebsphere85
- javaee6/jboss6
- javaee6/oracleweblogic1211
- Ensure that the support for the resource adapters and ensure it is on your path and classpath environment variables.
- You might need to provide the application server with a deployment descriptor for the resource adapter. Deployment descriptors
are supplied for the following application servers:
- JBoss -
mfcobol*ds.xml, which are supplied in the folder with the
.rar files
- WebLogic -
weblogic-ra.xml, which is packaged in each
.rar file
- WebSphere - does not require deployment descriptors
Among other things, the deployment descriptors specify the following connection information, and you must not change this.
Note: The JNDI name and the reference name that you enter both depend upon your Java version.
|
|
JNDI name
|
Reference name
|
| Java EE 5
|
eis\MFCobol_v1.5
|
CCIMFCobol_v1.5
|
| Java EE 6
|
eis\MFCobol_v1.5
|
CCIMFCobol_v1.5
|