Using the VI Analyzer in a built application

I have a application that is being designed for a continuous integration server. This application uses the VI Analyzer API (Labview 2009 at the moment) to run a set of tests on a folder of VIs. The issue is that when the program is run as VI everything is happy, the folder is added using the "VIAn Add Item.vi" and the task runs on the four VI's in the folder. But when the VI is built and ran as an exe, "VIAn Add Item.vi" appears to add the folder but the no vi's are analyzed and if a specific VI is given then error 53 is thrown by "NI_FileType.lvlib:Get File Type.vi". Is this simply a case of not being able to use the VI Analyzer API in a built application that is being run as a exe? I attached the front panel of the built app after it has been run and the back panel of the source code in question; there is more to it the rest of it is just for determining the paths to scan.
Solved!
Go to Solution.
Attachments:
fp of built app.png ‏96 KB
bp of built app.png ‏23 KB

It was decided the installing the editor environment on the server would not be a big deal, so I was able to get it working by writing a batch file that calls labview, passes the vi to it to be opened, and passes any user-defined augments to the vi. In the VI, I set the "run-on-call" option to true, and added a "quit Labview" block at the end. This way it "acts" like a built program, just with a long startup time.
I know its not ideal or "correct" (if there is such thing when using a product in a way that it not indented) but it only needs to be on the one server so in this case it is fine.
In the future this functionality (using the VI Analyzer API from within a built application) might be a nice thing to add to software validation tool set that is already in place, if its possible. (It may not be)
Anyway just my 2 cents on the subject, thanks for the help and quick responses.
- Christoher

Similar Messages

How to use the HTTP Analyzer with the embedded OC4J server?

JDeveloper version: Studio Edition Version: 10.1.3.0.3.3412
I have a web application, which I run in the embedded OC4J server.
I tried to use the HTTP analyzer to inspect http requests and responses, but I could not make the analyzer work.
I tried to setup the HTTP analyzer by looking at the help entry, but I could not make it work.
If the HTTP analyzer works for you in the embedded OC4J server, please write the steps on how to setup the analyzer.
(Maybe I could not make the correct settings about port numbers?)
Thanks in advance,
Regards,
Turgay Zengin

I was able to use the HTTP Analyzer by changing the proxy setting directly in Internet Options. Check the browser/proxy settings set in JDeveloper preferences and copy them to the Connections tab of Internet Options. See if that works for you.

Who uses the VI Analyzer?

I would like to know how people are using the VI Analyzer Toolkit to improve the style, performance, and robustness of their VIs. Do you use it more as a spot-checking utility for VIs as you write them, or have you utilized the programmatic interface to incorporate the VI Analyzer fully into your development process? What successes (or failures) have you had in doing so? Are there any tests that ship with the VI Analyzer that you have found particularly helpful, or are you finding holes in the test coverage?
For anyone who has not yet used the VI Analyzer, you should check out Mike Neal's VI Analyzer presentation, or better yet, try out the toolkit yourself with the LabVIEW Add-Ons Online Evaluation.
Thanks,
Darren N.
LabVIEW R&D
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Hi Joe,
Thanks very much for the feedback. It definitely sounds your development team would not find the stylistic checks provided by the VI Analyzer to be useful based on your current way of doing things. However, the VI Analyzer can prove extremely useful as a debugging tool, and I'm guessing that your development team does have to debug VIs on occasion.
Here's a scenario...imagine a very simple VI that uses the Increment function to add 1 to the value of a control and then sends the result to an indicator. However, when you run the VI, the number does not increment. A quick check of the wires shows that you accidentally wired the input wire of the Increment directly under the Increment's output terminal and straight to the indicator, such that it *looks* like you're wiring from the output of the function. Now this scenario would be extremely easy to debug in this simple VI, but what if this wiring error was present somewhere within a very large application, and you had to spend hours debugging some incorrect behavior of your application only to discover this errant wire as the culprit? There are actually two tests in the VI Analyzer that can very quickly discover this error...the Unused Code test would flag the Increment function as being unused (since its output wasn't wired), and the Wires Under Objects test would flag the input wire as going under the output terminal of the function.
Here's another scenario...imagine another simple VI that takes an input array and multiplies it by some constant value to scale all the values in the array. However, when you look at the VI Properties of the VI, it takes up over 8 MB of disk space! The reason for this is that someone, at some point, accidentally chose the "Make Current Values Default" option on the VI, and there were a million values in the array output indicator when they did it. Again, an easy situation to solve when looking at this simple VI, but not so easy if this problem existed in a large application. And again, there are two VI Analyzer tests that would help you discover this error...the VI Size test (for obvious reasons), and the Array Default Values test (which will flag any array control/indicator that is wired to the connector pane and has a non-empty default value). This is actually a real-life example...one of my colleagues used the VI Analyzer as part of a code review for another group internal to NI and discovered this very problem in one of their VIs they were going to ship in a LabVIEW toolkit.
I could go on and on here, but the point is that the VI Analyzer is much more than a style-checking tool, although many customers and internal NI groups have found it very useful in this regard. I would say that for your average LabVIEW programmer, the debugging potential of the VI Analyzer is by far its most compelling feature.
As for your other question, you are correct that the VI Analyzer is an edit-time tool, and does not perform run-time analysis. I agree with you that a run-time analysis tool for LabVIEW would definitely be useful.
Finally, you asked if NI uses the VI Analyzer as a matter of policy. The answer is yes, we have several groups internal to NI that use the VI Analyzer. Some groups use it informally as an aid with code reviews, while other groups have completely adopted it into their development and build processes.
I really appreciate your feedback. Please let me know if you have any other questions or comments.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Capture an image using the web camera from a web application

Hi All,
Could anyone please share the steps what have to be followed for capture an image using the web camera from a web application.
I have a similar requirement like this,
1) Detect the Webcam on the users machine from the web application.(To be more clear when the user clicks on 'Add Photo' tool from the web application)
2) When the user confirms to save, save the Image in users machine at some temporary location with some unique file name.
3) Upload the Image to the server from the temporary location.
Please share the details like, what can be used and how it can be used etc...
Thanks,
Suman

1) Detect the Webcam on the users machine from the web application.(To be more clear when the user clicks on 'Add Photo' tool from the web application)There's not really any good way to do this with JMF. You'd have to somehow create a JMF web-start application that will install the native JMF binaries, and then kick off the capture device scanning code from the application, and then scan through the list of devices found to get the MediaLocator of the web cam.
2) When the user confirms to save, save the Image in users machine at some temporary location with some unique file name.You'd probably be displaying a "preview" window and then you'd just want to capture the image. There are a handful of ways you could capture the image, but it really depends on your situation.
3) Upload the Image to the server from the temporary location.You can find out how to do this on google.
All things told, this application is probably more suited to be a FMJ (Freedom for Media in Java) application than a JMF application. JMF relies on native code to capture from the web cams, whereas FMJ does not.
Alternately, you might want to look into Adobe Flex for this particular application.

Is it possible to use the JS coding in webdynpro java application!!!

Hi Experts,
Is it possible to use the JS coding in webdynpro java application by any means?
If yes, kindly suggest the procedure or any pointers for the same.
Thanks in advance.
Regards,
Anurag

Hi,
I'm not an expert in this matter, but I will post here what I know:
In NW7 releases (at least 7.01.05) it is possible to run JS, also to capture any WD Event and run your own JS code after that, using IFRAME. I have jQuery running here, it would take some time till you create a "framework" to enable some easy usage. I just want to highlight that is possible, thou I think it's a lot of effort.
Not sure about CE7.1 it seems iFrame is deprecated. Still, being deprecated should not "block" the usage, thou it's not recommended since this functionality can be removed in next releases.
I've read that CE7.2 has JS support, and I think you should try having a word with Armin maybe..
Hope it helps,
Daniel

Using the JMS API in Java EE Applications

Hello to all,
this is some sort of theoretical question.
I been reading the JMS documentation for a while.
1.I could not understand what this statement means :
>
This section describes the ways in which using the JMS API in enterprise bean applications or web applications differs from using it in application clients.
2. What is the difference to use the JMS in java EE web orEJB container and application client ?
Thanks.

peterwkc wrote:
Hello to all,
this is some sort of theoretical question.
I been reading the JMS documentation for a while.
1.I could not understand what this statement means :
>
This section describes the ways in which using the JMS API in enterprise bean applications or web applications differs from using it in application clients.
What a developer is allowed to do is different depending on whether they are writing code to run in a container or not. The container already provides lots of services so some code you would write for outside a container is not needed when you write for a container. There are APIs that you are not allowed for in container code if you want to adhere to the spec.
>
2. What is the difference to use the JMS in java EE web orEJB container and application client ?
Thanks.Read more of that document to find out the differences. Application components in Web/EJBs must not create more than one active session per connection while application clients are allowed to do so.

Can I use the Apple Loops in my iPhone application ?

Hi,
I use the Apple Loops for GarageBand to create my application soundtrack. But I don't know if I have the rights to do it.
Someone can say me if I can ?
Thank you !

You can include the loops as part of your own soundtrack. But that soundtrack must be an original work. You cannot redistributed the loops by themselves. You have to make some new composition with them.

How to prevent a portal user from using the BEx Analyzer ?

Hi,
we have different type of users : most users may use the portal as well
as the analyzer ;
we have one special user with extended authorizations : this user
should use the portal , where he has a limited set of queries to run
with hardcoded filters ==> this user should not be able to use the
analyzer however, since he then would be able to call all other queries
by using the find function ;
how can we make sure this user cannot use the analyzer , using SAP
authorizations ?
best regards,
Erwin Van Giel.

Hi,
if I remove the complete S_RFC authorization for the user then the BEx Analyzer cannot connect anymore to the BW system, but neither can the user run reports from the portal : it needs the S_RFC with 'SYST'.
If I only remove the RRMX from the S_TCODE and from the S_RFC, it does not prevent the user from starting the BEx Analyzer and connecting to the BW system. It only stops the user if he would start the RRMX transaction from within an SAPGUI session.
Perhaps there should be a value in the S_RFC that allows connections from the portal but not from the BEx Analyzer .... ?
so not solved yet ....
best regards,
Erwin.

Why can't i use the ftp functions with a built file

I have created a report program that connects to an MS Access database and generates a series of reports from it. i also wanted to give the user the ability to download the database. we haev the database stored on a server at a different building. i have used the labview FTP function in the internet tool kit. the program works fine in the development mode. however if i build an application the ftp call fails to work. i have added traps so that if i get an error i will know it. unfortunatly the program flows through with no errors but the database is not copied.
i have also written an ftp function which works in the development mode and the application mode with no installer, but it does not work in the apli
cation mode with an installer.
Attachments:
test_ftp.vi ‏28 KB
shawns_ftp_get_files.vi ‏71 KB

Well once again I find myself on a machine that will not let be take a look.
I am glad to here that you have your app running.
I am troubled by by the solution. It makes me nervous when functions behave differently in the two environments. Have you run this past NI support?
I'll email myself this link as a reminder for monday.
Thank you for the update.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

How can I use the write palette.vi in an application when it is not supported by run time engine

I am making an application, that is used for distribution, to create a palette. In my VI I take the VIs in a file and create a palette with them using the write palette VI. When I run the VI it works perfectly, but when I build it into a .exe I get the attached error. Is there a way around this?
Attachments:
Write Palette error.PNG ‏10 KB

That makes sense that it doesn't work because you aren't running it inside of LabVIEW. Therefore, there is no palette to write to. What you could do is create a *.mnu file and just put it in a location so that LabVIEW will notice it next time it is started.
If LabVIEW is running, you may be able to invoke the paltte write or refresh via VI Server.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Setting breakpoints/debug using the HTTP Analyzer web development

I wonder if there is any way of setting breakpoints in a Web service class. For instance the method in the class shown in the tutorial "Building a POJO Annotation-Driven Service":
package annotation;
import javax.jws.WebMethod;
import javax.jws.WebService;
@WebService(serviceName = "HelloService")
public class HelloService{
public HelloService() {
@WebMethod
public String sayHello (String s) {
return "Hello " + s;
That is, while you run the HTTP Analyzerl, the code can be debugged by setting breakpoints etc.

Hi, I'm just using the default setup for HTTP Analyzer and having no problem using it.
Just make sure to run the HTTP Analyzer first before running or starting your app server (Integrated weblogic Server).

Using the Suspensibility property of a Webdynpro application

Hello Experts,
I have around 10 WDJ applications.All these applications are hosted on different iviews on portal.
I use the portal navigation to navigate between these applications.I want to use the Suspensibility property of the applications so that i dont have to reload them everytime they are called by other applications.
My Question is : The Suspensibility property stores the state of the application as it is. This will be done for multiple applications. Does anyone know where is this temporary storage done and how much of an effect will it have on the performance of the applications overall.
Regards,
Virag

Hi Virag,
You can use Suspend & Resume plugs for the same. Refer below SAP NetWeaver Library link & asoociated links.
http://help.sap.com/saphelp_nw04s/helpdata/en/68/3aee42c4257176e10000000a1550b0/frameset.htm
Hope this helps you.
Kind Regards,
Nitin

How to use the XSLT SE in a composite application

(The new XSLT SE as of July.)
I followed the setup using the XSLT wizard in Netbeans and the xsltse driver-tests out of the open-jbi-components checkout and now I am stuck. Kevan points out that BPEL and partnerlinks are no longer needed, so I'm not sure how to construct a CA with it.
I tried that route anyway by dragging my xsltModule wsdl into my bpelModule flow and it created a partnerlink for me (very cool). I then added both modules to my composite app. When I deployed the app to glassfish, it complained about duplicate xsd types because both of my modules use the same schema imported as rssext.xsd.
So do anyone have a suggestion as to which route to go and how to do it successfully?
Jeff

Kevan,
Thanks for your help, I finally get what I need to do. :)
I just need to get past an xslt TransformerException and I'll have it working. I'll reply back here with what I had to do start-to-finish so others can learn from my example.
Xslt transformation failed: org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted.
javax.xml.transform.TransformerException: org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted.
        at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:651)
        at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:281)
        at com.sun.transform.engine.xslt.XsltEngine.process(XsltEngine.java:127)
        at com.sun.transform.engine.xslt.XsltEngine.process(XsltEngine.java:70)
        at com.sun.transform.engine.runtime.impl.TransformUnitImpl.execute(TransformUnitImpl.java:53)
        at com.sun.transform.engine.runtime.impl.EngineImpl.runProcess(EngineImpl.java:130)
        at com.sun.transform.engine.runtime.impl.JbiEngine.process(JbiEngine.java:81)
        at com.sun.transform.engine.runtime.impl.ProcessInstanceImpl.execute(ProcessInstanceImpl.java:116)
        at com.sun.jbi.engine.xslt.process.XsltseMessageListener.onMessage(XsltseMessageListener.java:88)
        at com.sun.jbi.crl.mep.impl.SingleThreadManager.invoke(SingleThreadManager.java:67)
        at com.sun.jbi.crl.mep.impl.DefaultAcceptPoller.run(DefaultAcceptPoller.java:97)
        at java.lang.Thread.run(Thread.java:595)
Caused by: org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted.
        at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.insertBefore(CoreDocumentImpl.java:419)
        at com.sun.org.apache.xerces.internal.dom.NodeImpl.appendChild(NodeImpl.java:275)
        at com.sun.org.apache.xalan.internal.xsltc.trax.SAX2DOM.startElement(SAX2DOM.java:141)
        at com.sun.org.apache.xml.internal.serializer.ToXMLSAXHandler.closeStartTag(ToXMLSAXHandler.java:205)
        at com.sun.org.apache.xml.internal.serializer.ToXMLSAXHandler.characters(ToXMLSAXHandler.java:524)
        at gcitransform.template$dot$0()
        at gcitransform.applyTemplates()
        at gcitransform.applyTemplates()
        at gcitransform.applyTemplates()
        at gcitransform.transform()
        at com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:594)
        at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:644)
        ... 11 moreJeff

Using the local service registry from other applications (VC, GP)

Hi all,
I am not sure if this is the appropriate forum, but my problem is the service registry I think.
I am facing the problem of using services that I publish to my local service registry from VC and GP.
The problem is as follows:
I publish the services via the "publish" tab on the http://localhost:50000/sr page. The process is executed successfully according to the message.
Then on the Service Definitions Tab of http://localhost:50000/sr I can find and test the service, though on the System Details Tab All parameters are set to "No data available".
When I then try to search the service from the VC (searching in a Ws of type service registry, which I have previously configured through destination templates), I get "no services found".
In the GP I see the published services, but when I try to use them as callable objects, I get the following error message:
"WS-Interface initialization problem of GenericServiceFactory..., Local_Service_Registry - ServiceName not found. possible changes in the WSDL"?
I also tried publishing the web services through the ws restrictions, but they dont get published.
I have adjusted the UDDI_DESTINATION and CLASSIFICATION_DESTINATION properties according to the help page for the localhost system. I also use a Local_Service_Registry destination of type service registry as I thought I need it in oder to use the service registry.
Has somebody experienced this problem before?
Thanks in advance!
Best regards,
Vera

Hi,
the exact error trace is as follows:
#1#javax.ejb.EJBException: Exception raised from invocation of public com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesResponseType com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesType) throws com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishClassificationSystemValuesFault method on bean instance [email protected]8 for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxy~ejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)*
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:158)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:117)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)
     at $Proxy56_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(ServicesRegistryProxyFacade.java:302)
     at sun.reflect.GeneratedMethodAccessor810_10002.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
     at $Proxy34_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.createUDDIClassifications(SOACentralSRPublisherImpl.java:742)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.publishServiceDefinitions(SOACentralSRPublisherImpl.java:435)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.publish(PublishRulesHandler.java:282)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.process(PublishRulesHandler.java:248)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.process(SOATimeoutListenerImpl.java:128)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:51)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:72)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:144)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:242)
Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:340)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:961)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:700)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:152)
     ... 37 more
Caused by: java.io.IOException: Unable to connect to localhost:50100 - Connection refused: connect
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:666)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:658)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:621)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:499)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:450)
     at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getRequestStream(ClientHTTPTransport.java:481)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:298)
     ... 41 more
javax.ejb.EJBException: Exception raised from invocation of public com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesResponseType com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesType) throws com.sap.esi.uddi.sr.api.ws.PublishClassificationSystemValuesFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishClassificationSystemValuesFault method on bean instance [email protected]8 for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
     at $Proxy34_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.createUDDIClassifications(SOACentralSRPublisherImpl.java:742)
     at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.publishServiceDefinitions(SOACentralSRPublisherImpl.java:435)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.publish(PublishRulesHandler.java:282)
     at com.sap.esi.esp.service.server.mass.PublishRulesHandler.process(PublishRulesHandler.java:248)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.process(SOATimeoutListenerImpl.java:128)
     at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:51)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:72)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:144)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:242)
Caused by: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:158)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:117)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)
     at $Proxy56_10002.publishClassificationSystemValues(Unknown Source)
     at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystemValues(ServicesRegistryProxyFacade.java:302)
     at sun.reflect.GeneratedMethodAccessor810_10002.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
     ... 28 more
Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused: connect)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:340)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:961)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:700)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:152)
     ... 37 more
Caused by: java.io.IOException: Unable to connect to localhost:50100 - Connection refused: connect
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:666)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:658)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:621)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:499)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:450)
     at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getRequestStream(ClientHTTPTransport.java:481)
     at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:298)
     ... 41 more

Can I use the citrix metaframe to run windows applications on Mac OSX?

Sorry if I put this in the wrong forum, but I was wondering, if I could use the citrix metaframe to run Windows apps in OSX. Thanks in advance for the help!

Nope.

Using the VI Analyzer in a built application

Similar Messages

Maybe you are looking for