Connectors
This section describes the changed behavior for connectors in the Spring 2017 release.
Google BigQuery Connector
Effective in the Spring 2017 release, you cannot override the Google BigQuery source table name in a Data Synchronization task and mapping. The Source Table Name property has been removed from the Data Synchronization task and mapping advanced properties.
Previously, in a Data Synchronization task and mapping, you were able to override the Google BigQuery source table name that you specified in the Source transformation.
REST V2 Connector
Effective in the Spring 2017 release, the following changes affect mappings that use REST V2 Connector:
- Single "body" string for requests containing JSON values
If JSON data value is passed to a REST request as a single string value, the double quotes inside the JSON value are now escaped. For example, using the value "{"emp":"abc","empid":"em01"}":
- - Prior to the Spring 2017 release, the request is constructed as {"emp":"abc","empid":"em01"}
- - Beginning with the Spring 2017 release, the request is constructed as {\"emp\":\"abc\",\"empid\":\"em01\"}
It is recommended that you expand the request body definition using Swagger and map individual fields. Informatica Global Support can help you generate the Swagger specification.
- Single element array values
Single values passed for properties defined as arrays are included in the request as arrays.
Prior to the Spring 2017 release, these values were included as individual values.
- Numeric values
Numeric values for text properties are included as text values.
Prior to the Spring 2017 release, numeric values for text properties were automatically included in the request as numeric.
- Fields with empty values
Fields with empty values are included in the request only if the following Secure Agent configuration property is set:
-DRestRequestMode=Strict
Earlier, fields with empty values were included in the request even when the fields were not mapped.
If you do not set the -DRestRequestMode=Strict property, unmapped fields are not included in the request by default.
To set the -DRestRequestMode=Strict property, perform the following steps:
- 1. Click Configure > Runtime Environments.
- 2. Select the Secure Agent that you use for REST V2 connections.
- 3. Click Edit on the View Secure Agents page.
- 4. Select the Data Integration Server service.
- 5. Select the DTM type.
- 6. Add the following property to an empty JVM Option: -DRestRequestMode=Strict
- 7. Click OK to save your changes.
- String literal values as "null"
If a property has a value of "null", it is treated as a null/empty value.
Prior to the Spring 2017 release, if a property had a value of "null", "null" was passed as a text value.
If your configuration is not affected by these behavior changes, no change is required in your mappings. However, if your mappings are affected by any of these changes, you can set the -DPromoteToArray=FALSE flag, or you can modify your mappings to work with the new behavior. From a long-term perspective, it is recommended that you change your mappings as soon as possible. The default value for -DPromoteToArray is true. The -DRestRequestMode=Strict property works only if you set -DPromoteToArray=TRUE.
To set the -DPromoteToArray=FALSE property so that Informatica Cloud treats the above situations the way it did in prior releases, perform the following steps:
- 1. Click Configure > Runtime Environments.
- 2. Select the Secure Agent that you use for REST V2 connections.
- 3. Click Edit on the View Secure Agents page.
- 4. Select the Data Integration Server service.
- 5. Select the DTM type.
- 6. Add the -DPromoteToArray=FALSE property to an empty JVM Option.
- 7. Click OK to save your changes.
For more information, contact Informatica Global Customer Support.
SAP Connector
Effective in the Spring 2017 release, SAP Connector contains the following changes:
- •You must copy the SAP JCo libraries to the following directory:
<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\ext\deploy_to_main\bin\rdtm-extra\tpl\sap
Previously, if you were using a Secure Agent version earlier than 30, you copied the SAP JCo libraries to the following directory:
<Informatica Secure Agent installation directory>\main\bin\rdtm-extra\tpl\sap
- •You must copy the SAP NetWeaver RFC SDK 7.20 libraries and the sapnwrfc.ini file to the following directory:
<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\ext\deploy_to_main\bin\rdtm
Previously, if you were using a Secure Agent version earlier than 30, you copied the SAP NetWeaver RFC SDK 7.20 libraries and the sapnwrfc.ini file to the following directory:
<Informatica Secure Agent installation directory>\main\bin\rdtm