• Success
    Manage your Success Plans and Engagements, gain key insights into your implementation journey, and collaborate with your CSMs
    Success
    Accelerate your Purchase to Value engaging with Informatica Architects for Customer Success
  • Communities
    A collaborative platform to connect and grow with like-minded Informaticans across the globe
    Communities
    Connect and collaborate with Informatica experts and champions
    Have a question? Start a Discussion and get immediate answers you are looking for
    Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
  • Knowledge Center
    Troubleshooting documents, product guides, how to videos, best practices, and more
    Knowledge Center
    One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
    Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
    Information library of the latest product documents
    Best practices and use cases from the Implementation team
  • Learn
    Rich resources to help you leverage full capabilities of our products
    Learn
    Role-based training programs for the best ROI
    Get certified on Informatica products. Free, Foundation, or Professional
    Free and unlimited modules based on your expertise level and journey
    Self-guided, intuitive experience platform for outcome-focused product capabilities and use cases
  • Resources
    Library of content to help you leverage the best of Informatica products
    Resources
    Most popular webinars on product architecture, best practices, and more
    Product Availability Matrix statements of Informatica products
    Monthly support newsletter
    Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
    End of Life statements of Informatica products
Last Updated Date Jun 01, 2022 |

Challenge

When upgrading the PowerExchange Listener and Logger to a new version it is important to migrate all the related components in order for the new version of PowerExchange to be fully functional. This article provides best practices for migrating existing DataMaps and for capturing registrations and extraction maps to the new version’s environment.

Description

The target audience for this article is the person/people responsible for installing software upgrades. Typically, this is a system administrator for the system where the PowerExchange Listener and Logger execute.

This document assumes that the new version is installed into different libraries, directories, or datasets than the old version of PowerExchange. There is also an assumption that the capture process will be started with a COLD start, eliminating the need to copy the existing PowerExchange Log files. Another assumption is that the personnel using this document have at least minimal knowledge of PowerExchange. If assistance is needed to perform the upgrade, Informatica recommends arranging for skilled professional services personnel to come on site.

When the new version of PowerExchange is installed into new datasets, libraries, or files then the old objects should be copied from the old environment into the new environment. Exactly what needs to be copied varies depending on the Operating system of the PowerExchange listener and whether PowerExchange Change Data Capture (CDC) is used. This document describes what needs to be copied based on whether there are non-relational sources defined, and if CDC is used.

Non-relational sources will have DataMaps defined and those will need to be copied. If CDC is used, there are capture registrations and extraction maps. The capture registrations define the physical view of the source data and are used by the capture process. The extraction maps define a logical view of the captured data. The extraction maps are imported into PowerCenter to be used as sources in Mappings.

Migrating i5/OS Objects

The library names can vary by site. Typically, the library names are prefixed with PWXvrm where vrm is the version, release and modification level (i.e., 961 for PowerExchange 9.6.1). Using different library names for each version and release modification level allows the new and old listeners to be executed in parallel, providing that different port numbers are specified in the LISTENER statements and in the DBMOVER members.

  • dtllib– PWXvrmDTL contains the PowerExchange binary files.
  • datalib– PWXvrmDAT contains configuration files capture registrations and logs.
  • datamaps– PWXvrmDMAP contains datamaps for non-relational data.
  • cpxlib– PWXvrmCPX contains the extraction maps.
  • condlib– PWXvrmCND contains captured data and configuration file for the PowerExchange Logger.

Note:  Most i5OS installations do not use a local PowerExchange Logger. Refer to the “Upgrading PowerExchange to a New Release on i5/OS” in the PowerExchange Installation Upgrade Guide.

DataMaps

DataMaps are stored in a library file specified by the DMX_DIR parameter in the DBMOVER member in the datalib/CFG file (e.g., DMX_DIR=PWXvmrDMAP).

If PowerExchange is being upgraded from version vmr to version vmr+1 then the contents of the PWXvmrDMAP library must be copied to the PWXvmr+1DMAP library.

Capture Registrations

The capture registrations are in the CCT file in the datalib library. The contents of the CCT file of the old datalib library must be copied to the CCT file in the new datalib library.

For example, copy the contents of PWXvmrDAT/CCT to PWXvmr+1DAT/CCT.

Extraction Maps

The DataMaps are in the library specified by the CPX_DIR parameter in the DBMOVER member in the datalib/CFG file (e.g., CPX_DIR=PWXvmrCPX).

The contents of the old cpxlib library must be copied to the new cpxlib library.

For example copy the contents of PWXvmrCPX to PWXvmr+1CPX.

Migrating Linux, UNIX, and Windows Objects

Informatica recommends that different versions of PowerExchange be installed in distinctly different directories (e.g., <install>/<directory>/pwx/v<version number>). This will isolate the PowerExchange binaries, configuration files and other definitions into separate directories. This will allow for execution of both the old and new PowerExchange listeners at the same time without impacting each other if different port numbers are specified in the LISTENER statements of the dbmover configuration files.

Refer to the section named “Performing an Upgrade Installation on Linux or UNIX” or “Performing an Upgrade Installation on Windows” in the PowerExchange Installation and Upgrade Guide for more details.

DataMaps

DataMaps are stored in the directory specified by the DMX_DIR parameter in the dbmover configuration file used by the PowerExchange Listener.

The contents of the directory in the DMX_DIR parameter for the old version must be copied to the directory specified in the DMX_DIR parameter for the new version.

Capture Registrations

The capture registrations are in the directory specified by the CAPT_PATH parameter in the dbmover configuration file used by the PowerExchange Logger. Copy the contents of the directory in the old CAPT_PATH parameter to the directory in the new CAPT_PATH parameter.

Extraction Maps

The extraction maps are in the directory specified by the CAPT_XTRA parameter in the dbmover configuration file. Copy the contents of the directory specified by the old CAPT_XTRA parameter to the directory specified by the new CAPT_XTRA parameter.

Migrating z/OS Objects

The recommendations below assume that the Full Installation option of z/OS Installation Assistant was selected and a different dataset high level qualifier (HLQ) was specified. The IDCAMS REPRO utility can be used to copy the VSAM datasets.

REPRO
            INFILE(ddname)
            OUTFILE(ddname)
            REPLACE

or

REPRO
            INDATASET(old.hlqvs.DATAMAPS)
            OUTDATASET(new.hlqvs.DATAMAPS)
            REPLACE

DataMaps

DataMaps are stored in the dataset specified by the DATAMAPS DD statement in the PowerExchange Listener JCL. Normally this will be HLQVS.DATAMAPS where HLQVS is the dataset high level qualifier specified in the z/OS Installation Assistant for VSAM datasets. This defaults to HLQ.V1. The value for the HLQVS parameter can be found in the GENBULK member of the HLQ.RUNLIB dataset.

Copy the contents of the DATAMAPS DD dataset in the old Listener JCL to the dataset in the DATAMAPS DD dataset in the new Listener JCL.

Capture Registrations

The capture registrations are stored in the dataset specified in the DTLAMCPR DD statement in the PowerExchange Listener JCL (e.g., HLQVS.CCT).

Copy the contents of the DTLAMCPR DD dataset in the old Listener JCL to the dataset in the DTLAMCPR DD dataset in the new Listener JCL.

Extraction Maps

The extraction maps are stored in the dataset specified in the DTLCAMAP DD statement in the PowerExchange Listener JCL (e.g., HLQVS.DTLCAMAP).

Copy the contents of the DTLCAMAP DD dataset in the old Listener JCL to the dataset in the DTLCAMAP DD dataset in the new Listener JCL.

 

 

Table of Contents

Success

Link Copied to Clipboard