BeanConnect provides a number of tools in addition to the proxy and the resource adapter. These tools can be installed separately and are present in the form of JAR archives. The tools are available in the following archives:
MC-CmdHandler Cobol2Java |
|
Installing the BeanConnect tools in systems with a graphical user interface
In systems with a graphical user interface, proceed as follows:
In the relevant system, open a window for command entry, e.g. Shell or DOS prompt.
Switch to the directory in which the JAR file is located.
Unpack the JAR file using the following command
java -jar <jar-archive>
<jar-archive>
is the name of the relevant JAR archive displayed at the top of the list.Follow the instructions output by the graphical installation program and define the installation directory for the tool, possibly together with additional parameters.
Installing the BeanConnect tools in systems without a graphical user interface
An Auto.xml file is supplied for each tool to permit installation on systems without a graphical user interface. This file has the name <tool>-auto.xml
, where <tool>
is the name of the tool to be installed MC-CmdHandler
, Cobol2Java
).
Proceed as follows:
Open the Auto.xml file with a text editor and enter the required installation path for the tool in the
<installpath>
tag. In the case of some tools, you must also enter configuration data such as port number or password for additional tags that have been commented out.In the relevant system, open a window for command entry, e.g. Shell or DOS prompt.
Switch to the directory in which the JAR file is located.
Unpack the JAR file using the following command
java -jar <jar-archive> <tool>-auto.xml
This installs the tool automatically.
In the case of the tool MC-CmdHandler, you must enter the path to JDK in the file
javaenv.cmd
(Windows systems) orjavaenv.sh
(Linux, Solaris systems). You do this by editing the file with a text editor.