What os durable subscriber

With a durable subscriber, the subscriber can be closed and recreated, but the subscription continues to exist and to hold messages until the application calls the unsubscribe method. In Figure  create stands for a call to TopicSession.createDurableSubscriber, close stands for a call to TopicSubscriber.close, and unsubscribe stands for a call to TopicSession.unsubscribe. Messages published while the subscriber is closed are received when the subscriber is created again. So even though messages M2, M4, and M5 arrive while the subscriber is closed, they are not lost. 

What is nondurable and subscriber

With an ordinary, nondurable, subscriber, the subscriber and the subscription are coterminous and, in effect, identical. When a subscriber is closed, the subscription ends as well. Here, create stands for a call to TopicSession.createSubscriber, and close stands for a call to TopicSubscriber.close. Any messages published to the topic between the time of the first close and the time of the second create are not consumed by the subscriber. Subscriber consumes messages M1, M2, M5, and M6, but messages M3 and M4 are lost. 

   Nondurable Subscribers and Subscriptions

JMS Server Configuration

The file jbm-jms.xml on the server classpath contains any JMS Queue, Topic and ConnectionFactory instances that we wish to create and make available to lookup via the JNDI.
A JMS ConnectionFactory object is used by the client to make connections to the server. It knows the location of the server it is connecting to, as well as many other configuration parameters. In most cases the defaults will be acceptable.
We'll deploy a single JMS Queue and a single JMS Connection Factory instance on the server for this example but there are no limits to the number of Queues, Topics and Connection Factory instances you can deploy from the file. Here's our configuration:

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xsi:schemaLocation="urn:jboss:messaging ../schemas/jbm-jms.xsd ">

We deploy one ConnectionFactory
called ConnectionFactory and bind it in just one place in JNDI as
given by the entry element.
ConnectionFactory instances can be bound in many places in JNDI if you require.





Note
The JMS connection factory
references a connector called netty. This is a reference to a connector
object deployed in the main core configuration file jbm-configuration.xml which defines the transport and
parameters used to actually connect to the server.

JNDI configuration
When using JNDI from the client
side you need to specify a set of JNDI properties which tell the JNDI client
where to locate the JNDI server, amongst other things. These are often
specified in a file called jndi.properties on the client classpath, or you can specify them
directly when creating the JNDI initial context. A full JNDI tutorial is
outside the scope of this document, please see the Sun
JNDI tutorial for more information on how to use JNDI.



For talking to the JBoss JNDI
Server, the jndi properties will look something like this:



java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://myhost:1099
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces                        
        
Where myhost is the hostname or IP address of the JNDI server.
1099 is the port used by the JNDI server and may vary depending on how you have
configured your JNDI server.



In the default standalone
configuration, JNDI server ports are configured in the jbm-jboss-beans.xml file where the JNDIServer bean is
confgured, here's a snippet from the file:




    
        
    

    1099

    localhost

    1098

    localhost

                       

Note

If you want your JNDI server to be available to non local clients make sure you change it's bind address to something other than localhost!

Process definitions

Activities
    are the individual units of work within a process definition. Activities are available on the various palettes within TIBCO Designer. Each palette has a set of activities that can be performed for that palette.

Transitions
    describe the flow of processing within a process definition. A transition is represented by an arrow between two activities. The arrows are unidirectional, and you cannot draw a transition to a previously executed activity. Control flow in a process definition must proceed sequentially beginning with the Start activity (or a process starter) and ending with the End activity

TIBCO Designer - GUI

 

Basic section of Tibco BW interfaces and there use.

Project Panel -
    A project contains resources that implement the enterprise integration. Ex- SharedConnections, ProcessDefinition

Palette Panel -
    Palettes organize resources and allow you to add them to your project. You select resources in the palette  panel    and drag and drop them into the design panel to add them to your project. 

Design Panel -
    The design panel displays the current resource selected in the project panel. The contents of the selected resource are shown in the design panel. For example, if you select a folder, its contents is displayed

Configuration Panel -
    The configuration panel allows you to specify various configuration options for each resource. The type and the purpose of the selected resource determine the contents of the configuration panel.

SOA is designed to break-down monolithic applications, reduce costs and increase IT agility

TIBCO BusinessWorks™ helps organizations meet the challenge of connecting and coordinating all of their corporate assets by providing an integration platform that can also play an integral role in the deployment of an SOA. BusinessWorks can mediate interactions among disparate applications and databases, automate business processes, manage transactions and Web services, handle exceptions, and process events. As an independent integration backbone, it can also abstract the complexity that comes with maintaining different SOA ecosystems, including various brands of Java EE application servers as well as .NET.

TIBCO - Power of now