TIBCO | BW Project Strucutre

-
As explained in earlier post TIBCO Designer is used to develop Enterprise middleware applications. It is necessary to follow certain structure to develop BW Project to ensure low complexity and easier component understanding. Standard structure also allows to follow certain software design patterns in enterprise applications.



Please find below sample well structure of TIBCO BW Project.

  Above TIBCO BW Project consist of following main components.
  1. Process Structure
    1. Service Component 
    2. Proxy Component 
  2. Deployment Folder
  3. Shared Resources
    1. Connections 
    2. Schemas
    3. Loader Processes/Shared Processes
    4. Shared Properties/Variables
    5. WSDLs/XSLTs
  4. Design Time Library 
  5. Optional Test/Stub process folder

Process Structure

While creating BW process in project first thing which needs to be determine is design pattern. Design pattern solves certain problems such persisting messages before processing it. Proxy pattern can be used to take data from SAP or other system from adapter/SOAP-HTTP/JSON before sending it to main component for processing.

We also needs to determine whether the process is Inbound or Outbound. 
  1. Inbound - Request coming from channel or different system using JMS Queue/Topic receiver/Adapter Subscriber
  2. Outbound - Response/Request sent to other system using JMS Queue/Topic sender/Adapter Publisher
Find below sample structure of processes.


Deployment Folder

Deployment folder should be separate from process folder. Each ear should be named according to service. If project is following proxy pattern then different ears should be created. Each for service and proxy.

Shared Resources 

Shared resources folder is important as they have connection details/schema/loader processes. It is advised to keep JMS/HTTP/JDBC connection objects in this folder. Keep GVs for all connection object in order to change at deployment time.

Design Time Library

Design time library can be used to import already developed TIBCO libs such as logging libs

Useful Links

Comments

Post a Comment

Popular posts from this blog

Spring | Using TIBCO EMS with Spring framework

-
TIBCO EMS can be use with Spring Framework to support message publishing and subscription. Spring provides JMS template to send JMS messages and @JmsListener/ MessageListener to subscribe it. Steps 1 : Create new project in eclipse or IntelliJ Idea Create new project with Spring dependency. We can use maven to add all required libs for this project. Maven takes care of adding referred java libs to build path. TIBCO JMS jars need to be added to build path. Pom.xml will be as follows. As you can see in above pom file we have added TIBCO JMS and Spring JMS dependency. Step 2 : Create JMS bean configuration file(Jms-conf.xml) Next we will create bean configuration file. It will set JNDI and JMS properties. We can use same JMS listener class to subscribe multiple queues and topics. Spring bean configuration take care of JMS transport setup. Env variables values can be provided via properties file. Step 3 : Create JMS Queue/Topic sender and Listner ...
Read more

TIBCO | For Loop - Accumulate output

-
Image
In this post we will check how TIBCO for loop works. TIBCO provides Group Activity to iterate over processes or activities. Loops can be different types eg. For Loop, While util loop, if loop, repeat on error etc. TIBCO group can loop over sub-process and accumulate output in end activity to be used by next activities. TIBCO For loop with Accumulate output repeats over process/activity and return output of each iteration in output activity. This is helpful where we want to call sub-process repeatably with different input parameters and store each output in some variable.
Read more

TIBCO | JNDI Server & JMS Instance creation

-
Image
In this post we will be creating TIBCO JNDI server and other instance pointed to JNDI server. First lets see what is mean by JNDI. It is   Java API for a directory service that allows Java software clients to discover and look up data and objects via a name. TIBCO EMS uses JNDI concept to lookup for EMS objects and its relations in messaging service. While developing enterprise level TIBCO solution it is advise or say standard practice to create one JNDI server(also one backup JNDI server) and other instance servers according to the functionality or domains. In this tutorial we will be creating one JNDI server and two domain servers.
Read more