Problems with data sources

The application is having difficulty when it is accessing a data source. The data source can be either an ODBC data source or a JDBC data source. FTM cannot access a data source for a number of reasons:

• The ODBC settings in the ODBC initialization file might be incorrect. Possible errors are shown in the following list:
  • The database driver location might be incorrectly defined - check that this location exists and that the spelling is correct.
  • The database server location, port number, or both, are not defined or are incorrect. For some databases, these values need to be defined even if the database is on the same system as the driver.
  • The database name is misspelled or the database that you are trying to access.
  • Some databases require more parameters that need to be defined in the ODBC initialization file. These parameters are listed in the ODBC section of the documentation that relates to the database.
  • The username and password for the database that is used by the broker instance might be set incorrectly, which results in an error that indicates the credentials were not recognized during the authentication process.
  • The password that is used in the security identity was maybe changed, expired, or was locked out. A symptom of this problem is that the connection works correctly for some time but then fails.
• The JDBC settings for the IBM® App Connect Enterprise instance might be set incorrectly. Details on these settings and how to report on them can be found in the relevant section of the installation documentation. Issues that might arise are shown in the following list:
  • The initial settings used to connect IBM App Connect Enterprise to the database by using the mqsicreateconfigurableservice command might be incorrect. The critical parameters are the URL format and the class names. The appropriate values for these parameters are found in the documentation for the particular database that you are using (for example, Db2®).
  • Properties that are defined in the URL format might not have been defined by using the mqsichangeproperties command.
  • The database server location and port number might have been incorrectly defined by using the mqsichangeproperties command. For some databases, these values must be defined even if the database is on the same system as the driver.
  • The database driver location (defined in the jarsURL property) might have been incorrectly defined by using the mqsichangeproperties command. You need to ensure that the location is correct. For example, verify that the driver JAR files are located there.
  • The security identity was not created or was not applied to the broker instance. Details of the current settings can be found by using the mqsireportproperties command.
  • The properties of the security identity were incorrectly set, which results in an error that indicates that the credentials were not recognized during the authentication process.
  • The password that is used in the security identity was maybe changed, expired, or was locked out. A symptom of this problem is that the connection works correctly for some time but then fails.
• The database driver might be the incorrect version for the database or operating system that is being used. For example, you might need to use a 64-bit driver version to access a 64-bit database. The database documentation should be consulted. Sometimes, you need to add more parameters to the ODBC initialization file or set different properties on the JDBC provider.
• The database name might be incorrect. If you are accessing the database directly from your code, make sure that the spelling is correct. If you are using a User Defined Property (UDP), make sure that the property was populated correctly (or at all).
• The database schema might be incorrect. If you are accessing the database directly from your code, make sure that the spelling is correct. If you are using a User Defined Property (UDP), make sure that the property was populated correctly (or at all).