This content has been marked as final. Show 6 replies
As of today, you cannot launch OpenScript script from OTM on Linux. It's on the roadmap but no I have no timing yet.
1/ you deploy a remote agent on windows
2/ you create a custom script type of testcase and you use command line to execute a load test script
<InstalledDir>/jdk/bin/java -jar OLTCommandLine.jar -run -session=test1_ad1 -scenarioFile=/export/.../Test_Ad1.scn -OLTServer=localhost:8088 -user=oats -password=welcome1 -log=/export/.../ad1.log
Thank you for the quick response.
I will be waiting for this functionality to appear under linux installations. For now, both workaround options sound good.
I have a question about 2/ - did you mean that I can create a test in OTM of type "3rd Party Test" and assign a custom script? Or is there some way of extending OTM? I am asking this because I would like to minimize the complexity of creating these tests (compared to just selecting a OpenScript from a test repository). These tests will be created by testers, who will provide the initial data as an attachment.
As for 1/ when I first encountered this problem in linux, I tried running OpenScript remotely on windows host, but there was some problem with paths (windows agent tried to execute my OpenScript test in a location that is correct for linux environment, but does not exists in windows). Maybe there is some administrator's guide for such tasks? Is it me, or it is really hard to find documentation on OATS?
2/ Yes you can assign a custom script. You can even use a regular expression to get the result from standard output and define test status accordingly
1/ Best is of course to have a shared repository on a Windows (or Linux but with Samba) server, to develop your openscript scripts from there on your windows desktop and then to define in OTM the shared repository in the config.
About docs, outside the default documentations provided on OTN or in the OATS install dir, there are couple of web sites where you can get some docs and assistance, but I agree, not so much.
The point with Linux is that it was primarly intended to run Load Testing from where we needed more scalabilty than on Windows. And it's pretty new, so not so much experience/best practices to share.
I am trying to do what you suggested - to create a shared repository (windows host), but I am not able to make tests work in OTM (running in linux) when I use windows agent.
What I managed to do so far is:
1) OATS installed (in linux environment);
2) OATS agent installed (in windows environment);
3) Created a new repository via OpenScript named "ScriptRepository" (windows)
4) Shared repository folder (windows)
5) Mounted shared repository location to /mtn/win (linux)
6) Added new system via OTM (linux)
7) Added new repository via OTM named "ScriptRepository" (linux)
When I try to run a test in OTM (using windows agent system and a test from shared repository) it always fails. I get an error in the windows agent log:
09:59:33,591 ERROR [JWGController] JWG file does not exist: /mnt/win\Test1\Test1.jwg
09:59:33,599 ERROR [OTMLauncherEntryPoint] Failed to create script package from JWG file null
Am I doing something wrong? Is there some other way to define repository for OTM (not using web UI)?
I tried doing the same in OLT - it works fine, but OTM takes the repository location from linux environment and tries to use the same location for windows agent ("/mnt/win", which will always be wrong).
Feedback from internal team:
The key to getting this to work is to make sure OpenScript's "ScriptRepository" is pointing to a network path (i.e. \\<machine name>\oft). Otherwise replay will fail with the "JWG file does not exist" error. Below are steps required in order to replay OpenScript script from OTM Linux server on a Windows agent.
- Login to the Windows box using named user account (e.g MYSERVER\johndoe)
- Make sure ATS Agent and Server services are running as the same named user (e.g MYSERVER\johndoe)
- Share the Windows repository folder (e.g. C:\OracleATS\OFT)
- Launch OpenScript and add a new repository (e.g ScriptRepository) with the following network path (e.g \\MYSERVER\OFT)
- Mount the network path (e.g. \\MYSERVER\OFT) to a share (e.g. /mnt/win)
- Create the same OTM repository as defined in OpenScript (e.g. ScriptRepository) and map it to the same network path (e.g \\MYSERVER\OFT)
- Add an OpenScript test from "ScriptRepository" repository
- Add a windows agent
- Execute this script on the remote windows agent
They tested this with 126.96.36.199.383 and were able to get it working. Let us know if you still see issues.