Let's Talk

Papyrus Platform: Made for the Cloud

The modular distribution of products over operating systems, virtual layers and hardware allows us to collect or separate functionality to take full advantage of your infrastructure.

Papyrus Architecture Deployed in Containers

When deploying Papyrus nodes into a Container based architecture each container represents software components as a self-contained packages of the application processes – or App Groups. The ensures that the application runs quickly and reliably on one computing environment or another whilst removing dependencies to runtime libraries previously shared between applications. Furthermore, various orchestrator solutions like Kubernetes, RedHat, OpenShift provide the concept of "pods", which is a logical group of containers belonging together.

Papyrus allows for 1-n nodes to be collected into App Groups and deployed to Containers thus providing scalability at the service/function level whilst removing dependencies to other applications running on the same server and potentially sharing libraries.

App groups/Containers will be custom configured during the project based on the application’s requirements.

Requirements:

  • TCP/UDP communication between cloud server instances where Papyrus is running
  • Papyrus IPASaaS
  • Papyrus products running in concurrent mode

Papyrus Architecture Deployed to Virtual Servers

Papyrus software architecture and its nodes can be distributed across not only many operating system but also across a range of server architectures. Virtual servers have been with us for many years now and are fully supported within the Papyrus platform with many such deployments around the globe.

Papyrus Production, Development and Test environments are deployed onto your virtual servers, collecting application functions together to maximize performance. Your virtual platform must only allow TCP communication between the servers for Papyrus to operate over an unlimited amount of VMs.

Once Papyrus is deployed you can take advantage of the various features of virtual servers. For example, quick hardware scaling per virtual server instance is supported by Papyrus automatically. If you increase your server’s CPU and memory capacity temporarily or long term, Papyrus will automatically use more system resources to speed up your production. Hardware usage can be configured as limited or unlimited even at individual component levels to ensure you route the additional resources to the features prioritized by your business.

Requirements:

  • TCP/UDP communication between cloud server instances where Papyrus is running
  • Papyrus IPASaaS
  • Papyrus products running in concurrent mode

Designed to enable the enterprise to implement distributed object-oriented business solutions, the Papyrus Platform is a distributed system of objects (peer-to-peer architecture) in which all nodes (computers in a network) may use the same objects residing on the domain controller or any other nodes.

Papyrus software modules run functionally transparent on all supported versions of Windows, AIX, HP-UX, Sun Solaris, Linux and the IBM mainframe (z/OS, z/Linux, USS) as well as on virtualization platforms such as VMware, ESX Server, Citrix and Amazon Cloud.

All nodes use identical software features - there is no difference between client and server

The illustration shows an architecture distributed across different operating systems, which is very common in mid- and large enterprises.

How to Deploy Papyrus in the Cloud

Papyrus Distributed Architecture in the Enterprise

The Papyrus domain controller is the main and central point of the system. All other locations, branches or departments are nodes to the overall domain, and they use proxy replication for increased performance - allowing offline work for disconnected periods but still centrally maintaining all the process steps, document templates and resources.

Nodes can run on any of the supported operating systems, in a mixed environment and/or in a cloud infrastructure such as Amazon Cloud. In fact, Papyrus has unlimited scalability as it provides the capability to replicate nodes with load balancing and fail-over. With Papyrus, it is possible to run the core of the system in the cloud, while certain nodes, such as those to connect with internal applications, can be kept internally.

Papyrus enables companies to provide their thousands of business users and partners working remotely to work offline for a certain period. The Papyrus Digital Platform automatically performs a bi-directional sync when any of the business users connects to the network.

Papyrus SOA in a Peer-to-Peer Node Network

A typical production domain consists of several nodes, each of them providing specific services which are centrally managed. A node can run in isolation or together with other nodes on any of the supported operating systems.

Papyrus SOA-based architecture

The Papyrus Digital Platform makes use of the Service Oriented Architecture of the Papyrus Platform as it not only allows to run a case (one or more processes) on any of the nodes but it is also possible to define on which node a specific task should be executed.

Central or distribute execution

Papyrus ACM provides the ability to execute the processes centrally or distributed while the management of those processes can still be performed from a central point.

Click to read case study

Mobile
Business Solutions

With applications running natively on all mobile devices, enterprise users communicate and take action with direct back-office connectivity.

Read More

Click to read case study

Social
Media Integration

Does your customer service plan involve social media? Papyrus fully integrates with all channels – Twitter, Facebook, LinkedIn, etc.

Read More

Click to read case study

Papyrus
in the Cloud

The Papyrus Software platform can run on cloud infrastructure with unlimited scalability with load balancing and fail-over.

Read More

Click to read case study

Mobile
Inbound Capture

Enables flexible, accurate data capture and real-time processing from customer, remote staff or field service devices.

Read More