Upgrade to RPI v7.x
Overview
Redpoint Interaction (RPI) v7.x is the first cloud-native version of RPI, providing you with the latest in security, reliability, and flexibility.
The upgrade from RPI v6.x to RPI v7.x is more involved than previous upgrades, in that it involves migrating your infrastructure in addition to the RPI software itself. You can either perform the upgrade yourselves, or you can get assistance with the upgrade through Redpoint support/services. Alternately, you can move to a data-in-place or full SaaS model with Redpoint CDP, and not worry about upgrades again.
This page provides a high-level overview of why you want to upgrade to RPI v7, while the following pages cover the planning and upgrade processes:
Purpose
The purpose of this Redpoint Interaction upgrade path is to provide a well-defined strategy for upgrading Redpoint Interaction from v6.x to v7.x. It establishes guidelines and steps that guide Redpoint partners and on-premises clients through the upgrade process of Redpoint Interaction v7.x.
Scope
This upgrade path encompasses the processes and steps related to upgrading from RPI v6.x to RPI v7.x for all Redpoint partners and customers hosting in their private cloud or on-premises. This document is designed to cater to the needs and requirements for a successful upgrade to RPI v7.x. The upgrade process is applicable for Redpoint Interaction only.
Benefits
Make sure you have access to the best of RPI by upgrading to v7!
Some benefits include:
You no longer need to provision servers (virtual machines/VMs) to install RPI and its related services. VMs have limitations in terms of reliability, performance, and scalability, and can often be costly to maintain at the scale needed for perhaps just a subset of processes.
You no longer need to deploy multiple servers for high availability and/or disaster recovery. Deploying in containers ensures that if a single container/pod fails, another one will spin up for seamless recovery, making your environment more resilient. (See the next section for information about how specific RPI features also contribute to increased resilience.)
Make use of cloud-native services that provide increased security and reliability.
Benefit from the flexibility that comes from running in containers. Auto-scale makes it possible for a container to scale out to accommodate a resource-intensive process and then scale back down, ultimately resulting in overall environment cost savings.
Although you can install Kubernetes on-prem, doing so does not allow you to take advantage of the cloud services offered by providers such as Microsoft, Google, and Amazon.
Resilience
In addition to the increase in resilience related to containerization in general, upgrading to the latest version of RPI provides features that specifically improve resilience.
This list delineates the features that improve resilience in all of the RPI v7.x versions (through v7.4). Refer to the RPI release notes for more information about all of the new features added in each version.
Dedicated Queue Listener Containers
Queue Readers (dedicated container for draining/processing RPI queues)
Relevant to web events, web forms, visitor profiles, etc.
Previously managed via system tasks, which were much less resilient and scalable
Ops DB Housekeeping: Utilize Batching at Audit Data Deletion
This can help with mitigating contention issues
Auto-Replay Interaction: optionally configure an interaction to “auto-replay” on failure
Can include specific error strings to trigger auto-replay or always auto-replay
Improved Error Handling on “Execute Reader” failures at Export File Generation
Common transient error, added additional retry capability
Connection Resilience for SQL Server Error Code 18401 (related to transient errors)
Interaction Workflow Queueing
Setting max # of workflow executions at any given time
Ability to set interaction priority
Ability to set max time in queue
Next steps
Next you’ll plan your upgrade.