Preventive Service Planning
Abstract
This technote describes the feature comparison & migration scenarios of SAP BW Pack Open Hub Extract stage versus CPD SAP BW Extract connector.
Content
Disclaimer
CPD SAP BW Extract connector is a new connector dedicated to Cloud Pak for Data platform.
This document provide detailed guidance for migrating SAP BW Open Hub Extract Stage jobs on IIS to the SAP BW Extract Connector within the CPD. Only jobs compatible with the new SCAPI BW Connector features are subject for the potential automated migration.
New Cloud Pak for Data SAP BW 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)
- Cloud Pak for Data SAP BW connector only supports PUSH mechanism. PULL mechanism is not supported due to intermittent BW RFC server.
- In the Cloud Pak for Data SAP BW Extract Connector, the Source System Name and Program ID can be automatically created at runtime when the "Auto Generate Source System Name" option in Stage Properties is enabled by the user. The connector also allows you to set a custom Program ID prefix using the environment variable SAP_ACL_TP_PREFIX, which ensures ACL-compliant Program IDs in SAP environment.
For detailed configuration and usage information, refer to the corresponding technote. List of Environment Variables Supported by IBM Cloud Pak for Data SAP Connectors - When "Auto Generate Source System Name" checkbox is not enabled by the user, the Source System Name and Program ID must already exist in the SAP system. The connector runtime uses these values with read-only access to extract data into Open Hub Destination for third-party systems through process chains.
- Cloud Pak for Data SAP BW Extract connector supports Columns/Metadata through Asset Browser.
- Both sequential and parallel execution modes are supported
Migration Applicability Scenarios
- Automated migration process has been created to migrate the SAP BW stage jobs to SAP BW Extract connector. Users need to create the isx of older job design and import the same in Cloud Pak for Data environment.
Use ISTOOL for creating and exporting ISX files. For detailed instructions on the steps involved, refer
Export command for InfoSphere DataStage and QualityStage assests and How to use ISTOOL for EXPORT IMPORT Information Server ComponentsNote: Make sure that the ISX file export includes all dependencies if required, such as parameter sets and table definitions.
Here's a sample command:
istool export -dom DELVM04S02:9443 -u isadmin -p isadmin -ar /sap_bw_extract/BW_Extract_SNC_Load_Balancing_001.isx -ds 'DELVM04S02/dstage1/Jobs/BW_Legacy_CP4D_Migration/BW_Extract_SNC_Load_Balancing_016.pjb'If SAP BW Extract job is designed to use Parameter or Parameter Sets in job, ensure that you use the switch -includedependent in the command line tool.
istool export -dom DELVM04S02:9443 -u isadmin -p isadmin -ar /sap_bw_extract/BW_Extract_SNC_Load_Balancing_001.isx -ds 'DELVM04S02/dstage1/Jobs/BW_Legacy_CP4D_Migration/BW_Extract_SNC_Load_Balancing_016.pjb -includedependent''
Feature comparison
| Feature | Properties | IIS DataStage SAP BW Open Hub Extract Stage Support | CPD SAP BW Extract CONNECTOR Support | Feature Migration Feasibility |
|---|---|---|---|---|
| Source System | Attach Source System | You can attach source system from list of already existing source systems in SAP | List of available Source Systems is not present. Users can provide the Source System name in the "Source System" stage property. Prerequisite: The specified Source System and Program ID must already exist and be available in SAP before executing the job. | When the IIS stage is used, the selected Source System is displayed in the Source System stage property. |
| New Source System | Creates new source system within SAP | When "Auto Generate Source System Name" is enabled, the connector runtime automatically generates a valid Source System name and creates the corresponding Source System in SAP for use during data extraction. | IIS stage created source system will display for “Source System” stage property | |
| Remove Source System | Remove the selected source system from available list of source system in “DataStage Administrator for SAP BW”, doesn’t delete the source system from SAP | The connector runtime automatically deletes Source Systems that were created using the "Auto Generate Source System Name" option after successful data extraction. | Not Applicable | |
| Select Source System | From the list of attached source systems, select one | No list will be displayed for existing source system. You can only provide the source system name in stage properties | IIS stage selected source system will be available after migration | |
| Clear Source System | Clear the currently selected Source System in the job design. | This feature is more relevant in IIS, where source system property in “BW Open Hub extract stage” is non-editable and value is coming from “DataStage Administrator for SAP BW”. | Not Applicable | |
| Source System properties | Displays Source System Properties | This feature is more relevant in IIS, as source system creation happens in “DataStage Administrator for SAP BW”. | Not Applicable | |
| Program ID | Attach Program ID | The Program ID can be set in the Source System connection parameters during creation in IIS DataStage. This enables extraction into an Open Hub Destination for third‑party systems via process chains, while keeping the Program ID predefined in the Source System setup. | When the Auto Generate Source System option is uncheck by the user, the Source System Name and Program ID must already exist in SAP. The connector runtime then uses these values with read‑only access to extract data into an Open Hub Destination for third‑party systems via process chains. After the job completes, the Source System and Program ID remain unchanged on the SAP server. | IIS stage selected Program Id will be available after migration. |
| New Program ID | During Source System creation in IIS DataStage, the stage generates a Program ID in the format <IIS_DataStage_server_host>.<source_system> for the connection parameters. | When "Auto Generate Source System Name" is enabled by the user, the connector runtime generates a Program ID in the format HEXID_<autogenerated_SourceSystemName>. The Program ID is used during Source System creation and data extraction. | IIS stage auto-generated Program IDs will be migrated and made available as attached Program IDs in the CPD SAP BW Extract Connector. | |
| Process Chain | Select Process Chain | Select a Process chain from the list of available Process chains in SAP. | List of Process Chain names will be automatically populated in the stage properties “Process Chain” based on the selected Open Hub Destination during new flow creation. | IIS stage selected process chain will display for “Process Chain” stage properties. |
| Filter support for Process chain | Users can search the Process chain by name | List of Process Chain names will be automatically populated in the stage properties “Process Chain” based on the selected Open Hub Destination. No Filter option is available for Process Chain list. | Not Applicable | |
| Open Hub Destination | Select Open Hub Destination | Select the Open Hub Destination from the list of available OHDs in SAP. | List of available OHDs is available for new Jobs. | IIS stage selected OHD will display for “Open Hub Destination” stage properties. |
| Filter support for Open Hub Destination | Users can search the OHD by name | Users can search the OHD by name in displayed list of available OHDs for new jobs. | Not Applicable | |
| Skip Technical Keys | Skip Technical Keys | Un-Checked — Add technical keys in column metadata Checked — Remove technical keys from column metadata | Un-Checked — Add technical keys in column metadata Checked — Remove technical keys from column metadata | “Skip Technical Key” stage property will be checked/un-checked as per IIS stage selection. Un-Checked — Column metadata contains technical keys Checked — Column metadata doesn’t contain technical keys |
| Update BW | Update BW | Updates 3rd party parameters in SAP i.e., Source System, Process chain and Job name. | The connector runtime automatically updates the relevant third‑party parameter within the SAP environment. For all CPD SAP BW extract jobs, the DSJOB parameter in the Open Hub Destination is consistently set to the fixed value: CPD_SAP_BW_JOB_DEV110. | Not Applicable |
| Monitor RFC Server Logs | Monitor RFC | Display BW RFC Server logs in “DataStage Administrator for SAP BW”. | Connector runtime will initiate intermittent RFC Server; logs will display as Job logs. | Not Applicable |
| BW Table Name | BW Table Name | Display the underlying table name for the Open Hub Destination. | Not Supported | Not Supported |
| Column Metadata | Columns | Displays column metadata for OHD underlying table. | Displays column metadata for OHD underlying table. | IIS job column metadata will be present under columns. |
| Synchronize Columns | Synchronize and update the column metadata with SAP. | Not Supported | Not Applicable | |
| Validate Columns | Validate the column metadata with SAP. | Not Supported | Not Applicable |
The Static Program ID feature for the Cloud Pak for Data SAP BW Extract connector is supported starting from version 5.2.0 Patch 10, 5.3.0 Patch 4, 5.3.1 Patch 5, and all subsequent releases.
[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSHGYS","label":"IBM Cloud Pak for Data"},"ARM Category":[{"code":"a8m3p000000UoR7AAK","label":"Administration-\u003EConnections"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.0"}]
Was this topic helpful?
Document Information
Modified date:
03 August 2026
UID
ibm17250695