Agility 3.

Simon BOUTY
Sept 5th, 2023

IPC Confidential
© Copyright 2022 IPC Systems, Inc. All rights reserved. Connecting opportunities
 Agility 3.2 features

IPC Confidential 2
www.ipc.com
© Copyright 2022 IPC Systems, Inc. All rights reserved.
 New OVAs
• Agility 3.2 is delivered now with Redhat 9
• Redhat version 9.2 will brings more security with the latest security fixes
• New OVA delivered for initial deployment
• Sizing modified to accommodate it

• Blue Wave Micro-services support

• Was already supported, but we allocated more resources to standard OVA to support all APIs
Summary Description Base OS Version CPU Memory (GB) Disk size

Kubernetes node used for administration and

Master node – Standard RedHat 9.2 4 6 GB 50 GB
management of the cluster

Kubernetes node used for administration and

Master node – HA RedHat 9.2 4 6 GB 50 GB
management of the cluster

Kubernetes node used to run the containerized

Worker node – Small RedHat 9.2 6 26 GB 140 GB
applications within the cluster

Kubernetes node used to run the containerized

Worker node – Medium RedHat 9.2 7 28 GB 175 GB
applications within the cluster

Kubernetes node used to run the containerized

Worker node – Large RedHat 9.2 8 32 GB 232 GB
applications within the cluster

Kubernetes node used to run the containerized

Worker node – XL RedHat 9.2 10 36 GB 346 GB
applications within the cluster

Kubernetes node used to run the containerized

Worker node – XXL RedHat 9.2 14 40 GB 484 GB
applications within the cluster

IPC Confidential
© Copyright 2022 IPC Systems, Inc. All rights reserved. IPC Proprietary 2023
www.ipc.com
Feature Introduction to Product Owners
3
 Additional features / Information

• Kubernetes and Base image OS and internal components for applications have been upgrade for security improvements
• No behavior change
• Check the compatibility matrix for impacts
• Improvement related to installation bandwidth limitation (allow an installation with 40Mbps minimum)
• It will take longer, if you have a smaller bandwidth, but won’t fail

• Sale items remain the same (use UNG-AGILITY-XXX for Agility 3.1 and above – the version is defined in the site prep)
• Upgrades still require a sale order / Project
• Do a change order to use the right sale items
• Site prep validation process remain the same
• Upgrades are still done by manufacturing with OVFs / disk swap
• Procedure available for OVFs checksum :
https://ipcsystems.atlassian.net/wiki/spaces/KNOW/pages/3146121318/Agility+OVFs+Checksum+Verification
• AMUI (Agility Management User interface) has been upgraded to version 2.1
• You have the possibility to get a report of your customer version on it (for customer which have been build from AMUI – so 3.0 and
above)

IPC Confidential
© Copyright 2022 IPC Systems, Inc. All rights reserved. IPC Proprietary 2023
www.ipc.com
Feature Introduction to Product Owners
4
 Site prep

• New Site prep Available: Version 7.8.7

• Number of Soft Client user

• Agility version updated
• Soft client version updated
• Unigy Version updated
• BWMS in the list of applications available
• Still need the ION ID as we use it for the naming convention in AMUI

• As a reminder, we propose to have ION deployed on Agility, only for the customer who already have it (so basically for upgrades) and for
expansion of an existing Agility customer.
• For an expansion you need to order a virtual ION separately
• Other use case should be through IPC safe connect for remote access

• As a reminded, do not forgot to add 2 Ips to the Starting IP address, for upgrade, as we don’t assign anymore ION Ips in the site prep. This
will allow you to keep the same IP for the VMs and HTTPS VIP

IPC Confidential
© Copyright 2022 IPC Systems, Inc. All rights reserved. IPC Proprietary 2023
www.ipc.com
Feature Introduction to Product Owners
5
 HTTPS Connectivity

• Available since Agility 3.1

• We have deployed it and used it for both Internet and Connexus
• Connexus required some NATTING, please contact NS delivery team to have it configured

• Customer facing documentation available on confluence specifically for HTTPS Connecitivity

• Includnig prerequites like DNS
• Explaining the role of the customer proxy
• Explaining the role of the Agility Local Management (ALM) and the requirement related to the customer AD for it
• https://ipcsystems.atlassian.net/wiki/spaces/KNOW/pages/3144908967/Agility+B2B+HTTPS+Connectivity+Why+How+When

IPC Confidential
© Copyright 2022 IPC Systems, Inc. All rights reserved. IPC Proprietary 2023
www.ipc.com
Feature Introduction to Product Owners
6
 Agility 3.2 – Documentation

• My.ipc.com

• Confluence article : Agility+Agent+CLI+guide+-+Production+usage+Agility+3.2

IPC Confidential
© Copyright 2022 IPC Systems, Inc. All rights reserved. IPC Proprietary 2022
www.ipc.com
Feature Introduction to Product Owners
8
 IPC Agility Deployment model
Agility 2.3 Agility 3.0 Agility 3.1 / 3.2

Log forwarding Through ION on Agility HTTPS (communication path HTTPS (communication path
agnostic) agnostic)

Ad hoc log enablement Through ION on Agility HTTPS (communication path HTTPS (communication path
agnostic) agnostic)
SCD Unigy ISO download Through ION on Agility HTTPS (communication path HTTPS (communication path
agnostic) agnostic)

Application update / Application Through ION on Agility HTTPS (communication path HTTPS (communication path
configuration change agnostic) agnostic)

Agility core update Through ION on Agility Through ION on Agility HTTPS

Ability to close connection for Log N/A N/A Web interface on Agility accessible
forwarding / App upgrade / to the customer
Configuration upgrade / Core
upgrade
Remote Access Embedded in Agility (ION) Independent of Agility Independent of Agility

IPC Confidential
© Copyright 2022 IPC Systems, Inc. All rights reserved. IPC proprietary and confidential information
© Copyright 2022 IPC Systems, Inc. All rights reserved. IPC Proprietary 2022
www.ipc.com
Feature Introduction to Product Owners