The following subsections describe the installed file structure of the IMS/TM connector on a UNIX or Windows system.
Table 19 describes the UNIX file structure used by the
connector.
Table 19. Installed UNIX file structure for the MAS connector for IMS/TM
Subdirectory of $ProductDir | Description |
---|---|
connectors/Ims_tm | Contains the connector CWIMS_TM.jar and the start_IMS_TM.sh files. The startup script for the connector. The script is called from the generic connector manager script. When you click Install from Connector Configurator (WebSphere MQ Integration Broker as the integration broker) or the Connector Configuration screen of System Manager (ICS as the integration broker), the installer creates a customized wrapper for this connector manager script. When the connector works with ICS, use this customized wrapper only to start and stop the connector. When the connector works with WebSphere MQ Integration Broker, use this customized wrapper only to start the connector; use mqsiremotestopadapter to stop the connector. |
connectors/messages | Contains the IMS_TMConnector.txt file. |
repository/Ims_tm | Contains the CN_IMS_TM.txt file. |
For more information on installing the connector component, refer to one of the following guides, depending on the integration broker you are using:
To install the connector on a Windows system, run IBM WebSphere InterChange
Server Installer and select the connector. IBM WebSphere InterChange
Server Installer installs standard files associated with the connector.
Table 20 describes the Windows file structure used by the
connector.
Table 20. Installed Windows file structure for the MAS connector for IMS/TM
Subdirectory of %ProductDir% | Description |
---|---|
connectors\Ims_tm | Contains the connector CWIMS_TM.jar and the start_IMS_TM.bat files. |
connectors\messages | Contains the IMS_TMConnector.txt file. |
repository\Ims_tm | Contains the CN_IMS_TM.txt file. |
For more information on installing the connector component, refer to one of the following guides, depending on the integration broker you are using: