Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(2 Ratings)
facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

PowerCenter on Azure Marketplace
Content

Overview

PowerCenter, the industry’s leading data integration solution, is now available to run on Azure. PowerCenter is a metadata-driven, visual, highly scalable tool that seamlessly connects disparate data systems on-premise and in the cloud. PowerCenter delivers an end-to-end agile data integration process to support business agility and quickly deliver quality data to support decision making. It is unparalleled in the industry for ease of use, connectivity, productivity, and support for data integration use cases.

Use Cases

You can use PowerCenter on Azure to help you solve several business problems:
  • Move data centers from on-premise to the Azure cloud.
  • Perform cloud data integration tasks, such as reading from or writing to Salesforce and Microsoft DW.
  • Work on data integration projects on demand and avoid on-premise costs and complexities, such as procuring hardware and databases.

Key Benefits

PowerCenter on Azure offers several benefits, such as:
  • Faster time to quality data for decision making.
  • Easy to learn and use the visual tool.
  • Increased productivity through automation and reuse of work, skills, and resources.
  • Reduced costs associated with data integration development lifecycle.
  • Unparalleled connectivity to data sources, from mainframe to cloud and every data system in between.
  • Improved SLAs and data trust.
  • A highly scalable platform that supports enterprise environments.
  • Self-documenting, metadata-driven tool improves visibility into code and data flows.
  • Broadly applicable to multiple use cases including data warehousing, application-to-application integration, application migration and consolidation, data governance, hybrid environments, and more.

Offerings

Informatica offers the following options for using PowerCenter on Azure:
  • PowerCenter 10.1.1 on Windows and RHEL
  • PowerCenter 10.0 Standard & Advanced Editions Windows
  • PowerCenter 10.0 Standard & Advanced Editions on Ubuntu

License

PowerCenter is provided on Azure as a Bring Your Own License (BYOL) listing. You must work with Informatica directly to obtain a license and key. If you hold a PowerCenter license agreement, contact Informatica to confirm that the product and version are compatible with PowerCenter on Azure before you initialize the Azure Virtual Image. If you do not hold a PowerCenter license agreement, contact Informatica to obtain a license.
 
Contact Azure for any infrastructure issues, such as VM, operating system, or database issues.
 
Contact Informatica for any PowerCenter issues. Log Informatica support cases on the Informatica Global Customer Support website: http://network.informatica.com
 
You can register on Informatica Network to log a case. Use the project ID that you received after you purchased your PowerCenter license. You can also contact one of the Informatica Global Support centers by phone. Go to the following website to find local support centers: https://www.informatica.com/services-and-training/support-services/contact-us.html#fbid=6M9V6HUzlPy

Details

  • PowerCenter 10.0:
  • Standard Edition on Windows Server 2012 64-bit Enterprise Edition
  • Standard Edition on Ubuntu 14.04.3
  • Advanced Edition on Windows Server 2012 64-bit Enterprise Edition
  • Advanced Edition on Ubuntu 14.04.3
  • Multiple nodes on the Informatica domain
  • SQL Server 2014 as the domain database
  • Once provisioned, domain services are available outside of the Azure environment through public IP addresses.
  • Work in a hybrid environment. Use the PowerCenter client tools on-premise or on Azure client VMs and connect to the provisioned domain in the VM.

What’s in the VM Image?

  • A VM image provided by Azure has been enhanced to include PowerCenter 10.1.1 or 10.0.0, depending on your license.
  • One or more node images are available:
    • The first image contains the domain
    • Additional images are nodes that are registered with the domain
  • A private virtual network that includes the database machine and all node machines, which enables seamless communication among the machines
  • A public IP address associated with each machine that contains a node, which makes the machine accessible through the internet
  • All resources are created under the specified Azure resource group
  • A shared file directory that can be accessed across all nodes as common log location:
    • On Linux: /mnt/infaaemnt/informatica_10 
    • On Windows: I:\informatica_10
  • Install locations:
    • Windows:
      • Domain: %SystemDrive%\Informatica\10.1.1 or %SystemDrive%\Informatica\10.0.0
      • Setup: %SystemDrive%\Informatica\Archive
    • Linux:
      • Domain: $HOME/Informatica/10.1.1 or $HOME/Informatica/10.0.0
      • Setup: /opt/Informatica/Archive
    • Client Installer: To install the client on a machine and connect to the domain in the Azure cloud, download the installer from the link provided with the license.

    Getting Started

    After you receive a PowerCenter installation on Azure VM, use the following information to get started with PowerCenter:
    • Apply your own license to the domain.
    • Create the application services that you need to develop and run workflows that contain PowerCenter mappings.
    • You can log in to SQL Server Management Studio using trusted connection to create users or database configurations.
    • Use the following connection credentials configured during provisioning:
      • Domain
      • Domain/Node virtual machine
      • Database
      • Database virtual machine
    • Configure connections to external data sources on the VM instance to avoid being blocked by firewalls.
    • If you are using PowerCenter Advanced Edition, configure high availability using any clustered file system available on Azure.
    • On Windows, inbound communication for a node on a VM is allowed between ports minimumProcessPort(6014) and maximumProcessPort(6114). Add firewall inbound and outbound rule for service ports that are outside this range.
    • To run workflows on a grid in PCAE, disable private network firewalls on all node VMs.

    Limitations of the VM Image

    • You must manually add nodes to the domain. You cannot add nodes to the domain using provisioning.
    • You can create VM instances on Azure from this image only for the stated operating system and database.
    • You cannot configure domain properties, such as the domain name, node name, log location, and port during VM provisioning.
    • LDAP and Kerberos authentication are not supported.

    Troubleshooting

      DEPLOYMENT OVERVIEW

       
      1. Infrastructure is created for VMs. This includes the following resources:
          • Storage
          • VNET and SUBNET
          • Network security group
        2. Database VM is created:
          • Storage
          • VNET and SUBNET
          • Network security group
        3. VM is created for master node:
          • Firewall exception is added for port range 6005 – 6008 and 6014 – 611
          • Azure file service is created on the Azure storage and 1 TB of space is allocated (maximum supported). File service folder is mounted as I: drive on Windows and /mnt/infaaeshare on Linux.
          • Informatica domain installation is started using the Silent installer. 
        4. VMs for other gateway nodes are created:
          • Firewall exception is added for port range 6005 – 6008 and 6014 – 6114.
          • File service folder is mounted as I: drive on Windows and /mnt/infaaeshare on Linux.
          • Informatica node installation is started using the Silent installer.

        FAILURES AND LOGS

         
        Resource Creation Failure


         

        For resource creation failures, see Troubleshoot common Azure deployment errors with Azure Resource Manager to resolve common Azure deployment errors. You can also check the resource status at resources.azure.com


         
        Database User Creation Failure

         

        If there are no resource deployment failures but the domain is still inaccessible, database user creation might have failed. To debug this issue, log in to the SQL Server VM and check the following logs:


         

        1. ​Createdbuser.log


         

        LocationC:\Informatica\Archive\scripts\createdbusers.log​



        ​​The following examples show createdbuser.log success and failure:

        Success

         

        02/07/2017 08:51:21 : Creating user: user1

        02/07/2017 08:51:22 : Connection to MSSQL Server succeed

        02/07/2017 08:51:36 : Statement execution passed

         

        Failure


        12/26/2016 10:43:56 : Creating user: user1​ 

        12/26/2016 10:43:56 : Connection to MSSQL Server succeed

        12/26/2016 10:44:04 : Statement execution passed

        12/26/2016 10:44:07 : Error: User does not have permission to perform this action.

        12/26/2016 10:44:36 : Statement execution passed

        12/26/2016 10:44:37 : Error: Cannot add the principal 'user1', because it does not exist or you do not have permission.

        Cannot add the principal 'user1', because it does not exist or you do not have permission.

        12/26/2016 10:45:06 : Statement execution passed

        12/26/2016 10:45:07 : Error: Cannot find the user 'user1', because it does not exist or you do not have permission.

        CREATE SCHEMA failed due to previous errors.​​


        2. CustomScriptHandler.log

        LocationC:\WindowsAzure\Logs\Plugins\Microsoft.Compute.CustomScriptExtension\<extensionversion>\CustomScriptHandler.log​
         
        The following example shows CustomScriptHandler.log success:
         

        [2936+00000001] [02/07/2017 08:51:06.37] [INFO] Starting IaaS ScriptHandler Extension v1

        [2936+00000001] [02/07/2017 08:51:06.39] [INFO] HandlerEnvironment = Version: 1, HandlerEnvironment: [LogFolder: "C:\WindowsAzure\Logs\Plugins\Microsoft.Compute.CustomScriptExtension\1.8", ConfigFolder: "C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\1.8\RuntimeSettings", StatusFolder: "C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\1.8\Status", HeartbeatFile: "C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\1.8\Status\HeartBeat.Json"]

        [2936+00000001] [02/07/2017 08:51:06.39] [INFO] Installing Handler

        [2936+00000001] [02/07/2017 08:51:06.39] [INFO] Handler successfully installed

        [2936+00000001] [02/07/2017 08:51:06.39] [INFO] Removing user-level access rules for 2 directories

        [2936+00000001] [02/07/2017 08:51:06.42] [INFO] Removing Users access rules from directory 'C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\1.8'

        [2936+00000001] [02/07/2017 08:51:06.43] [INFO] Removing Users access rules from directory 'C:\WindowsAzure\Logs\Plugins\Microsoft.Compute.CustomScriptExtension\1.8'

        [2936+00000001] [02/07/2017 08:51:06.43] [INFO] Finished removing user-level access rules

        [3960+00000001] [02/07/2017 08:51:09.80] [INFO] Starting IaaS ScriptHandler Extension v1

        [3960+00000001] [02/07/2017 08:51:09.81] [INFO] HandlerEnvironment = Version: 1, HandlerEnvironment: [LogFolder: "C:\WindowsAzure\Logs\Plugins\Microsoft.Compute.CustomScriptExtension\1.8", ConfigFolder: "C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\1.8\RuntimeSettings", StatusFolder: "C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\1.8\Status", HeartbeatFile: "C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\1.8\Status\HeartBeat.Json"]

        [3960+00000001] [02/07/2017 08:51:09.81] [INFO] Enabling Handler

        [3960+00000001] [02/07/2017 08:51:09.81] [INFO] Handler successfully enabled

        [3960+00000001] [02/07/2017 08:51:09.86] [INFO] Loading configuration for sequence number 0

        [3960+00000001] [02/07/2017 08:51:09.88] [INFO] HandlerSettings = ProtectedSettingsCertThumbprint:

        blicSe

        e: }

        on...

        [3960+00000001] [02/07/2017 08:51:10.01] [WARN] Storage Account Name and/or Key are empty - will try to download files withou

        t them

        [39

        60+00000001] [02/07/2017 08:51:10.01] [INFO] DownloadFiles: File not in Azure storage, fileUri = https://gallery.azure.com/artifact/20151001/informatica.powercenter-previewpc-byol-10-1-1.1.0.3/Artifacts//createsqldbuser.ps1

        [3960+00000001] [02/07/2017 08:51:10.01] [INFO] DownloadFileAsync: Downloading file to fileDownloadLocation = Downloads\0\createsqldbuser.ps1

        [3960+00000001] [02/07/2017 08:51:10.16] [INFO] Waiting for all async file download tasks to complete...

        [3960+00000001] [02/07/2017 08:51:10.16] [INFO] Files downloaded. Asynchronously executing command: 'SecureCommand_0'

        [3960+00000001] [02/07/2017 08:51:10.17] [INFO] Command execution task started. Awaiting completion...

        [3960+00000001] [02/07/2017 08:51:39.91] [INFO] Command execution finished. Command exited with code: 0

         
        3. 0.status

        LocationC:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\<extensionversion>\Status\0.status​

         
        The following example shows 0.status success:

         

        [{"status":{"code":0,"formattedMessage":{"lang":"en-US","message":"Finished executing command"},"name":"SecureCommand_0","operation":"Command Execution Finished","status":"success","substatus":[{"code":0,"formattedMessage":{"lang":"en-US","message":"Ok.\\n\\n\\n\\n    Directory: C:\\Informatica\\Archive\\n\\n\\nMode                LastWriteTime     Length Name                              \\n----                -------------     ------ ----                              \\nd----          2\/7\/2017   8:51 AM            scripts                           \\n\\n"},"name":"StdOut","status":"success"},{"code":0,"formattedMessage":{"lang":"en-US","message":""},"name":"StdErr","status":"success"}]},"timestampUTC":"\/Date(1486457499916)\/","version":"1"}]


        Note
        You can also log in to the SQL database from database VM, which has SQL client installed, using SQL Management Studio.

         

        Domain Installation Failure


        For domain installation failures, check the installation logs in the following installation locations:


        • Windows: C:\Informatica\10.1.1 
        • Linux: /home/Informatica

        If you do not find logs in the installation location, check for an installer error log. Installation happens with the SYSTEM user on Windows and root user on Linux. The installer error log is created under C:\ on Windows and /root on Linux (change the shell to root shell with ‘sudo csh’ to access /root).


         

        For other failures like a missing firewall setting, or if no logs are present, check the following locations:

        • Windows: C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\<extensionversion>\Status\0.stat
        • Linux: /var/log/azure/Microsoft.OSTCExtensions.CustomScriptForLinux/<extensionversion>\/extension.log (Change shell to root shell with ‘sudo csh’ to access this location)


        More Information


        Reference


        Attachments


        Applies To
        Product(s): PowerCenter
        Product Version(s): PowerCenter 10.0; PowerCenter 10.1.1
        Database:
        Operating System(s):
        Other Software:

        Last Modified Date: 9/7/2018 1:32 PM ID: 495167
        People who viewed this also viewed

        Feedback

        Did this KB document help you?



        What can we do to improve this information (2000 or fewer characters)