TIBCO Business Works (BW) is the platform where the Tibco process (known as integrations) are running. For developing the TIBCO integration, they have provided a tool which is known as TIBCO Designer. TIBCO Business Works is a Java-based platform, however, normally very little development is done in Java. At its heart, TIBCO Business Works is an XSLT processing engine with lots of connectivity components known as pallets. Development is done graphically by linking the Starter to Activities and eventually to an End Activity, very much like a traditional process diagram. Normally it looks like the below one.
Each of these diagrams is called a Process Definitions. we can create a number of Process Definitions based on our requirement. For developing a new project, you need to start with the Process Definition pallet from the pallet tab on the left-hand side.
Each Process Definition will have a start and End. To make our integration running we need to have a Process Starter instead of a Start Activity. Refer the below fig. I have highlighted some pallets in red which all are starter pallets. You can simply drag it into the right-hand side and this pallet will replace the normal start activity. The normal Start Activity, which indicates that it invoked from another Process Definition. such as Process starters.
The Process Starter triggers the invocation of the Process Definition based on some event. For instance, a File Poller Process Starter will trigger when a file placed in a specific directory which specified in its configuration. There are many such Process Starters, JMS Queue receiver, SOAP, HTTP, SMTP etc..
As you can see in the above figure, I selected Mapper pallet (Tokenize Rows) and giving input from the read file activity. then we can modify the content based on the requirement. Likewise, the are many Activities, including the ones above and JDBC, JAVA and FTP and we will be able to configure all these in our way in the configuration and input tab.