If your deployed EJB does not work, check the following things:
- Have you stopped and restarted the application server? Sometimes this is required to pick up changes to deployments and configuration. Whenever you reboot the WebLogic machine, you also need to restart the WebLogic server from the Start menu.
- Is the enterprise server you require running?
- Are the required services deployed to the enterprise server? Were they deployed successfully? You can check this by looking in the Enterprise Server Administration console,
http://locahost:86, in
deploy\...\deploylog.txt and
%USERPROFILE%\Documents\Micro Focus\Enterprise Developer\WORKAREA
\esname\console.log (Windows) or
deploy/.../deploylog.txt and
/var/mfcobol/es/esname/console.log (UNIX), where
esname is your enterprise server name, such as ESDEMO.
- Was any information written to the resource adapter log file
cobcon.log? This log file is located in the directory defined in your Java system's user.home property. This directory equates by default to your user profile directory. If there wasn't any information written to the log file, the failure occurred before the resource adapter was invoked. The failure might lie in the application server setup. Notice that there are backup log files
cobcon1.log and
cobcon2.log.
- For WebSphere application servers, is the
trace property for your
mfcobol-notx.rar resource adapter set to
true? If it is, then you can find trace information written to the WebSphere log file. For information on configuring resource adapters in WebSphere, and for the location and contents of the WebSphere log file, see your IBM WebSphere documentation.
- For JBOSS and WebLogic application servers, is the
trace parameter in the
ra.xml file set to
true? If so, you can find trace information in the JBOSS or WebLogic log file respectively. For information on editing the
ra.xml file, see
Deployment Descriptors that Are Required
. See your JBOSS or WebLogic documentation for further details with regard to the log file.
- Was any information written to the communications server log file
log.html? See
Communications Server Log Files for more information.
- When you generated your EJB using the Deploy tool, did you use the J2EE connector classes specific to your application server? For example, you must use
WebLogic.jar for WebLogic EJB generation and
j2ee.jar for WebSphere EJB generation. You specify these classes in the Classpath settings of the Deploy tool.
- Is the JNDI name of the resource adapter set to the respective
eis/MFCobol_v1.n as specified in the topic
To Deploy a Micro Focus Resource Adapter to a Java Application Server? Is this JNDI name mapped to the resource references of the EJB.
- Is the JNDI name for each EJB the same wherever it is referred to? When you assign a JNDI name to an EJB, any client or other software that uses that EJB must use that same JNDI name.
- Are the EJB and the resource adapter successfully deployed in your application server?
- What failures are recorded in your application server's log files? All the supported application servers have a
logs subdirectory.
