Preventive Service Planning
Abstract
This technote describes the feature comparison & migration scenarios of SAP Pack Delta Extract connector versus CP4D SAP Delta Extract connector.
Content
Disclaimer
Cloud Pak for Data SAP Delta Extract connector is a new connector dedicated to Cloud Pak for Data platform. It should not be positioned as the next version/generation of the existing Information Server SAP Pack connectors. As such there is no goal to have 1:1 feature parity with the legacy SAP Pack connectors. There is also no plan to provide automatic migration process from the legacy SAP Packs connectors to the new Cloud Pak for Data SAP connectors. The migration is only possible for selected scenarios where the feature and technology matching are possible.
New Cloud Pak for Data SAP Delta Extract connector features and limitations
- Cloud Pak for Data connector uses Cloud Pak for Data Connections UI’ to manage (create/modify/delete) SAP connection objects (no dedicated Admin UI available)
- According to the latest SAP recommendations only Operational Data Provisioning (ODP) extraction method is supported in the new Cloud Pak for Data connector.
- Cloud Pak for Data Delta Extract connector supports Columns/Metadata through Asset Browser
- Both sequential and parallel execution modes are supported
Migration Applicability Scenarios
- Only jobs created with SAP Application Pack Version 8.2.0.2 or newer are the potential migration candidates
- Only jobs compatible with the new Cloud Pak for Data Delta Extract connector features and limitations, described on the previous slide, are subject for the potential automated migration
- This especially applies to the ODP extraction mode. In case the original extractor is BW, no migration is possible. However, the user can still execute the job in Cloud Pak for Data by manually providing a subscriber name if the selected data source is ODP enabled in SAP system.
- Automated migration process is supposed to recreate in Cloud Pak for Data both SAP Delta Extract connection objects (available through ’Connections UI’) and corresponding Cloud Pak for Data Delta Extract connector instances usable in DataStage Designer
- We plan to create and publish more guides covering migration of jobs not compatible with automated migration tooling
Feature comparison
|
Feature/Properties
|
Delta Extract Stage Support
|
CP4D Delta Extract connector Support
|
Feature Migration feasibility
|
|
Extractor Type
|
Delta Extract Stage supports two extractor types:
1.Business Information Warehouse (BW)
2. Operational Data Provisioning (ODP)
This must be selected before you select DataSource.
|
Only ODP extraction is supported
|
Migration of job is only supported if the ODP extraction mode is selected originally. However, in case the original extractor type is BW, the user can still execute the job in CP4D by manually providing a subscriber name if the selected DataSource is ODP enabled in SAP.
|
|
Data Fetch mode
|
Supported modes
1. Full
2. Delta
|
Supported
|
This property shall be available in the migrated job. However, please note following
1. Delta Extraction would only be possible for the ODPs that are enabled for the Delta Extraction
2. Actual delta data extraction result for different Data Fetch modes will depend on last delta run of the job for that combination of DataSource and Subscriber in legacy environment.
|
|
DataSource
|
User can select a DataSource from the connected SAP system using this option.
|
Supported
|
User can select DataSource from Asset Browser. The selected DataSource, if ODP enabled, shall be available after migration to CP4D.
However, if BW extraction enabled, DataSource cannot be migrated
|
|
DataSource type
|
User can select the type of DataSource. Available options:
1. Transactional
2. Master
2.1 Attribute
2.2 Text
2.3 Hierarchical
|
Supported
|
This property shall be migrated in the migrated job as uneditable property that means user cannot change DataSource Type selection in the migrated job
|
|
Description
|
Gives description of the selected DataSource
|
Supported
|
This property would be available after migration
|
|
Hierarchy Selection
|
User can select a hierarchy name for the Hierarchical DataSource
|
Hierarchy browser is not supported in CP4D connector. However, as a workaround, user can manually enter the hierarchy name in the flow.
|
This property shall be migrated automatically
|
|
Hierarchy
|
Able to view the hierarchy of a DataSource
|
Supported
|
Property can be migrated to Hierarchy name
|
|
Activate Filters
|
Supported
|
Data Filters are supported but there is no UI to define the filter. The filter condition must be defined manually
|
Created Filters shall be available in the migrated job. Activate & remove filters are UI features and are not available in the new CP4D Delta Extract stage
|
|
Remove filters
|
Supported
|
Data filters are supported, but manual intervention is required to remove the filter
|
Created Filters shall be available in the migrated job. Activate & remove filters are UI features and are not available in the new CP4D Delta Extract stage
|
|
Restore columns
|
This option allows user to wipe the local changes in column definition and bring back actual copy of the metadata as retrieved from SAP during the selection of DataSource.
|
Not supported
|
This feature is not applicable for migration since users can only populate the column definition through asset browser.
|
|
Validate Columns
|
This option allows user to validate the metadata as present in the columns section against the actual metadata in SAP.
|
Not supported
|
This feature cannot be migrated to CP4D environment.
This feature was relevant in legacy environment only when the user edits column definition. Since, in the CP4D environment, the column definition is populated through asset browser only and user is not expected to edit the column definition.
|
|
Save
|
User can save the column definition by using this option.
|
Not supported
|
Same reason as cited above
|
|
Load
|
User can load from a given column definition by using this option.
|
Not supported
|
Same reason as cited above
|
|
Buffering mode
|
Buffering is used as technique in the DataStage jobs to make sure a constant and uninterrupted flow of data.
|
Not supported
|
Since this is the feature of DataStage and not the connector, hence migration is not applicable.
|
|
Connections
|
Establishing connection between SAP and DataStage through Admin tool
|
Don’t require any additional tool for adding a connection
|
All the connection parameters available in Delta Extract Stage are available in CP4D after job migration
|
| Execution Mode |
Uses Parallel/Sequential Mode
|
Can support both Parallel/Sequential Modes.
|
The Delta Extract connector has implemented partitioning support that allows user to run the migrated job in multiple runtime engine instance pods. Thus parallelism support can be migrated.
|
| Validate Stage |
Supported
|
The Delta Extract does not support the option of Validating Stage on UI.
|
Stage validation feature is not available in the CP4D environment. Since most of parameters validated by using this feature are BW extractor related, hence the customer impact is minimized.
|
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHGYS","label":"IBM Cloud Pak for Data"},"ARM Category":[{"code":"a8m0z000000GoyHAAS","label":"Tutorials"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
30 August 2022
UID
ibm16612969