| ||||||||||||||||||
| ||||||||||||||||||
| ||||||||||||||||||
|
The following questions and answers will help you better understand the Informatica Intelligent Cloud Services migration. This is a live document, and we will be adding questions and answers as they arise.
This document is organized in sections by Service: common questions, Data Integration questions, API and Application Integration questions, and Data Integration Hub questions.
Migration to the new Informatica Intelligent Cloud Services platform will begin in early Q2 2018.
As a first step, Informatica Cloud Services (ICS) customers that do not use the Informatica Cloud Real Time (ICRT) services will be migrated. ICRT customer migration, including customers that have licensed Cloud Premium services, is commencing in July 2018. ICRT customers are grouped by functional usage. Migration of customers is planned to be completed before the end of 2018.
See the IICS Navigation Overview for ICS and ICRT Users video to for a quick tour of IICS. This video provides an overview of Informatica Intelligent Cloud Services for users that are already familiar with Informatica Cloud.
The Migration folder of the Cloud Application Integration Community Site provides links to a number of resources that can help you with this. These include:
For ICS Users
For ICRT Users
Migration will be performed in multiple batches to ensure maximum flexibility and a minimal amount of disruption to customers. These batches may include ICS and ICRT customers.
Customers will be notified 6 weeks prior to the migration. The communication will go out to all users of the Informatica Cloud organization being migrated.
All customers will be migrated to a Sandbox environment before they are migrated to the production environment. The Sandbox environment will be available to you for at least three weeks, to allow you to perform testing. Your Informatica Cloud assets will be migrated to the Sandbox environment, but an asset that you create in the Sandbox environment will not be migrated to the production environment. If you create assets in Informatica Cloud during the three weeks of preview testing, these assets will be migrated to the production environment. After the three weeks of the preview, testing has elapsed, your organization will be migrated to the production environment. If you have concerns or need more time please contact Informatica Global Customer Support.
Yes, all customers are expected to test the migration in the Sandbox environment. It is critical for all customers to participate in the testing to ensure a smooth transition from Informatica Cloud to Informatica Intelligent Cloud Services. As a minimum, Informatica recommends that you test at least one organization with a good mix of use cases.
Yes. When you are notified of the upcoming migration you will be able to access your Sandbox environment. The following instructions apply to the Sandbox environment:
ICRT service users should also review the ICRT Service Migration to the Cloud API and Application Integration Service guide.
IICS supports the following browsers: Google Chrome, Microsoft Internet Explorer 11, and Mozilla Firefox. For more information, see the PAM for Informatica Intelligent Cloud Services (IICS) on Informatica Network.
If you use IE11, note the following:
During the production migration, all of your Informatica Cloud Secure Agents will be upgraded to the latest version. Secure Agents that you downloaded from the IICS Sandbox environment will not be upgraded.
The migration process retains the following items:
The migration process does not retain manual changes that you made to configuration files in the Secure Agent installation directory or its subdirectories.
Note: As a best practice, Informatica recommends that you back up your Informatica Cloud Secure Agent directories before the migration so that you can restore them easily in the unlikely event of a rollback.
To calculate the free space required for upgrade, use the following formula:
Minimum required free space = 3 * (size of current Secure Agent installation directory - space used for logs directory) + 1 GB
The approved Secure Agent IP address ranges for production and Sandbox environments are listed in KB article 524982.
The migration will affect your service’s availability. The exact duration of the downtime will be communicated to each customer as part of the migration notification. The exact downtime depends upon the number of Informatica Cloud assets and organizations that a customer has. Informatica estimates the downtime to be in the range of 1-4 hours.
The Informatica Cloud organization will be deactivated, but its metadata will be retained for 30 days post-migration to ensure that Informatica has a copy for comparison and for roll-back in case of unforeseen issues.
Yes. You will get a temporary organization ID in the Sandbox environment. During production migration, your organization will get a new, permanent organization ID.
Informatica will build the migration batches and communicate the migration schedule to each customer. If the published schedule does not meet your needs, customers are requested to contact support to reschedule to a different migration batch.
While this is possible, Informatica doesn’t recommend this. Customers should consider the impact of having the organizations in different platforms for even a short duration. Customers should work with their customer success manager and Informatica Global Customer Support to ensure that organizations are scheduled in the appropriate batches.
We have introduced user-defined roles in Informatica Intelligent Cloud Services. User roles are automatically created for corresponding user groups in Informatica Cloud. If there are any asset-level custom permissions in Informatica Cloud in which asset permissions granted to a user are higher than the permissions granted to the user via the user group, then these asset permissions are not honored for the user. Customers need to pay attention to this and manually adjust asset-level permissions as needed.
Post-migration, if the customer raises a P1 ticket that can’t be resolved within 24 hours, Informatica will consider the rollback option. Rollback should be done only after all other avenues to resolve the issue have been exhausted. Rollback requires an approval from the project management team.
Informatica has a rollback script that deactivates the Informatica Intelligent Cloud Services organization, reactivates the Informatica Cloud organization, and downgrades the Secure Agent back to the Informatica Cloud version. If any jobs have been run in Informatica Intelligent Cloud Services either partially or successfully prior to the rollback, the state of those jobs and their job logs will not be rolled back, nor will they be ported back to Informatica Cloud.
Usernames in Informatica Intelligent Cloud Services must be unique. If there is already an IICS user account that has your Informatica Cloud username, then your IICS username will be appended with some extra characters to form a unique name. For example, if your Informatica Cloud username is infaclouduser, your IICS username might be changed to infaclouduser.IICS. (Your Informatica Cloud username will not change.) Informatica will send you an email with the new IICS username, and you will be able to log in to IICS using the new name.
If you use SAML or Salesforce single sign-on and there is already an IICS account with your username, the IICS username that appears in your user profile will be appended with a string such as “.SAML” or “.Salesforce” to ensure that the username is unique. You will be able to log in to IICS using single sign-on as you did with Informatica Cloud.
After migration, login API requests will be automatically redirected to Informatica Intelligent Cloud Services. This redirection service will be available through February 28, 2019. As before, you must construct subsequent API requests based on the <serverUrl> and <icSessionId> that was received in the login response. Ensure that you have not hard-coded the base URL for any other API endpoints other than the login API endpoint.
After February 28, you must replace your current Informatica Cloud domain URLs with the Informatica Intelligent Cloud Services (IICS) URLs mentioned in KB article 524982 to use the APIs in IICS. (For example, if your POD is located in North America, the new IICS domain URL is https://dm-us.informaticacloud.com, and the V2 login IICS API endpoint to use is https://dm-us.informaticacloud.com/ma/api/v2/user/login.)
New features such as export/import are currently only available through the V3 APIs. To leverage these APIs, use the V3 endpoints described in the REST API Reference. (For example, use the V3 login API with the following endpoint: https://dm-us.informaticacloud.com/saas/public/core/v3/login.)
Please review the https://kb.informatica.com/faq/7/Pages/21/535281.aspx articles for the whitelist of either Domain names or the IP address ranges.
The production migration process is seamless, and existing assets will continue to work after migration without manual changes. (Please see question 2 for potential post-migration tasks.)
Before:
1. Ensure that no metadata is modified during the migration window.
2. As a best practice, back up your Secure Agent directories so that you can restore them easily in the unlikely event of a rollback.
3. Set up appropriate blackout window.
4. Ensure that your Informatica Cloud Secure Agents are up and running.
5. Make sure that you have completed any task provided by Informatica Global Customer Support for migration.
6. Prepare a checklist to validate post-migration.
During:
Monitor your email for any communication from Informatica Global Customer Support.
After:
1. Log into the new Informatica Intelligent Cloud Services organization and do a quick validation to ensure that all metadata counts are in line.
2. Verify that jobs are running as expected.
3. Reset the blackout window.
4. Review the activity logs and audit logs.
5. If you see any discrepancies, log a support ticket as soon as possible.
Informatica is making every effort to automate the migration from end-to-end. However, there are certain areas that need attention:
Public views in Informatica Cloud are replaced with tags in Informatica Intelligent Cloud Services. All assets in the view will be labeled with a tag in IICS Data Integration that has the same name as the view. For example, if you created custom view called SalesObjects that contained 30 mappings in Informatica Cloud, all 30 mappings will be labeled with the tag SalesObjects in IICS Data Integration.If the same view name was used for different asset types, the tag names will have different suffixes in IICS Data Integration. For example, if you created the SalesObjects view for mappings and also for mapping tasks, mappings might be labeled with the tag SalesObjects and mapping tasks with the tag SalesObjects_1.You will be able to browse tagged assets and view all assets with a specific tag.Private views, views that are associated with connectors, and activity log views are not migrated.
REST API version 1 is no longer supported. For IICS, use REST API version 2 and version 3. The Informatica Cloud Data Integration REST API Reference explains the two REST API versions in detail and how to use each of them to interact with Data Integration using REST API calls.
Yes. To use the utility in Informatica Intelligent Cloud Services, update the restenv.properties file to use the new Informatica Intelligent Cloud Services URL:
Note that if you run the utility with the task name (-n) option, and you have multiple tasks with the same name in different folders, the utility runs the task in the Default folder. To run a task in a different folder, use the task ID (-i) option instead of the task name option.
In Informatica Intelligent Cloud Services, Informatica no longer includes the MySQL ODBC and JDBC drivers with the MySQL connector. Before you use the MySQL connector, download and install the drivers. For information about installing and configuring the drivers, see the following article or videos:
Preview/Sandbox Migration:
Create and invoke processes in the sandbox account. However, do not use sandbox service URLs in any production activity. Sandbox service URLs are not permanent and are only for testing.
Be careful when you invoke processes in the sandbox environment. Verify that the execution of a process does not affect production. For example, if you execute a "Create Order" process in the sandbox, an order will be created.
Scheduled Processes
Your schedules are migrated to the sandbox in the 'Not Enabled' state. This is to ensure that there is no duplicate process invokes because legacy Informatica Cloud Real Time continues to function during the sandbox testing period. To test schedules, create new processes in the sandbox and assign schedules to the processes.
Invoked Processes
Processes invoked before migration do not appear on the sandbox Application Integration Console service. Use the legacy Process Console to use these processes.
Processes that you invoke using sandbox service URLs will appear in the sandbox Application Integration Console service.
Production Migration:
Post the migration to IICS/CAI Production, the client will still be able to send requests to the older ICRT Service URL, which will be automatically redirected to the equivalent CAI Service URL. However, please note that this redirection will be available only for a short period of time until the end of September 2019. We suggest that you should plan to update your client to send the requests to the new CAI Service URL, as soon as possible to reduce the number of network hops and thereby improve the performance.
It is suggested to turn off the requests from the client at the time of migration (that has been communicated over email), although it is not mandatory. Please plan ahead. You need to be cognizant that any requests that are instantiated at the time of production migration, will likely not complete successfully. You might receive an HTTP 500 or HTTP 503 as a response, and the runtime of the instance 'attempted' to be instantiated in ICS/RT will not be migrated to the IICS/CAI Production server.
The Migration folder of the Cloud Application Integration Community Site provides links to a number of resources that can help you with this. These include:
Most ICRT service customers use ICS data integration services. To see what's available to you as you migrate to IICS, see the Essential Cloud Data Integration Demos set of videos.
To prepare for Sandbox, or before and after migration to your Production Environment you should review the ICRT Service Migration to the Cloud API and Application Integration Service document.
All your assets have been migrated to the Default folder on the Explore page.
If a process uses the Run Cloud Task service, and you have moved the cloud asset from the Default project to another project or folder, you must go to the process and reselect the cloud task. Save and publish the process.
Yes, all schedules will be migrated to your sandbox account. However, to avoid multiple invokes of the same process, they will be migrated into the 'Not Enabled' state. Informatica suggests that you verify that no processes are scheduled during the migration window.
Yes, old service URLs will still be valid post sandbox migration. Continue to use these URLs until Informatica migrates your organization to a production account. Do not embed sandbox service URLs anywhere.
No, you do not need to republish assets after migration. All published assets will be migrated in the published state.
Your Secure Agent will be migrated, as will all assets that are published to the agent. You do not need to download an agent again.
Please review the https://kb.informatica.com/faq/7/Pages/21/535281.aspx articles for the whitelist of either Domain names or the IP address ranges.
Managed APIs will not be migrated. If an API Manager customer needs to migrate the existing managed APIs, then the customer should contact the customer success manager or support manager.
No, old managed API URLs will not be valid post-production migration if you do not arrange with your customer success manager to migrate the existing managed APIs. Instead, create a new managed API for each service that you want to manage, and use the new URL.
If you do request to migrate existing managed APIs, the old URLs will resolve after production migration and DNS resolution. However, it is recommended to use new URLs.
After production migration, do not use the old API Manager. Instead, use Informatica Intelligent Cloud Services API Manager to create and perform all operations with managed APIs.
No, do not embed sandbox URLs anywhere.
Yes, you must manually update the Salesforce guide setup URLs after migration. The guide setup URLs will not be automatically redirected after migration.
You must log in to Salesforce and manually update the Informatica Cloud Real Time Host URL specified under advanced settings in the Guide Setup tab. If you had embedded guide URLs, you must manually update them with the new URLs after migration. See the next question for more information.
If you use the Salesforce managed package, you must perform the following tasks after migration:
Log in to Salesforce and verify your guides.
Log in to Salesforce and verify that your guides are visible on the relevant Salesforce object pages. If you do not see your guides, log out of Salesforce, clear the browser cache, and then log in to Salesforce.
Log in to Salesforce and verify the Informatica Cloud Real Time Host URL.
Log in to Salesforce and verify that the Informatica Cloud Real Time Host URL specified under advanced settings in the Guide Setup tab is correct.
The format of the Host URL must be as follows: <Cloud Application Integration URL>,<Informatica Organization ID>
For example: https://na1.ai.dm-us.informaticacloud.com,afdq9RWEA4vjIQWQcE88XB
To view your Cloud Application Integration URL, log in to Informatica Intelligent Cloud Services and select the Application Integration service. From the browser address bar, copy the URL from https till .com as shown in the following image:
To view your Informatica Organization ID, log in to Informatica Intelligent Cloud Services, select the Administrator service and then click Organization. Copy the Informatica Organization ID displayed in the ID field as shown in the following image:
No. Informatica does not support Guide Designer in Salesforce. To create a guide, log in to Informatica Intelligent Cloud Services and use the Application Integration Guide Designer.
If you had assigned custom permissions to a Data Integration task and are invoking the Data Integration task through an Application Integration process or a guide, after migration, you must complete either of the following tasks:
The following image shows an Application Integration anonymous user account that is authorized to run a Data Integration mapping:
More Information:
If you have licensed Application Integration, Informatica Intelligent Cloud Services creates a system user called CAI_Anonymous_<Organization_ID>. Application Integration needs this user when you invoke an anonymous process that calls a Data Integration task.
Important: Do not edit or delete the Application Integration anonymous user if you need to invoke an anonymous process that calls a Data Integration task.
The following image shows an Application Integration anonymous user account named CAI_Anonymous_6gPInky12gwbSxPUcH8v0H:
By default, Application Integration uses TLS 1.2 version to connect to third-party services. TLS version 1.1 has been deprecated.
If a process connects to a service that uses TLS version 1.1 or earlier, you must manually edit the server ssl-enabled-protocols property to point to TLS version 1.1.
Perform the following steps after migration:
These errors occur because UNIX limits the number of files that can be created by a single process. The NOFILE parameter defines the maximum number of files that can be created by a single process, which is 1024.
Edit the UNIX security configuration file to allow a larger number of files to be opened. Configure the value of the NOFILE parameter to raise the limit from the default 1024 value. A value of 10240 should suffice.
Open the file /etc/security/limits.conf and add the following line:
- nofile 10240
If you are unsure of the value, you can set the value to unlimited.
If you had published a process on the agent and the status still shows as running even though the process successfully completed in Informatica Cloud Real Time, you must manually apply a patch to fix the issue. For more information, see the following Informatica Knowledge Base article: 566279.
Integration Hub artifacts will not be migrated. Informatica Cloud publication and subscription mappings and tasks will be migrated and can be used to create Integration Hub artifacts in Informatica Intelligent Cloud Services. If an Integration Hub customer needs to use the existing Integration Hub artifacts in Informatica Intelligent Cloud Services, then the customer should contact the customer success manager or support manager prior to the migration.
Organizations with invalid Informatica Cloud user credentials will not be migrated. Before you start the migration, verify that the Informatica Cloud user credentials in the B2B Gateway Settings page are valid.
All of your B2B Gateway artifacts, including customers, suppliers, and monitoring rules, will be migrated. Customer and supplier schedules will be created in Administrator.
Intelligent structure models that are used in B2B Gateway partner definitions will be created in Data Integration.
B2B Gateway events will not be migrated.
No, Run Partner API and Event Status API URLs will not be valid after the migration. You must update the API requests with the new URLs, as follows:
...where <pod> is the name of the Informatica Intelligent Cloud Services point of delivery (PoD) where you access Cloud B2B Gateway. For example: usw1.