Beruflich Dokumente
Kultur Dokumente
Share 0
Tibco
44,500
THURSDAY, SEPTEMBER 30, 2010 SEARCH THIS BLOG
Search
2010 (5) September (5) TIBCO Adapters FAQ'S TIBCO EMS FAQ'S TIBCO RV FAQ'S TIBCO FAQ'S TIBCO BW FAQ'S
CONTRIBUTORS
vinay Arun
arun-tibco.blogspot.in/2010/09/tibco-adapters-faqs.html
1/7
2/12/13
Adapter Services : Adapters are responsible for making information from different applications available to other applications across an enterprise. To do so, an adapter is configured to provide one or more of the following services: Publication Service Subscription Service Request-Response Service Request-Response Invocation Service Publication Service : An adapter publication service recognizes when business events happen in a vendor application, and asynchronously sends out the event data in realtime to interested systems in the TIBCO environment. For example, an adapter can publish an event each time a new customer account is added to an application. Other applications that receive the event can then update their records just as the original application did. When an application receives a request to create a customer record, the application notifies the adapter about the request and the adapter publishes the event. User Interface-----------------Application X--------------Adapter -------------- TIBCO Messaging Create record Send to adapter Publishing Polls on the source data table (base table). Reads data from the source table. Sends the data to the message bus. Subscription Service: An adapter subscription service asynchronously performs an action such as updating business objects or invoking native APIs on a vendor application. The adapter service listens to external business events, which trigger the appropriate action. Referring to the previous example, an adapter subscription service can listen for customer record creation events (happening in an application and published to the TIBCO infrastructure) and update another application. TIBCO Messaging------------Adapter-----------Application Y Subscribing Update record Reads data from the message bus. Gives the data to the destination table. Request-Response Service: In addition to asynchronously publishing and subscribing to events, an adapter can be used for synchronously retrieving data from or executing transactions within a vendor application. After the action is performed in the vendor application, the adapter service sends a response back to the requester with either the results of the action or a confirmation that the action occurred. This entire process is called request-response, and it is useful for actions such as adding or deleting business objects. Receives requests from other applications. Parses the requests. Returns response (Sends only the requested data to the message bus). Request-Respons Invocation Service: An adapter request-response invocation service is similar to the request-response service, except that the roles are reversed. The vendor application is now the requester or initiator of the service, instead of the provider of the service. The adapter service acts as a proxy, giving the vendor application the ability to invoke synchronously functionality on an external system. How can u fine-tune an ADBAdapter? What are the different parameters that can be used? a) we can use publish by value or publish by reference for high speed and data type support like oracle long respectively. b) Can use polar or alerter for frequent and infrequent data changes respectively. c) Adb.PollingInterval, _ADB.DUPDECT.adapter_instance_name parameters can be used to do flow control and avoid duplication respectively.
arun-tibco.blogspot.in/2010/09/tibco-adapters-faqs.html
2/7
2/12/13
arun-tibco.blogspot.in/2010/09/tibco-adapters-faqs.html
3/7
2/12/13
arun-tibco.blogspot.in/2010/09/tibco-adapters-faqs.html
4/7
2/12/13
arun-tibco.blogspot.in/2010/09/tibco-adapters-faqs.html
5/7
2/12/13
files that match the specified criteria.
In Asynchronous mode the publication service allows other services of the instance to receive events while it is processing and publishing a file. By default Subscription service always operates in Asynchronous mode. If the configuration has more than one service or if the publication service is expected to process large file sizes or large set of files, setting the publication service in asynchronous mode is recommended. Types of file records (file adapter) File records can be classified into two categories: 1. delimited file record 2. positional file record Delimited file records are used to interpret lines that have a well-defined delimiter between the fields. Delimiters can be of single or multiple characters. These can be identified by the number of fields or by using a constant field value. Positional file records are used to interpret lines that have well defined field lengths. These can be identified using line or record length or by using a constant field value ie; constant line length. what is opaque table The subscription service uses two logical layers when processing a message. The first layer decodes data from the message and the second layer provides the database transaction. If an exception occurs in the first layer, the adapter logs the message to the opaque exception table. In the second layer, if any DML command fails at any level, the adapter rolls back this transaction and starts another transaction, inserting into exception tables. If the insert into exception table transaction fails, the adapter then logs the message to the opaque exception table. what is the difference between exception table and opaque exception table? The subscription service uses two logical layers when processing a message. The first layer decodes data from the message and the second layer provides the database transaction. If an exception occurs in the first layer, the adapter logs the message to the opaque exception table. In the second layer, if any DML command fails at any level, the adapter rolls back this transaction and starts another transaction, inserting into exception tables. If the insert into exception table transaction fails, the adapter then logs the message to the opaque exception table. What are the transport types supported by ADB adapters? The transport types supported by ADB adapters are: 1) Rendezvous 2) JMS Rendezvous Quality of service supported by Rendezvous: 1) Reliable 2) Certified 3) Transactional Wire Formats Supported by Rendexvous: 1) Active Enterprise Message 2) Rendezvous Message 3) XML Message JMS Wire Formats Supported by JMS: 1) XML Message Connection Factory Type Supported by JMS: 1)Topic 2)Queue Delivery Mode Supported by JMS: 1) Persistent 2) Non-Persistent
arun-tibco.blogspot.in/2010/09/tibco-adapters-faqs.html
6/7
2/12/13
Posted by Arun at 1:12 AM Labels: TIBCO Adapters FAQ'S
3 comments:
tibco said... REALLY U DID A GREAT JOB ..NO ONE IS SHARING INFORMATION ABOUT TIBCO EVEN THEY KNOW..BECAUSE OF HAVING MARKET VALUE FOR THAT COURSE CAN U POST A SMALL EXAMPLE USING XSLT AND XML AND OTHER PALLATES PLZZZZZZZ January 8, 2011 at 6:39 PM
Javin @ tibco messaging tutorial said... Nice article , you have indeed covered the topic quite well. I have also blogged my experience as Tibco Tutorials for beginners and intermediates , let me know how do you find it. Javin TIBCO Interview Questions asked in Investment banks July 2, 2011 at 9:42 PM
Anonymous said... Good one... CAn you tell me how to install SAP adapter? July 9, 2012 at 11:45 PM Post a Comment
arun-tibco.blogspot.in/2010/09/tibco-adapters-faqs.html
7/7