What were the main components of the Common Data Provider architecture?

CDP's architecture included components for data collection, transformation, and forwarding. Specific components included the Data Streamer, which collected data from z/OS sources; the Data Router, which transformed and filtered the data; and the Data Forwarder, which sent the data to target systems.

How did the components of Common Data Provider communicate with each other?

CDP communicated between components using internal APIs and message queues. The Data Streamer sent data to the Data Router, which in turn forwarded it to the Data Forwarder. Communication with external systems used protocols like TCP/IP and syslog.

How did Common Data Provider transform data?

CDP supported data transformation using mapping rules defined in configuration files. These rules allowed users to extract specific fields from log records, convert data types, and enrich data with additional information. This ensured that the data was in the correct format for the target analytics platform.

What business value did Common Data Provider provide?

By forwarding z/OS data to analytics platforms, CDP enabled organizations to gain insights into their mainframe operations. This allowed them to identify performance bottlenecks, detect security threats, and optimize resource utilization. This improved decision-making and operational efficiency.

How did Common Data Provider help reduce costs?

CDP helped organizations reduce the cost of mainframe operations by optimizing resource utilization and improving problem resolution. By providing insights into system performance and security, CDP enabled organizations to proactively address issues and prevent costly outages.

What authentication methods did Common Data Provider support?

CDP supported authentication using z/OS security mechanisms such as RACF, ACF2, and Top Secret. It integrated with these security systems to verify the identity of users and control access to data. This ensured that only authorized users could access sensitive information.

What access control model did Common Data Provider use?

CDP used an access control model based on z/OS security profiles. Access to data and functions was controlled by defining profiles in RACF, ACF2, or Top Secret. Users were granted access based on their roles and responsibilities.

What audit/logging capabilities did Common Data Provider have?

CDP logged all security-related events, such as authentication attempts, access violations, and configuration changes. These logs provided an audit trail of user activity and helped organizations detect and investigate security incidents. The logs were typically stored in SMF records or syslog files.

What administrative interfaces were available for Common Data Provider?

CDP provided a command-line interface (CLI) for administrative tasks. The CLI allowed administrators to configure data sources, define filtering rules, and monitor system performance. It also provided commands for starting and stopping the CDP components.

What monitoring and logging capabilities did Common Data Provider have?

CDP monitored system performance and logged events to SMF records and syslog files. Administrators could use these logs to identify performance bottlenecks, detect errors, and troubleshoot problems. CDP also provided commands for displaying system status and statistics.

What were the main configuration parameters for Common Data Provider?

CDP's configuration parameters included data source definitions, filtering rules, transformation mappings, and target system settings. These parameters were defined in configuration files and could be modified using the CLI. Proper configuration was essential for ensuring that CDP collected and forwarded the correct data.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Common Data Provider

IBM Not Supported z/OS

Data Discovery Mining and Processi Operations

Vendor

IBM

Product Overview

Common Data Provider (CDP) featured a three-tier architecture comprising the Data Streamer, Data Router, and Data Forwarder. The Data Streamer collected data from z/OS sources like SYSLOG, SMF, and VSAM files. The Data Router transformed and filtered the data based on configuration file rules.

The Data Forwarder then sent the processed data to analytics platforms like Splunk and Hadoop. Communication between components relied on internal APIs and message queues. Configuration was file-based, defining data sources, filtering rules, and transformation mappings.

LOGREC' with a type of 'SMF'. CDP integrated with z/OS security systems, supporting RACF, ACF2, and Top Secret for authentication and access control. Data transformation involved mapping rules defined in configuration files, allowing for data enrichment and format conversion.

CDP is no longer supported. Organizations should migrate to alternatives like Splunk Connect for z/OS, IBM Z Operational Log and Data Analytics, or Elasticsearch with appropriate connectors. Migration requires a detailed assessment of existing configurations and a phased approach to ensure minimal disruption.

Frequently Asked Questions

What type of data did Common Data Provider collect and what did it do with it?

Common Data Provider (CDP) collected z/OS system logs, SMF data, and other operational data. It then transformed and forwarded this data to analytics platforms. It supported filtering and data mapping to customize the data stream.

How was Common Data Provider configured?

CDP used configuration files to define data sources, filtering rules, and target analytics engines. These files specified which logs to collect, how to transform them, and where to send the processed data. The primary configuration file was often named something like 'cdp.config'.

With what platforms did Common Data Provider integrate?

CDP supported integration with analytics platforms like Splunk, Hadoop, and IBM Operations Analytics. It forwarded data in formats compatible with these platforms, such as syslog or delimited text. It could also load data directly into DB2 Data Analytics Accelerator.

Related Products

More from IBM

Access 1

Not Supported

z/OS

Alternatives available

Access 1 was a system monitoring tool designed to provide a centralized view of system resources across multiple platforms, including z/OS. It collected data from...

Operating System Application/Application Enviroment

View Details →

ACF/NCP

Not Supported

z/OSz/VMzVSE/VSEn

Alternatives available

ACF/NCP is a mainframe-based network operating system for communication controllers, initially developed in the 1970s. It supports protocols like SDLC, X.25, and SNA, enabling connectivity...

Supporting Services Networks and Communication

View Details →

ACF/SSP

Supported

z/OS

ACF/SSP is a suite of programs designed to support and manage ACF/NCP (Network Control Program) on z/OS systems. Key components include the NCPGEN utility for...

Supporting Services Networks and Communication

View Details →

ACO SolutionPac

Not Supported

z/OS

Alternatives available

ACO SolutionPac was an IBM solution for automating MVS operations on z/OS. It integrated with NetView to manage both system and network tasks. The core...

Operating System Automation

View Details →

Ada/370

Not Supported

z/OSz/VM

Alternatives available

Ada/370 was an IBM compiler for the Ada programming language, targeting z/OS and z/VM mainframe environments. It facilitated the development of robust and reliable applications....

Programming Language

View Details →

ADF II

Supported

z/OS

Alternatives available

ADF II was a mainframe-based 4GL application development system designed to create online applications for IMS and CICS environments. Its primary function was to accelerate...

CASE/Code Generation Application Development

View Details →

Similar Products

2cOPS

Active

by AnSyNova

z/OS

2cOPS is a comprehensive operations management solution for z/OS environments. It offers key features such as real-time system monitoring, automated job scheduling, and proactive alerting....

Operations Tools and Utilities

View Details →

Adabas Text Retrieval

Active

by Software AG

z/OSz/VMzVSE/VSEn

Adabas Text Retrieval is a text indexing and search solution designed for ADABAS databases. It enables full-text search capabilities, allowing users to efficiently search and...

ADABAS Data Discovery

View Details →

Application Discovery

Active

by IBM

z/OS

Application Discovery is a static code analysis tool designed to provide insights into application assets and their relationships, especially within z/OS environments. It helps organizations...

Infrastructure and Computing Assets Data Discovery

View Details →

Application Discovery and Delivery Intelligence

Active

by IBM

z/OS

Application Discovery and Delivery Intelligence (ADDI) offers a comprehensive solution for understanding and managing complex applications. It discovers application assets, including programs, copybooks, databases, and...

Infrastructure and Computing Assets Data Discovery

View Details →

ASG-becubic

Supported

by Rocket Software

z/OS

ASG-becubic is a multiplatform tool designed to discover and map IT resources, including platforms, application environments, database managers, applications, databases, job schedules, and middleware. It...

Infrastructure and Computing Assets Data Discovery

View Details →

ASG-Manager Products

Supported

by Rocket Software

z/OS

ASG-Manager Products offer a comprehensive solution for managing metadata within a z/OS environment. The suite includes several key components such as ASG ControlManager for metadata...

Data Discovery Mining and Processi

View Details →

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Are You a Vendor? Claim Your Listing

Common Data Provider

Product Overview

Frequently Asked Questions

What type of data did Common Data Provider collect and what did it do with it?

How was Common Data Provider configured?

With what platforms did Common Data Provider integrate?

What were the main components of the Common Data Provider architecture?

How did the components of Common Data Provider communicate with each other?

What configuration files were used by Common Data Provider?

How did Common Data Provider transform data?

What business value did Common Data Provider provide?

How did Common Data Provider help reduce costs?

What authentication methods did Common Data Provider support?

What access control model did Common Data Provider use?

What audit/logging capabilities did Common Data Provider have?

What administrative interfaces were available for Common Data Provider?

What monitoring and logging capabilities did Common Data Provider have?

What were the main configuration parameters for Common Data Provider?

Related Products

More from IBM

Similar Products

Help Improve This Directory

Are You a Vendor? Claim Your Listing