Thin Client Support
I am using MAC Mini Leopard. How can I provide Thin Client Support ? Is there any version which already have the Thin Client support ?
Mac OS X does not natively provide "thin client" support except via X11 or UNIX command line. There is a third-party product that purports to provide such support:
http://www.aquaconnect.net/
but I don't know how well it works, and their FAQ says only that it works with Mac OS X 10.4, not with Leopard. You can contact them and ask if they have, or will have soon, a version that works with Mac OS X 10.5.
Similar Messages
-
The iTunes Installation files include 4 driver dlls that I can install on a Windows thin client to enable the iPhone to be charged.
The iPhone hard drive or photos are not detected. I guess I need scanner driver support to cope with the camera.
Can anyone tell me which files from the iTune installation set are needed.
It is not practical (or even possible?) to install the whole iTunes package.
I've seen this question asked by a lot of people but never seen an answer.
Please, can someone help...Thanks for the reply.
A thin client is used to connect to a Terminal Server, or in my customer's case, a Citrix Server. I need the thin client to see the iPhone as a camera and pass it to the Citrix Client so the photos can THEN be either stored on a network storage device, or e-mailed.
Because the thin client doesn't even SEE a camera (i.e. the iPhone) it won't be able to connect to iCloud to do anything useful.
I think the question I should be asking, is how do I give the thin client Camera Support.
I've just seen a 2008 forum comment that said the iPhone DOESN'T handle photos through iTunes, but the PC (Scanner support) or MAC (iPhoto) handles them directly. I should be putting the question to HP.
This is still a good place for THIS question, because I've seen so many iPhone users asking it...
If I get a satisfactory answer I'll post it back here. -
Hello,
Does LabView support a thin client or dumb terminal (diskless workstation) type of deployment? I have a need to run LabView on some sort of dumb terminal / diskless workstation. If someone has deployed LabView in this matter, please provide me all the details on how this was accomplished (software, hardware, etc.)
ThanksSorry, can't call you.
My first suggestion has nothing to do with LV. It is simply connecting as a remote client to the windows server and controlling the windows session on the server.
My second suggestion involved writing a program which will contact the PLCs directly using Modbus and get the data from them. As mentioned, you can find some Modbus client implementations for LV by searching the web (or, if you have LV 8 and the DSC module, I think it should come built in).
My third was writing 2 programs - one would run on the server and one on the client\s. The server program would be responsible for sending the data to the client and the client would be responsible for interacting with the user and sending the appropriate messages to the server. I already gave you pointers on what to search for (the example finder can be found by going to Help>>Find Examples and the site can be searched from the box at the top of the page, but make sure you don't search just the forums).
In both cases, you would need to design the program and the interface for the user.
Wi-Fi also has nothing to do with LV and is simply a way to form a wireless network. Any mobile device would almost definitely have support for it and buying an access point to form the wireless network is easy and cheap.
To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here, here, here and here are a few you can start with and here are some tutorial videos. You can also contact your local NI office and join one of their courses.
In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf).
Try to take over the world! -
Attendant Console supported on a thin client station ?
Does somebody know if it's possible to install the attendant console on a diskless HP station (thin client station) working with the RDP protocol ?
I'm using CCM 4.1(3)We run attendant console on our windows 2003 terminal server. You will need to have 1 copy of the installation for each user (just install it on a normal pc and copy the folder to the terminal server).
-
Problem using Weblogic 6 and Weblogic 8.1 thin clients from same applicatio
We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
at weblogic.kernel.Kernel.initialize(Kernel.java:138)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 moreuday naik <> writes:
The thin-client isn't supported on 6.1, I'm not sure what you are doing.
andy
We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
at weblogic.kernel.Kernel.initialize(Kernel.java:138)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more -
Installing Adobe Reader on a Thin Client
I have 27 Thin clients (HP t5639w) to set up in the next day or two... the problem: right out of the box, I am unable to install Adobe Reader on them. I have made room to install by using a flash drive to increase RAM, and Reader appears to have successfully loaded, but each time I try to open after install I get the following error message: "Font Capture: AcroRd32.exe Application Error.... The exception unknown software. Exception (0xc06d007e) occurred in the application at location 0x7c812afb."
I've tried to contact HP customer support - unfortunately, they refer me to the HP website and tell me to download the version there. It's the same version I've tried to install - no luck. I have installed other software on the Thin Clients successfully, but I'm only having an issue with Reader.
Anyone else have a similar issue? Any ideas?Here's the process:
· Download Adobe to USB drive
· Remove write filter – reboot
· Create temporary TEMP and TMP folders on C: drive
· Change Windows TEMP variables (both TEMP and TMP) to a folder on the “Hard Disk” – Reboot (Make a note of values before changing).
· Install Adobe Reader – Reboot
· Run Adobe Reader – If runs reboot
· Replace TEMP and TMP variable entries (Usually Z:\TEMP and Z:\TMP respectively) – Reboot
· Delete temporary TEMP and TMP folders – reboot
· Re-enable write filter
This worked for me! -
Font Smoothing CE 6.0 Thin Clients
We need to handle Font Smoothing on HP Thin Clients. This is supported on newer Thin Clients with RDP7 and Font Smoothing settings.
Older Win CE 6.0 do not appear to support Font Smoothing.
Is there a way to set up Font Smoothothing or can these thin clients be updated with RDP option to support Font Smoothing?
Thanks LexI too had the same problem just last night. It happened when I was changing the font and font size. It seemed that everytime I switched the font and font size, the text got more and more pixelated and less smooth (identical to the screenshot you just posted).
I backed up my Torch, did a security wipe and then restored the backup file back onto the device. That didn't work, as the text still looked horrible.
So what I did next was do a device switch from my Torch back onto my Bold 9000, security wiped the Torch then did a device switch from the Bold 9000 back onto the Torch and the text was back to normal! It was a long process but it seemed to do the trick. So if you have another BlackBerry sitting around it might be worth trying, just remember to back up your Torch before hand.
My Torch is also running v6.0.0.246, Platform 6.4.0.105 through Rogers. Hope this helps you out.
Good Luck!
Ed -
How to use authid with rwservlet via WebLogic Thin Client
1. Using J2EE Thin Client for WebLogic (WL) to submit interactive requests for Oracle Reports (App Server 10g) running on another server without SSO.
2. After starting basic Infrastructure, we start rwserver in batch mode (no other mid-tier components are used).
3. It appears that the cgicmd.dat file in the Thin Client conf directory on the WL server controls the DB access with the key:connect string info it has.
4. We had been allowing the testers to come in via the web through a SunOne (iPlanet/Netscape) web server instance, which in turn connects to the WL server running the Thin Client instance.
5. We noticed that anyone could run rwservlet to view report status with the showjobs command via a URL through the same mechanism as point #4 above, and were concerned about security of the reports - "bad".
6. Then someone realized the showmap command could also be specified, and thus see the DB connect string (Id/pw/SID) - "worse".
I researched securing Reports, and read through the white paper, "Securing Oracle9i Reports", and although it discusses security without using SSO, all it says is "users accessing a secured instance of Oracle9iAS Reports Services will be challenged to identify themselves by the Reports Servlet, using its own authentication mechanism (as with Reports6i)", but I can find no explanation of how that works, nor how it would work with the WL Thin Client.
Questions:
1. How are the Id's/passwords set up under AS 10g "as with Reports6i" in this environment going through the WL Thin Client?
2. Is there anything else that needs to be done to secure the created reports, and the connect string info (i.e. using authid with rwservlet?showjob, and not allowing the rwservlet?showmap to be executed at all)?
TIA,
ROCthe JDBC Developer's Guide (11gR2)
gives an example in chapter 9 under "JDBC Thin Driver Support for Encryption and Integrity", sub- "Setting Encryption and Integrity Parameters in Java"
from Oracle SQL Devloper, without redirecting the client to use the OCI/thick driver, choose, new database connection, connection type Advanced. add the entry from the example noted above to the Custom JDBC URL form.
for example:
Properties prop = new Properties();
prop.setProperty(OracleConnection.CONNECTION_PROPERTY_THIN_NET_ENCRYPTION_LEVEL,"REQUIRED");
prop.setProperty(OracleConnection.CONNECTION_PROPERTY_THIN_NET_ENCRYPTION_TYPES,"(AES128)");
OracleDataSource ods = new OracleDataSource(); ods.setProperties(prop); ods.setURL(jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxx)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=xxxx)(INSTANCE_NAME=xxxx))));
Connection conn = ods.getConnection();
strange side note!, we could not get this to encrypt unless the sqlnet.ora file included the SQLNET.ENCRYPTION_SERVER=required. if this was set to default(accepted), and even though the jdbc thin client properties set to required, the network traffic was still clear text.
good luck -
Reports 9i/10g J2EE Thin Client for Websphere Application Server 5.x /6.x
We are having Reports developed in 6i which needs to be migrated to Reports 9i/10G and we want to deploy these reports in web using Websphere Application Server 5.x /6.x without Oracle iAS.
Do we have Reports 9i/10g J2EE Thin Client for Websphere Application Server 5.x /6.x and if so please let me know.
Also if anybody has the configuration details please let me know?
Thanks in Advance.No there is not. I don't think you can use reports services with Websphere - besides as far as I know it is not supported by Oracle (not anywhere in their support matrix).
-
Using SUN Ray thin client for UCCE CAD Agents
Hi,
Does anyone tested the thin client SUN Ray for Cisco Agent Desktops? Is this supported by Cisco?
We know that Cisco supports Citrix for Cisco Agent Desktop but using thin client for IP Communicator is not supported at all.
Thanks.I guess it all depends on what the SunRay client is connecting to? If it's a VDI, terminal server, or something else as long as that platform is supported by Cisco/CAD then it should be okay - after all the SunRay is just a way of connecting to a desktop environment that then runs the CAD software.
Hope you're SunRay deployment goes well!
Jeff -
Setting up oracle thin client for 9i?
Does anyone have experience stting up data pools using oracle's 9i thin client that ships with BEA WLS 6.1? I am on a Sun Solaris box running Solaris 8 and oracle client 9i. I have followed all of the instrcutions (that I can find anyway) and it does not seem to work. Can someone please tell me exactly what to put in each field on the console for the Data Pool and in the classpath?
Thanks in advance!!
AdamHi Adam,
Configuration of a connection pool for oracle 9 is the same
as for oracle 8.
The only thing you should do is downloading a new
classes12.zip that supports oracle 9, and putting it in to
weblogic class path.
You can download classes12.zip from otn.oracle.com.
To put it to the weblogic classpath you need to modify
weblogic startup script.
Regards,
Slava Imeshev
"adam landefeld" <[email protected]> wrote in message
news:[email protected]..
Does anyone have experience stting up data pools using oracle's 9i thinclient that ships with BEA WLS 6.1? I am on a Sun Solaris box running
Solaris 8 and oracle client 9i. I have followed all of the instrcutions
(that I can find anyway) and it does not seem to work. Can someone please
tell me exactly what to put in each field on the console for the Data Pool
and in the classpath?
>
Thanks in advance!!
Adam -
12.1.3 EBS with JDBC Thin Client
Hello,
I have question about JDBC Thin Client, typically dbc file and context file define connection to RAC Database using thin client, as far as I know jdbc thin client does not support TAF feature when there is database node down, the connection not direct to surviving node until relogin.
APPS_JDBC_URL=jdbc\:oracle\:thin\:@(DESCRIPTION\=(ADDRESS_LIST\=(LOAD_BALANCE\=YES)(FAILOVER\=YES)(ADDRESS\=(PROTOCOL\=tcp)(HOST\=XXXX-SCAN.xxx.com)(PORT\=1521)))(CONNECT_DATA\=(SERVICE_NAME\=DBSID)))
<jdbc_url oa_var="s_apps_jdbc_connect_descriptor">jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=XXXX-SCAN.xxx.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=DBSID)))
And parameter APPS_JDBC_DRIVER_TYPE=THIN in dbc file, is it must to be THIN? What is the function of FND_JDBC_USABLE_CHECK=false/true?
Also to make connection work to surviving database node, we need to restart process OACORE that connect to down node, is that expected behavior and workaround? Is there a way or is it supported to use THICK client in R12 EBS?
Thank you.Please see the following docs.
Is Transparent Application Failover (TAF) Supported on the JDBC Thin Driver? (Doc ID 297490.1)
Configuring and Managing E-Business Application Tier for RAC (Doc ID 1311528.1)
Thanks,
Hussein -
J2SE JRE on a thin client problems!!!!!!!!!!
HELP!
I would like some help regarding a situation where a webstartable application totalling approx 400k as a prototype app is being sent to a thin client. This thin client is a Wyse computer with a 96mb flash card for its hard disk space. The Java app uses the Swing api and JBoss client jars. The application works smoothly on WinNT or Win2000, 256mb, 700Mhz PC installed with J2SE but the problem is that the target client has a Windows NT Embedded OS which only gives around 7.5mb free hard disk space on its flash card. This is a problem as the client OS needs Java 2 JRE which is a whopping 20.8mb. WebStart when installed totals to approx 1.9mb on a PC. So, the complete deployment for the application would reach approximately 24mb going way past the 7.5mb max limit. The client does have IE+MSJava but uninstalling this JVM is not an option as apparently, it is being used for some other app. I am aware of the option of upgrading the machine but that won't go down too well as it will involve upgrading hundreds of clients. Also, this demo needs to show off Swing to the max so that such an upgrade decision can be made. Getting the application+JRE+WebStart deployed within the limit means that there will be a chance for Java to grow on both the client and server side in Carphone Warehouse, one of the top mobile phone retail companies in the UK. However, if this is not achieved then the alternative is that IE will be used to provide an HTML-based limiting, slow user interface for our users in our stores.
A related question I have is whether J2Micro Edition is an avenue that may be useful to explore. I have looked at it a little and as a guess I'd say that the configurations I have found are for too simple for the device targetted by us as it is near enough to a PC's spec except that it has limited chip power, hard disk and memory space.
Please could someone help us with this as it would really promote Java in our company.
regards,
Amar Syed
Carphone Warehouse UK
Email: [email protected]Well, here are a few suggestions, although I'm not sure how feasible they are at this point...
1) Is it essential that you use WebStart and have the code on the client? That's not really a "Thin client" solution... ;-) Can you refactor your app as a JApplet, and just use the java plugin to run it (~5MB)? This would still enable you to use swing. (You could even just have a "launching" applet in a browser that launches your main GUI JFrame in front of the browser.)
2) I've never used this product, but it's worth a mention - WebCream, by CreamTect (http://www.creamtec.com/webcream/) - it runs your swing app on the server, and sends a DHTML representation of it to the client's browser. Looks pretty convincing from their examples...
3) J2ME is probably not an option, since it doesn't support Swing - it has its own limited API for displaying stuff on mobile devices' small screens.
4) Failing that, there's still server-side java - the JSP/Servlet option, creating your own customized HTML (or super-interactive DHTML) pages and sending them to a browser on the client machine.
Hope some of this helped a little! Let us know how you get on.
M -
Installing Creative Cloud apps on a thin client
The bulk of our staff are using thin clients connected to application and data servers. How are the apps installed in this case?
Hi MiwatjHealth,
I am sorry but Creative Suite 6 and Creative Cloud Applications are not tested on Vitual Environment also they are not Server products. and so we can't provide much help to you. As per my understanding Applications will get installed on Server and it will create a Session for Thin Client user to access their system.
Please visit this link for more details.
http://helpx.adobe.com/creative-suite/kb/technical-support-boundaries-virtualized-or.html
regards,
Abhijit -
Wyse Thin client not connecting to Windows 2008 R2 server
Configuration
SBS 2011 Server
Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
WYSE WT3125SE thin clients with Windows CE 5
I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client. Then I installed the License Manger and applied my Open license using User Cals. Was able to login. Next day I get the following
error-"Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again" I still can connect fine from other machines even Windows Home Ed.
I remove license server and still was unable to connect. Built a second Windows 2008 R2 server with RDS on it. Was able to connect without issue. Pointed it to the first RDS server license manager and have still been able to connect with
the Thin Client. The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger. So my issue is with the license and so my question is what is it with the license server
running on that server that is keeping thin client from connecting. I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
from domain still not able to connect. Any help would be appreciated.We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again"
After reading all of the postings about this issue and tried the reactivate solution of the license server,
I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
What I did, I installed a new license server activate it but did not install licenses on it.
I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Certificate
X509 Certificate
X509 Certificate ID
X509 Certificate2
Then reboot.
After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
reboot and all worked fine.
So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
x509 certs so it keeps working.
I hope this helps someone
This issue was driving me crazy so very happy that it is resolved now
Cheers Frits
Maybe you are looking for
-
How to see several windows at the same time?
I know this is too basic. I have 1 window open. The tab shows 3 separate items each of which I can click on and see. But I don't want to see each window 1 at a time. I want to see all 3 items at one time. I know how to tile once I see all 3 windows.
-
Hey all-- I'm an iMovie newbie with a question about themes. I'd like to use some of the theme elements, but whenever I drop in a clip it reverts to the original clip start point and doesn't retain any of my clip length edits. Do I need to prepare my
-
Hi All, Now i've 2 years of experience in ABAP .Now i want to change my career . My organisation is going to train me on BW.Shall i accept BW or Shall i ask them to train me on HR ABAP,but it will take few months time or Shall i study WEB DYNPRO by m
-
Inaccurate colors in organizer thumbnails
System is Win7 PSE 8; RAW I've been using this system for several months without problems. Yesterday I took some flower pictures, but when I imported them into the organizer the color was way off - very red. They were correct in camera and in the P
-
Scroll bar in spark application
hi all i have developed a spark application, but its vey strange that scroll are not coming automatically if the application is resized. So how can i get the scroll bars. Please Help regards kapil arora