Resolution:
When the design-time palette code contacting with the EMS DTA for fetching the schema, it works in a way like RPC (Remote Procedure Call). Please find below the detailed steps of design-time palette code for doing 'fetch schema' operation:

1. The palette code will send a request, in this issue it is 'fetch schema' request, to a topic on which the DTA is waiting, and meanwhile the palette code creates another temporary topic for receiving the reply sent back by the DTA.

2. DAT will receive the request, and then busy with getting schema from Domino. You could notice that this could be a long time consuming job if there has so many fields need to be fetched from Domino side.

3. After the request has been sent out, the palette code will wait for a while (the waiting period is actually the timeout value configured in the field 'Request Timeout (milliseconds)' under the Design-time Connection tab), if it received no reply on that temp topic before timeout, this temp topic will be deleted from the EMS server.

4. Thus when later the reply finally comes back from the DTA side, the topic for sending this reply message is gone, so you will find the error log:
    com.tibco.sdk.MNestedException: "JMS error: "Invalid temporary destination"
to be printed on the DTA's console.

Solution:
We need to increase the timeout value configured in the 'Request Timeout (milliseconds)' under the Design-time Connection tab when configuring the adapter in Designer. This is to make the reply message received before the reply destination expired, thus avoid the issue.