Integrity

Prerequisites

In order to establish a connection between the adapter and the Integrity server, the API based connection must be enabled on the Integrity server side. This is usually controlled through a configuration file <server>/config/client/IntegrityClientSite.rc.

For testing purposes the policies ICAllowAllConnectionPolicy and ICNoAuthenticationPolicy should be enabled. Consult the Integrity documentation for more details on a production type configuration.

Supported Native Datatypes

The following tables shows which native datatypes are supported and how they translate into symphony datatypes:

Native datatype	Symphony datatype
integer	Integer
pick	List
float	Double
logical	Boolean
date	Date
datetime	Date/Time
shorttext	String
longtext	String
rich	Markup
user (single)	Identity

note

When a user field is transferred having multiple users selected only the first one in the Integrity response will be taken into account

Custom query

The adapter provides a builtin query that is based on the project and type specified in the configuration.

To allow customers more detailed control of the query, a custom query can be specified.

The custom queries available in the configuration are all queries of the connected user.

warning

If you configure a custom query, you are responsible that the query result contains only objects from the configured project and type. Queries that do not satisfy this condition will lead to unexpected results and behavior.

Troubleshooting

If you experience issues, where the error message from the MKS api is unclear such as null, you can enable more detailed logging for tke MKS api communication by adding the following java system property:

IntegrityAPI.logging.enabled=true

This will by default produce enhanced logging in a file called mksapi.log located in the java temp folder. If you want to control the location of the log file, add the following java system property:

IntegrityAPI.log.filename=/home/me/mksapi.log