1) A SAF Agent logs when it encounters problems, but the log messages are typically INFO or WARNING level, which won't show up in the stdout log. Check your main logs (typically under <domain-dir>/servers/<server-name>/logs).
2) Try send messages using a stand-alone client that runs in the same
3) If the SAF domain is different from the target domain, this requires setting up "cross domain security".
Thanks for your response.
In the AdminServer\logs\safagents\TestAgent
I can see log file is created but it's 0 KB
I tried to check others logs, not able to find any information related in Info,warning or error.
2) I tried to insert the message in a local queue using java program
3) cross domain security is Enabled
There are always WL server log files unless they've been deleted by something external. By default they're located in <domain-dir>/servers/<server-name>/logs/<server-name>.*log* -- and usually not in a subdirectory under logs titled "safagents". The server log file location is configurable - if it's been overridden, the location can be deduced by either (A) looking at the stdout capture file for the server, or (B) the config.xml server stanza for the server.
Note that if the send to the local JNDI name of the imported destination succeeded, but the message is not being forwarded, then you should be able to see the 'unforwarded' message reflected in the statistics for the imported destination.
Note that there's no need to configure a JMSServer or JMS Local Q in the local domain. If you give the JMS Server hosted Local Q with the same JNDI name as the imported destination Local JNDI Name, then these two JNDI names will conflict when the SAF Agent attempts to create an imported destination with this local JNDI Name. Based on your description of the source configuration, you might have configured such a conflict.
It's working fine. Local JNDI was the issue.