Incoming and outgoing HTTP snap-in invocation

Last Updated : Feb 13, 2018 |

Avaya Breeze® platform enables a snap-in to display both webpages and web services to external browsers and applications. Avaya Breeze® platform snap-ins have access to the full suite of Java Enterprise Edition (JEE) classes and methods such as HttpServlet. Additionally, Jax-RS implementation enables developers to write RESTful web services. SOAP web services can be used by including SOAP libraries such as Apache Axis in the WAR module and the Service Archive file.

Developers do not need to concern themselves with routing of incoming HTTP requests to their Avaya Breeze® platform snap-in. When an Avaya Breeze® platform snap-in is deployed, the security module and the JEE container are configured on behalf of the deployed snap-in. Therefore, messages are correctly routed to the snap-in. This configuration ensures that any request sent to a URL of the form http(s)://<Avaya Breeze_FQDN>/snap-ins/<SNAP-IN_NAME> invokes the snap-in. If multiple versions of a snap-in are deployed concurrently, the preferred version is invoked.

In addition to enabling snap-ins to handle incoming HTTP requests, Avaya Breeze® platform snap-ins can invoke external web services by using the HTTP client library such as Apache HttpClient. For REST invocation, a snap-in developer can use Apache Wink. The Avaya Breeze® platform installer enables optional configuration of an outbound HTTP proxy if snap-ins invoke web services external to an enterprise firewall.

Avaya Breeze® platform must trust the far-end server’s certificate. For more information, see Avaya Breeze Snap-in Development, Outbound HTTPS Sample Snap-in, and Javadoc for the class com.avaya.collaboration.ssl.util.SSLUtilityFactory.