Warehouse builder is thin or thick client

Is warehouse builder a thin or thick client..

There is a OTN forum for Oracle Warehouse Builder that you should use for this question.

Similar Messages

  • 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

  • Thin & Thick Client - Update UI on a data change in server.

    Hello friends -
    I need to develop a application. It has both Thin(Web) & Thick client(Swing/SWT). Both clients display some table information. Table information is collected from many different datasources.
    Problem: How to update both Thin & Thick clients on a data updation. There might be 10K+ users accessing the server for this table information, either through Web browser or Java thick client (Swing/SWT). And every sec, data is updated in the database (there will be atleast 100 messages /sec updating the datasources). Web clients need to poll to get the update. And Thick clients need to be notified of data change by the server.
    Is there any (open source) framework available to achieve this. I have some thoughts for this, but would like to know is there is any proven architecture available for this kind of problem.
    Thanks.

    Those update rates are pretty low for a typical JMS system, so you should be fine with most decent JMS providers.
    For the thing clients you could consider using Ajax to avoid unnecessary database polling by large numbers of clients...
    http://activemq.org/Ajax
    James
    http://logicblaze.com/

  • Differences between Oracle JDBC Thin and Thick Drivers

    If any body is looking for this information...
    ============================================================
    I have a question concerning the Oracle JDBC thin vs. thick drivers
    and how they might affect operations from an application perspective.
    We're in a Solais 8/Oracle 8.1.7.2 environment. We have several
    applications on several servers connecting to the Oracle database.
    For redundancy, we're looking into setting up TAF (transparent
    application failover). Currently, some of our apps use the Oracle
    <B>JDBC thin</B> drivers to talk to the database, with a connection
    string that like this:
    <B> jdbc:oracle:thin:@host:port:ORACLE_SID </B>
    In a disaster recovery mode, where we would switch the database
    from one server to another, the host name in the above string
    would become invalid. That means we have to shut down our application
    servers and restart them with an updated string.
    Using the Oracle <B>OCI (thick)</B> driver though, allows us to connect
    to a Net8 service instead of a specific server:
    <B> jdbc:oracle:oci8:@NET8_SERVICE_NAME </B>
    Coupled with the FAILOVER=ON option configured in Net8, it is
    then possible to direct a connection from the first server to
    the failover database on another server. This is exactly what
    we would like to do.
    My question is, from an application perspective, how is the Oracle
    thick driver different from the thin driver? If everything
    else is "equal" (i.e. the thick driver is compatible with the
    app servers) would there be something within the the thick/OCI
    driver that could limit functionality vs. the thin driver?
    My understand, which obviously is sketchy, is that the thick
    driver is a superset of the thin driver. If this is the case,
    and for example if all database connections were handled through
    a configuration file with the above OCI connection string, then
    theoretically the thick driver should work.
    ============================================================
    <B>
    In the case with the Oracle, they provide a thin driver that is a 100% Java driver for client-side use without the need of an Oracle installation (maybe that's why we need to input server name and port number of the database server). This is platform indipendent, and has good performance and some features.
    The OCI driver on the other hand is not java, require Oracle installation, platform dependent, performance is faster, and has a complete list of all the features.
    </B>
    ========================================================
    I hope this is what you expect.
    JDBC OCI client-side driver: This is a JDBC Type 2 driver that uses Java native methods to call entrypoints in an underlying C library. That C library, called OCI (Oracle Call Interface), interacts with an Oracle database. <B>The JDBC OCI driver requires an Oracle (7.3.4 or above) client installation (including SQL*Net v2.3 or above) and all other dependent files.</B> The use of native methods makes the JDBC OCI driver platform specific. Oracle supports Solaris, Windows, and many other platforms. This means that the Oracle JDBC OCI driver is not appropriate for Java applets, because it depends on a C library to be preinstalled.
    JDBC Thin client-side driver: This is a JDBC Type 4 driver that uses Java to connect directly to Oracle. It emulates Oracle's SQL*Net Net8 and TTC adapters using its own TCP/IP based Java socket implementation. <B>The JDBC Thin driver does not require Oracle client software to be installed, but does require the server to be configured with a TCP/IP listener. Because it is written entirely in Java, this driver is platform-independent.</B> The JDBC Thin driver can be downloaded into any browser as part of a Java application. (Note that if running in a client browser, that browser must allow the applet to open a Java socket connection back to the server.
    JDBC Thin server-side driver: This is another JDBC Type 4 driver that uses Java to connect directly to Oracle. This driver is used internally by the JServer within the Oracle server. This driver offers the same functionality as the client-side JDBC Thin driver (above), but runs inside an Oracle database and is used to access remote databases. Because it is written entirely in Java, this driver is platform-independent. There is no difference in your code between using the Thin driver from a client application or from inside a server.
    ======================================================
    How does one connect with the JDBC Thin Driver?
    The the JDBC thin driver provides the only way to access Oracle from the Web (applets). It is smaller and faster than the OCI drivers, and doesn't require a pre-installed version of the JDBC drivers.
    import java.sql.*;
    class dbAccess {
    public static void main (String args []) throws SQLException
    DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
    Connection conn = DriverManager.getConnection
    ("jdbc:oracle:thin:@qit-uq-cbiw:1526:orcl", "scott", "tiger");
    // @machineName:port:SID, userid, password
    Statement stmt = conn.createStatement();
    ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
    while (rset.next())
    System.out.println (rset.getString(1)); // Print col 1
    stmt.close();
    How does one connect with the JDBC OCI Driver?
    One must have Net8 (SQL*Net) installed and working before attempting to use one of the OCI drivers.
    import java.sql.*;
    class dbAccess {
    public static void main (String args []) throws SQLException
    try {
    Class.forName ("oracle.jdbc.driver.OracleDriver");
    } catch (ClassNotFoundException e) {
    e.printStackTrace();
    Connection conn = DriverManager.getConnection
    ("jdbc:oracle:oci8:@qit-uq-cbiw_orcl", "scott", "tiger");
    // or oci7 @TNSNames_Entry, userid, password
    Statement stmt = conn.createStatement();
    ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
    while (rset.next())
    System.out.println (rset.getString(1)); // Print col 1
    stmt.close();
    =================================================================

    Wow, not sure what your question was, but there sure was a lot of information there...
    There really is only one case where failover occurs, and it would not normally be in a disaster recovery situation, where you define disaster recovery as the obliteration of your current server farm, network and concievably the operational support staff. This would require a rebuild of your server, network etc and isn't something done with software.
    Fail over is normally used for high availablity that would take over in case of hardware server failure, or when your support staff wants to do maintenance on the primary server.
    Using the thin and thick driver should have ZERO affect on a failover. Transparent failover will make the secondary server the same IP as the primary, therefore the hostname will still point to the appropriate server. If you are doing this wrong, then you will have to point all your applications to a new IP address. This should be something that you tell your management is UNACCEPTABLE in a fail-over situation, since it is almost sure to fail to fail-over.
    You point out that you are providing the TNSNAME, rather than the HOSTNAME when using the thick driver. That's true within your application, but that name is resolved to either a HOSTNAME, or IP ADDRESS before it is sent to the appropriate Oracle server/instance. It is resolved using either a NAME server (same as DNS server but for Oracle), or by looking at a TNSNAMES file. Since the TNSNAMES files profilerate like rabbits within an organization you don't want a fail over that will make you find and switch all the entries, so you must come up with a fail over that does not require it.
    So, the application should not be concerned with either the hostname, or the IP address changing during fail over. That makes use of the thin or thick client acceptable for fail over.
    Don't know if this will help, but this shows the communication points.
    THIN DRIVER
    client --> dns --> server/port --> SID
    THICK DRIVER
    client --> names server --> dns --> server/port --> SID
    client --> tnsnames     --> dns --> server/port --> SID

  • 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

  • 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.

  • 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 :)

  • Instant Client 10.2.0.4 and Warehouse Builder 11.2 on Same Machine

    Previously we used instant client 10.2.0.4 on our development box to connect to 8.1.7.4 and 10.2.0.4 databases. After installing warehouse builder 11.2 we could no longer connect to 8.1.7.4 since the environment was updated to use the 11.2.0.2 client from warehouse builder.
    Attempting to fix that, i changed the PATH setting in Windows to put the instantclient directory ahead of the OWB path. Even after restarting, connections to 8.1.7.4 fail with ORA-03134.
    How can I get instantclient 10.2.0.4 working without uninstalling OWB?

    Client 11g can only connect to 9iR2 onwards only.
    You also have to look for ORACLE_HOME environment/registry variable and remove the 11.2 directories from the PATH.
    If possible use a batch script specific to the versions you want to use and set the PATH/ORACLE_HOME appropriately.

  • Installed Oracle Warehouse Builder which broke SQL Developer

    Version 1.5.4 build MAIN-5940
    SQL Developer worked fine. I installed Oracle Warehouse Builder and now SQL Developer cannot make a connection when I click on a connetion in the connectons window. When I look at the properties of the connection they look fine and when I click the "test" button I get a success message. When I click the "connect" button it appears to connect. However, When I click a connection on the navigator window I get this error message
    Invalid connection information specified.
    Verify the URL format for the speicified driver.
    Vendor Code 0
    I reinstalled SQL Developer but no help.

    Don't know OWB, but I asume it installs some version of client, which could be picked up by sqldev.
    If the problem really is that client, here's something that usually does it: trick sqldev by changing your ORACLE_HOME within a batch file inside sqldev's folder. This would force using the supplied thin driver:
    set ORACLE_HOME=%CD%
    start sqldeveloper.exeHope that helps,
    K.

  • Problem in DB Link creation ( Oracle warehouse builder 3i  )

    I am facing a problem in DB Link creation.
    Backend: Oracle 8i Server on my machine
    DW Software: Oracle warehouse builder 3i ( client , repository asistant.....)
    Operating system: Windows NT 4 SERVICE PACK 6
    I wants to use the scott database( default database given by oracle ) as my input source.
    How can I create the DB LINK ( for scott database) ?
    How can I create the DB LINK ( for any other database) ?
    Should I need to add anything in Setting of"ODBC DATASOURCE ADMINISTRATION"
    ==================
    Settings done:
    ==================
    DB Link Name :scott
    Host name
    Host name: my machine's ip address
    port number: 1521
    oracle sid: prashant ( my oracle sid)
    user name:scott
    password:tiger
    ==================
    Gives error:
    ==================
    Testing...
    Failed.
    ORA-02085 Database link %s connects to %s
    *Cause:   a database link connected to a database with a different name.
    The connection is rejected.
    *Action:   create a database link with the same name as the database it
    connects to, or set global_names=false.
    Please change it to false by doing :
    first option:
    Log in the database with DBA privilege and use the command:
    alter system set GLOBAL_NAMES = false
    second option:
    Change the GLOBAL_NAMES to false in database system parameter file, init.ora
    ==================
    Options tried:
    ==================
    1. I tried to change GLOBAL_NAMES = false but still not able to create the DB LINK.
    2. As per suggestion of one the friend
    "A file named "Logon.Properties" under the directory $OWB_HOME/wbapp
    in this file please set the property
    OWBSingleUserLockUsage = false"
    I tried the same but it is still not working.
    How should I proceed further.
    I am expecting URGENT FEEDBACK.
    Reply me on : [email protected]
    From
    Prashant

    I solved the problem.
    Procedure I followed :
    UNINSTALL ORACLE WRAEHOUSE BUILDER SOFTAWARE.
    'GLOBAL_NAMES = FALSE' in init.ora file.
    RESTARTED MY MACHINE.
    INSTALL THE ORACLE WRAEHOUSE BUILDER SOFTAWARE.

  • A bug in the warehouse builder regarding mappings of dimensions

    Hi there
    I do not know if this is the right place to submit a possible bug. Anyways - here goes.
    Warehouse builder client: 10.1.0.2.0
    Warehouse builder repository: 10.1.0.1.0
    I'm creating a dimension, having one level attributes property as a varchar2(30). Thus it has a length of 30. Now, later on I decide this was an error. I update the property to a number, deploys, and reconcile the dimension inbound in the mapping. From now on, it will give an error, since it remembers the length. And a number has a size, not a length. If I remove the dimension from the mapping, and inserts it again, the error still occurs.
    By the way, I am able to reproduce this.
    Anyone who has experienced this, and can blame the stupid user (me) or classify this as a bug?
    Yours
    Kim Andersen

    Hi Igor
    The "error" is actually a "warning":
    Warning: VLD-1004: Column length of ASD_ASDASD is longer than the target column length.
    where ASD_ASDASD is the dimension property, which I altered. It is annoying, though, to have warnings on the list, that aren't needed. And I also spent considerable time thinking that was the error in a mapping, whereas it was a stupid mistake made by me somewhere else :)
    If it's a registered bug, do I get to win some branded Oracle candy?! :)
    Yours
    Kim

  • Oracle Warehouse Builder 10.1.0.4 on Windows 2008 - 64 bits

    Hi Gurus.
    I'm currently working with a customer who wants to migrate all their database-servers to Windows 2008 on 64-bits processors. They're using Oracle Database Enterprise Edition 10g Release 2 (10.2.0.4) and Oracle Warehouse Builder (10.1.0.4). The OWB-clients will still run on Windows XP. I've used the "Certify"-funcionality on Metalink, but it doesn't really answer my questions. (It does* ansver some of my questions, but it also raises a few new ones....)
    My main question is: Can you run serverside OWB 10.1.0.4 on Enterprise Edition 10.2.0.4 for Windows 2008 64-bits?
    Thanks in advance:-)
    Best regards
    Helge
    Edited by: user613304 on Mar 6, 2009 11:10 PM

    No.
    Oracle Warehouse Builder version 10.1.x was desupported on 16-JUL-2007.
    The desupport notice is available on Metalink (Note 376384.1).
    The Warehouse Builder installation as part of the 11.1.0.7 installation should be certified, but I cannot find specifics.

  • Oracle Applications Release 12 and Oracle Warehouse Builder 10gR2

    Hi
    I'm trying to deploying process flows to Workflow but I get the following error:
    RPE-02054: The version of Oracle Workflow is incompatible with this Control Center. Required 2.6.3, but found 2.6.0.
    Comment I found on another thread: "As far Workflow Versions with Oracle Applications is concerned, it is always 2.6.0. Workflow is not identified with its 2.6.x versioning in Oracle Applications. The 2.6.x.x versioning is purely for Workflow Standalone."
    Oracle Warehouse Builder Client: 10.2.1.31
    Oracle Warehouse Builder Repository: 10.2.0.1.0
    Oracle Applications Release 12
    Any help would be appreciated.

    May be the excerpt from the other thread is a response I posted.
    So, when you say, deploying process flows to Workflow, I do not understand what you are doing exactly? If this involves the Oracle Warehouse Builder you may want to explain a little more in detail since I do not understand how OWB works with Workflow. But as far as I have heard, it is Workflow standalone that is packaged with OWB but you are deploying into Oracle Applications.
    What is the version of Oracle Workflow Builder you are using?
    Is the steps you are doing certified to be done with Oracle Applications R12?
    Thanks

  • Confuse about Configuring Oracle Warehouse Builder

    newbie here... i am abit confuse on how to configure the Oracle Warehouse builder...
    I have 2 database... 1 source and 1 new one...
    I understand that i have to install the Runtime Repository in the database computer and the Target Schema through the client's computer...
    so all this while... i am just confuse about what to install into the source database and what to install into the new database...
    Please help...

    Location is a logical entity in your OWB design that can be either a database schema, a flat file location, an SAP application location etc. Once you complete your design and are ready to deploy the design into the runtime environment, you will have to 'register' the locations by providing the physical details of your location to OWB (user name/password, database, hostname etc.).
    I am a bit confused by your configuration - are the source and the target in two separate schemas or in the same schema? Your posts are somewhat contradictory.
    If they are in two different schemas, you should:
    1. Create a source module pointing to a source schema (you can then import data object structures from the source schema - i.e. you don't have to create source tables manually in OWB, but you can import them into the module automatically). This module will have a source location (for example SRC_LOC).
    2. Create a target module where all your target objects will be (i.e. where the data will be loaded). This module will have a different location (TGT_LOC). In your target module you will also create the mappings.
    3. When deploying, you will register SRC_LOC with the physical details of your source schema, while the target location will be registered with the physical details of the target schema. The code generated by OWB during deployment will make sure that the data is extracted from the source schema and inserted into the target schema (either by generating and using DB links or by qualifying the schemas in the extraction queries if source and target are in the same database instance).
    On the other hand, if both source and target objects are in the same db schema, you can have all your objects in the same target module and you will only have to register the location of this target module when deploying (LOC_TGT).
    That said, there can be a variety of reasons why there is no data in the target after you run the extract mapping that have nothing to do with locations, such as logical errors in the mapping (an inappropriate filter or a wrong join), insufficient privileges etc. I suggest you take a look in the runtime audit browser that should contain the error messages relative to your mapping.
    Regards:
    Igor

Maybe you are looking for