HFM Thin Client and Thick Client

Hi
can anyone tell me what is HFM thin client and thick client
Thanks

Thick client is the actual application client view. Most administrators limit that view to only them and provide a workspace (the thin client) as a method of accessing hfm. This is because more can be done in terms of metadata and security changes in the thick client than the thin client.

Similar Messages

Difference between Thin Drivers and Thick Drivers

hi all,
can any one tell me the difference between Thin Drivers and Thick Drivers.
regards
ravi

OCI is Oracle Call Interface. That's the lowest-level client API Oracle offers and the API that every thick client application eventually uses. For example, a C++ application using ADO would use the OLE DB driver which is itself written in OCI.
From a deployment standpoint, the major difference is that the thin driver can be deployed to any machine that has Java installed. The OCI driver can only be deployed to machines that have the Oracle client installed.
From a performance & functionality standpoint, there are features that only the OCI driver provides. Depending on the application, the OCI driver may also be faster.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

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

JDBC thin and thick clients

What is the difference between JDBC thin and JDBC thick clients and their usage ?

hi,
in sort tearms,
Oracle has a thin client driver which mean you can connect to a oracle database without the Oracle client installed on your machine.
Thick client would need the Oracle Client database drivers etc.. Drivers include JDBC-ODBC bridge drivers JDBC drivers depending on tns resolution.
thanks

Difference bewteen thin client and thick client

Hi:
can someone explain the difference between the thin client app and thick client app?

Thin Client: Little to no logic on front end. Typically a 3 tier architecture. Example is a web browser
Thick Client: Typically a client-server type architecture where some business logic/processing occurs on the front end

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

THICK CLIENTS & THIN CLIENTS

Can any body please tell me in detail what is the difference between a Thick client and a Thin client. Also tell me using either of these in specific occassions.

And it's normally called a 'Rich Client' not 'Thick Client'.No, "rich client" is a newer developer.
s/developer/development/I think it's more than a when Sales/Marketing people wanted to promote thin client solutions (during the fashionable thin 90's) they used devisive language of (Thick/Fat) against the alternative traditional Client Server solutions even though these could be Rich or Thin. I remember when Applets where considered thin, then it had to be Web-Pages to be really Thin and now that things have gone full circle with the introduction of things like AJAX and WebStart they use the old^Wnew terminology, or Rich Clients to distance it from the negitive associations of Thick and Fat.
To me, fashions come and go but they will always be Thin or Rich :)

Rich client and thin client

Hello experts,
Rich contents are data manager, console, import manager and syndicator GUI clients
thin contents are portal way of looking mdm using iviews.
is this true??
Regards
Eva M

Hi Eva,
Good Day !
You are right .
A thing client (generally a software application/portal) depends primarily on a central server ( MDM server in this case) .It will drive communicating inputs from user to server and delivering back outputs from server to the user.Thin clients are independent of the machine you are using .
Eg:Portal
A thick client passes on data from an MDM user to Server . Such clients are generally used for performing data storage and processing activities directly at server level.Thiick clients need dedicated installations of GUIs and are machine dependant.
Eg:data manager, console, import manager and syndicator GUI clients
Hope this clarifies your query.
Regards,
Vinay M.S

Database connection encryption and integrity with ColdFusion and Oracle thin client

As ColdFusion datasource we are using the Oracle thin client to connect with the database. So, basically we are using a JDBC URL such as jdbc:oracle:thin:@... and as Driver Class oracle.jdbc.OracleDriver. This works successfully however we would like to set encryption and integrity parameters as well. In Java this is done similarly by setting a Properties object prior to getting a connection as follows:
Properties prop = new Properties();
prop.put("oracle.net.encryption_client", "REQUIRED");
prop.put("oracle.net.encryption_types_client", "( DES40 )");
prop.put("oracle.net.crypto_checksum_client", "REQUESTED");
prop.put("oracle.net.crypto_checksum_types_client", "( MD5 )");
OracleDataSource ods = new OracleDataSource();
ods.setProperties(prop);
ods.setURL("jdbc:oracle:thin:@localhost:1521:main");
Connection conn = ods.getConnection();
Is there a way that I can pass these parameters to the ColdFusion datasource. Ideally, I would love to do this centrally in such way that a change to all the cfquery or cfstoredproc is not needed.
I also know that in application servers such as Oracle AS there is an option when creating a datasource which says "Add Properties". In there you can add such properties. So, I was thinking of maybe creating a JNDI DS in the app. server and then magically connecting to it but this may have some impacts on the app.
Besides this I was also thinking of communicating with the CF datasource through the CF admin API (cfide.adminapi.administrator) and also the option of extending the Oracle driver so that when CF connects with it these params are already set.
I would love to have your professional opinion and suggestions on this.

I believe the thin driver actually needs the IP address (not the DNS name). Also, is "java" the name of the Oracle instance to which you are trying to connect?
Try the following:String driver = "jdbc:oracle:thin";
String dbIP = "W2RZ1NXG01's IP address";
String dbPort = "1530";
String dbSid = "java";
String dbUser = "Admin";
String dbPswd = "apassword";
String cnctStr = driver + ":@" + dbIP + ":" + port + ":" + dbSid;
try
    Class.forName("oracle.jdbc.driver.OracleDriver");
    con = DriverManager.getConnection( cnctStr, dbUser, dbPswd );
    stmt = con.createStatement();
    stmt.executeUpdate(createString);
    stmt.close();
    con.close();
catch(SQLException ex)
    System.err.println( "The following SQLException occurred: " + ex );
    System.err.println( "Message: " + ex.getMessage() );

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.

HP t510 Thin Client and USB Printer Redirectiion

We have HP t510 thin clients connecting to server side XenCenter and running Windows 7 virtual sessions hosted on the server. We are trying to connect a USB lablewriter printer to one of the thin clients. On the t510 device, XEN Connection General Settings Manager/Local Resources/Local Device Redirection is selected for Printers/Printer Mapping. Also on the t510 device under Peripherals/USB Manager, Protocol/All USB is set to Citrix and Devices has the USB printer selected/checked and set to Redirect.
We have also tried within the assigned Windows session, a registry key has been created under HKLM\SOFTWARE\Citrix\ICA Client\GenericUSB\Devices, using both a generic redirect for all usb printers as well as device specific using the VID and PID hardware information of the printer.
When we have booted into the Windows session and have installed the USB drivers/printing software and physically conencted the usb printer, it is not being recognized by Windows at all. Device Manager is not showing any unknown devices or anything.
Has anyone seen this same issue? Is there an easy workaround? Will there need to be a hardware policy written in XENCenter?
Thank you,
Gregory Hall

Hi Mitchell,
You might get better assistance on the HP Enterprise Business Forum since you have a business class PC.
I'll also ask a moderator to escalate your issue.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

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

Use of SQL*Loader and Thin Client

I have a java application that is currently using the thin client. For portability issues, I am unable to use an OCI driver. My application also uses SQL*Loader.
My big issue is that The Thin client requires the HOST and SID for a connection.
But, for SQL*Loader to work in a client/server environment it needs to use the SERVICE_NAME and net8. Is there any way to have SQL*Loader use similar information that the thin client is using?
I know the right solution is to use the OCI drivers, but right now that is not feasible.
Thanks for any help in advance
Jeff McNurlan
Navigation Technologies.

I assume you are using an ObjectInputStream. Without seeing your code or a snippet I can't be certain...
The JDBC spec says the following about ObjectInputStream :
"An ObjectInputStream deserializes primitive data and objects previously written using an ObjectOutputStream"
Since there was nothing written by ObjectOutputStream, ObjectInputStream has nothing to deserialize and this exception would be raised.

WebLogic 10.0 JMS Thin Client and JVM 1.4

As mentioned in [WebLogic JMS Thin Client|http://download.oracle.com/docs/cd/E11035_01/wls100/client/jms_thin_client.html#wp1026979], it can be used on JVM 1.4 client, but it seems that wljmsclient.jar and wlclient.jar compiled using java 1.5 compiler with no 1.4 compatibility.
Where can I get a 1.4 complied version of this jars for WebLogic 10 ?
Edited by: user10385140 on 02.10.2008 2:32

Hi,
The doc is correct that the 1.4 JVM is supported for thin 10.0 clients, but note that 1.4 is not supported for 10.3 (the latest version). If you confirm that there's a problem, I recommend contacting customer support. Meanwhile, as a work-around, you can use a client jar from an earlier version (such as 9.2 at the latest MP).
The latest updated version of the 10.0 client doc is at http://edocs.bea.com/wls/docs100/client/basics.html, the link you provided points to an older version of the edoc.
You might want to look at using a generated "full client" rather than a thin client unless a smaller jar size is important in your use case. The reasoning is stated in the updated edoc.
Regards,
Tom Barnes
WebLogic JMS Developer Team
Edited by: TomB on Oct 2, 2008 6:52 AM

Runtime error - class not found using JDBC driver and thin client

Hi,
We are running a small Java application on a Sun server which acts as a thin client connecting to an Oracle 8i server running on a different server.
JDK version: 1.3.1_01
OS version: Solaris 7
JDBC classes file: classes12.zip
It compiles fine, but get a runtime error (the DriverManager.registerDriver method )
cruncher [40]% javac -classpath /export/home/mrscot/classes12.zip JDBCtest.java
cruncher [41]% java JDBCtest
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jdbc/driver/OracleDriver
at JDBCtest.main(JDBCtest.java:7)
cruncher [42]%
Program:
import java.sql.*;
import java.math.*;
class JDBCtest {
public static void main (String args []) throws SQLException {
try {
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection(
"jdbc:oracle:thin@xxxxxxxxx:1521:xxxx", <userid>,<password>);
Statement stmt = conn.createStatement ();
ResultSet rset = stmt.executeQuery (".............");
while (rset.next ())
System.out.println (rset.getString ("......."));
rset.close();
stmt.close();
conn.close();
} catch (Exception e) {
System.out.println("Error: " + e);
Any ideas? Probably something very, very stupid I'm overlooking!
Thanks
Scotty ([email protected])

Supplementary question:
Hi,
We are running a small Java application on a Sun server which acts as a thin client connecting to an Oracle 8i server running on a different server.The Oracle version is 8.1.6
Will the 'classes12.zip' for 8.1.7 work with
1.3.1 of the Java JDK, and Oracle 8i 8.16 ??
Thanks Scotty

HFM Thin Client and Thick Client

Similar Messages

Maybe you are looking for