Verifying
installation
The sections below describe the paths and filenames of
the product after installation and how to verify your adapter installation.
Verifying installation on a Windows
system
Before you begin, install the adapter. The Installer copies
the standard files associated with the adapter into your system.
The utility installs the connector into the ProductDir\connectors\JText directory, and adds a shortcut for the connector to the Start
menu.
To verify the adapter installation on a Windows system, change
to the directory where you installed the adapter ProductDir\ and compare the contents to those listed in Table 3.
Table 3 describes the Windows file structure used by the adapter,
and shows the files that are automatically installed when you choose
to install the adapter through Installer.
Table 3. Windows file structure for the connector
Subdirectory of ProductDir |
Description |
\connectors\JText\CWJText.jar |
Contains classes used by the JText connector
only |
\connectors\JText\start_JText.bat |
The startup script for the generic connector |
\connectors\messages\JTextConnector.txt |
Message file for the connector |
\repository\JText\CN_JText.txt |
Repository definition for the connector. The
default name is CN_JText.txt. |
\connectors\JText\start_JText_service.bat |
The startup script for
the connector service. |
\connectors\JText\dependencies\ commons-net-1.1.0.jar, dependencies\ jakarta-oro-2.0.8.jar |
Third party.jar packaged with the connector |
Note:
All product pathnames are relative to the directory
where the product is installed on your system.
Verifying installation on a Linux system
Before you begin, install the
adapter. The Installer copies the standard files associated with
the adapter into your system. The utility installs the connector
agent into the ProductDir/connectors/JText directory.
To verify the adapter installation on a Linux system,
change to the directory where you installed the adapter ProductDir/ and compare the contents to those listed in Table 9.
Table 4 describes the Linux file structure used by the
adapter, and shows the files that are automatically installed when
you choose to install the adapter through Installer.
Table 4. Linux file structure for the connector
Subdirectory of ProductDir |
Description |
/connectors/JText/CWJText.jar |
Contains classes used by the JText connector
only |
/connectors/JText/start_JText.sh |
The startup script for the generic connector |
/connectors/messages/JTextConnector.txt |
Message file for the connector |
/repository/JText/CN_JText.txt |
Repository definition for
the connector. The default name is CN_JText.txt. |
/connectors/JText/dependencies/ commons-net-1.1.0.jar, dependencies/ jakarta-oro-2.0.8.jar |
Third party.jar packaged with the connector |
Note:
All product pathnames are relative to the directory
where the product is installed on your system.
Verifying installation on i5/OS systems
By default, the adapter is installed
int he /QIBM/ProdData/WBIServer44/product directory (referred to
as ProductDir). Table 4 describes the i5/OS file structure used
by the connector, and shows the files that are automatically installed
during a typical installation. To verify the adapter installation
on an i5/OS system, change to the directory were you installed the
adapter and compare the contents to those listed in Table 5.
Table 5. i5/OS file structure for the connector
Directory |
Description |
ProductDir/connectors/JText |
Contains the connector CWJText.jar file and the start_JText.sh
startup file. |
ProductDir/repository/JText |
Contains the BIA_CN_JText.txt repository definition. |
ProductDir/connectors/JText/Dependencies |
Contains the license agreement, REAME files,
and the third-party commons-net-1.10.jar and jakarta-oro-2.0.0.jar files. |
ProductDir/connectors/messages |
Contains the JTextConnector.txt file and the JTextConnector_ll_TT.Ttxt
files (message files specific to a language (ll)
and a country or territory (TT)). |
ProductDir/lib |
Contains the WBIA.jar
file. |
ProductDir/bin |
Contains theCWConnEnv.sh file. |
Note:
You can quickly start the connector with the Console
function. For more information, refer to the online help provided
with the Console.
