> It supports a simple Java API for invoking Web services, no matter how or where the services are provided.
> The WSIF API allows clients to invoke services focusing on the abstract service description-the portion of WSDL that covers the port types, operations and message exchanges without referring to real protocols.
> The abstract invocations work because they are backed up by protocol-specific pieces of code called providers.
> The decoupling of the abstract invocation from the real provider that does the work results in a flexible programming model that allows dynamic invocation, late binding, clients being unaware of large scale changes to services - such as service migration, change of protocols,etc.
> WSIF also allows new providers to be registered dynamically, so you could enhance your client's capability without ever having to recompile its code or redeploy it.
Showing posts with label Web Services. Show all posts
Showing posts with label Web Services. Show all posts
Jul 22, 2008
J2EE Connector architecture
The J2EE Connector architecture defines a standard architecture for connecting the J2EE platform to heterogeneous EIS systems. Examples of EIS systems include ERP, mainframe transaction processing, database systems, and legacy applications not written in the Java programming language. By defining a a set of scalable, secure, and transactional mechanisms, the J2EE Connector architecture enables the integration of EISs with application servers and enterprise applications.
The J2EE Connector architecture enables an EIS vendor to provide a standard resource adapter for its EIS. The resource adapter plugs into an application server, providing connectivity between the EIS, the application server, and the enterprise application. If an application server vendor has extended its system to support the J2EE Connector architecture, it is assured of seamless connectivity to multiple EISs. An EIS vendor needs to provide just one standard resource adapter which has the capability to plug in to any application server that supports the J2EE Connector architecture.
Multiple resource adapters (that is, one resource adapter per type of EIS) are pluggable into an application server. This capability enables application components deployed on the application server to access the underlying EIS systems.
The J2EE Connector architecture enables an EIS vendor to provide a standard resource adapter for its EIS. The resource adapter plugs into an application server, providing connectivity between the EIS, the application server, and the enterprise application. If an application server vendor has extended its system to support the J2EE Connector architecture, it is assured of seamless connectivity to multiple EISs. An EIS vendor needs to provide just one standard resource adapter which has the capability to plug in to any application server that supports the J2EE Connector architecture.
Multiple resource adapters (that is, one resource adapter per type of EIS) are pluggable into an application server. This capability enables application components deployed on the application server to access the underlying EIS systems.
More on :
Web Services
JMS Queue vs Topic
JMS Queue
> A staging area that contains messages that have been sent and are waiting to be read. As the name queue suggests, the messages are delivered in the order sent. A message is removed from the queue once it has been read.
> point-to-point
> Only one consumer will get the message
> The producer does not have to be running at the time the consumer consumes the message, nor does the consumer need to be running at the time the message is sent
> Every message successfully processed is acknowledged by the consumer
JMS Topic
> A distribution mechanism for publishing messages that are delivered to multiple subscribers
> Multiple consumers can get the message
> There is a timing dependency between publishers and subscribers. The publisher has to create a subscription in order for clients to be able to subscribe. The subscriber has to remain continuously active to receive messages, unless it has established a durable subscription. In that case, messages published while the subscriber is not connected will be redistributed whenever it reconnects.
> A staging area that contains messages that have been sent and are waiting to be read. As the name queue suggests, the messages are delivered in the order sent. A message is removed from the queue once it has been read.
> point-to-point
> Only one consumer will get the message
> The producer does not have to be running at the time the consumer consumes the message, nor does the consumer need to be running at the time the message is sent
> Every message successfully processed is acknowledged by the consumer
JMS Topic
> A distribution mechanism for publishing messages that are delivered to multiple subscribers
> Multiple consumers can get the message
> There is a timing dependency between publishers and subscribers. The publisher has to create a subscription in order for clients to be able to subscribe. The subscriber has to remain continuously active to receive messages, unless it has established a durable subscription. In that case, messages published while the subscriber is not connected will be redistributed whenever it reconnects.
More on :
Web Services
Subscribe to:
Posts (Atom)