Hi Atul,

It might be possible to add the .sh script to your External Scripting engine and within a report have the script get triggered, but this hasn't been tested so I can't promise that it will work and it really isn't properly supported to do that. It may also be possible to use another scripting language, such as Python or Perl and use that script to trigger your shell script. You could build a Java module to trigger this script as well, but this extensibility goes beyond what we would support for the LabKey platform.

With regard to the external schemas, they are only recognized within LabKey if they are configured in the labkey.xml. We have no other way of accessing databases otherwise as external schemas.

When you say that you are getting an internal server error when trying to access an external schema and table via the LabKey API, can you give us some more details? What API are you trying to use? Can you view the data within LabKey itself? What is the exact error you're receiving? Can you provide us with the stack error that appears when you do try to access the data?

Regards,

Jon