How to run a not directly executable application? : General Questions

[Gregstom]

Hello,

1. Please check the screenshot attached - for a "New Recording" window what should I specify in the "File name" and "Arguments" fileds in order to launch apipro7.CMD?

2. If I have an optional invoke action (OK button pressing for a window which may popup) - how do I customize the default 1min timeout? "Set Search timeout" selection on action's right mouse click doesn't do anything...

BR, Grygoriy

[Support Team]

Hi,

Add1:
You can just select the specific file and the arguments, if you need to set some.
If you need to set a working directory you just have to right click on the generated action and set the working directory in the appeared properties view.

Add2:
You can set the "Search Timeout" of each repository item, just right click on it and open the properties window, now you are able to set another Search Timeout.

Regards,
Markus
Ranorex Support Team

[Gregstom]

Hello Markus,

Thanks for your efforts,
1. As you see from the 1st screen when application is launched from CMD file it looks for two 'arguments' which are apipro.pf and apipro.ini files located in Work catalog. So I set 'File name' to progress environment and what should I type in "Arguments" filed? I attach another screen where I tried to separate them by coma still it gives an error.. any specific syntax?

2. I found "Properties" window. But the default value is grayed-out.. how do I change it?

[Support Team]

Hi,

Ad 1.: to set the mentioned command line arguments you have to type them the same way as you do in your batch file:

Code: Select all

-pf apipro.pf -ininame apipro.ini

Ad 2.: The Effective Timeout is the sum of each Timeout affecting your repository item.
So if you have a Search Timeout of 30s for your Applications folder and a Search Timeout of 30s for the specific control the Effective Timeout is 1m.
So, you can't set the Effective Timeout, but the Search Timeouts it is based on.
Note: The Search Timeout is the maximal time span Ranorex is trying to find your control - it's not some kind of delay.
So, if you'd like to make a delay, you might set the duration of the specific step in your Action Table.

Regards,
Tobias
Support Team

[Gregstom]

Thanks Tobias,

Now it's clear as for Ad2
Regarding Ad1: sorry but I still cannot manage it to work. It gives an error:

AFAIK it happens because we miss the working path. To be more specific:
1. We have work catalog D:\apiproinst\APIPRO7_0_02\WORK
2. We have PROGRESS environment c:\progress\OpenEdge\bin\prowin32.exe which launches the app
3. We have 2 parameters which are apipro.ini and apipro.pf files (located in WORK folder)
Considering the described above, what should be the input for Recording fileds 'File name' and 'Arguments'?

BR, Grygoriy

[Support Team]

Hi,

If you use the RunApplication action, just right click the action and open the properties. A pad should be shown with the properties of this action. There you will find a property named WorkingDirectory. With this property you can set the working directory and start your batch file.

Regards,
Peter
Ranorex Team

[Gregstom]

Hello Peter,

>>If you use the RunApplication action,

- You mean 'New recording' window, right?
>>just right click the action and open the properties.
- here I'm starting to miss the point....
>> A pad should be shown with the properties of this action.
- what is a pad and how does it look like?
>> There you will find a property named WorkingDirectory. With this property you can set the working directory and start your batch file.
- Sorry since I'm new to this it is hard to follow your quick thought. Can you be more specific please?

BR, Grygoriy

[Support Team]

Hi,

I guess you have a batch file where you start your executable with parameters. Am I right?
If you use a new recording and select run application then just select your batch file and press OK and stop the recording. Now you should have an action in your recording named run application. If you right-click this action now, you should have a context menu entry named properties. Click this one. Now a pad should be shown on your screen and there you will find the working directory to set it.

If this doesn't work for you. Could you please post me your cmd file and your working directory and I will create you a recording to show you how it should be.

Regards,
Peter
Ranorex Team

[Gregstom]

I guess you have a batch file where you start your executable with parameters. Am I right?
- Yes, exactly

If you use a new recording and select run application then just select your batch file and press OK and stop the recording.
- It gives an error
---------------------------
msgOpen: unable to open message file: PROMSGS
---------------------------
Now you should have an action in your recording named run application. If you right-click this action now, you should have a context menu entry named properties. Click this one. Now a pad should be shown on your screen and there you will find the working directory to set it.
- Yes I have something like this but not sure how to use:

If this doesn't work for you. Could you please post me your cmd file and your working directory and I will create you a recording to show you how it should be.
- This would be very nice! You can see the contents of CMD in my very first post. Here is it again:

Code: Select all

cd work
start c:\progress\OpenEdge\bin\prowin32.exe -pf apipro.pf -ininame apipro.ini

[Support Team]

Hi,

before I post the recording for you, please read following link http://www.progresstalk.com/showthread. ... le-PROMSGS
It seems to be the same issue as yours.

Regards,
Peter
Ranorex Team

[Gregstom]

Thanks, not really the same - when I double click on .CMD it launches the application just fine without errors (I also adjusted the .ini according to solution provided via that link but it did'nt work out when launching with ranorex)

[Support Team]

Hi,

Please try the attached recording for your executable.

StartApp.rxrec

(1.27 KiB) Downloaded 10 times

Regards,
Peter
Ranorex Team

[Gregstom]

Thank you, it produces the same error, and I assume the reason for that is that system doesn't know where to look for arguments (which are located in D:\apiproinst\APIPRO7_0_02\WORK) Should we somehow add a work path or should I copy them to c:\progress\OpenEdge\bin\ ?

[Support Team]

Hi,

Please try this one

StartApp.rxrec

(1.35 KiB) Downloaded 12 times

. Otherwise you have to copy the files to the executable folder.

Regards,
Peter
Ranorex Team

[Gregstom]

Peter, you did the trick! Thank you very much! This can be closed.