7.

Problem With The Documentation And Installation

I found some broken links in the TIBCO web site, such as https://docs.TIBCO.com/
TIBCODoc that shows a page requested does not exist message. (A more complete
list can be found in the appendix of this manual)
Apart from the documentation, I had problems with the installation. Later on I realized
that the sequence of product installation mattered a lot and that each product should
be unzipped individually and installed individually in a particular.
The problem was caused by my manipulation of the zips. I unzipped the Rendezvous,
the Runtime Agent and the Business Work, all together into a single directory. Then I
executed the UniversalInstaller. The installation finished but reported a warning
saying the Rendezvous should come before anything else.
Being a warning, I went on. My concern was to get acquainted with the products, so I
opened the Designer and started looking for some basic tutorial, which I ran and
looked promising at first.
Integration Knowledge Kit Appvance Inc. August 5, 2013
TIBCO BusinessWorks Developers Journal Page 14 of 75
8. Getting To Know The Designer
Tuesday, June 18
th
Time: 8 hours
I started the day following some tutorial for working with the Designer, which
starts with some really simple examples. I spent the day trying the test all the
features I was going to require for the job at hand.
Architects Comment: The developers strategy was to learn and get
familiarized with the tool first, before jumping on development. Still, there
were some functionalities that were not that intuitive at first, like the use of
predefined XSDs in the service input and output tabs. The work model is
different, and the expectation was to be able to create the transportation and
message definition in the service. Instead, the tools requires you to create
first other resourced to be used later on in the service definition, for instance.
Integration Knowledge Kit Appvance Inc. August 5, 2013
TIBCO BusinessWorks Developers Journal Page 15 of 75