What are the most common commands/operations users perform?

Common operations include collecting output (COLLECT), collating reports (COLLATE), bundling outputs (BUNDLE), sorting reports (SORT), and distributing reports (DISTRIBUTE). Configuration files are used to define processing rules and output destinations.

What types of APIs does this product expose?

The system exposes REST APIs for integration. Specific API endpoints include /reports for report management and /users for user management. Integration is supported through Java and C++ SDKs.

What administrative interfaces are available?

The administrative interface is available through a web console. User management is handled through the console, allowing administrators to create, modify, and delete user accounts. Configuration parameters are managed through configuration files.

What encryption is used and where?

Encryption is used for data at rest and in transit. Data at rest is encrypted using AES-256. Data in transit is encrypted using TLS 1.2. Audit logs capture user activity and system events.

How does Papyrus PostProcessing, PrintPool improve business value?

Papyrus PostProcessing, PrintPool automates report generation and distribution, reducing manual effort and improving efficiency. It centralizes output management, providing a single point of control for all output.

How does it reduce risks and improve compliance?

By automating report generation and distribution, Papyrus PostProcessing, PrintPool reduces the risk of errors and ensures timely delivery of critical information. It also improves compliance by providing audit trails and access controls.

How does it integrate with existing systems?

The system supports integration with existing systems through REST APIs and message queues. This allows organizations to leverage their existing investments and streamline data flows.

What authentication methods are supported?

Papyrus PostProcessing, PrintPool supports authentication methods such as LDAP, Kerberos, and X.509 certificates. It uses RBAC to manage access control, allowing administrators to define roles and assign permissions.

What access control model is used?

The access control model is based on RBAC, allowing administrators to define roles and assign permissions to users. This ensures that users only have access to the resources they need.

What encryption is used and where?

Data at rest is encrypted using AES-256. Data in transit is encrypted using TLS 1.2. This ensures that data is protected both when it is stored and when it is transmitted.

What audit/logging capabilities exist?

Audit logs capture user activity and system events. These logs can be used to track user actions and identify potential security breaches.

What administrative interfaces are available?

The administrative interface is available through a web console. This console allows administrators to manage users, configure the system, and monitor its performance.

How is user management handled?

User management is handled through the web console. Administrators can create, modify, and delete user accounts, as well as assign roles and permissions.

What are the main configuration parameters?

Configuration parameters are managed through configuration files. These files define processing rules, output destinations, and other system settings.

What monitoring/logging capabilities exist?

The system provides monitoring and logging capabilities. Administrators can monitor system performance through the web console and review audit logs to track user activity and system events.

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

Papyrus PostProcessing, PrintPool

ISIS Papyrus Active z/OS

Report Generation and Management Printing and Output Automation

Vendor

ISIS Papyrus

Product Overview

Papyrus PostProcessing, PrintPool features a modular architecture designed for scalability and resilience. The core components include the Input Manager, responsible for collecting output from sources such as JES, WebSphere MQ, CICS queues, databases, and text files; the Processing Engine, which transforms and manipulates the data; the Output Manager, handling the delivery of reports to various destinations; and the Archive Manager, storing reports for later retrieval. These components communicate via internal APIs and message queues, ensuring loose coupling and fault tolerance.

The system supports REST APIs for integration, with endpoints like `/reports` and `/users`. 509 certificates, with access control managed through RBAC. 2.

Competing products include IBM Content Manager OnDemand and OpenText Output Management. Papyrus distinguishes itself with its flexible input options, robust API integration, and comprehensive security features.

Frequently Asked Questions

What types of input sources does Papyrus PostProcessing, PrintPool support?

Papyrus PostProcessing, PrintPool collects output from JES, WebSphere MQ, CICS queues, databases, and text files. It collates, bundles, sorts, and distributes this output. Multiple outputs can be combined into a single report.

Where can reports be distributed or stored?

Output can be distributed to users or stored in DB2. The system supports bundling multiple outputs into single reports, which can then be distributed to one or more users.

What are the main system components?

The system architecture includes components such as the Input Manager, Processing Engine, Output Manager, and Archive Manager. These components communicate via internal APIs and message queues.

What authentication methods and access control models are supported?

Papyrus PostProcessing, PrintPool supports authentication methods such as LDAP, Kerberos, and X.509 certificates. Access control is managed through RBAC, allowing administrators to define roles and assign permissions.

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

Papyrus PostProcessing, PrintPool

Product Overview

Frequently Asked Questions

What types of input sources does Papyrus PostProcessing, PrintPool support?

Where can reports be distributed or stored?

What are the main system components?

What authentication methods and access control models are supported?

What are the most common commands/operations users perform?

What types of APIs does this product expose?

How do the main system components communicate?

What administrative interfaces are available?

What encryption is used and where?

How does Papyrus PostProcessing, PrintPool improve business value?

How does it reduce risks and improve compliance?

How does it integrate with existing systems?

What authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

What administrative interfaces are available?

How is user management handled?

What are the main configuration parameters?

What monitoring/logging capabilities exist?

Related Products

More from ISIS Papyrus

Papyrus DocEXEC

Papyrus Host

Papyrus PostCalc

Papyrus WebArchive

Similar Products

_beta access audit

_beta access monitor

_beta doc|z plus

_beta doc|z transform

$avers

ABARS/Assist

Help Improve This Directory

Are You a Vendor? Claim Your Listing