Resolution:
INSTALLATION

Q1.What are the different hardware and Operating systems supported?
Answer: Adapter version 3.2.1 is supported on NT 4.0, Solaris 2.6, Solaris 2.7, Solaris 2.8


Q2.Can Adapter and Infranet Server application installed on different machines?
Answer: Yes. It should be possible but we have not done any cross-platform testing.
--------------------------

EXECUTION

Q3. When starting the adapter, what if the repository not found?
Answer: Start the TIB/Repository server before starting the adapter.

Q4. Why does the adapter initialization fail?
Answer: Either the repository file (dat) is not placed in the &ltinstall_path>\tibco\repository\remoterepos directory, or the .dat file is not properly configured.

Q5. When an error occurs in the subscription mode, where is it displayed?
Answer: Errors that occur in the request-reply mode are sent to the client. Errors that occur in the subscription mode are logged to a trace file.

Q6. When running the adapter, why does the following error occur:
Answer: Connection to TIB CR failed You have referred an incorrect.DAT file in your command line.

Q7. Why does the adapter initialization fail, even after specifying the appropriate DAT file?
Answer: You must start the repository server before you start the adapter.

Q8. Why does the adapter fail to respond to a request after receiving it?
Answer: The subject name may be inconsistent. The subject name to which the adapter listens may be different from that of the subject name of the client.

Q9. How do you handle task group/task routing and errors from tasks?
Answer: Within a task group, you can send the output of the previous task to the next task. In addition, the task group attributes and the output of the previous task, if any can be routed to the next task. The task grouping does not have the scripting language required for conditional branching, which needs to be implemented using TIB/MessageBroker, TIB/IntegrationManager or TIB/InConcert.
You may execute a task group in transactional and non-transactional modes as explained below:
While running a task group in transactional mode, if a task fails in the task group, subsequent tasks are not executed and all the executed tasks will be rolled-back. The error from the task will be sent to the TIB/MessageBroker sheet (RVRPC Client).
For example, consider that there are four tasks in a task group namely T1, T2, T3, and T4. If T1 and T2 are successful and T3 fails, tasks T3 and T4 will will not be executed. The executed tasks T1 and T2 will be rolled-back. An error from Task T3 will be sent back to TIB/MessageBroker (RVRPC Client).
While running a task group in non-transactional mode, if a task fails in the task group, the subsequent tasks will not be executed. The successful tasks will not be rolled-back. The error from the task will be sent to the TIB/MessageBroker sheet (RVRPC Client).
Portal Infranet error messages are automatically mapped to the output class of the task group because you select gen_reply_base class (which stores error descriptions) as the super class for the output class. You need not map the error messages specifically. The error message catches the error information thrown by Infranet in the buffer pin_ebuf_t.

FAQs for Infranet Adapter Release 3.2.1