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

Similar Messages

Fat Client and Thin Client

Hello, everyone
I am a newbie with websphere 5. I am wondering if anyone know fat clients(Swing GUI) work with websphere. I know thin clients(web-based interface) work with websphere. My scenario is like this and this is all experimental purposes:
I want to program a Swing GUI interface as the client that accesses the enterprise javabeans that is installed on websphere. So the Swing GUI is the client and Websphere is the server, which makes it a 2-tier Application. My question is basically, does websphere only work with web-based application or does it work with both desktop application clients and web-based application clients also?
Any Ideas?

Thanks, that's the kinda of straight answer I am looking for. I have been researching for this answer to this question for a long time and even posted several similar questions on Java forum, but no one seemed to have a straight answer. What I was thinking of programming is:
client/server program using websphere.
Client:
GUI interface using Swing that is just like a regular desktop application and not a web browser (I notice the most common application using websphere are web based applications like portals).
Server:
Using Websphere to accept connection when requested by the client and act as a bean container, which holds EJBs. The EJBs will connect to the database (mssql server) to pull data from.
Does this sound OK and can this be done using Websphere? I am using Websphere 5.
Thank you, I am just a newbie in j2ee, just trying to get started in this area of programming.

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.

How to determine using MDM rich client OR thin client?

We want to save but also want to make sure nothing missing
SO could you tell me how to decide rich client or thin client?
Thanks!

Hi Jessica,
MDM Rich Clients: A rich client is a networked computer that has some resources installed locally (MDM Components) but also depends on other resources distributed over the network (MDM SERVER). It Provides rich functionality.
e.g MDM Components (MDM Console, MDM Import Manager, MDM Data Manager and MDM Syndicator)
MDM Thin Clients: If a user only needs to perform select tasks and does not need all the functionality of a standard computer or program, a thin client may be the right tool for the job. e.g. SAP Enterprise Portal (Iviews for Search and Read access)
You can verify that MDM Components are Rich clients and SAP Enterprise Portal is a Thin client on page 4/41 Components in a MDM landscape as given in below link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/284a5534-0601-0010-da9f-b70996d5ce90?quicklink=events&overridelayout=true
Regards,
Mandeep Saini

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.

LabVIEW license for terminal servers and thin clients (e.g. LTSP)

Does NI plan to provide a license agreement for terminal servers and thin
clients?
I've been told to purchase a multi-seat license. That doesn't make much
sense since the thin clients won't be accessing DAQ hardware. They're
just used for developing the LV source.
Comments/suggestions?

On Thu, 04 Nov 2004 13:43:58 -0600, jbrohan wrote:
> As far as I know it's the capability to edit the source code that NI has
Yes, this is a very good point. Quite a unique situation when compared to
text based languages. Keep in mind I certainly don't mind paying for that
but I see no need to pay for much of the other features - like running it.
This is certainly one of the other features you pay for with LV. Since
we never plan to run the app on the thin client, why pay for that
feature?
What we do is crank out source code on the thin clients. We then send the
source code to this wireless mobile DAQ station running WindowsXP. From
there we can roll it up to our clients' target systems. That machine is
used for debugging then compilin
g so it has its own LV Prof Dev license
installed on it. Also, it can be operated locally or remotely via remote
desktop (one user at a time).
I know it may sound strange but it works great. And as the NI Software
License Agreement(NISLA) specifies, we have separate licenses on all
machines that load LV into local memory. The thin clients load nothing
into local memory, hence no need for a separate license.
> I express myself clearly in the hope of guidance. I am a one man shop
Yes, this is understandable. Installing one license on multiple machines
is a big no-no. However, that is not what I'm trying to do. Take a peek
at the "Grant of License" and "Single Seat License" sections of the NISLA.
> You say "That doesn't make much sense since ..." One of my clients has a
Ha! How about this scenario: As wireless hardware (bluetooth, wifi)
becomes more common, perhaps NI will have a peer scanner on all PCs with
LV installed. That way if you get within 100 feet of a P
C with the same
LV serial number, you get locked out and it sends a small message to the
NI batcave.
Thanks for the response. I'm hoping NI chimes in soon.

ABAP Client and J2EE client mismatch

Hello,
we detected mismatch between default ABAP login client and J2EE client.
Now we need to change J2EE client to default ABAP client.
Its ABAP + JAVA installation and diff. occured after client copy.
Can you please let us know where we need to change all setting for j2ee engine like default client for UME, sld etc.
Best Regards,
Tushar

Hello. By default JAVA used the 001 client in ABAP+JAVA installation, be cautious with change it.
you can chage it through Config tool :
http://help.sap.com/saphelp_nw70/helpdata/EN/0b/50ad3e1d1edc61e10000000a114084/frameset.htm
or from UME --> configuration --> ABAP system. You need to read about change datasources :
http://help.sap.com/saphelp_nw70/helpdata/EN/7e/a2d475e5384335a2b1b2d80e1a3a20/frameset.htm
and about SAPJSF user.
http://help.sap.com/saphelp_nw70/helpdata/EN/db/8b9b801df84aaaa76bdbcbc0b9725f/content.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/43/03e11edc6a6e99e10000000a11466f/content.htm
Regards.

Difference between Golden Client and Master Client

Dear,
What is the Difference between Golden Client and Master Client?
Thanx & Regards,
Mohammad Nabi,
[email protected]

Golden Client is similar or is the the same as Development Client, which should not be used for testing.
Master Client ???
Note on SAP Landscape:
Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different landscape DEV, QAS and PROD.
- DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.
- QAS may again have multiple clients for ex: 300- Integration Test, 700 to 710 Training.
- PROD may have something like a 200 Production.
These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario.
Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving every time. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example).
You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful transport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients.
But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.
The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.
In summary:
Landscape : is the arrangement for the servers
IDES : is purely for education purpose and is NOT INCLUDED in the landscape.
DEVELOPMENT ---> QUALITY -
> PRODUCTION
DEVELOPMENT : is where the the consultants do the customization as per the company's requirement.
QUALITY : is where the core team members and other members test the customization.
PRODUCTION : is where the live data of the company is recorded.
A request will flow from Dev->Qual->Prod and not backwards.
1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process.
2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server.
3. Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new development is done is development client and the request is transported to production.
These three are landscape of any Company. They organized their office in these three way. Developer develops the program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server.
Presentaion Server- Where SAP GUI has.
Application Server - Where SAP Installed.
Database Server - Where Database installed.
Regards,
Rajesh Banka
Reward points if helpful

Difference between native client and workstation client.

hi,
I am confused with the difference between native client and workstation client.In
some docs,it is said that native client is one which run on the same system as
the server,in other it is said running on other machine in the same domain.So
what about workstation client?So can anyone please helpme out in knowing this
difference?

subhash wrote:
hi,
I am confused with the difference between native client and workstation client.In
some docs,it is said that native client is one which run on the same system as
the server,in other it is said running on other machine in the same domain.So
what about workstation client?So can anyone please helpme out in knowing this
difference?The simple answer is that /WS clients are compiled with the -w option.
The complicated answer has to do with how the client connects to Tuxedo during the
tpinit(), and all subsequent traffic. A Tuxedo Domain (instance) has a Bulletin
Board, which is a chunk of shared memory with all kinds of information about Servers
and Clients. A Native Client, since it is running on the same machine that the
Bulletin Board exists on, can directly access the shared memory. However, /WS client
(also called a remote client) cannot access this shared memory. Instead, we have the
WSL server to make connections with, and then WSH processes that access the Bulletin
Board on behalf of the remote client.
So Native Clients run on the same machine as the Servers and where the Bulletin Board
is located, and have direct access to shared memory and other IPCs. Workstation
Clients/WS Client/Remote Clients (all the same thing) cannot access IPCs and have the
WSH do it on their behalf.
In NT, the Tuxedo IPC Service mimics Unix IPCs, and so all the above is still true.
Brian Douglass
Transaction Processing Solutions, Inc.
8555 W. Sahara
Suite 112
Las Vegas, NV 89117
Voice: 702-254-5485
Fax: 702-254-9449
e-mail: [email protected]
[briand.vcf]

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.

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

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

ISE Profilinh and Thin Clients

I have ISE 1.2 and HP T610 thin client on the network
802.1x authorization is working correctly but clients are profiled as generic HP-devices or HP printers
I don't know how to create custom profiling policy for 'HP-Thin-Client' device.
What OUI conditions to assign for HP T610 clients?
Thanks in advance,
Vice

I have advanced license
Also I checked Feed Service, it is enabled but there is no updates listed under 'Update Information and Options'
I have configured external syslog server but I don't know which logging categories needs to be enabled to get syslog messages from Profiler Feed Service
Thanks in advance,
Vice
Sent from Cisco Technical Support iPad App

Q: Anonymous user and thin client jars

Hi all. I've recently upgraded from WLS 7.0 to WLS 8.1. One of the changes I
did with this was update my java client from using weblogic.jar to wlclient.jar
and wljmsclient.jar (the thin client jars). When I do this and attempt to connect
to my WLS instance anonymously, I get the following message:
SubjectManager not installed
If I either use the 8.1 weblogic.jar or use the thin client jars with JAAS, everything
works.
I'd still like to be able to have anonymous connections to my instance and use
the thin client jars. Is there an additional jar I need to include?
Thanks,
Ed

Hi all. I did some more digging, and it looked like our client code was using
some class wrappers which assumed a JAAS Subject was being used, when it wasn't.
The end result was we were calling into an empty Subject instance. This is what
was causing the error. Pilot error on our part. :)
Ed
"Ed Hillmann" <[email protected]> wrote:
>
Hi all. I've recently upgraded from WLS 7.0 to WLS 8.1. One of the
changes I
did with this was update my java client from using weblogic.jar to wlclient.jar
and wljmsclient.jar (the thin client jars). When I do this and attempt
to connect
to my WLS instance anonymously, I get the following message:
SubjectManager not installed
If I either use the 8.1 weblogic.jar or use the thin client jars with
JAAS, everything
works.
I'd still like to be able to have anonymous connections to my instance
and use
the thin client jars. Is there an additional jar I need to include?
Thanks,
Ed

Wireless broadcom pci mini adapter and thin client t620

Hi
I need toknow if part code 582564-001 will work in the thin client F5A54AT. Are there driver availalbe?
Thanks

I finally solved this problem by retrying the steps posted elsewhere in the community. I did NOT revert my o/s to Windows 8 and reinstall the upgrade to 8.1. I simply went into Device Manager and uninstalled the wireless adapter and its software. I then downloaded and installed the Realtek 8188CE Windows 8 driver from the Lenovo H520 drivers page. Finally, I followed the steps to update that driver, selecting the option to choose the driver myself. You should see a Microsoft driver and a Realtek driver - pick the Realtek driver and you should be good to go.

Rich client and thin client

Similar Messages

Maybe you are looking for