ISIS Papyrus z/OS

Papyrus WebArchive Modernization Guide

Report Generation and ManagementPrinting and OutputAutomation

Papyrus WebArchive is a report generation and management product by ISIS Papyrus. Explore technical details, modernization strategies, and migration paths below.

Product Overview

Papyrus WebArchive archives print output, providing access through a web interface or an XML API.

Authentication methods include LDAP and Active Directory.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What is the primary function of Papyrus WebArchive?

Papyrus WebArchive is used to archive and retrieve print output. It captures output streams, indexes them, and makes them accessible through a web interface or API.

What output formats does Papyrus WebArchive support?

WebArchive supports output formats including PDF, TIFF, GIF, and AFP. This allows for archiving a wide range of document types.

How do users access archived output?

Users can access archived output through a standard web browser or programmatically via an XML interface. The web interface provides search and viewing capabilities, while the XML interface allows for integration with other applications.

Technical

What are the main system components of Papyrus WebArchive?

The main system components include the Capture Engine, Indexing Service, Storage Manager, Web Server, and XML API. The Capture Engine intercepts print streams, the Indexing Service creates searchable indexes, the Storage Manager handles data storage, the Web Server serves the user interface, and the XML API provides programmatic access.

What type of API does Papyrus WebArchive expose?

Papyrus WebArchive exposes an XML API for programmatic access. This API allows external applications to search, retrieve, and manage archived output.

What databases or storage mechanisms are used?

The system uses a relational database such as DB2 or Oracle for storing metadata and indexes. The actual archived output is typically stored on disk or in a content management system.

Business Value

What is the business value of using Papyrus WebArchive?

By archiving print output, organizations can reduce paper consumption, improve compliance with regulatory requirements, and provide faster access to information. This leads to cost savings and increased efficiency.

How does Papyrus WebArchive integrate with other systems?

The XML API allows for integration with other enterprise systems such as ERP, CRM, and ECM platforms. This enables seamless access to archived output from within these applications.

Security

What authentication methods are supported?

Papyrus WebArchive supports authentication methods including LDAP, Active Directory, and SAML. This allows for integration with existing identity management systems.

What access control model is used?

The system uses role-based access control (RBAC) to manage user permissions. Users are assigned roles, and each role has specific permissions to access archived output.

What encryption is used and where?

Data is encrypted both in transit and at rest. SSL/TLS is used for communication, and AES encryption is used for data stored on disk.

What audit/logging capabilities exist?

Papyrus WebArchive provides audit logging capabilities. All user actions, including logins, searches, and document access, are logged and can be reviewed for security purposes.

Operations

What administrative interfaces are available?

The system provides a web-based administration console for managing users, configuring settings, and monitoring system performance. A command-line interface (CLI) is also available for advanced administration tasks.

How is user management handled?

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

What monitoring/logging capabilities exist?

Papyrus WebArchive provides comprehensive monitoring and logging capabilities. System administrators can monitor system performance, track user activity, and troubleshoot issues using the administration console and log files.

Ready to Start Your Migration?

Download our comprehensive migration guide for Papyrus WebArchive or calculate your ROI.

Calculate ROI