www.ironjacamar.orgCommunity Documentation
Table of Contents
The IronJacamar distribution features a resource adapter information tool, that can provide the important information about the resource adapter and a sample deployment descriptor.
The information about the resource adapter is generated using the following command:
./rar-info.sh myeis.rar
where the report will be located in myeis-report.txt
. The tool can take an optional
-classpath
parameter such that additional external dependencies can be resolved against
the resource adapter.
The report will contain information about
MANIFEST.MF
file
The tool (rar-info.sh
) is located in the doc/as/
directory of the
distribution.
The IronJacamar distribution features a migration tool, that can convert the deployment format used in JBoss Application Server prior to version 7, and JBoss Enterprise Application Platform versions prior to version 6.
Since there are different formats (XSDs) to deploy datasources and a resource adapters the tool can convert to both these formats.
The tool (converter.sh
) is located in the doc/as/
directory of the
distribution.
A resource adapter deployment is converted using the following command:
./converter.sh -ra old-ds.xml new-ra.xml
which will convert the file old-ds.xml
to new-ra.xml
. The content of
new-ra.xml
can then be copied into the resource-adapters
subsystem
in WildFly or used directly in the IronJacamar/Standalone distribution.
The resource adapter converter tool can also convert the Oracle WebLogic weblogic-ra.xml
files
to the IronJacamar format.
The following command line can be used:
./converter.sh -ra --weblogic weblogic-ra.xml new-ra.xml
to get a best effort convertion of the Oracle WebLogic deployment file.
A data source deployment is converted using the following command:
./converter.sh -ds old-ds.xml new-ds.xml
which will convert the file old-ds.xml
to new-ds.xml
. The content of
new-ds.xml
can then be copied into the datasources
subsystem
in WildFly or used directly in the IronJacamar/Standalone distribution.
Debugging Java EE Connector Architecture scenarios can be a complex task, as the interaction between the application and the resource adapter depends both on the implementation of the resource adapter but also on how it is configured.
IronJacamar features a tracer tool that will help users to get an overview of the interactions performed between the application and resource adapter.
The tracer produces machine readable codes at the TRACE
logging category
org.jboss.jca.core.tracer
which can then be processed with the tracer-report
tool, located in docs/as/
.
The tool is executed with
./tracer-report.sh logfile
where logfile
contains the TRACE
logging.
The output are HTML reports that shows the interaction performed by all active resource adapters, and the applications using them.
In addition, a UML sequence diagram is produced for valid interaction scenarios, which can be converted into
an image using the SDedit
application.
For invalid interaction scenarios the tool will try and highlight the issue such that the collected log between the two timestamps identified can be investigated.