Develop > Developer Reference > Creating Discovery and Integration Adapters > Developing Generic Database Adapters > Troubleshooting and Limitations – Developing Generic Database Adapters

Troubleshooting and Limitations – Developing Generic Database Adapters

This section describes troubleshooting and limitations for the generic database adapter.

ClosedGeneral Limitations
  • When you update an adapter package, use Notepad++, UltraEdit, or some other third-party text editor rather than Notepad (any version) from Microsoft Corporation to edit the template files. This prevents the use of special symbols, which cause the deployment of the prepared package to fail.

  • In most of the cases, after making a change, it is needed to reload the adapter on the probe side, otherwise the adapter will not function properly

    1. Log in to the probe JMX console: https://localhost:8453/
    2. Locate the adapters bean, and reload adapter with the integration point name.

    If the adapter is not reloaded after each change, issues may occor (wrong error messages, query failures, and so on).

ClosedJPA Limitations

  • All tables must have a primary key column.

  • CMDB class attribute names must follow the JavaBeans naming convention (for example, names must start with lower case letters).

  • Two CIs that are connected with one relationship in the class model must have direct association in the database (for example, if node is connected to ticket there must be a foreign key or linkage table that connects them).

  • Several tables that are mapped to the same CIT must share the same primary key table.

ClosedFunctional Limitations

  • You cannot create a manual relationship between the CMDB and federated CITs. To be able to define virtual relationships, a special relationship logic must be defined (it can be based on properties of the federated class).

  • Federated CITs cannot be trigger CITs in an impact rule, but they can be included in an impact analysis TQL query.

  • A federated CIT can be part of an enrichment TQL, but cannot be used as the node on which enrichment is performed (you cannot add, update, or delete the federated CIT).

  • Using a class qualifier in a condition is not supported.

  • Subgraphs are not supported.

  • Compound relationships are not supported.

  • The external CI CMDBid is composed from its primary key and not its key attributes.

  • A column of type bytes cannot be used as a primary key column in Microsoft SQL Server.

  • TQL query calculation fails if attribute conditions that are defined on a federated node have not had their names mapped in the orm.xml file.

Send Help Center feedback