Have a look at my configuration that will respond to the client after a SOAP request is sent to a JMS queue.
It is a common scenario that an API Server must call out to a Security Token Service (STS) "off to the side" in order to get a SAML assertion issued for a user. This SAML Assertion then then usually inserted into the request, often as a HTTP header. Let's see how this is done with the Axway/Vordel API Server...
A common question about the Axway/Vordel API Server is "How do you change its listening port?". The key to answering this question is to understand what are the "Services" groups under Policy Studio for the API Server:
I will use WSO2 Developer Studio to write the custom mediator in this tutorial. You'll see a snippet of my sample proxy service below.
HATEOAS is a REST architecture principle where hypermedia is used to change application state.
Having worked with COBOL and Fortran legacy programs, it's easy to describe this legacy VB code as an abomination. Several customers. Several applications. Not a simple size of one. Abomination.
Going back to my previous post I said we should be able to use the same API to build our website as we expose. But what about when we want to have additional information on the website that isn’t pushed out to the client.
Prerequisites: Start the Synapse configuration numbered 6: wso2esb-samples -sn 6. Then start the Axis2 server and deploy the SimpleStockQuoteService if not already done
This linksheet has a nice big list of quick start guides, FAQs, and best practices for several of the major Java enterprise integration frameworks and utilities.
When implementing process automation initiatives, it is important to have a reuse strategy – why? Because, the process flows are a rich minefield for reusing services and common interfaces across a variety of use cases.
From a performance perspective, Apache Camel with Apache Tomcat depends on the Tomcat transport to provide high performant message transfer.
For this, we set up an experiment, which is very simple: Money has been stolen! We know that there are suspects, but we do not know who did it. The students have to build a Polygraph (Lie Detector) and have to test who is guilty or not.
This introduction shows the deployment of CXF-based SOAP web services as a WAR on embedded or standalone Apache Tomcat and as an OSGi bundle on Apache Karaf. How to create SOAP clients-both OSGi and standalone Java--is also covered.
This blog does not try to compare all available Web Services Development Frameworks but focuses only on three popular approaches regarding three Open Source frameworks: Apache CXF, Apache AXIS & Spring WS.
This tutorial runs through a method for building a Java web service in Eclipse using Apache Tomcat and Apache Axis. The process takes under ten minutes.
This is a brand new demo project that was put together by our very own Red Hat UKI SA team.
One of the first things you will want to know about Java EE 7, is how you can integrate some of the new APIs like WebSockets, with existing ones like JMS. That's why I decided to write this article "Integrating WebSockets and JMS with CDI Events in Java EE 7".
Spring MVC forms a solid foundation to implement REST based web-services in Java. However, in real-world projects developers still face challenges when it comes to advanced questions of REST. How to really leverage hypermedia?
We can do without architecture early on, but at some point a clearly communicated architecture offers big productivity benefits to developers who otherwise drown in the expanding implementation-level detail.
Typically most software engineering design patterns fall into one of three categories in regards to types. Three types of software design patterns include: Creational Type Patterns, Structural Type Patterns, and Behavioral Type Patterns
CMIS is an open standard that allows different content management systems to inter-operate over the Internet. Specifically, CMIS defines an abstraction layer for controlling diverse document management systems and repositories using web protocols.
We'll talk about common usability traps and the bugs we make or prevent consuming applications. Finally, we'll discuss approaches to API development that improve usability.
We'll cover resource modeling (URI design, and HTTP verbs/status code canonical usage), multiple representation support, testing, cache control, security (Http and OAuth), and API versioning. HATEOAS and REST maturity model are also discussed, along with an implementation of a sample API in JAX-RS and Spring MVC.
In this final video we take a look at the BPM process features, designer and examine how JBoss BRMS integrates decision tables into our online shopping cart application.