I am newbie in windows application automation, I dont see WindowsElement in java client 8.2.0.
Any work around, I see Windowselement in java client 7.6.0
Br
Related
I have Mirth Connect Version 2.2.3.6825 installed on RHL I want to access my Mirth my Local Machine which have Java 1.8(Java 1.7 it Work fine), I am not able to launch the Administrator tool of Mirth. When I clicked on the administrator button, It opened the window saying starting application after giving User name and Password it give error 'There was an error connecting to the server at the specified address. Please verify that the server is up and running'
http://www.mirthcorp.com/community/wiki/display/mirth/System+Requirements
Java 8 should work with version 2.2.3, but you must be using the Oracle JRE. OpenJDK only recently became supported with version 3.7.
You may also want to try using the new Administrator Launcher available on the mirth downloads page. It comes bundled with a Java 8 JVM so that you don't need to install one separately. It works with all versions of mirth from 2.x and up. See announcement here: https://www.mirthcorp.com/community/forums/showthread.php?t=218662
I'm developing an application in Java using vaadin, JPA, maven and JAX-WS technologies.
When I publish the application in the glassfish server I can see the generated wsdl using this url:
http://localhost:8080/at/PrimaryTransmissionService?wsdl
When I publish the application in the wildfly server I can see the generated wsdl using this url:
http://localhost:8080/at-1.0/PrimaryTransmission?wsdl
When I publish the application in the jetty server I can't find to which endpoint is deployed, but I can use the webapp by using this url:
http://localhost:8080/at
Could you help me?
If you are using JPA and JAX-WS via Java EE API dependencies relying implementation bundled in Glassfish / Wildfly, which are Java EE compliant application containers, that would explain the observation. That is because Jetty is not Java EE container and does not contain implementation e.g. for JAX-WS out of the box.
I know that the recommended approach is to monitor WebLogic 11g via HP SiteScope. However, my client hasn't purchased a HP SiteScope license.
I was looking at http://easyloadrunner.blogspot.com/2013/07/how-to-set-up-weblogic-monitor.html
and it appears that LoadRunner has a native WebLogic JMX monitor.
Does anybody know if it supports WebLogic 11g?
If not, any suggestions short of HP SiteScope?
--Thank you,
--Mike
If your client has LoadRunner past version 8 then a base 500 point SiteScope instance comes as a part of the LoadRunner license. This is part of the monitoring foundation of the LoadRunner
I am experimenting with WineBottler and I would like to try to run my win32 native application written in Delphi on OSX.
The application runs, but I stop at login screen since I cannot connect to SQL Server.
Does anyonw know how to install and configure SQL Server native client on OSX so that it is usable with WineBottler?
Note: I put "wine" as tag since "winebottler" is not available.
I have a Delphi application that uses MDAC 2.8 for ADO connection to the Jet provider. I use Winetricks to install MDAC 2.8, and it works great. If you can't get SQL Server Native Client to install, perhaps your application can use the OLEDB SQL Server provider by tweaking your connection strings. Are you using any features that are only in SQL Server Native Client?
You would have a lot less trouble if you put in some middleware like kbmMW, Remote Objects, or DataSnap. All of them can use plain TCP/IP (via http or like higher level protocol), and don't require client side libs. You will need an extra server, but it is easy to create one that just forwards your SQL and data between clients and SQL server. Note that SQL server licensing remains.
On the other hand, you can try to install SQL Server native client, some older version of it - eg. for SQL Server 2005, in that "bottle" with your application. Yet, I'm not sure if that is legal thing to do. I think that MS prohibits native client installation on OS other than Windows.
There is FreeTDS native client that works with MSSQL from unices, but it is not ported to be usable from Delphi (like dbx driver).
I built a Delphi-7 Windows Application which uses some web services. The application is built in such a way that it does not require run-time DLLs. When I deployed it on a Windows 2003 server it fails while calling the web service. It results in error "Access violation at address 00c05269. Write of address 00c05269". I believe the reasons is that it needs some package to be installed. Can anybody help me to figure that out?
TIA
Just a guess: If the client was built with D7, that runtime will AV on machines with DEP enabled. See the following link for more information:
groups.google.com/group/borland.public.delphi.webservices.soap/msg/b19f3c2681de50f4
You can disable DEP for just that client (or system-wide) on the Win 2003 machine to see if that's the issue:
technet.microsoft.com/en-us/library/cc738483(WS.10).aspx
And if it is, you can download a SOAP runtime fix from here:
http://cc.embarcadero.com/Item/24535
Cheers,
Bruneau
Some troubleshooting suggestions.
Can you browse to the web service from a web browser? If not, you have a connectivity problem.
If this works, I would build a bare bones client that consumes the web service and calls a couple of methods but doesn't read from or write to any external files.