Jakarta EE (Enterprise Edition) Connector v4

This page is intended to give a high-level technical overview of the Jakarta EE Connector v4. To prevent malicious actors from compromising the security of our customer's high-profile sales and registrations, we host our in-depth Connector v4 documentation in private repositories.

If you need more detailed integration documentation than this page offers, connect with one of our technical experts who can understand your use case and determine the optimal setup for your tech stack.

The following diagram shows the Queue-it logic with a server-side Connector.

1. User requests a page.
2. The validation method sees that user has no Queue-it session cookie and no Queue-it token and sends him to the correct waiting room with a valid token based on the configuration.
3. User waits in the queue.
4. User is navigated back to your website, now with a valid token.
5. The validation method validates the token and creates a Queue-it session cookie.
6. The user browses to a new page and the Queue-it session cookie will let him proceed without queuing again.

To integrate using the Queue-it Jakarta EE Connector v4, you will need:

• An active Queue-it account
• Working Java Environment
• Queue-it admin available (Someone available with Queue-it GO platform access and familiarity with GO account configuration settings.)
• Java developer available (Someone available with knowledge of Java code, how to make changes to it and installing Maven Packages.)
• A non-production Java environment that can be used for the initial implementation and testing the new Queue-it Connector.

Complete these steps in order for best results.

1. Install Queue-it Jakarta EE Connector Framework either by adding dependency or Maven package
2. Implement Queue-it in the Code

Waiting rooms and their protection scope are created and configured in the GO Queue-it Platform and server-side (KnownUser) configuration information must be propagated to the application environment for real-time access by the Queue-it Connector. When an integration configuration is saved (published) in the GO Platform, the server-side configuration settings are packaged into a server-side JSON file and positioned on the Queue-it server, ready for secure downloading. Propagation of these settings (JSON) to the Java environment is performed automatically by the Queue-it Jakarta EE Connector whenever the Queue-it integration configuration is published.

Prepare for the integration in the GO Queue-it Platform:

1. Create a basic waiting room with an “Always Visible” queue page. (Make sure your domain is added in the waiting rooms configuration)
2. Create a KnownUser QUEUE action associated with the new waiting room and select the All Pages (Queue-it) built-in trigger. (Integration > Actions)
3. Publish the configuration. (GO Settings > Integration > Overview)