Papyrus WebRepository

Product Description

The Papyrus WebRepository is a facility using the Papyrus Objects infrastructure. It is based on the Object Meta System Architecture developed by ISIS Papyrus and also using an Objectspace-DB fully managed by the Papyrus Kernel. User access is available through Papyrus Desktop connected to a local Kernel (Fat Client) or a Browser communicating with a Papyrus Portal Node (Thin Client).Papyrus Objects is a Peer-To-Peer Application and Process Development Environment and requires that each node runs its own Objects Kernel. Objectspaces are supported on z/OS-USS, AIX, Solaris, HP/Itanium, Linux and Windows Vista and newer.

Papyrus WebRepository enables control for all document types and for all users online and offline, across platforms and output channels. Centralized management, installation and administration with a single point of control of

  • all document resources (text, forms, fonts, logos, ...) with version/variant control and validation
  • control of reused resources across multiple document applications (parent /child)
  • management and version control for Papyrus Eye GUIs and Scripts (Papyrus WebPortal)
  • user authorizations by ROLE/PRIVILEGE and POLICY
  • Change Management
  • automatic resource distribution
  • integrated Print Management/Job Control and Hot standby / Load balancing
  • security and auditing for the complete document lifecycle
  • offline operation by Proxy replication
  • application integration with Papyrus Adapters and Typemanagers

The WebRepository can be accessed through Fat Clients (Papyrus Desktop) or Thin Clients using a Browser connected to a Papyrus Portal Node. The GUIs are an integral part of the application design and can be freely configured with the Papyrus Eye GUI Designer guaranteeing identical results for Fat and Thin Clients and provide all resources in the open and standard IBM AFP format.

Papyrus Plug-Ins for standard web browsers enable the perfect reproduction of all documents and resources on all operating system platforms and printers.

Features

Functional description

The Papyrus WebRepository is unique as it does not predefine the object types made available to the application. The developer can define any CLASS definition required and build an application framework. By means of defining a state machine for an object, its behavior for complex business processes can be defined simply and executed as business objects in the Papyrus Objects environment. Objects are stored in a proprietary compressed binary format and are usually just a few kilobytes big, reducing memory, disk space and bandwidth.

Any kind of resource can be stored in a binary attribute, enabling the management of fonts, forms, logos, source code, executables, XML, HTML and virtually any other format. By enabling relationships powerful object structures can be defined and reduce the need for a relational database.

The WebRepository can also be accessed through the WebDesktop (Thin Client) and does not require an Objectspace installation. To define new CLASSES the GUI based Papyrus Desktop on Windows has to be used.

When used in conjunction with the features of the Papyrus Document Solution the most flexible and powerful management system for document applications and resources is available to the large corporation. It can also be used for website content management and managing a large network of distributed printers.

Papyrus WebRepository offers the following features

  • A central facility to store CLASS and TEMPLATE definitions
  • Manage any type of object and define its features
  • Version control for CLASS and TEMPLATE with from/to validity dates
  • Variant control for TEMPLATES with definable selector keys
  • Lifecycle Management for CLASS/TEMPLATE with development status
  • Import/Export of Object Frameworks
  • Versioning and Change Management for all document resources
  • Integrated Portal for thin client solutions

WebRepository Management Features implemented in Objectspace

  • System Framework (Metaclass, Template, Node, Repository, Library)
  • Authorization Framework (User, Role, Policy, Agent)
  • Role Based Access Control controls the access to objects and methods
  • PQL object queries
  • Several application Frameworks which can be applied as-is or individually adapted/extended to customer needs.
  • Application Analyzer (APA) Framework for full Papyrus on-line tracing and graphical monitoring of application and system resources

UML compatible CLASS Elements

  • CLASS Type
  • Attributes with its type and properties, standard GET/SET
  • Methods (operations) either supported by inheritance, delegation, as a material interface or by mapping to an external tool program
  • Relationships (reference, part, composed, contains, any)
  • State machine and transitions, send and receive events
  • UML CDL Constraints definition language for method calls

The Papyrus Desktop offers

  • The Class Editor
  • The Template Editor
  • The Object Window with display types
  • The ability to support standard browser Plug-Ins

The Papyrus Web Interface using the integrated Portal is a feature of the Repository or a dedicated Papyrus Application Server. A session object is instantiated for each user and communicates with the users browser.

The Papyrus Web Interface offers through Papyrus Eye

  • The Template Editor
  • The Object Window
  • Standard browser Plug-Ins
  • Customized GUIs for any corporate user based on ROLEs

The Objectspace Kernel supports

  • Persistent Disk Caching of all objects
  • Fetch-by-value object replication across IP communication
  • Modification level verification of changes (auditing)
  • Transaction management for multiple methods with Commit/Rollback
  • Address Space Separation through Shared Memory Interface

Prerequisites

  • TCP/IP services and Papyrus Objects (OMS)
  • Any Papyrus supported platform
  • Optionally standard databases (DB/2, Oracle, ...) for application integration and direct SQL queries using the Papyrus TypeManagers