Java automation

[VratHimbo]

Hi all,
i read the documentation about java automation, the challenge is to automate a java web-based application, and i noticed that the process is really slow, i've used a normal attach to "win32" and a wait stage with java element before every "navigate" state.
Is that normal? There are some hint to use in this type of automation?
Thanks in advance

------------------------------
Vrat Himbo
------------------------------

[james.man]

The Java Automation guide here https://portal.blueprism.com/system/files/documents/Java%20Automation%20Guide_0.pdf may have some things you can try. Page 7 have some tips regarding wait stages, and page 8 has some application wizard options that you can try.


------------------------------
James Man
Professional Services
Blue Prism
Asia/Hong_Kong
------------------------------

[VratHimbo]

Thanks for the help @james.man,
i've follow the best practice from the java automation guide, my problem is, sometimes JIT goes in error (i think for a cpu overload), so my first question is: how can i improve that?
And then, in java automation guide i've read this.
"Avoid using Wait stages that continually check for the existence of a Java element. A
ten-second wait stage would thrash the application model considerably. An alternative
would be to use a Wait stage with a fixed time period before the Wait stage that
checks whether the element exists. By doing this, sufficient time should have passed
to allow the element to appear, meaning that the first check of the application model
should suffice."​
Is not better to use a "sleep action" instead of a "wait stage" in unkown elements with a fixed time before the wait stage for searchin the java element?? My collegue suppose that and i need to improve that, so any help would be appreciate.

Thanks in advance

------------------------------
Vrat Himbo
------------------------------

[VratHimbo]

up please

------------------------------
Vrat Himbo
------------------------------