Board-Book_April_16_Special_Meeting.pdf — PaddleOCR-VL (Baidu)

All prerequisites must be verified during the project planning and kickoff phase prior to implementation;
If Client is a member of a Banner consortium and that consortium will be managing software releases through ESM then the supporting infrastructure to manage the release process in ESM for consortia members must be in place prior to the Banner 9 Essentials Plus engagement, including:

O BEIS Utilities

O BEIS SSO Manager

0 Application Navigator

0 Banner 9 Administrative Pages (Deployment)

0 The ‘master’ Consortia ESM instance has been installed; and

0 The 'master' Consortia ESM instance has been configured for consortia release management.

Client Responsibilities

Enterprise Infrastructure:

0 Provision the Virtual Machines ("VM"), including Operating System for:

Ellucian Solution Manager: 1 VM

0 Note that one ESM server can support multiple environments and Banner instances

Ellucian Ethos Identity: 2 or 4 VM's depending on deployment model

0 2-Node Cluster (recommended): Total of 4 VM's including 2 for non-production and 2 for production plus a load-balancer or proxy in a known working state.

0 Single-Node: Total of 2 VM's including 1 for non-production and 1 for production

BEIS (Utilities & SSO Manager): 1 VM

0 Total of 1 VM including 1 for production

Note that in non-production, the BEIS applications will reside on the same VM as the Banner 9 applications in the respective non-production environment

Banner 9 (Application Navigator & Banner Admin Pages): 2 VM's

0 Total of 2 VM's including one for each non-production environment

0 Ellucian Ethos Identity requires an Oracle or Microsoft SQL Server Database Instance in both non-production and production (cannot co-exist on the Banner Database Server).

O Request and install required SSL certificates from a trusted certificate authority for use in non-production and production environments.

0 Provide network administrative support for the configuring of firewalls, load balancer, and network devices as required.

Ellucian Ethos Identity:

The viability of clustering Ethos Identity (2-node) will be assessed during the planning phase. A load-balancer or proxy must be in place in a demonstrated working state. If determined that clustering will put the project at risk, a single node will be installed.

0 Provision constituent data into the primary user store for authentication. Note that if a non-production user store is not present, a container ("OU") in the production user store must be created for non-production accounts.

0 Provision the Banner UDCID's to the primary user store for authentication retrieval.

For Clients who cannot provision UDCIDs, UDCID Attribute Store Configuration must include:

0 Ellucian Ethos Identity (v2.0+) must be installed in non-production and production

O Banner must allow the ability for encrypted server requests (for JDBC connection with Ethos Identity) within the database server's “$ORACLE_HOME/network/admin/sqlnet.ora” file.

O User accounts exist within the client's primary user store; login ID's used for authentication (i.e., sAMAccountName or uid) must match the Banner gobtpac external user element.

Existing Identity Provider:

0 Ellucian will consider supporting SSO of the Banner applications in scope to an Identity Provider other than Ellucian Ethos Identity if certain requirements are met (below). The viability of this approach will be assessed during the planning phase and if it is determined that if using such approach will put the project at risk, Ellucian Ethos Identity will be installed.

One of the following Identity Providers are installed in a known working state with at least 1 service provider connection in both non-production and production:

Ellucian Ethos Identity (version 2.0 +)
Apero (JASIG) CAS (must support CAS v3.x protocol)
Active Directory Federation Services (ADFS)