What is thin client ?

Please expalin me what is "Thin client? and what is seemless connections among all the 4 Tiers in HFM Applivation? and what is Classic HFM Application? and What is Artifacts?

Hi,
If we access a clients from web based are thin clients. We can access HFM through workspace or direct HFM weblink.
The client tier contains the user interface and the ability to communicate with the application tier. You can display data and metadata, enter data, and maintain metadata in this tier.From the Web server tier, you access the Web-enabled portions of Financial Management.The middle tier contains the domain intelligence and connections to the relational database and The data tier contains the relational database and all Financial Management data and metadata.
we can create two types of application in HFM classic or EPMA. Classic applications are individual to each application.
In EPMA we can share same dimention structures among multiple applications. dimension library maintains the dimension and application library maintains the all the application whinch is created in EMPA only.
Kiran

Similar Messages

What is thin client and Fat Client

Hi Experts,
I would like to know about Fat Client and Thin client in detailed words.
Thanks and Regards.
Chilla..

Hi Chilla,
     The thin clients are clients that reduce the load on servers.
Let me explain hw thin clients will get works.
     Thin clients are stores,all required library files in you local system,so that the corresponding applications which are using will be used the library files in your local system and it get execute and where as in the case of Fat clients the library files are not stored in your local system.
   Please let me know if you have any doubts regarding this.
Thanks and Regards,
Chandu.

What is Thin and Thick Client ? Differences between the Two ? Which is Best

Dear All,
I like to develop both web-based and also standalone applications. i like to choose the best drivers for my applications. can anybody suggest which one to choose and what are the drawbacks in each driver ?
Thanks,
J.Kathir

Dear All,
I like to develop both web-based and
h web-based and also standalone applications. i like
to choose the best drivers for my applications. can
anybody suggest which one to choose and what are the
drawbacks in each driver ?I dont get what excatly you meaned by driver but basicaly a thin client means it only does the prescentation of data to its user and all the logics will be in a server. for every task it will connect to the server.
In a Thick client it can do more processing and it will connect to the server only for the tasks that it cant perform with the data it has in the client.
>
Thanks,
J.KathirHere is a general comparison between main features of thin/thick(fat) clients
Both thin and thick clients has their own advantages and disadvantages. most of time one wins when other fails.
1. Thin client extencvely uses the server to all its operations which will increace the network traffic and the load on the server. as a result the perfomance of the client will depend on the load and the resources available for the server
2. But all the logic is in the server so if you are developing multiple clients for the same application (Ex:- Standallone app, Web client, Mobile clients......) you will not need to duplicate logic in each client.
3. Fat clients reduce the load on server and less dependant on the server. but since they are fat they will take more processing power and memory on client computers.
4. If you are developing multiple clients as menctioned in 2 you will need to duplicate the logics written the clients

What is thin and fat client

Hi,
I would like to know
what is thin and fat client.
what is the difference between thin and fat client.
How to copy config only client. (No data copy)
Appreciate for your reply... I will reward the points.
Thanks
Atul-

Hi Atul,
Thin Clients
A thin client is designed to be especially small so that the bulk of the data processing occurs on the server. Although the term thin client often refers to software, it is increasingly used for the computers, such as network computers and Net PCs, that are designed to serve as the clients for client/server architectures. A thin client is a network computer without a hard disk drive. They act as a simple terminal to the server and require constant communication with the server as well.
Thick Clients
In contrast, a thick client (also called a fat client) is one that will perform the bulk of the processing in client/server applications. With thick clients, there is no need for continuous server communications as it is mainly communicating archival storage information to the server. As in the case of a thin client, the term is often used to refer to software, but again is also used to describe the networked computer itself. If your applications require multimedia components or that are bandwidth intensive, you'll also want to consider going with thick clients. One of the biggest advantages of thick clients rests in the nature of some operating systems and software being unable to run on thin clients. Thick clients can handle these as it has its own resources.
Thick vs. Thin - A Quick Comparison
Thin Clients
- Easy to deploy as they require no extra or specialized software installation
- Needs to validate with the server after data capture
- If the server goes down, data collection is halted as the client needs constant communication with the server
- Cannot be interfaced with other equipment (in plants or factory settings for example)
- Clients run only and exactly as specified by the server
- More downtime
-Portability in that all applications are on the server so any workstation can access
- Opportunity to use older, outdated PCs as clients
- Reduced security threat
Thick Clients
- More expensive to deploy and more work for IT to deploy
- Data verified by client not server (immediate validation)
- Robust technology provides better uptime
- Only needs intermittent communication with server
- More expensive to deploy and more work for IT to deploy
- Require more resources but less servers
- Can store local files and applications
- Reduced server demands
- Increased security issues
To copy only config client , there are few more profiles that you can choose in scc8
SAP_EXBC - SAP_UCSV with cross-client customizing
SAP_EXPA - SAP_ALL with cross-client customizing
SAP_EXPC - SAP_CUSV with cross-client customizing
if it helful reward points are appreciated
Message was edited by:
Pierluigi Demaria
Message was edited by:
Pierluigi Demaria

What files do I need to download iPhone photos to a thin client (HP)? Apple Mobile Support gives 4 dll files to enable the iPhone to be detected and charged but the thin client doesn't see the camera or hard drive.

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.

Problem in Using Oracle with Thin Clients(Image) Technology

I am running Oracle on Server and mine clients are thin clients.I have image on Oracle Server from where I am booting thin clients.The Problem I am facing is when I use single Thin client then everything works but as I starts using more than one thin client mine I got the error rwrun60 and it gives the that close or ignore message.I am using run_product for running reports.Then I tried to use run_report_object but how can I pass paramater using run_report_objects

i m not getting much from what you are saying.... but i found something.i created a windows application and then was able to create a dataset from ODAC connection to oracle. then dragging the dataset on windows form... i was able to create a data grid containing the data. hittin F5 the app was running successfull. however when tryin to do same in asp.net...when configuring the data source using sql datasource it gave me following error ...
ORA-00942: table or view does not exist
help help

Creating a thin client network in VMWare Workstation

I have recently been informed that many our customers have a thin client network in place using Microsoft RDP, Terminal Services / Remote Desktop Services.
What I would like to do is create a virtual thin client network using Server 2008 | Server 2008 R2 | Server 2012. What I am not certain of is how to emulate the "desktop" environments for the clients and how to configure VMWare to work with this type of network.
Is this possible?
I admit that I have never configured a TS before, so hopefully someone here has done this before and can provide some pointers.
I have been searching Google for information but so far have come up short. Perhaps my search criteria is wrong.
I have VMWare Workstation 10 and access to MSDN for a number of ISOs.
Thank you.
Dan

user12049849 wrote:
I have Oracle VM server release 2.1.5, IPTABLES is disable on both the VM Server host and client. I am able to ping the gateway from the VM Host; but, not from the VM client. I can't even ping the VM Host from the VM client or ViceVersa.
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif2.0vif2.0 is the connection between the bridge and your guest. It is connected to xenbr0
peth0
vif0.0
xenbr1 8000.feffffffffff no peth1
vif0.1
xenbr2 8000.feffffffffff no peth2
vif0.2
xenbr3 8000.feffffffffff no peth3
vif0.3
ethtool -i peth1
driver: e1000
version: 7.6.15.5ora-NAPI
firmware-version: 5.11-2
bus-info: 0000:25:00.1Why are you showing us information about peth1? Did you intend to connect the guest to it / xenbr1?
VM HOST:
# ping 10.1.1.1
PING 10.1.1.1 (10.1.1.1) 56(84) bytes of data.
64 bytes from 10.1.1.1: icmp_seq=1 ttl=255 time=0.812 ms
64 bytes from 10.1.1.1: icmp_seq=2 ttl=255 time=0.765 ms
64 bytes from 10.1.1.1: icmp_seq=3 ttl=255 time=0.885 msWhere is this 10.1.1.1 on your network? What is the relevance of this output?
>
>
The VM Client ifconfig shows eth0 configured correctly IP, MASK and Broadcast, then the loopback... nothing else. Route command shows the correct Gateway. Well, nobody is perfect, so maybe you can post the complete config for review? Maybe you used xenbr1 when you should be using xenbr0, or something like that. Saying that it's correct is not the same as showing us that it is correct.
- ifconfig -a on dom0 and domU
- route -n on dom0 and domU
- vm.cfg of the domU

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 more

uday 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

Issue with non-english application in thin client - virtual directory issue

Hi,
I have just completed Siebel 8 installation on solaris machine along with SunOne Web server 6.1.
I have installed both ENU and ARA language packs for Siebe Enterprise, Sweapps.
The issue is after installation and repository installation for both ENU and ARA, I am able to open only ENU applications in thin client.
When I try to open the ARa applications the browser gives "Page not found" error.
I have verified first, whether the Siebel components running or not. Confirmed that for example for Callcenter SCCObjMgr_ara component is active and online.
But what I observed is, in SUNOne web server instance's config folder, there is a file obj.conf.
In this file there are entries for only enu applications like,
NameTrans fn="pfx2dir" from="/callcenter_enu" dir="/siebelapp/sweapp/public/enu"
There are no links for ARA applications.
I think this could be the reason for issue.
But while installing and configuring sweapps, I have selected the logical profile location as "/siebelapp/gtwysrvr/admin/Webserver".
So this should create such links in obj.conf for ARA as it created for ENU apps. But it didn't happend.
Please advise, how to get the ARA applications.
Thanks
Vamshi
Edited by: user4619223 on Mar 23, 2010 11:36 AM

I see some message about a proxy. Have you checked that you can use the proxy from you network?
If not you should turn the proxy off.
Timo

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 Lex

I 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

Diff between Thin client and Rich client

Hi Everyone,
Can someone give me a clear picture of the what is the diff between Thin client and Rich client.
Thanks,
Krishna

Hi,
thick client (rich client) has/stores all the data inside itself
so it can do application processing without the server with data
thin client uses resources from host computer (from server)
and wihtout that you are not able to work with that kind of client
does that answer your question ?
Regards,
michal

Printer for Terminal Services / Thin Clients

Hi, Just checking on what multifunction printer you would suggest for use with a Terminal Services environment? We only require the printer to go through TS. The other features will be used locally (photo copy/fax).
I am looking at the CM2320, a good choice?
Terminal Services: Windows 2003
Thin Client: T5730 using RDP 6.0
Many thanks

Hi,
Thank you for posting in Windows Server Forum.
A mandatory user profile is a special type of pre-configured roaming user profile that administrators can use to specify settings for users. With mandatory user profiles, a user can modify his or her desktop, but the changes are not saved when the user
logs off. The next time the user logs on, the mandatory user profile created by the administrator is downloaded. There are two types of mandatory profiles: normal mandatory profiles and super-mandatory profiles.
User profiles become mandatory profiles when the administrator renames the NTuser.dat file (the registry hive) on the server to NTuser.man. The .man extension causes the user profile to be a read-only profile.
User profiles become super-mandatory when the folder name of the profile path ends in .man; for example, \\server\share\mandatoryprofile.man\.
More information:
Mandatory User Profiles
http://msdn.microsoft.com/en-us/library/windows/desktop/bb776895(v=vs.85).aspx
Using User Profiles in Windows Server 2003
http://technet.microsoft.com/en-us/library/cc776120(v=ws.10).aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Make a test with thin client

Hi all,
I'm facing a strange boring problem. I've a tomcat runs a webapp that using thin client connects to a remote DB.
From about a week is not able to connect anymore. Java hangs and report this error:
java.sql.SQLException: Io exception: Connection reset
So I've no firewall and listener is correctly working. Telnet to listener is working.
Does anyone has a simple java class to run to make a connection test?
Thanks
Stefano

Use preparedStatement either like this
String query = update tableName set datefield= TO_DATE(?, 'YYYY-MM-DD HH24:MI') where id= ? ";
and setString(1, string);
or
String query = "update tableName set datefield= ? where id= ?";
and setTimestamp() or setDate () depends what you need in your date field .
Bets regads Alexey.

ADF panel opening too many JDBC Thin Client database sessions.

Hi All,
I have several ADF Panels, which allows the user to run a few simple queries against an Oracle database done using ADF view objects and ADF view links and ADF application module.
Each ADF panel as I said contains several View Link queries, and links under the form of Jbuttons to other ADF Panels running other ADF View Links.
Running the ADF Panel as described here opens up to 21 database sessions displaying as “JDBC Thin Client” when I look them up from v$session.
Why do I end up with that many database sessions.
Why doesn’t it just use one or two database sessions to run all these View Links? It seems that it is opening one database session for each of these view links.
How can I change this destructive behavior? I only one to see one or two database sessions for the entire ADF panel no matter how many ADF View Links it contains.
Your suggestions are most appreciated.
Thanks.
Bobby A.

Thanks for your response.
I took a quick look at the docs you pointed me to. It seems that I can set some parameters in bc4j.xcfg of each application module Home to control number of database connections that the application module will create. In that case maybe you can recommend which parameters and what value they should be set to.
Your response will be most helpful as my background is rather in database admin and not java.
Thanks.
Bobby A.

Connection through jdbc thin client taking more time than from sqlplus!!!

Hello All
Machines A and B
Applicaion in A is connecting to B(9.2.0.6),db server.
The schema is so small with few tables and data in each table less than 500 rows
We are in the process of migrating the Application Schema in B to C[9.2.0.8].
But the response time is more when the application fetches from C.
Even while selecting the sysdate from dual.
The application is using the jdbc thin client for fetching the data.
When the same sql is executed by (from A to C)
sqlplus -s user/pass @execute.sql, its gets done in a fraction of a second.
But when the same is done through the application which uses jdbc thin client, it takes few seconds
to complete.
When tried with a small java program that uses classes12.jar (from A to C)
conn = DriverManager.getConnection(URL,UID,PASS);
               stop = System.currentTimeMillis();
               System.out.println("Connection time in milli sec: " + (stop - start));
               System.out.println();
..It was found that creating the connection was taking time.
But the same is not happening when tired through the sqlplus
Could someone throw some light into this?
What could be the reason for jdbc to get slower while establishing connections?
TIA,
JJ

are you using latest drivers - http://www.oracle.com/technology/tech/java/sqlj_jdbc/index.html
you may want to check some options reducing jdbc connection cost from the otn samples - http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/index.html

What is thin client ?

Similar Messages

Maybe you are looking for