PowerExchange Adapters
This section describes release tasks for PowerExchange adapters in version 10.2.
PowerExchange Adapters for PowerCenter
This section describes release tasks for PowerCenter adapters in version 10.2.
PowerExchange for Amazon Redshift
Effective in version 10.2, for existing mappings where public schema is selected, ensure that the schema name is correct and works for the Redshift table. The public schema might not work for all the tables.
For more information, see the Informatica 10.2 PowerExchange for Amazon Redshift User Guide for PowerCenter
PowerExchange for Amazon S3
Effective in version 10.2, when you upgrade from 9.5.1 or 9.6.1, the upgrade process does not retain all property values in the connection. After you upgrade, you must reconfigure the following properties:
Property | Description |
|---|
Access Key | The access key ID used to access the Amazon account resources. Required if you do not use AWS Identity and Access Management (IAM) authentication. Note: Ensure that you have valid AWS credentials before you create a connection. |
Secret Key | The secret access key used to access the Amazon account resources. This value is associated with the access key and uniquely identifies the account. You must specify this value if you specify the access key ID. Required if you do not use AWS Identity and Access Management (IAM) authentication. |
Master Symmetric Key | Optional. Provide a 256-bit AES encryption key in the Base64 format when you enable client-side encryption. You can generate a key using a third-party tool. If you specify a value, ensure that you specify the encryption type as client side encryption in the target session properties. |
For more information, see the Informatica 10.2 PowerExchange for Amazon S3 User Guide for PowerCenter
PowerExchange for Microsoft Dynamics CRM
When you upgrade from an earlier version, you must copy the .jar files in the installation location of 10.2.
- •For the client, if you upgrade from 9.x to 10.2, copy the local_policy.jar, US_export_policy.jar, and cacerts files from the following 9.x installation folder <Informatica installation directory>\clients\java\jre\lib\security to the following 10.2 installation folder <Informatica installation directory>\clients\java\32bit\jre\lib\security.
If you upgrade from 10.x to 10.2, copy the local_policy.jar, US_export_policy.jar, and cacerts files from the following 10.x installation folder <Informatica installation directory>\clients\java\32bit\jre\lib\security to the corresponding 10.2 folder.
- •For the server, copy the local_policy.jar, US_export_policy.jar, and cacerts files from the <Informatica installation directory>java/jre/lib/security folder of the previous release to the corresponding 10.2 folder.
When you upgrade from an earlier version, you must copy the msdcrm folder in the installation location of 10.2.
- •For the client, copy the msdcrm folder from the <Informatica installation directory>\clients\PowerCenterClient\client\bin\javalib folder of the previous release to the corresponding 10.2 folder.
- •For the server, copy the msdcrm folder from the <Informatica installation directory>/server/bin/javalib folder of the previous release to the corresponding 10.2 folder.
PowerExchange for SAP NetWeaver
Effective in version 10.2, Informatica implemented the following changes in PowerExchange for SAP NetWeaver support for PowerCenter:
- Dropped Support for the CPI-C Protocol
Effective in version 10.2, Informatica dropped support for the CPI-C protocol.
Use the RFC or HTTP protocol to generate and install ABAP programs while reading data from SAP tables.
If you upgrade ABAP mappings that were generated with the CPI-C protocol, you must complete the following tasks:
- 1. Regenerate and reinstall the ABAP program by using stream (RFC/HTTP) mode.
- 2. Create a System user or a communication user with the appropriate authorization profile to enable dialog-free communication between SAP and Informatica.
For more information, see the Informatica PowerExchange for SAP NetWeaver 10.2 User Guide for PowerCenter.
- Dropped Support for ABAP Table Reader Standard Transports
Effective in version 10.2, Informatica dropped support for the ABAP table reader standard transports. Informatica will not ship the standard transports for ABAP table reader. Informatica will ship only secure transports for ABAP table reader.
If you upgrade from an earlier version, you must delete the standard transports and install the secure transports.
For more information, see the Informatica PowerExchange for SAP NetWeaver 10.2 Transport Versions Installation Notice.
- Added Support for HTTP Streaming for ABAP Table Reader Mappings
Effective in version 10.2, when you run ABAP mappings to read data from SAP tables, you can configure HTTP streaming.
To use HTTP stream mode for upgraded ABAP mappings, perform the following tasks:
- 1. Regenerate and reinstall the ABAP program in stream mode.
- 2. Create an SAP ABAP HTTP streaming connection.
- 3. Configure the session to use the SAP streaming reader, an SAP ABAP HTTP streaming connection, and an SAP R/3 application connection.
Note: If you configure HTTP streaming, but do not regenerate and reinstall the ABAP program in stream mode, the session fails.