Do you see any errors in the server startup? You can check if the enabled property in /atg/dynamo/messaging/SqlJmsProvider is set to true. Also if SQLJMSAdmin module is added under ATG-Required in your manifest file then your EAR should be having webModule.war for sqlJmsAdmin web-app.
There are no error regarding sqlJmsAdmin in logs.
When i am accessing http://localhost:8080/sqlJmsAdmin only blank tables are displayed.
Showing below messages on this page.
There are currently no SQL-JMS Clients
There are currently no SQL-JMS Queues
There are currently no SQL-JMS Topics
Have you defined the JMS destination queue and topic? SQL-JMS Admin would look for the lists of queue and topic names defined in requiredQueueNames and requiredTopicNames properties of /atg/dynamo/messaging/SqlJmsProvider component. So make sure you have defined JMS destinations using the requiredQueueNames and requiredTopicNames properties of the /atg/dynamo/messaging/SqlJmsProvider component within your application's config layer. You would also need to add the newly defined destination entries in dynamoMessagingSystem.xml.
You may also need to refer to ATG JMS messaging implementaion - Patch Bay configuration documentation to understand it better. Once you do all this you can do a JNDI lookup for the newly defined destinations in your application code and use them. Then you will also be able to see their data in SQL-JMS Admin.
SQL JMS admin interface internally uses various session and entity EJBs to fetch all the client, topic and queue data from the database. You can find all these in <ATG>\SQLJMSAdmin\j2ee-apps\sqlJmsAdmin\ejbModule. DMSEntityBean is the base entity bean which provides JDBC connection datasource through JNDI lookup of java:comp/env/jdbc/datasource.
Now this JNDI resource is declared in the app-server specific manner e.g. for JBoss it would be in <ATG>\SQLJMSAdmin\j2ee-apps\sqlJmsAdmin\ejbModule\META-INF\jboss.xml. The default JNDI name mentioned in it could be like java:/ATGMysqlDS which should be changed to match your actual ATG datasource name. You may directly change it the exploded directory of your EAR but also ensure that your change is gone into sqlJmsAdmin.ear present in the location <ATG>\SQLJMSAdmin\j2ee-apps when you reassemble and redeploy.