Re^2: passing values from perl to unix app and getting result from the app

Thanks Chris(taint). I guess this should work.

Let me explain a bit. There is a tool which comes along with CA application. And that application has more than 100 options to choose from, and i am trying to automate that without even seeing the options on the screen. And that tool is called XPSExplorer. Below is the code on what i working on.

I have created a .txt file and run the code as below

perl callxps.pl input.txt

use warnings;
use strict;
use ARGV::readonly;
use Netegrity::PolicyMgtAPI;
system(XPSExplorer);
while (<>)
    {
        print;
    }
[download]

But what happens is that it doesn't pass the value in the text file to the command line, rather when i quit, it prints the value

Comment on Re^2: passing values from perl to unix app and getting result from the app Download Code

Replies are listed 'Best First'.
Re^3: passing values from perl to unix app and getting result from the app by taint (Chaplain) on Jun 06, 2014 at 13:43 UTC
Hello, ChristieJS. If I understand you correctly. You're working with `callxps.pl`, which is the XPSExplorer application/initiator, and attempting to pass input.txt, as argument(s) to that file. If so, the problem (I suspect) is. That `callxps.pl` wasn't designed that way. If you were on a NIX based box. You might* be able to make use of "redirection" -- (`callxps.pl < input.txt`). But, I suspect, a bit of a long-shot. Even if redirection worked. You're still going to need the keys. So that you can create key / value pairs. eg; `# assuming name, password are keys my $name = qw(ChristieJS); my $password = qw(SuperSecret); # or name = ChristieJS password = SuperSecret # or name: ChristieJS password: SuperSecret` [download] and how to best pass those, largely depends on the format expected from `callxps.pl`. You might even be able to pass `input.txt` as `perl callxps.pl & input.txt` [download] again, a bit of a stretch. Honestly, as should be pretty apparent by now, I'm groping. We still don't have enough details to effectively provide a reasonable solution. You might be able to find the keys in `callxps.pl`, and create a wrapper, that calls `callxps.pl`, passing the key values to `callxps.pl`. This, I think, for your situation, would be the best choice. But in the end. Without those keys. Providing a more specific answer/solution, is pretty much, a futile endevour. Now that you have a better idea of exactly what's required, perhaps you can figure it out. Or provide better details, so we might be better prepared to answer. --Chris Ąλɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: passing values from perl to unix app and getting result from the app
by taint (Chaplain) on Jun 06, 2014 at 13:43 UTC

ChristieJS

If I understand you correctly. You're working with callxps.pl, which is the XPSExplorer application/initiator, and attempting to pass input.txt, as argument(s) to that file.

If so, the problem (I suspect) is. That callxps.pl wasn't designed that way. If you were on a *NIX based box. You might be able to make use of "redirection" -- (callxps.pl < input.txt). But, I suspect, a bit of a long-shot.

Even if redirection worked. You're still going to need the keys. So that you can create key / value pairs. eg;

# assuming name, password are keys
my $name = qw(ChristieJS);
my $password = qw(SuperSecret);
# or
name = ChristieJS
password = SuperSecret
# or
name: ChristieJS
password: SuperSecret
[download]

pass

callxps.pl

input.txt

perl callxps.pl & input.txt
[download]

Honestly, as should be pretty apparent by now, I'm groping. We still don't have enough details to effectively provide a reasonable solution.

You might be able to find the keys in callxps.pl, and create a wrapper, that calls callxps.pl, passing the key values to callxps.pl. This, I think, for your situation, would be the best choice. But in the end. Without those keys. Providing a more specific answer/solution, is pretty much, a futile endevour.

Now that you have a better idea of exactly what's required, perhaps you can figure it out. Or provide better details, so we might be better prepared to answer.

--Chris

Ąλɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH

[reply]
[d/l]
[select]