lohithhr wrote:
I have one requirement in which source is the flat file (data content is delimited by "|" ) which need to be read and upload data after validation into clarity system. For this, I thought performance perspective UNIX scripting is the best option to perform file operation to accomplish this requirement
I agree with you
100%; use Unix for simple file manipulation at o/s level every time!
lohithhr wrote:
however I don't have solution on calling UNIX scripting from clarity application.
As I tried to reply earlier; we can't just call a Unix script from a Clarity job. Clarity is only talking to the application server and it does not really "
know"
anything about the underlying operating system (or where
YOU have decided to deploy
YOUR Clarity servers - Unix / Windows / etc)
lohithhr wrote:
Could you please advice how this requirement is achieved from clarity?
However,
YOU know a bit more than Clarity does....
YOU know where your Unix server is (for example I don't; I don't know where your Clarity servers are (Windows/Unix), I don't know where your database server is (Windows/Unix) - I'll assume at least one of your servers is a Unix server (but even then that might not be true?))
So I have tried to give you the "tools" to work out what
YOU can build (that can be initiated as a Clarity 'job') which can "host out" to the operating system (in some manner). The solution that is appropriate to
YOU depends on
YOUR system configuration.
--
Alternatively, have you considered ignoring Clarity totally for this - control everything from Unix / Unix job schedulers etc and just "call" Clarity from Unix when you need to?