If you encounter problems when you create TDI-based feeds, use these suggestions to troubleshoot the problems.
The TDI server does not start
If the TDI server port (the default port is 8071) is already in use, the TDI server will not start properly. Edit the MashupIntegrationServer.properties
file and set the httpPort
property to another unused port number. Go to: install-dir\\Hub\\installedApps\\Mashup Hub.ear\\mashuphub-enterprise.war\\server\\plugins\\com.ibm.mashuphub.plugin.tdi\\server\\MIS\\
. Use the netstat -an command to list the ports that are already in use.
After you change the port, the TDI server should start. When the TDI server starts, you can verify that the server and port are working properly by typing the http://localhost: [newPort]/mis/atom
URL in a browser window. A list of feed types should appear.
SAP feeds do not work
Ensure that the SAP Java™ Connector (JCo) component version 3.0.5 has been installed on the TDI server. See Creating a feed from SAP Application Functions
After the component is installed, the following files are located in the directory where MashupHub is installed: installation_path/Hub/TDI/platform
Error creating TDI, Domino, LDAP, or SAP feeds
It is often helpful to run the TDI server in console mode so that you can look for exception traces, which can help debug errors when you create feeds. To run the TDI server in console mode:
- Stop the TDI server:
Start the editMIS.bat file, which is located in the directory where MashupHub is installed: install-dir\\Hub\\installedApps\\Mashup Hub.ear\\mashuphub-enterprise.war\\server\\plugins\\com.ibm.mashuphub.plugin.tdi\\server\\.
Right-click AssemblyLines > 1_FeedServer and select Run.
- Log on to MashupHub as an administrator.
- Go to Settings -> Environment -> TDI Server Status.
Parent topic: Troubleshooting problems: imc3