Skip navigation

Cloud Integration Hub Technical Deep Dive Webinar and Demo

Scott Hedrick, Director Product Marketing, Etty Afriat, Director Product Management, Amit Vaswani, Product Specialist Leader
Sep 6, 2017 8:00 AM PT     Click here to Register

 

Are you starting to build up difficult to manage data integration spaghetti as your cloud data integrations proliferate? Organize and simplify multi-point cloud data integrations with Cloud Integration Hub, the modern publish/subscribe solution for efficiency and productivity. Reduce data transfer and API charges by removing redundant Cloud synchronizations with Informatica’s Hub for data. Jumpstart your use of the Cloud Integration Hub with the new Salesforce Accelerator. Existing Informatica Intelligent Cloud Services Premium and Advanced customers can get started right way with the one year of basic Cloud Integration Hub with their subscriptions.

In this webinar, we will:

 

  • Provide a technical overview of the key capabilities and value of Cloud Integration Hub by Informatica experts
  • Demo the latest version of Cloud Integration Hub including the new Salesforce Accelerator
  • Show how existing Informatica Intelligent Cloud Services customers can get started with the one year of basic Cloud Integration Hub included in their subscriptions.


We will be moving the data center for App2. The migration should be seamless to you, and there will be no product changes. If you currently whitelist Informatica Cloud IP addresses, you will need to whitelist the new IP addresses before the data center move. For you to validate your whitelisting, go to https://app20.informaticacloud.com/saas/icsalive.html from any browser within the network to verify you can connect and get the message "ICS NODE IS ALIVE".

 

What IP Addresses need to be whitelisted?

  1. 168.128.27.61/32
  2. 168.128.27.47/32
  3. 168.128.29.12/32
  4. 168.128.29.92/32

 

Can I remove the old IP addresses?

No you cannot. Please retain the IP addresses as we use these for DR and an entry point for app.informaticaondemand.com.

 

Why are we moving data centers?

The new data center has the latest infrastructure and can provide room for growth, higher availability and reliability.

 

Will there be any product changes?

No, we will not be making any changes to the product during this move. This is not a release of any product, and there will be no product enhancements or changes during the move.

 

Is there an update of the agent?

The agent will not be changed in any way. There are no application, patch, package or agent updates during this move.

 

Do I have to whitelist the IPs to run jobs after the migration?

You only must whitelist the IP’s if you had to do this for the current data center. We strongly recommend using the pre-release agent and testing connectivity to verify and validate your organization’s readiness.

 


If you have any questions please contact us through Global Customer Support at 1-877-INFAHELP from the US, or Worldwide click here.  You may also email pre-release@informatica.com for any questions or concerns regarding this notice.

 

For more information on IP Address Ranges in Informatica Cloud, including previous IP ranges see this KB:112401

ROOT CAUSE ANALYSIS REPORT

 

 

OVERVIEW

Applicable to

Informatica Customers on APP2 Only

PRODUCTS AFFECTED

ICS, ICRT, DQ RADAR, B2B

   INCIDENT START/END: June 20, 2017 22:35 PDT – June 21, 2017 15:15 PDT

RCA COMPLETED:  6/22/2017

INCIDENT DETAILS

INCIDENT SUMMARY

The ICS product hosted on “APP2” became unavailable to handle customer traffic via secure agents caused by a “channel issue due to insufficient memory”. During the Tuesday portion, service was intermittent and then escalated into full outage during Wednesday. This caused other dependent services that rely on ICS, including ICRT, DQ Radar and API Gateway to be unavailable. The customer impact was inability to process any jobs through the Informatica Cloud Services.  The root cause of this incident was server memory / swap space exhaustion on the channel server nodes.  This caused the service response to be intermittent or unavailable, since the agent to host communication was impacted. 

ROOT CAUSE ANALYSIS

The memory footprint on the channel server nodes have increased after the recent Informatica Cloud upgrades as part of new functionality, but within the limits of tolerance. There was errant backup process that started consuming 50% of the available, 90% of CPU time and swap space, and this ‘caused the machine to hang and become unavailable.  This resulted in the communication failure between the agents and host and caused ICS tasks to hang or fail.  Also, real time messages were not processed during this disruption.

 

The initial symptom was observed Tuesday night (June 20th) 22:35 PDT and task and process failures were detected for a few Orgs.   Remediation was made to address the problem initially, however the problem reappeared Wednesday morning (June 21st) at approximately 07:30 PDT, and caused the channel server nodes to go down causing the ICS, ICRT and related services to become unavailable for all customers on APP2 on Wednesday morning (June 21st).

 

Note: A Disaster Recovery (DR) process was started the morning of June 21st, but was later stopped once we addressed the issue on the APP2 host.

 

Once the problem was addressed on the channel server nodes and the nodes were restarted, they operated normally.   ICS tasks were manually restarted, or automatically executed, based on schedules.  

 

Applicable to ICRT Customer: Post an agent restart ICRT processes operated normally.

Applicable to ICRT outbound messaging customers: The ICRT Salesforce outbound listener was resumed to process the incoming messages from Salesforce.

 

 

 

RISK-REDUCTION REMEDIATION ACTIONS TAKEN

Actions that have already been taken to reduce the risk of a future occurrence.

DATE

 

ACTION TAKEN and Planned for this incident

6/21/2017

1. Focus on Audit system parameters monitoring and alerts. Swap space monitoring for this channel server was missing. We now added Swap space monitoring to the monitoring/alerting system. Tested and working fine.

2. Introducing an additional channel server to distribute the load. Adding this additional server will not impact customers.

3. Re-evaluate the emergency notification and escalation process, including more frequent simulations.

4. RCA with Vendor in-progress to determine the backup process impact on the system, which triggered a spike in swap space utilization.   The backup service is an optional service and has been turned OFF on the channel server nodes.

 

Long Term Remediation Plan

Roadmap to a quicker recovery to reduce the downtime duration

DATE

Plans

7/14/2017

Review the current DR process and adjust criteria for when to start the DR process.

7/14/2017

Work with hosting provider and gain full visibility of all processes running on the nodes.

7/14/2017

Add additional monitoring for relevant system parameters and define thresholds on which we can get alerted.

8/15/2017

Additional emergency communication & notification plans (other than trust site updates).

TBD

An enhancement to the Trust Site to subscribe for notifications.

Preface/Overview:

 

The main goal of this feature is to encourage/enable existing PowerCenter customers to leverage the wide connectivity options available in Informatica Cloud.

Informatica Cloud has over 150+ Connectors, a much higher number compared to the connectors available in PowerCenter.

 

Using this feature/architecture PowerCenter customers can run jobs where the source/target is an Informatica Cloud-based connector.

 

CaaS - Features

 

·        The CaaS architecture is designed such that minimal Informatica Cloud knowledge/skill is required by  a PowerCenter Developer/Administrator

·        Tasks like developing a CaaS based mapping and running it, follows the regular PowerCenter clients and development flow.

·        The only additional steps required are:

o   Login to the Informatica Cloud Server (web portal)

o   Download and install the Informatica Cloud Secure Agent.

o   Create connections in the ICS Org, for the desired end-points.

               (All these steps need to be performed only once)

·        Currently, several ICS connectors are supported by CaaS architecture. More connectors will be added to this list soon.

·        Pros :

o   One can leverage ICS Cloud Connectors from within PowerCenter

o   No learning curve i.e. no additional skill required for PowerCenter developer.

o   Seamless integration between PowerCenter and Informatica Cloud

o   Informatica internal advantage – If a connector is already available on Cloud need not develop a PowerCenter connector for the same.

·        Cons :

o   Requires Secure Agent installation in the customer’s network.

o   Performance can be slower compared to a regular task as this architecture involves data transfer between 2 DTMs (Described below).

o   Firewall modifications to enable PowerCenter Server Communication to the ICS Server.

 

Mapping Internal Conversion:

 

A CaaS based PowerCenter mapping will internally be converted to two mappings as described in the below diagram:

pc1.jpg

                     (Runs on Secure Agent machine)                         (Runs on PowerCenter Server machine)

 

 

Run-time behavior of a CaaS based PC Mapping:

 

Below figure show the activities that happen when a CaaS based job is triggered from PowerCenter.

In the diagram, the scenario is a PC Mapping with CaaS based source and a regular target.

 

pc2.jpg

 

 

1)     PowerCenter Integration Service spawns the pmdtm process.

2)     The pmdtm process detects that the source is a CaaS based source (not a regular source) and sends a request to the ICS Server.

The request has required mapping metadata (ICS Connection, ICS Source Object etc.)

3)     ICS Server generates a Cloud Mapping on the fly and sends an execute request to the Secure Agent.

4)     The Secure Agent spawns a DTM process (Cloud DTM) and executes the generated Cloud Mapping.

5)     The Cloud DTM process reads data from the Source end-point.

6)     The Cloud DTM feeds this data to the PowerCenter pmdtm.

7)     PowerCenter pmdtm executes any other transformation in the PowerCenter mapping and finally loads data into the Target.

Are you facing issues after the Informatica Cloud Spring '17 upgrade? We are here to help. We have identified some of the common issues encountered by users and pulled together a list of solutions to help you address them. Read on to know more.

 

Note: If you have any concerns please open a case with Informatica Support by clicking on Contact Support option within Informatica Cloud.

 

SUMMARY

 

At the bottom of this post, we have a running list of known issues in Spring '17 upgrade and their solutions. We will continue to update this list so check back later for more updates. If you already have a network.informatica.com login, we recommend following  this post so that you can automatically receive updates for any new issues.

 

You can also follow us on Twitter @INFAsupport for all the latest updates on Informatica Cloud Spring '17

 

ISSUES AND SOLUTIONS (APP2/3) April 22, 2017

Spring '17 Documentation

Informatica Cloud Spring 2017 - Helping customers accelerate their journey to the cloud

Issue: All tasks are failing post the upgrade and session log is not generated.

Internal error. The DTM process terminated unexpectedly

 

Solution:

 

Check if the session log directory is a non-default value. If so, revert it to the default value.

Steps:

Login to the ICS UI, Configure > Secure Agent.

Under System Configuration Details, choose Service = Data Integration Server and Type = DTM.

Check if the value of setting ‘$PMSessionLogDir’ is the default value '$PMRootDir\..\logs'.

If not, edit and revert back to the default value.

 

Wait for the Data Integration Service to restart automatically and then start the task.

Issue: The upgrade was not successful. [================================  02/06/2016  1:36:27.41  copy upgrades\fullupgrade\FileLockDetect.exe FileLockDetect.exe        1 file(s) copied. Waiting for file handles to clean up ERROR: Input redirection is not supported, exiting the process immediately. JAVA_HOME: .\jre agentCoreMajorUpgrMarker exists  Do major upgrade.  Interim agent exists before upgrade, so remove it first.  main2\tomcat\work\Tomcat - The directory is not empty. main2 cannot be removed.  ]


 

Solution: Please visit the discussion link: https://network.informatica.com/message/199683

Issue: “[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database driver error” with Oracle/SQL Server/MySQL tasks after Informatica Cloud Spring 2017 upgrade on Windows Secure Agent

 

Solution:

This error may happen if the Registry entries that are sent as part of this upgrade were not updated during the upgrade.

Please follow the steps in this KB to resolve the issue: https://kb.informatica.com/solution/23/Pages/61/511902.aspx

Issue: The test connection for $SAP_CNX failed. Could not initialize class com.sap.conn.

jco.rt.JCo.JCoRuntimeFactory

The test connection for $SAP_CNX failed. Error getting the version of the native layer: Java.lang.UnsatisifiedLinkError: no sapjco3 in java.library.

 

Solution: You need to have the correct JCO libraries for the 64 bit Agent in the environment. If you have moved from 32 to 64 bit agent, then you need to download and setup the JCO files before connectivity to SAP can be established.

 

See the Solution in this KB 504336

Issue: Tasks with Hierarchy Builder transformation and REST V2 connector not processing data after Spring 2017 upgrade.

 

Solution:

This can happen if hierarchical data is sent to a string field in the REST V2 connector. The Request payload seen in the session log would show that there are “\” escape characters added to the request.

 

This issue can be resolved by adding a JVM Option to the Secure Agent configuration.

-      Navigate to Configure > Runtime Environments > Secure Agent.

-      Select “Data Integration Server” under Service and select Type as “DTM”

-      Edit the JVMOption1/2/3 etc.(whichever is available) and add the parameter '-DPromoteToArray=false'

-      Click on “Ok” to save the setting and wait for the Data Integration service to restart.

-      Run the task after the new Data Integration service is up.

Issue: Tasks that use Business Services will fail if the Business Services are edited, Existing unmodified tasks and newly created tasks will work fine.

 

Details:

The Spring 2017 release includes the following enhancement for REST V2 Connector:

 

A fault group to process fault response is enabled when you create a new business service or edit an existing business service.

 

After you upgrade to Spring 2017 release, if you edit a business service that is used in a REST V2 midstream transformation, the respective mapping will fail.


Solution:

 

To avoid this issue, do not edit the business service. If you edit the business service, recreate the midstream transformation and map all the required fields.

Issue: CA Certs Post Upgrade Task

 

 

Solution: ONLY if after past releases you have had to copy security Jars from the Jre2 backup directory back to the Jre directory, you will need to copy these files to a new location as the directory structure will change.

 

1.      Copy the local_policy.jar and the US_export_policy.jar files from the following directory:

<Secure Agent installation directory>\jre2\lib\security

2.      Paste the jar files to the following directory:

<Secure Agent installation directory>\jre\lib\security

3.      Restart the agent


connectors using security certificates - Amazon (Redshift, S3), Microsoft Dynamics CRM

Issue: Jobs on Windows using ODBC fail with the following error: Data source name not found and no default driver specified Database driver error.


Solution: The agent should run as an Administrator

During the upgrade the agent will update the registry to add need ODBC entries. If your agent does not have access to update the registry you may face the following error:

WRT_8001 Error connecting to database... WRT_8001 [Session s_dss_000GSG0I0000000000xx Username YOURUSER Error -1 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using username and connection string [odbc://dbtype=<oracle or SQLServer>;host=,host.;port=<port>;database=<database>].]

This occurs in Windows for Oracle and SQL Server type connections.

 

Cause: Since there is a new ODBC driver for oracle and SQL server, as a part of upgrade, the registry will be updated to add new entries for these 2 drivers, if the user running the agent does not have permission to modify the registry entries, then these entries will not be added to the registry, hence when the task tried to load the drivers, it looks for registry entry and fails.

 

Solution: If you are not running your agent as an Administrator we recommend you run as an Administrator before the upgrade. KB149494 has the steps to run as an Administrator.

 

What if I face the above error after the upgrade?

 

1) Trigger the upgrade by modifying the infaagentversion file (in a text editor) in {agent}/main and change 26.* - to 25.*

2) Restart the agent as admin (steps same as in KB149494)

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icoss1.informaticacloud.com/saas/download/upgrade-22.3.2.1.0.0.0/fullupgrade/linux32/upgrade.zip: [Download failed due to HTTP 403 response.]]

 

Solution: Please visit the document  link: Secure Agent IP Address KB:112401

Issue: Upgrade failure. [Cannot download upgrade file:https://icsdownloadsecure.informatica.com/ICS/r23/mirror2/download/upgrade-22.3.2.1.0.0.0/fullupgrade/win32/upgrade.zip: [Download failed due to HTTP 502 response.]]

 

Solution: This is because our mirror sites have not been whitelisted in your network. Please contact Informatica Cloud Support with your orgid, so that we can push the download via a secure site.

Issue: ODBC DSN not found on Linux after the upgrade will encounter the following error:

The connection test failed because of the following error: [unixODBC][Driver Manager]Data source name not found, and no default driver specified (0)


Solution:


This is because the odbc.ini file was in the main directory and it was backed up to main2 folder during the upgrade.

To fix the issue copy over the odbc.ini file from infaagent/main2 to infaagent/main.

Also you should store the odbc.ini outside of main, going forward, or keep a copy in rdtm-extra directory, so it is copied back automatically after future upgrades.

Issue: Copy Customized connector configuration files (if any)

If any of your licensed connector has configuration files, custom configured in your Informatica cloud secure agent, it is recommended that you copy these files

From

<Secure Agent installation directory>\main2\bin\rdtm\javalib\<plugin ID>\

 

To

<Secure Agent installation directory>\downloads\<latest connector zip package>\package\rdtm\javalib\<Plugin ID>

 

And

 

From:

<Secure Agent installation directory>\main2\tomcat\plugins\<plugin ID>\

 

To

<Secure Agent installation>\downloads\<latest connector zip package>\package\plugins\<Plugin ID>

 

connectorConfig File
AvaturecustomFields.ini
Birstbirstconfiguration.ini
Box APIconfig.properties
Coupacoupa.ini, read.xsd
Dropboxconfig.ini
Eloqua Bulk APIActivityConfig.json
Google APIconfig.properties
HadoopsetHadoopConnectorClassPath.sh
JDBCjdbc.ini
Jiraconfig.ini, jirafields.ini
JSON Targetconfig.ini
Marketoactivityattributes.csv
Open AirOpenAirCodes.properties
Quickbooks V2connectionparameters.ini
Workdayfields.ini
XML Sourceconfig.ini

Issue: Will Discovery IQ package available in Informatica Spring 2017 release.

 

During R27 upgrade, DiscoveryIQ package would be automatically removed and you may want to uninstall DiscoveryIQ agent  (especially windows agent env) from your environment.

Please refer to blog post for details of supported features of DiscoveryIQ and steps to uninstall DiscoveryIQ agent.

Issue:Tasks that use ODBC Connection, configured with DataDirect SequeLink driver, fail with error:

Specified driver could not be loaded due to system error  182:  (DataDirect SequeLink 6.0, C:\Program Files\DataDirect\slodbc60\dwslk22.dll).

 

Solution:

Copy the following files from the SequeLink/main2 folder

icuuc34.dll

libeay32.dll

ssleay32.dll

to

%AGENT_HOME%\downloads\package-ICSAgent_Rxx\package\ICS\main\bin\rdtm folder.

(Choose option ‘Copy and Replace’ when prompted)

 

This change will cause tasks that use Salesforce Connection with API version 32 or less to fail with:

Couldn't load the library [pmsfdcXXX.dll] for plug-in #310600.  Error msg: [Database driver event...Error occurred loading library [pmsfdcXXX.dll]. System error encountered is 182. Error text is The operating system cannot run %1.].

 

To resolve the problem with the Salesforce connection, change the Service URL in Salesforce to use API version 33 or higher.

 

ISSUES AND SOLUTIONS (APP) April 15, 2017

Spring '17 Documentation

Informatica Cloud Spring 2017 - Helping customers accelerate their journey to the cloud

Issue: The upgrade was not successful. [================================  02/06/2016  1:36:27.41  copy upgrades\fullupgrade\FileLockDetect.exe FileLockDetect.exe        1 file(s) copied. Waiting for file handles to clean up ERROR: Input redirection is not supported, exiting the process immediately. JAVA_HOME: .\jre agentCoreMajorUpgrMarker exists  Do major upgrade.  Interim agent exists before upgrade, so remove it first.  main2\tomcat\work\Tomcat - The directory is not empty. main2 cannot be removed.  ]


 

Solution: Please visit the discussion link: https://network.informatica.com/message/199683

Issue: The test connection for $SAP_CNX failed. Could not initialize class com.sap.conn.

jco.rt.JCo.JCoRuntimeFactory

The test connection for $SAP_CNX failed. Error getting the version of the native layer: Java.lang.UnsatisifiedLinkError: no sapjco3 in java.library.

 

Solution: You need to have the correct JCO libraries for the 64 bit Agent in the environment. If you have moved from 32 to 64 bit agent, then you need to download and setup the JCO files before connectivity to SAP can be established.

 

See the Solution in this KB 504336

Issue: CA Certs Post Upgrade Task

 

 

Solution: ONLY if after past releases you have had to copy security Jars from the Jre2 backup directory back to the Jre directory, you will need to copy these files to a new location as the directory structure will change.

 

1.      Copy the local_policy.jar and the US_export_policy.jar files from the following directory:

<Secure Agent installation directory>\jre2\lib\security

2.      Paste the jar files to the following directory:

<Secure Agent installation directory>\jre\lib\security

3.      Restart the agent


connectors using security certificates - Amazon (Redshift, S3), Microsoft Dynamics CRM

Issue: Jobs on Windows using ODBC fail with the following error: Data source name not found and no default driver specified Database driver error.


Solution: The agent should run as an Administrator

During the upgrade the agent will update the registry to add need ODBC entries. If your agent does not have access to update the registry you may face the following error:

WRT_8001 Error connecting to database... WRT_8001 [Session s_dss_000GSG0I0000000000xx Username YOURUSER Error -1 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using username and connection string [odbc://dbtype=<oracle or SQLServer>;host=,host.;port=<port>;database=<database>].]

This occurs in Windows for Oracle and SQL Server type connections.

 

Cause: Since there is a new ODBC driver for oracle and SQL server, as a part of upgrade, the registry will be updated to add new entries for these 2 drivers, if the user running the agent does not have permission to modify the registry entries, then these entries will not be added to the registry, hence when the task tried to load the drivers, it looks for registry entry and fails.

 

Solution: If you are not running your agent as an Administrator we recommend you run as an Administrator before the upgrade. KB149494 has the steps to run as an Administrator.

 

What if I face the above error after the upgrade?

 

1) Trigger the upgrade by modifying the infaagentversion file (in a text editor) in {agent}/main and change 26.* - to 25.*

2) Restart the agent as admin (steps same as in KB149494)

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icoss1.informaticacloud.com/saas/download/upgrade-22.3.2.1.0.0.0/fullupgrade/linux32/upgrade.zip: [Download failed due to HTTP 403 response.]]

 

Solution: Please visit the document  link: Secure Agent IP Address KB:112401

Issue: Upgrade failure. [Cannot download upgrade file:https://icsdownloadsecure.informatica.com/ICS/r23/mirror2/download/upgrade-22.3.2.1.0.0.0/fullupgrade/win32/upgrade.zip: [Download failed due to HTTP 502 response.]]

 

Solution: This is because our mirror sites have not been whitelisted in your network. Please contact Informatica Cloud Support with your orgid, so that we can push the download via a secure site.

Issue: ODBC DSN not found on Linux after the upgrade will encounter the following error:

The connection test failed because of the following error: [unixODBC][Driver Manager]Data source name not found, and no default driver specified (0)


Solution:


This is because the odbc.ini file was in the main directory and it was backed up to main2 folder during the upgrade.

To fix the issue copy over the odbc.ini file from infaagent/main2 to infaagent/main.

Also you should store the odbc.ini outside of main, going forward, or keep a copy in rdtm-extra directory, so it is copied back automatically after future upgrades.

Issue: Copy Customized connector configuration files (if any)

If any of your licensed connector has configuration files, custom configured in your Informatica cloud secure agent, it is recommended that you copy these files

From

<Secure Agent installation directory>\main2\bin\rdtm\javalib\<plugin ID>\

 

To

<Secure Agent installation directory>\downloads\<latest connector zip package>\package\rdtm\javalib\<Plugin ID>

 

And

 

From:

<Secure Agent installation directory>\main2\tomcat\plugins\<plugin ID>\

 

To

<Secure Agent installation>\downloads\<latest connector zip package>\package\plugins\<Plugin ID>

 

connectorConfig File
AvaturecustomFields.ini
Birstbirstconfiguration.ini
Box APIconfig.properties
Coupacoupa.ini, read.xsd
Dropboxconfig.ini
Eloqua Bulk APIActivityConfig.json
Google APIconfig.properties
HadoopsetHadoopConnectorClassPath.sh
JDBCjdbc.ini
Jiraconfig.ini, jirafields.ini
JSON Targetconfig.ini
Marketoactivityattributes.csv
Open AirOpenAirCodes.properties
Quickbooks V2connectionparameters.ini
Workdayfields.ini
XML Sourceconfig.ini

Issue: Will Discovery IQ package available in Informatica Spring 2017 release.

 

During R27 upgrade, DiscoveryIQ package would be automatically removed and you may want to uninstall DiscoveryIQ agent  (especially windows agent env) from your environment.

Please refer to blog post for details of supported features of DiscoveryIQ and steps to uninstall DiscoveryIQ agent.

Issue: Tasks that use Business Services will fail if the Business Services are edited, Existing unmodified tasks and newly created tasks will work fine.

 

Details:

The Spring 2017 release includes the following enhancement for REST V2 Connector:

 

A fault group to process fault response is enabled when you create a new business service or edit an existing business service.

 

After you upgrade to Spring 2017 release, if you edit a business service that is used in a REST V2 midstream transformation, the respective mapping will fail.


Solution:

 

To avoid this issue, do not edit the business service. If you edit the business service, recreate the midstream transformation and map all the required fields.

Issue:Tasks that use ODBC Connection, configured with DataDirect SequeLink driver, fail with error:

Specified driver could not be loaded due to system error  182:  (DataDirect SequeLink 6.0, C:\Program Files\DataDirect\slodbc60\dwslk22.dll).

 

Solution:

Copy the following files from the SequeLink/main2 folder

 

libeay32.dll

ssleay32.dll

to

%AGENT_HOME%\downloads\package-ICSAgent_Rxx\package\ICS\main\bin\rdtm folder.

(Choose option ‘Copy and Replace’ when prompted)

 

This change will cause tasks that use Salesforce Connection with API version 32 or less to fail with:

Couldn't load the library [pmsfdcXXX.dll] for plug-in #310600.  Error msg: [Database driver event...Error occurred loading library [pmsfdcXXX.dll]. System error encountered is 182. Error text is The operating system cannot run %1.].

 

To resolve the problem with the Salesforce connection, change the Service URL in Salesforce to use API version 33 or higher.

journey.jpg

 

Earlier this month, the Informatica Cloud virtual summit event showcased how Informatica is uniquely positioned to help customers in their journey to the cloud, whether it is a cloud first or hybrid cloud journey. Today, I’m excited to announce the preview program of Informatica Cloud Spring 2017 which will further help customers to more efficiently address their complex data management needs particularly cloud data warehousing.

 

Informatica Cloud Spring 2017 delivers significant capabilities across all application areas – Cloud Application and Data Integration, B2B Gateway and Cloud Integration Hub along with underlying Platform elements like Connectivity and Secure Agent that enable all integration patterns for different deployment models.

 

Here is a sneak peek into key capabilities of Informatica Cloud Spring 2017:

 

Secure Agent Platform

Customers always wanted minimal downtime and component level isolation during Informatica Cloud upgrades or customer-driven maintenance activities. The Spring 2017 release made this a reality. Customers can now take advantage of the Secure Agent platform to run multiple services independently. Built on microservices architecture, the Secure Agent platform can intelligently run multiple pluggable engines and auto-update itself with uninterrupted job execution during quarterly upgrades or monthly patches.

 

Secure Agent Audit Filtering

Customers can easily filter the Secure Agent audit information on the Agent Audit page by date range, component type and message type.

 

Sub-organization Secure Agent Group Sharing

In addition to high availability and scalability, the release provides agent deployment flexibility and resource optimization through Sub-organization Secure Agent group sharing. Using this capability, OEMs can now setup a single Secure Agent group for the parent organization and use that Secure Agent group for more than one customer, where each customer uses a sub-organization. Similarly, enterprises can now use Secure Agent group resources of the parent organization across multiple departments, where each department runs its jobs in a sub-organization.

 

Cloud Application Integration

Cloud Application Integration customers also benefit with the introduction of new Secure Agent platform capabilities offered in this release. The Process Server service is a new engine of the Secure Agent platform. It is the component of the Informatica Cloud Real Time service responsible to execute processes deployed to the Secure Agent. This version of the agent-based Process Server service offers:

• PostgreSQL as a replacement to the H2 Database. The PostgreSQL database will handle larger amounts of data than the H2 database previously-bundled could. You will also observe performance improvements.

• HTTPS Listener Support. This version now provides the ability to instantiate agent-based REST and SOAP processes using an HTTPS transport in addition to JMS and AMQP queues and topics.

• Secure Agent Group Awareness. This release provides the ability to employ the Secure Agent group feature to logically group agent-based Process Servers and distribute the load across each member of the group. This provides the ability to scale.

• Agent Clustering. This release provides you with the ability to cluster two or more Secure Agent group members into a single logical Process Server instance to benefit of high-availability features such as process instance failover in the case of a node failure.

 

 

Cloud API Management

This release provides Cloud Application Integration customers with new API Management capabilities. Customers can not only API-enable services and data sources, and create composite service and data APIs using OData, REST/XML, JSON or SOAP/WSDL using the Informatica Cloud Real Time Application Integration Service, they can now expose managed APIs to partners, customers and internal consumers through the Informatica Cloud API Gateway. In conjunction with API Manager, API gateway provides the means by which to control and secure access to the APIs you expose.

 

 

Cloud Application Integration customers can now take advantage of new API management features delivered with Informatica Cloud Real Time Advanced and Informatica Cloud Premium editions.

 

 

Cloud B2B Gateway

Artificial Intelligence is now embedded inside Cloud B2B Gateway. Using Intelligent Structure Discovery functionality to discover, parse, and map non-EDI messages, Cloud B2B Gateway expedites the on-boarding of partners that do not use EDI files. This release also provides end to end order-to-cash and procure-to-pay processes on EDI and EDIFACT standards, with out-of-the-box EDI solutions with full visibility and tracking to files exchanged with the partner community.

 

 

Cloud Integration Hub

Cloud Integration Hub simplifies data integration and increases user efficiency by allowing users to publish data once and consume data from multiple subscribing applications. Cloud Integration Hub Salesforce Accelerator is available with this release. The accelerator automatically creates the entities that are required to connect Salesforce to Cloud Integration Hub, so users can publish data from salesforce and have it ready for other applications to consume.

 

Cloud Integration Hub is now offered as a free trial to all Informatica Cloud Premium and Advanced edition customers. Customers will find the user interface modern, clean and simple to use.

 

Power Exchange for Cloud Applications

Existing PowerCenter customers can now take advantage of PowerExchange capability made available in this release to accomplish hybrid integration scenarios.Customers can continue to use the PowerCenter Designer interface that they are already familiar with and seamlessly access all Informatica Cloud connectors associated with the Informatica Cloud account directly from PowerCenter. Informatica Cloud thus acts as an agile connectivity service layer for PowerCenter installations in enabling the above scenario.

 

Connectivity

Informatica continues to provide increased support to all leading cloud PaaS providers (AWS, Microsoft, Google) and SaaS vendors (like Salesforce, NetSuite, Workday, Marketo, etc.) so customers can easily light up their cloud data warehouse and analytics use cases.

The following connectors are made available in this release:

• JIRA Cloud

• Teradata Parallel Transporter API

• IBM DashDB via ODBC Connector

• Zuora REST API

• SWAGGER definition generation for REST API connector

• Oracle bulk insert support via REST API connector

 

Connector enhancements to cloud ecosystems in this release include advanced configurations to the user to customize integrations with various sources/targets suitable for their needs, performance and security benefits. Below are some examples.

 

Amazon Web Service

Customers can now manage source/target connection strings effectively and securely by passing Amazon KMS-generated keys for connections associated with Amazon S3 & Redshift services.

 

Customers can now take advantage of multi-part upload option for improved performance and increased throughput when moving data using Amazon S3 & Redshift services.

 

Customers can now read and write multiple files from/to Amazon S3 through configuration settings.

 

 

Microsoft Cloud

From this release, customers can use Informatica hosted secure agent to connect to DocumentDB. The new Microsoft Azure SQL Data Warehouse V2 connector enables customers to read data from and write to SQL Data Warehouse. The connector supports insert, upsert and delete operations. Microsoft Azure Data Lake Store V2 connector is coming soon in May.

 

Dynamics CRM connector is enhanced to connect to Dynamics 365.

 

 

Google Cloud

Customers who use Google data storage services for their analytics scenarios can now leverage Informatica connector enhancements to Google Big Query and Google Cloud Storage.

 

It’s now simple and easy to perform read, write, and update operations against Google Big Query.

 

Customers can create standard Informatica asset types like mappings, mapping configuration tasks, and data synchronization tasks against Google Cloud Storage and read data in binary or string formats in single or multi-threaded fashion. Customers can also use Google Cloud Storage for staging purposes to write to Google Big Query.

 

Support for New Regions

This release introduces new connector code pages to all Informatica supported relational connectors. The support enables customers to manage their data in key Asian and middle-eastern languages.

 

Customers using AWS services for their data integrations can now leverage Informatica support to read and write to S3 buckets / Redshift data warehouses located in US East (Ohio), Asia Pacific (Mumbai) and Canada regions.

 

 

Learn More

You can see demos of some of the capabilities above in action in the upcoming webinar on wednesday, Apr 12, 9:00am. More videos in cloud first / hybrid cloud jouney series:

 

General Availability of this release is expected to be on Apr 22nd 2017. For questions about the Spring 2017 pre-release, send an email to pre-release@informatica.com.

 

Informatica Cloud Spring 2017 is an important milestone. We are incredibly excited to put this into the hands of our customers to accelerate their journey to the cloud. We can’t wait to see how customers around world use Informatica Cloud Spring 2017 to increase their productivity and unlock insights.

Are you facing issues after the Informatica Cloud Fall '16 upgrade? We are here to help. We have identified some of the common issues encountered by users and pulled together a list of solutions to help you address them. Read on to know more.

 

Note: If you have any concerns please open a case with Informatica Support by clicking on Contact Support option within Informatica Cloud.

 

SUMMARY

 

At the bottom of this post, we have a running list of known issues in Fall '16 upgrade and their solutions. We will continue to update this list so check back later for more updates. If you already have a network.informatica.com login, we recommend following  this post so that you can automatically receive updates for any new issues.

 

You can also follow us on Twitter @INFAsupport for all the latest updates on Informatica Cloud Fall '16

 

ISSUES AND SOLUTIONS (APP2 and APP3) Nov 19, 2016 -

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icsdownloadsecure.informatica.com/ICS/r23/mirror1/download/upgrade-24.1.2.1.0.0.0/fullupgrade/win32/upgrade.zip: [There is not enough space on the disk]]

 

Solution: The minimum free space required for the upgrade is equal to 2X size of the current <SecureAgent>\Main directory plus 1 GB. Please ensure that enough disk space is available.

You may remove old upgrade backups such as Main2, Main3, Main4 etc. You can check the cache directory and remove any files there. You can remove the tomcat log or session logs that has gotten large or accumulated over time.

ISSUE 2: The upgrade was not successful. [================================  02/06/2016  1:36:27.41  copy upgrades\fullupgrade\FileLockDetect.exe FileLockDetect.exe        1 file(s) copied. Waiting for file handles to clean up ERROR: Input redirection is not supported, exiting the process immediately. JAVA_HOME: .\jre agentCoreMajorUpgrMarker exists  Do major upgrade.  Interim agent exists before upgrade, so remove it first.  main2\tomcat\work\Tomcat - The directory is not empty. main2 cannot be removed.  ]

 

SOLUTION 2: Please visit the discussion link: https://network.informatica.com/message/199683

Problem: Jobs on Windows using ODBC fail with the following error: Data source name not found and no default driver specified Database driver error.


Solution: The agent should run as an Administrator

During the upgrade the agent will update the registry to add need ODBC entries. If your agent does not have access to update the registry you may face the following error:

WRT_8001 Error connecting to database... WRT_8001 [Session s_dss_000GSG0I0000000000xx Username YOURUSER Error -1 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using user [xxx] and connection string [odbc://dbtype=<oracle or SQLServer>;host=,host.;port=<port>;database=<database>].]

This occurs in Windows for Oracle and SQL Server type connections.

 

Cause: Since there is a new ODBC driver for oracle and SQL server, as a part of upgrade, the registry will be updated to add new entries for these 2 drivers, if the user running the agent does not have permission to modify the registry entries, then these entries will not be added to the registry, hence when the task tried to load the drivers, it looks for registry entry and fails.

 

Solution: If you are not running your agent as an Administrator we recommend you run as an Administrator before the upgrade. KB149494 has the steps to run as an Administrator.

 

What if I face the above error after the upgrade?

 

1) Trigger the upgrade by modifying the infaagentversion file (in a text editor) in {agent}/main and change 26.* - to 25.*

2) Restart the agent as admin (steps same as in KB149494)

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icoss1.informaticacloud.com/saas/download/upgrade-22.3.2.1.0.0.0/fullupgrade/linux32/upgrade.zip: [Download failed due to HTTP 403 response.]]

 

Solution: Please visit the document  link: Secure Agent IP Address KB:112401

Issue: Upgrade failure. [Cannot download upgrade file:https://icsdownloadsecure.informatica.com/ICS/r23/mirror2/download/upgrade-22.3.2.1.0.0.0/fullupgrade/win32/upgrade.zip: [Download failed due to HTTP 502 response.]]

 

Solution: This is because our mirror sites have not been whitelisted in your network. Please contact Informatica Cloud Support with your orgid, so that we can push the download via a secure site.

Issue: ODBC DSN not found on Linux after the upgrade will encounter the following error:

The connection test failed because of the following error: [unixODBC][Driver Manager]Data source name not found, and no default driver specified (0)


Solution:


This is because the odbc.ini file was in the main directory and it was backed up to main2 folder during the upgrade.

To fix the issue copy over the odbc.ini file from infaagent/main2 to infaagent/main.

Also you should store the odbc.ini outside of main, going forward, or keep a copy in rdtm-extra directory, so it is copied back automatically after future upgrades.

Issue: Issues while reading data using Microsoft Excel connector:

You might notice issues when trying to use Microsoft excel connector on ICS. The test connection would be successful however when trying to select the connection as a source in DSS\mapping task we receive error occurred while fetching objects.


Solution:

We have a solution for this issue and customers can reach out to Informatica Support to get the patch.

Issue: Data source name not found and no default driver specified Database driver error


Solution:

The agent should run as an Administrator

During the upgrade the agent will update the registry to add need ODBC entries. If your agent does not have access to update the registry you may face the following error:

WRT_8001 Error connecting to database... WRT_8001 [Session s_dss_000GSG0I0000000000xx Username YOURUSER Error -1 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using user [xxx] and connection string [odbc://dbtype=<oracle or SQLServer>;host=,host.;port=<port>;database=<database>].]

This occurs in Windows for Oracle and SQL Server type connections.

 

Cause: Since there is a new ODBC driver for oracle and SQL server, as a part of upgrade, the registry will be updated to add new entries for these 2 drivers, if the user running the agent does not have permission to modify the registry entries, then these entries will not be added to the registry, hence when the task tried to load the drivers, it looks for registry entry and fails.

 

Solution: If you are not running your agent as an Administrator we recommend you run as an Administrator before the upgrade. KB149494 has the steps to run as an Administrator.

 

What if I face the above error after the upgrade?

 

  1. 1) Trigger the upgrade by modifying the infaagentversion file (in a text editor) in {agent}/main and change 26.* - to 25.*
  2. 2) Restart the agent as admin (steps same as in KB149494)

 

ISSUES AND SOLUTIONS (APP only) Nov 12, 2016 -

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icsdownloadsecure.informatica.com/ICS/r23/mirror1/download/upgrade-24.1.2.1.0.0.0/fullupgrade/win32/upgrade.zip: [There is not enough space on the disk]]

 

Solution: The minimum free space required for the upgrade is equal to 2X size of the current <SecureAgent>\Main directory plus 1 GB. Please ensure that enough disk space is available.

You may remove old upgrade backups such as Main2, Main3, Main4 etc. You can check the cache directory and remove any files there. You can remove the tomcat log or session logs that has gotten large or accumulated over time.

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icoss1.informaticacloud.com/saas/download/upgrade-22.3.2.1.0.0.0/fullupgrade/linux32/upgrade.zip: [Download failed due to HTTP 403 response.]]

 

Solution: Please visit the document  link: Secure Agent IP Address KB:112401

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icsdownloadsecure.informatica.com/ICS/r23/mirror2/download/upgrade-22.3.2.1.0.0.0/fullupgrade/win32/upgrade.zip: [Download failed due to HTTP 502 response.]]

 

Solution: This is because our mirror sites have not been whitelisted in your network. Please contact Informatica Cloud Support with your orgid, so that we can push the download via a secure site.


New features and Documentation - Fall '16

Informatica Cloud Fall 2016

ISSUE: Log File Name Change Starting from next release, Fall ‘16, we are providing an option to create the tomcat and infaagent logs with rolling log appenders after a certain size for e.g.: 100MB. This will help to ensure that the filesize is limited, and help to resolve disk space issues. The infaagent.log will still be created and will contain output from the windows service (infaagent.exe) and scripts (agent_start, runAgentCore, etc.). There is a separate file called agentcore.log from the agentcore process, which will now contain the current content of the infaagent.log. Log rolling configuration is applied to the tomcat.log as well.


Solution:

How will this impact me?If you are parsing the infaagent.log file currently, you will need to start parsing agentcore.log, after the upgrade to Fall ’16.  If you simply read the logs when there is an issue, then there is no impact. The only impact is if you have any process that automatically reads/parses the log files. For more details on default log size and configuring/tuning to your specific requirements, please refer to the following KB.

Issue: ODBC DSN not found on Linux after the upgrade will encounter the following error:

The connection test failed because of the following error: [unixODBC][Driver Manager]Data source name not found, and no default driver specified (0)


Solution:


This is because the odbc.ini file was in the main directory and it was backed up to main2 folder during the upgrade.

To fix the issue copy over the odbc.ini file from infaagent/main2 to infaagent/main.

Also you should store the odbc.ini outside of main, going forward, or keep a copy in rdtm-extra directory, so it is copied back automatically after future upgrades.

Issue: Customers on Linux with PowerCenter and Cloud using the same user to start both services will encounter the following error: Internal error. The DTM process terminated unexpectedly. Contact Informatica Global Customer Support.

 

Solution: Put a line on the top of the agent_start.sh file, located under <agent install Dir>  ‘unset INFA_HOME’  and restart your agnet.

Issue: Task fails at runtime with below Error message on windows for Oracle or SQL Server type connections: WRT_8001 Error connecting to database... WRT_8001 [Session s_dss_000XXX0I00000xxxxxxx Username User_Name DB Error -1 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using user [User_Name] and connection string [odbc://dbtype=<oracle or SQLServer>;host=,host.;port=<port>;database=<database>].]

 

Solution:

Please reach out to Informatica Support with the infaagentversion file and we shall help you resolve the issue.



We are excited to announce the pre-release program for Informatica Cloud Fall 2016. It begins on October 24th 2016 and runs through November 11th 2016.

 

You can find more about our pre-release program here. To learn more about the new features and capabilities of Informatica Cloud register for the webinar on November 1st at 12 noon PT here.

 

For now, here is a sneak peek into the new capabilities of Informatica Cloud.  See the What's New document (attached below) for other details.  See this article for the Release Noteshttps://network.informatica.com/docs/DOC-16879.


The complete documentation for the Fall 2016 release is available here:  https://network.informatica.com/onlinehelp/ics/r26/en/index.htm.


Cloud Mapping Designer

  • Hierarchy transformation enhancements:
    • New Hierarchy Builder transformation that lets you create JSON/XML targets from multiple sources
    • New Hierarchy Parser transformation lets you read from XML and JSON sources and map them to relational targets.
    • Enhancements to the Web services transformation to support REST sources with simplified field mapping.
  • Introducing support for partitioning - Ability to execute a simple mapping in multiple partitions for improved performance. You can define the number of partitions for flat file, relational and Redshift data sources.
  • New Router transformation that lets you route data to output groups based on multiple filter conditions.
  • Enhancements to Lookup transformation to support cached lookup for Redshift, JDBC and many other data sources.
  • Flat-file enhancements:
    • Ability to process a list of files with a single source transformation using the Flat file connector. The list of source files can also be generated using operating system commands.
    • Ability to edit the metadata for parameterized flat file data sources.
    • Availability of Source Filename as a field to be processed in the mapping.
  • Support for creating relational targets dynamically based on the incoming schema.
  • Enhancing parameterization capabilities to support partially parameterized source filters.

 

Cloud Connectivity Enhancements

  • New REST connector:
    • Makes it easy to consume third party REST services as a source, target or “midstream.”
    • Supports basic, Digest and OAuth authentication.
    • Uses Swagger 1.2 definition to get metadata. For services that do not have a definition, it can be generated and deployed using a utility.
  • Launching new connectors for:
    • Aurora
    • Microsoft Dynamics AX 2012
    • Google BigQuery
    • Google Cloud Storage
    • Netsuite REST
    • MongoDB
    • LinkedIn
  • Various enhancements to the following connectors:
    • SFDC ,SFDC-A, SFDC Marketing
    • AWS S3, Redshift
    • Azure BLOB, DW
    • Complex file, File Processor
    • JDBC, ODBC, Oracle, mySQL, SQL Server
    • Workday
    • Marketo
    • NetSuite
    • SAP, SuccessFactors
    • SugarCRM, MSD CRM


Cloud Platform

  • REST API Enhancements
    • Ability to perform partial updates to most of the resources by specifying only the modified object fields.
    • Support for obtaining resource details with the name attribute instead of an ID.
    • New Connector resource provides a list of available connectors in the organization.
    • New LicenseInfo resource to get license information and to provision licenses to sub-organizations.
  • Secure Agent Advanced Features
    • New version of Secure Agent based on microservices is available for all new customers.
    • Supports clustering and high availability with reduced down time during agent updates.

 

Cloud B2B Gateway

  • Introducing Support for Procure-to-Pay process (in addition to Order-to-Cash) – which lets organizations exchange messages with their suppliers.
  • Enhancements to support exchange of non-EDI files – for partners that are not able to send EDI X12 files.
  • Expanding the list of X12 messages and introducing customization support.
  • Simplify and expedite exchanging EDIFACT messages with partners with built-in message processing and validations.


Cloud Integration Hub

  • Publish and subscribe to data from cloud and on premise applications – central hub for integration and synchronization between cloud and on-prem application.
  • Fully hosted and highly secure publication repository with complete data encryption.

 

We look forward to your participation in the pre-release program.  Reach out to pre-release@informatica.com for questions/concerns and feedback.

Informatica Cloud now supports Java 8.  You'll need to uninstall and download the latest agent from the 'agent download' in Informatica Cloud in order to get the Java 8 version of the agent. All upgraded agents were upgraded to the Java 7 version.

 

If you are interested, or have the requirement to use Java 8, please refer to the following Yonyx with step by step instructions:  498429

 

The default agent available before Summer' 16 upgrade uses Java 7, and was not updated to Java 8 during the upgrade. The migration to Java 8 needs to be performed by the user. If you download a new agent from Informatica Cloud, it uses Java 8.

Java 8 agents allows better performance when it comes metadata fetch by avoiding the use of the legacy ODBC-JDBC bridge. Java 8 also supports TLS encryption by default.

Informatica

Register

 

Informatica Webinar:
Informatica Cloud Summer 2016 Release
Replay

 

 

Watch the Summer 2016 Webinar Replay -

 

Join the Informatica Cloud product team to find out what's new in the Summer 2016 release and explore all the key capabilities. The Summer 2016 release is packed with many new platform capabilities, new and enhanced connectors and various other additions to the Cloud suite to help our customers drive their businesses better with unified and secured data.

Register

Register today and you will learn about:

  • Cloud Data Integration Hub offers centrally managed hub to streamline and automate data integration across cloud and on-premise sources
  • Innovative features of Informatica Cloud platform to manage global and distributed data integrations like state-ful time sensitive variables, advanced data transformations like unions and sequences
  • Intelligent data masking capabilities included in Informatica Cloud Data Integration to enable masking of sensitive data dynamically saving time and development efforts
  • Cloud B2B Gateway is the leading data exchange platform for enterprises and it’ partners and customers providing end-to-end data monitoring capabilities and support for highest level of data quality
  • Cloud Application Integrations widget framework, part of SDK, enabling ISVs and third parties to build customized integration solutions
  • Native connectors for popular cloud applications like Workday, SAP Success Factors, Oracle, SugarCRM, MongoDB, Teradata Cloud, SAP Concur, Salesforce Financial Cloud

Not just that but extensive enhancements to support ease-of-use, self-service and more richer experience. We look forward to seeing you.

Register

Sincerely,
Informatica

We are excited to announce the Informatica Cloud Summer 2016 release. Informatica Cloud Summer 2016 includes the following new features and enhancements:

 

Cloud Mapping Designer

  • Added three new transformations:
    • Union - lets you merge data from multiple sources into a single pipeline.
    • Sequence - lets you generate a sequence of numeric values that can be used to create unique primary key values, replace missing primary keys, etc.
    • XML to Relational - lets you handle and extract information from XML data easily.
  • Support for In-Out Parameters. These are persistent parameters that retain values even after task execution and can be used to save the state of Mapping Configuration tasks.
  • Support for parameterization of the Data Masking transformation.
  • Enhancements to the Mapplet transformation to preserve the metadata and field mapping information even after mapplets are refreshed.

Informatica Cloud Real Time

  • Enhanced design time capabilities including support for broader attachments and broader multi-protocol endpoint.
  • Informatica DiscoveryIQ for app integration and operational visibility.
  • Enhancements to App Integration connectivity including S/FTP, AWS S3, AWS SQS, AWS SNS, SAP BAPI, Informatica ICS, DaaS and AddressDoctor, and Service Connector auto-generation.
  • Introducing support for built-in services including Shell Service and Alert Service.

Informatica Cloud Platform

  • Informatica Cloud has been certified with Java 1.8 runtime. Users can upgrade their environment by request and requires re-installation of the secure agent.
  • Enhanced SAML single sign-on support that allows users to login with SAML token and organization ID.
  • Introducing the limited availability of new micro-services based Advanced Agents that provide high availability and clustering with uninterrupted job execution and operation during upgrades and patches.
  • New REST API has been added for Expression validation.
  • Enhancements to the REST APIs to get/set Sequence Generator and In-Out Parameter values.
  • Support for customizing bundles. Users will now be able to copy and edit the contents of a bundle according to their needs.
  • SAP Metadata utility is now available in Informatica Cloud which enables users to browse BAPI metadata and generate new mapplets. It also has support for uploading SAP IDoc extensions.
  • Upgrading the SAP Classic RFC SDK libraries to Netweaver RFC SDK for SAP BAPI, IDoc & Table writer interfaces.
  • Intelligent Structure Discovery is now available within Informatica Cloud and provides the ability to automatically create structures and extract meaningful information from any log file and transform common JSON structures.

Cloud Test Data Management

  • Introducing passive Mapplets that let you create custom masking logic for the tasks.
  • Support for “UPDATE” operation that allows users to populate partial copy sandboxes.
  • Ability to start and stop the staging database from front end, with automatic creation of JDBC connection.

Connectivity Enhancements

  • Launching the new Workday Connector to support all Workday services. The connector simplifies handling complex hierarchical workday data structures and lets you map them seamlessly to relational endpoints. It also stays current with Workday API updates.
  • SAP BW/BI with ability to extract data from InfoCubes, InfoSets, MultiProviders and DataStore objects.
  • Launching new connectors for:
    • SAP Concur
    • SAP SuccessFactors
    • Microsoft Dynamics CRM
    • Amazon Aurora
    • Salesforce Financial Cloud
    • Microsoft DocumentDB
    • SugarCRM
  • Various enhancements to the following connectors:
    • Marketo
    • NetSuite
    • Tableau
    • Amazon S3, RedShift
    • Salesforce Sales and Service cloud
    • Microsoft Azure SQL DB, Data Lake and DW
    • SAP
    • Box
    • ServiceNow
    • Concur V1
    • JIRA
    • Eloqua
    • JDBC (RT)
    • Sharepoint
    • Workday V2 (request from support)
    • Salesforce Marketing Cloud (request from support)

On Wednesday May 11, 10:00 PM PT we made a change to the way Cloud Support Cases are created.

 

Informatica is excited to announce our New Cloud Support interface to improve our customer experience. We will be enhancing the Informatica Cloud Support access on Wednesday May 11, at 10:00 PM PT. Your agent will NOT be affected and there will be NO downtime for this update.

 

What is the new support interface?

 

Over the last several months we have been working on improving the user interface and increasing the learning options for our customers. We understand the use of our cloud products are in mission critical projects and access to right content and support help should be made easy.

 

We have designed a new and more robust way to access all aspects of support, as well as case creation, from Informatica Cloud using the new Informatica Network customer experience platform.  With a click of a button from Informatica Cloud product you can now access our robust Knowledge base, discussions, chat with an expert, and online case interface. The link you used to use to submit a case will now take you directly to the Cloud Support page in the Informatica Network.

 

Watch a quick 2 minute introduction video here.

 

How do I access support?

 

Simply click on the renamed “Contact Support” (previously “Submit a Case” button) from your Informatica cloud interface.

 

img1.JPG

 

FAQ

 

1. What is Informatica Network and how do I register?

Informatica Network is the one-stop shop community platform for all learning and support needs. It has over 120000 registered users and has a vibrant community of developers, administrators and architects

Now Informatica Cloud customers can take complete advantage of Informatica Network resources which includes 70000+ knowledge base articles, how-to libraries, support videos, product documentation and many more..

To register simply click on ‘Contact Support’ and follow the guided steps to register. Please use your work email address, and look for a validation link once you click on submit during the registration process. If you have already registered in the past, use your existing login.


2. What benefits does it preset for Informatica Cloud customers?

 

Informatica Cloud customers can now take complete advantage of Informatica Network. Some of the features includes:


     - Access to all product documentation

     - Knowledge base search across all content sources

     - SupportTV with over 1000 learning videos

     - Expert moderated communities

     - Chat with Support

     - Guided troubleshooting wizard

     - eSupport access to open and manage cases (only for support contacts)


3. Can I use the same login as my Informatica Cloud?

 

Network is our unified portal for Informatica support and hence it needs a new registration but you can use the same email address used in Informatica Cloud to register... Please ensure that you choose your company email address that is registered with Informatica Cloud, so that your cases will be assigned to your support project. If you have more than 1 email registered with Informatica Cloud, please use your primary work email address.

 

4. Can I post to community?

 

Yes, you can take advantage of our communities once you register and can also participate in discussions on others posts. Community allows both be private and public discussion.

 

5. How can I create a case?

 

In the new Cloud Support page as you scroll down you will see a button “Create Case” and that will take you to Informatica Network login page (if you are not already logged in)

 

img2.JPG

 

“Click on “Access eSupport” to start creating the case. Choose create a technical case, and fill the required fields and priority to submit a case. The kb is integrated with the case submission process, so relevant matches will be tied to the case keywords.

 

6. How will  I add myself to a support project as a Read/Write contact?

 

You can place a request with your primary contact to add yourself to the list of Read/Write contacts. Please note there is a numerical limit to the list of contacts for a support project based on your support entitlement.

 

7. I do not know who my primary contact is. How can I find it?

 

Please send an email to ics_contacts@informatica.com with your questions. You can also send an email to support_admin@informatica.com.


8. I am user in more than one Informatica cloud Org. So should I register with multiple users in Network?

 

No, you can register with the same email address that is tied to the multiple Informatica cloud users once which should be sufficient.


9. Do I need to be a Read/Write contact to search for knowledge base solutions?

 

No, you can search even if you are not a listed as read-only or Read/Write contact. You can encourage any of the users from your organization to access network.informatica.com.


10. What is a Read/Write contact?

 

Informatica support offers its customers the ability to register a certain number of named contacts that  have the ability to create/update cases on behalf of the support project. Those who have this permission are called Read/Write contacts. There is another type of user with Read Only permission and this is unlimited, but these users cannot create cases.

 

12. How do I view/update open cases?

 

Once you login to e-support page, you shall see all cases open for both your support project as well as the ones opened by you. You can click to open any case and view/update as necessary.


13. Is there a comprehensive document about your policies and procedures?

 

Yes, Please refer to our Policies and Procedures document.


14. I am a trial customer, how do I get support?

 

Trial customer support is now done via Community Discussions. You may create a public discussion or choose a private discussion and we will provide answers to your issues via the discussion. To create a discussion click on Create Discussion, and the default is in the public Cloud Integration forum. If you prefer a private discussion choose the Specific People radio button and the user “CloudTrial”. Our discussion forums are moderated by Informatica Cloud support engineers.

 

 

15. How can I provide Feedback?

Click on the feedback button at the top of the page. We look forward to hearing your feedback.

img4.png

 

We hope you find these changes enhance your support experience and give you an opportunity to explore all of our resources and materials in a unified location.

 

Quick Links for our Network Tutorial Videos:

 

How to post a question on to Informatica community:

 

How to create new Technical Case in Esupport:

 

How to Add a new Contact in Esupport:

 

How to Update a Case in ESupport

 

How to create a new Technical profile

 

How to register to network

 

If you have any questions please contact us through Global Customer Support at 1-877-INFAHELP from the US, or Worldwide click here.


Important Links:

1. DiscoveryIQ

2. Cloud Community Page

3. Global Customer Support

 

 


Thank you,

Informatica Cloud Team
https://www.informatica.com/cloud

We are excited to announce the release of Informatica Cloud Winter ’16 Pre-Release.

 

Before the release, we would like our customers to try some of the new features, and give us any feedback. Pre-release began TODAY, Monday January 11 and will end on Friday January 29. You can submit any questions or concerns to pre-release@informatica.com. For any technical issues please create a support case through the normal channel.

 

For more information on the pre-release process, login url, and best practices, please read this community post: Informatica Cloud Summer '19  Pre-Release Program

 

You can submit any questions or concerns to pre-release@informatica.com. For any technical issues please create a support case through the normal channel.


We strongly encourage our customers to participate in the pre-release and provide feedback.

Filter Blog

By date: By tag: