www.ironjacamar.orgCommunity Documentation

Chapter 10. Other tools

Table of Contents

10.1. Resource adapter information tool
10.2. Migration tool
10.2.1. Resource adapters
10.2.2. Data sources
10.3. Tracer tool

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

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.

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


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.