T1708 - Exhibit 2 Technical Environment 11.07.2025.pdf

Exhibit 6 Technical Environment

23DPP00838 1 | Pa g e

CURRENT TECHNICAL ENVIRONMENT

The NJKiDS application is based on the J2EE platform with multiple logical tiers: the presentation, business, and database and integration tiers.

The NJKiDS web application framework is built on J2EE Model View Controller (MVC Model 2) pattern. This pattern uses a controller servlet between the browser and the JSP pages (or servlet content for AJAX calls) being delivered.

The controller centralizes the logic for dispatching requests to the next view based on the request URL, input parameters, and application state. The controller also handles view selection, which decouples JSP pages and servlets from one another.

Model 2 applications are easier to maintain and extend, because views do not refer to each other directly. The Model 2 controller servlet provides a single point of control for security and logging, and encapsulates incoming data into a form usable by the back-end MVC model.

NJKiDS application has four IBM p series hardware devices to serve all tiers and environments. There are two dedicated LPARS setup for the HTTP Servers in a clustered environment. The load balancer will distribute the load between these two HTTP servers. In case one HTTP server is down, all the requests will be routed to the other HTTP server and thus, providing for high availability of service. These HTTP Servers work in conjunction with application servers. The WebSphere Application Server supports a variety of web servers. The web servers direct traffic from users' browsers to the applications running in WebSphere via the WebSphere plug-in to be installed on the Web servers. For NJKiDS, it will act as a router, deciding what traffic will be forwarded to WebSphere and what traffic the Web server itself will handle.

This workload management process also takes care of failover and backup servers in the event that one cluster member should fail.

Zones Network Components Description 4 Local Area Network (LAN) Site location specific. The LAN traffic is routed out of a

Site location through the DHS Enterprise Network or Wide Area Network.

3 Wide Area Network (WAN) A site location’s backup network path to the DHS Enterprise Network and can access the Enterprise Core applications and State legacy application and network services. Through the use of firewalls and router access control lists, network traffic will be restricted to only allow access to authorized applications and network services.

2 Enterprise Network A site location’s primary network path to the DHS Enterprise Core applications. Through the use of firewalls and router access control lists, network traffic will be restricted to only allow access to the NJKiDS application and network services.

1 Enterprise Core The Enterprise Core consists of network connectivity between various tiers and systems. Through the use of firewall access control, network traffic will be restricted to only allow access from network to server and server to server.

The following software specifications of the Array Networks APV/AVX load balancers are utilized in NJKiDS.

23DPP00838 2 | Pa g e

1. Layer4-7 Load Balancing – This feature is configured to enable the APV/AVX to use a Virtual Interface Protocol (VIP) address to load balance web traffic to web servers based on URLs.

2. Sticky Cookies – This feature will be configured so that if the APV/AVX determines that a client is already served by a particular service, it will place the client request on that service, regardless of the load balancing criteria specified by the matched content rule. If the APV/AVX determines that the client is not stuck to a particular service, it will apply normal load balancing to the content request.

3. TLS/SSLTermination – This feature will be configured so that when an entry is created in a proxy list to define the flow between an TLS/SSL module and a client, the module will operate as a virtual T LS / SSL server by adding security services between a web browser (the client) and the HTTP connection (the server). All inbound TLS/SSL flows from a client will terminate at an APV/AVX

Server Software

• IBM WebSphere : The NJKiDS application will be deployed on the IBM WebSphere Application Server The NJKiDS application will provide for deployment in the form of an EAR (Enterprise Archive) file.

• IBM HTTP Server: IBM HTTP servers will be used as Web servers for the NJKiDS application.

The Web server receives requests from a user and directs them to an appropriate application server for further processing.

• Rational ClearCase LT: Rational ClearCase is the versioning software used for version control of software artifacts and documents. All project related documents, source code and EAR files will be maintained in Rational ClearCase.

• WebSphere MQ: NJKiDS application will use WebSphere MQ as the integration broker to interface with the AOC’s FACTS application.

• Oracle: All NJKiDS data requirements are served by an Oracle database.

• TOAD: Quest Software’s TOAD will be used to develop PL/SQL stored procedures.