Connecting to TimesTen using DataSource in WebLogic on Linux

We are trying to use weblogic 9.2 to connect to TimesTen7.0, both are on Linux.
We have installed Oracle 10g client and then installed TimesTen 7.0 Client on the Linux server hosting weblogic.
Created Client DSN in /var/TimesTen/sys.odbc.ini file as follows:
[ODBC Data Sources]
TTclientMaster=TimesTen 7.0 Client Driver
[TTclientMaster]
TTC_SERVER="TTServerHostName"
TTC_SERVER_DSN=TTmaster
When we are trying to create DataSource in weblogic Admin console it does not show up TTClient Driver in the list.
We tried setting up using "Others" for driver and databasetype but then it asks for databasename which we don't have since TT uses DSN.
We are looking for any pointers or references that can explain how to configure weblogic to use TimesTen using TT 7.0 client DSN.

If you have access to a copy of TimesTen 6.0 you can look in the AppServer Configuration Guide (appsrv.pdf) that was shipped with that release. This guide is currently being rewritten and so is not yet available for 7.0.
If you can't get hold of a copy, e-mail me at [email protected] and I'll send it to you.
Chris

Similar Messages

  • Use DataSource of weblogic in a standalone Java file

    Hi,
    We have a requirement to run a java file at a scheduled time in a day using cron scheduler on our linux server.
    We need to fetch data from the database & perform some business logic in this standalone JAVA file.
    Our application has an EAR which is deployed on Weblogic 10.3 server & in our application, we are utilizing the datasource created in that domain using Hibernate.
    Now, can we create a standealone Java file & use exisitng datasource (without Hibernate) instead of legacy JDBC code to connect to DB.
    Also, do we need to keep this JAVA file a part of this EAR, WAR or can we put the class file in anylocation outside this EAR & then utilize datasource feature.
    Please help on the same in implementation.
    Thanks,
    Uttam

    Hi Ravi,
    I did create Datasource domain & put wlclient.jar in my application classpath (Add jar in Java Build path of application), but, when I ran application, its giving below error
    Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/kernel/KernelStatus
         at weblogic.jndi.Environment.<clinit>(Environment.java:78)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:198)
         at TestDataSource.main(TestDataSource.java:37)
    Also, I'm putting code here as I there is no provision to attach the file here. Please let me know whats wrong here.
    Also, I've given the name of datasource as testDataSource through Admin console of the domain. Do we need to prefix the name with jdbc/ in the code or without that also it works?
    import java.sql.Connection;
    import java.sql.ResultSet;
    import java.sql.SQLException;
    import java.sql.Statement;
    import java.util.Hashtable;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import javax.sql.DataSource;
    public class TestDataSource {
         public static void main(String[] args)
              DataSource ds=null;
              Connection conn=null;
              Statement stmt=null;
              ResultSet rs=null;
              Context ctx=null;
              try
                   Hashtable ht = new Hashtable();
                   ht.put(Context.INITIAL_CONTEXT_FACTORY,
                   "weblogic.jndi.WLInitialContextFactory");
                   ht.put(Context.PROVIDER_URL,
                   "t3://172.19.244.180:7001");
                   System.out.println("HERE");
                   ctx=new InitialContext(ht);
                   ds=(DataSource)ctx.lookup("jdbc/testDataSource");
                   System.out.println("HERE AFER CONTEXT CREATION");
                   conn=ds.getConnection();
                   stmt=conn.createStatement();
                   rs=stmt.executeQuery("select distinct(circle) from AIRCEL_STORE_FINDER order by 1 ");
                   while (rs.next())
                        System.out.println("circle name "+rs.getString(1));
              }catch (Exception e) {
                   System.out.println("Error in Main "+e.toString());
                   e.printStackTrace();
              finally{
                   try{
                   if(rs!=null)
                        rs.close();
                   if(stmt!=null)
                        stmt.close();
                   if(conn!=null)
                        conn.close();
                   if(ds!=null)
                        ds=null;
                   if(ctx!=null)
                        ctx.close();
                   }catch (SQLException e) {
                        System.out.println("Error in SQLException Finally "+e.toString());
                   catch (NamingException e) {
                        System.out.println("Error in NamingException Finally "+e.toString());
    }

  • Using Datasources with Weblogic 7.2

    Hi everyone,
    I am using Weblogic 7.2 with Db2 8.1 fp3(Type 4 Drivers). I am wanting
    to set up a Datasource that would allow my application to connect to
    DB2 using the JNDI lookup for that data-source.
    My question is: what additions/changes I need to make to config.xml in
    order to set this up.Looking at the Websphere Admin Doc, it seems to
    me that I need to atleast add 2 elements to my domain in config.xml:
    1. JDBCConnectionPool
    2. JDBCDataSource(and link it to the above pool)
    I have previously set-up datasources on WAS 5.0. What is confusing me
    w.r.t Weblogic is that there seems to be no way to specify the
    implementing class for the DataSource. e.g. WAS5.0 allows you to
    specify the implementationClassName of the
    datasource(com.ibm.db2.jcc.DB2ConnectionPoolDataSource in my case) while
    defining the DataSource.JDBCConnectionPool element in Weblogic does
    have an attribute called "DriverName" but per the documentation it
    should be set to an implementor of java.sql.Driver interface: there
    seems to be no way to set an implementor of javax.sql.DataSource
    anywhere.
    Could anyone please shed some light on how to set this up?
    Thanks much in advance,
    Sachin

    Mitesh,
    Many thanks for the reply. If you don't mind, I have a couple of follow-up questions
    for you.
    1> Does this mechanism work with Type 4 Pure Java Drivers?
    e.g. if I specified the connection pool as
    <JDBCConnectionPool DriverName="com.ibm.db2.jcc.DB2ConnectionPoolDataSource" Name="IBM-db2"
    Password="MYPASSWORD" Properties="user=USERNAME;DatabaseName=DATABASE" Targets="MYSERVER"
    TestTableName="SQL SELECT COUNT(*) FROM SYSIBM.SYSTABLES" URL="jdbc:db2:DATABASE"/>
    ==> I changed the DriverName to "com.ibm.db2.jcc.DB2ConnectionPoolDataSource"
    which
    is what I believe is the Type-4 version
    2> Setting the DriverName to a javax.sql.DataSource extension seems to suggest
    that the documentation in the "BEA Server Configuration Reference" guide is incorrect:
    -- For the DriverName attribute of the Connection Pool, the guide says that "DriverName
    must be the name of a class that implements the java.sql.Driver interface"
    Thanks again
    Sachin
    Mitesh Patel <[email protected]> wrote:
    <JDBCConnectionPool DriverName="COM.IBM.db2.jdbc.DB2XADataSource"
    Name="IBM-db2-xa"
    Password="MYPASSWORD"
    Properties="user=USERNAME;DatabaseName=DATABASE"
    Targets="MYSERVER"
    TestTableName="SQL SELECT COUNT(*) FROM SYSIBM.SYSTABLES"
    URL="jdbc:db2:DATABASE"/>
    <JDBCConnectionPool DriverName="COM.IBM.db2.jdbc.app.DB2Driver"
    Name="IBM-db2"
    Password="MYPASSWORD"
    Properties="user=USERNAME;DatabaseName=DATABASE"
    Targets="MYSERVER"
    TestTableName="SQL SELECT COUNT(*) FROM SYSIBM.SYSTABLES"
    URL="jdbc:db2:DATABASE"/>
    Then setup your datasource using one of this connection pools in your
    config.xml. Also, make sure your driver zip files are in the classpath.
    Thanks,
    Mitesh
    Sachin Arora wrote:
    Hi everyone,
    I am using Weblogic 7.2 with Db2 8.1 fp3(Type 4 Drivers). I am wanting
    to set up a Datasource that would allow my application to connect to
    DB2 using the JNDI lookup for that data-source.
    My question is: what additions/changes I need to make to config.xmlin
    order to set this up.Looking at the Websphere Admin Doc, it seems to
    me that I need to atleast add 2 elements to my domain in config.xml:
    1. JDBCConnectionPool
    2. JDBCDataSource(and link it to the above pool)
    I have previously set-up datasources on WAS 5.0. What is confusingme
    w.r.t Weblogic is that there seems to be no way to specify the
    implementing class for the DataSource. e.g. WAS5.0 allows you to
    specify the implementationClassName of the
    datasource(com.ibm.db2.jcc.DB2ConnectionPoolDataSource in my case)while
    defining the DataSource.JDBCConnectionPool element in Weblogic does
    have an attribute called "DriverName" but per the documentation it
    should be set to an implementor of java.sql.Driver interface: there
    seems to be no way to set an implementor of javax.sql.DataSource
    anywhere.
    Could anyone please shed some light on how to set this up?
    Thanks much in advance,
    Sachin

  • Cannot connect to TimesTen using ODBC

    Hi,
    I have a TT datastore setup on an AIX server. I have a DSN on the AIX server setup in such a fashion that I can connect to the TT datastore and query the TimesTen database.
    Now I installed a TT client on my windows XP laptop and I am trying to establish a connection from the ODBC to the AIX TT database.
    On the XP client I have setup a dsn as test3 it has the following TTC settings:
    TTC_SERVER = aix server name
    TTC_SERVER_DSN = CacheData_tt70 (this is the dsn used to connect to tt dadatabase on the AIX server machine)
    TTC_TIMEOUT = 60
    Now when I try connecting from the Windows XP box I use the following command:
    connect "dsn=test3;UID=ttadmin;PWD=ttadmin";
    I am getting the following message:
    12701: DatabaseCharacterSet attribute required for data store creation. Refer to the TimesTen documentation for information on selecting a character set.
    What I don't understand is that I have ALREADY created the datastore on the AIX server. I do not see what the issue is here.
    Last thing ......The datastore was created with character set AL32UTF8. The Oracle database that is used in the Cache Connect was created w/ a character set of AL32UTF8.
    Any help from anyone would be appreciated.
    Regards Chris Tabb

    Hi Susan,
    The .ODBC.INI file on AIX is quite long (sorry for that). I am using the "CacheData_tt70", here it is:
    # Copyright (C) 1999, 2007, Oracle. All rights reserved.
    # The following are the default values for connection attributes.
    # In the Data Sources defined below, if the attribute is not explicitly
    # set in its entry, TimesTen 7.0 uses the defaults as
    # specified below. For more information on these connection attributes,
    # see the accompanying documentation.
    # Lines in this file beginning with # or ; are treated as comments.
    # In attribute=_value_ lines, the value consists of everything
    # after the = to the end of the line, with leading and trailing white
    # space removed.
    # Authenticate=1 (client/server only)
    # AutoCreate=1
    # CkptFrequency (if Logging == 1 then 600 else 0)
    # CkptLogVolume=0
    # CkptRate=0 (0 = rate not limited)
    # ConnectionCharacterSet (if DatabaseCharacterSet == TIMESTEN8
    # then TIMESTEN8 else US7ASCII)
    # ConnectionName (process argv[0])
    # Connections=64
    # DatabaseCharacterSet (no default)
    # Diagnostics=1
    # DurableCommits=0
    # ForceConnect=0
    # GroupRestrict (none by default)
    # Isolation=1 (1 = read-committed)
    # LockLevel=0 (0 = row-level locking)
    # LockWait=10 (seconds)
    # Logging=1 (1 = write log to disk)
    # LogAutoTruncate=1
    # LogBuffSize=65536 (measured in KB)
    # LogDir (same as checkpoint directory by default)
    # LogFileSize=64 (measured in MB)
    # LogFlushMethod=0
    # LogPurge=1
    # MatchLogOpts=0
    # MemoryLock=0 (HP-UX, Linux, and Solaris platforms only)
    # NLS_LENGTH_SEMANTICS=BYTE
    # NLS_NCHAR_CONV_EXCP=0
    # NLS_SORT=BINARY
    # OverWrite=0
    # PermSize=2 (measured in MB; default is 2 on 32-bit, 4 on 64-bit)
    # PermWarnThreshold=90
    # Preallocate=0
    # PrivateCommands=0
    # PWD (no default)
    # PWDCrypt (no default)
    # RecoveryThreads=1
    # SQLQueryTimeout=0 (seconds)
    # Temporary=0 (data store is permanent by default)
    # TempSize (measured in MB; default is derived from PermSize,
    # but is always at least 6MB)
    # TempWarnThreshold=90
    # TypeMode=0 (0 = Oracle types)
    # UID (operating system user ID)
    # WaitForConnect=1
    # Oracle Loading Attributes
    # OracleID (no default)
    # OraclePWD (no default)
    # PassThrough=0 (0 = SQL not passed through to Oracle)
    # RACCallback=1
    # TransparentLoad=0 (0 = do not load data)
    # Client Connection Attributes
    # ConnectionCharacterSet (if DatabaseCharacterSet == TIMESTEN8
    # then TIMESTEN8 else US7ASCII)
    # ConnectionName (process argv[0])
    # PWD (no default)
    # PWDCrypt (no default)
    # TTC_Server (no default)
    # TTC_Server_DSN (no default)
    # TTC_Timeout=60
    # UID (operating system user ID)
    [ODBC Data Sources]
    TT_tt70=TimesTen 7.0 Driver
    TpcbData_tt70=TimesTen 7.0 Driver
    TptbmDataRepSrc_tt70=TimesTen 7.0 Driver
    TptbmDataRepDst_tt70=TimesTen 7.0 Driver
    TptbmData_tt70=TimesTen 7.0 Driver
    BulkInsData_tt70=TimesTen 7.0 Driver
    WiscData_tt70=TimesTen 7.0 Driver
    RunData_tt70=TimesTen 7.0 Driver
    CacheData_tt70=TimesTen 7.0 Driver
    ttdbgdev=TimesTen 7.0 Driver
    TpcbDataCS_tt70=TimesTen 7.0 Client Driver
    TptbmDataCS_tt70=TimesTen 7.0 Client Driver
    BulkInsDataCS_tt70=TimesTen 7.0 Client Driver
    WiscDataCS_tt70=TimesTen 7.0 Client Driver
    RunDataCS_tt70=TimesTen 7.0 Client Driver
    ttdbgdevCS=TimesTen 7.0 Driver
    # Instance-Specific System Data Store
    # A predefined instance-specific data store reserved for system use.
    # It provides a well-known data store for use when a connection
    # is required to execute commands.
    [TT_tt70]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
    DataStore=/u01/app/oracle/TimesTen/tt70/info/TT_tt70
    DatabaseCharacterSet=US7ASCII
    # Data source for TPCB
    # This data store is created on connect; if it doesn't already exist.
    # (AutoCreate=1 and Overwrite=0). For performance reasons, database-
    # level locking is used. However, logging is turned on. The initial
    # size is set to 16MB.
    [TpcbData_tt70]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
    DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/TpcbData
    DatabaseCharacterSet=US7ASCII
    PermSize=16
    WaitForConnect=0
    Authenticate=0
    # Data source for TPTBM demo
    # This data store is created everytime the benchmark is run.
    # Overwrite should always be 0 for this benchmark. All other
    # attributes may be varied and performance under those conditions
    # evaluated. The initial size is set to 20MB and durable commits are
    # turned off.
    [TptbmData_tt70]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
    DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/TptbmData
    DatabaseCharacterSet=US7ASCII
    PermSize=20
    Overwrite=0
    Authenticate=0
    # Source data source for TPTBM demo in replication mode
    # This data store is created everytime the replication benchmark demo
    # is run. This datastore is set up for the source data store.
    [TptbmDataRepSrc_tt70]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
    DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/TptbmDataRepSrc_tt70
    DatabaseCharacterSet=US7ASCII
    PermSize=20
    Overwrite=0
    Authenticate=0
    # Destination data source for TPTBM demo in replication mode
    # This data store is created everytime the replication benchmark demo
    # is run. This datastore is set up for the destination data store.
    [TptbmDataRepDst_tt70]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
    DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/TptbmDataRepDst_tt70
    DatabaseCharacterSet=US7ASCII
    PermSize=20
    Overwrite=0
    Authenticate=0
    # Data source for BULKINSERT demo
    # This data store is created on connect; if it doesn't already exist
    # (AutoCreate=1 and Overwrite=0).
    [BulkInsData_tt70]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
    DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/BulkInsData
    DatabaseCharacterSet=US7ASCII
    LockLevel=1
    PermSize=32
    WaitForConnect=0
    Authenticate=0
    # Data source for WISCBM demo
    # This data store is created on connect if it doesn't already exist
    # (AutoCreate=1 and Overwrite=0). For performance reasons,
    # database-level locking is used. However, logging is turned on.
    [WiscData_tt70]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
    DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/WiscData
    DatabaseCharacterSet=US7ASCII
    LockLevel=1
    PermSize=16
    WaitForConnect=0
    Authenticate=0
    # Default Data source for TTISQL demo and utility
    # Use default options.
    [RunData_tt70]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
    DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/RunData
    DatabaseCharacterSet=US7ASCII
    Authenticate=0
    # Sample Data source for the xlaSimple demo
    # See manual for discussion of this demo.
    [Sample_tt70]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
    DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/Sample
    DatabaseCharacterSet=US7ASCII
    TempSize=16
    PermSize=16
    Authenticate=0
    # Sample data source using OracleId.
    # Before using the CacheData DSN, uncomment both the OracleId and
    # DatabaseCharacterSet attributes and insert the appropriate values for
    # the name of your Oracle database and its database character set.
    # See the jdbc demo README for information on how to obtain these values.
    [CacheData_tt70]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
    DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/Test1
    DatabaseCharacterSet=AL32UTF8
    OracleId=dbgdev
    PermSize=16
    UID=oracle
    # Authenticate=1
    # New data source definitions can be added below.
    [ttdbgdev]
    Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.so
    DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/Test1
    PermSize=20
    TempSize=20
    DatabaseCharacterSet=AL32UTF8
    #UID=chris
    OracleID=dbgdev
    # This following sample definitions should be in the .odbc.ini file
    # that is used for the TimesTen 7.0 Client.
    # The Server Name is set in the TTC_SERVER attribute.
    # The Server DSN is set in the TTC_SERVER_DSN attribute.
    # Data source for TPCB
    [TpcbDataCS_tt70]
    TTC_SERVER=LocalHost_tt70
    TTC_SERVER_DSN=TpcbData_tt70
    # Data source for TPTBM demo
    [TptbmDataCS_tt70]
    TTC_SERVER=LocalHost_tt70
    TTC_SERVER_DSN=TptbmData_tt70
    # Data source for BULKINSERT demo
    [BulkInsDataCS_tt70]
    TTC_SERVER=LocalHost_tt70
    TTC_SERVER_DSN=BulkInsData_tt70
    # Data source for WISCBM demo
    [WiscDataCS_tt70]
    TTC_SERVER=LocalHost_tt70
    TTC_SERVER_DSN=WiscData_tt70
    # Default Data source for TTISQL demo and utility
    [RunDataCS_tt70]
    TTC_SERVER=LocalHost_tt70
    TTC_SERVER_DSN=RunData_tt70
    # Default Data Source for ttdbgdev
    [ttdbgdevCS]
    TTC_SERVER=LocalHost_tt70
    TTC_SERVER_DSN=ttdbgdev
    Now for the Windows ODBC.ini file, I am trying to use the "Test3" connection. Specifics of this connection are in the windows registry. Please note I have tried setting the connectionCharacterSet to AL32UTF8 as well as a few others:
    [ODBC 32 bit Data Sources]
    dwhdev=Oracle in OraHome92 (32 bit)
    dwhqas=Oracle in OraHome92 (32 bit)
    RunDataCS_tt70_32=TimesTen Client 7.0 (32 bit)
    TpcbDataCS_tt70_32=TimesTen Client 7.0 (32 bit)
    TptbmDataCS_tt70_32=TimesTen Client 7.0 (32 bit)
    BulkInsDataCS_tt70_32=TimesTen Client 7.0 (32 bit)
    WiscDataCS_tt70_32=TimesTen Client 7.0 (32 bit)
    test1=TimesTen Client 7.0 (32 bit)
    MS Access Database=Microsoft Access Driver (*.mdb) (32 bit)
    Excel Files=Microsoft Excel Driver (*.xls) (32 bit)
    dBASE Files=Microsoft dBase Driver (*.dbf) (32 bit)
    test2=TimesTen Client 7.0 (32 bit)
    test3=TimesTen Client 7.0 (32 bit)
    dbgdev=Oracle in OraHome92 (32 bit)
    [dwhdev]
    Driver32=c:\oracle\BIN\SQORA32.DLL
    [dwhqas]
    Driver32=c:\oracle\BIN\SQORA32.DLL
    [RunDataCS_tt70_32]
    Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
    [TpcbDataCS_tt70_32]
    Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
    [TptbmDataCS_tt70_32]
    Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
    [BulkInsDataCS_tt70_32]
    Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
    [WiscDataCS_tt70_32]
    Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
    [test1]
    Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
    [MS Access Database]
    Driver32=C:\WINDOWS\system32\odbcjt32.dll
    [Excel Files]
    Driver32=C:\WINDOWS\system32\odbcjt32.dll
    [dBASE Files]
    Driver32=C:\WINDOWS\system32\odbcjt32.dll
    [test2]
    Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
    [test3]
    Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
    [dbgdev]
    Driver32=c:\oracle\BIN\SQORA32.DLL
    Regards,
    Chris

  • CANT CONNECT TO DB USING DATASOURCE ON J2ME PERSONAL PROFILE

    Having installed the optional JDBC package for J2ME and using the personal profile. I cant seem to connect using a datasource provided by HSQLDB. I keep getting the following error in WSDD:
    This compilation unit indirectly references the missing type javax.naming.Referenceable (typically some required class file is referencing a type outside the classpath)
    My classpath contains the database.jar file.
    Where am I going wrong?
    please please could some one help.
    Thanks

    Just a guess according to my Personal Java experience: maybe that optional JDBC package for J2ME is only JDBC1.2 compatible so that your should use HSQLDB JDB1.2 package? Thanks for correction.

  • Retrieve db connection using datasource object

    The problem is: i can't retrieve the connection to database
    using datasource object in jsp.
    my jsp was build by Oracle9i Report Builder,then deployed
    to OC4J jsp container,
    i define the datasource at container level,
    but an error "log on not specified" arise.
    is it possible to use datasource object in such a way or not?
    thanks you for your help.

    What is the full Java and os versions you are using to compile and to run. Note that with JDEV the platform used for your code may be different than the platform used by JDEV itself.
    Please modify all of your exception handlers to print the stack trace. Add this as the first line in each handler.
    ex.printStackTrace();The stacktrace contains important information about where the problem really occured.
    See the Java docs for NamingException - http://docs.oracle.com/javase/6/docs/api/javax/naming/NamingException.html
    >
    This is the superclass of all exceptions thrown by operations in the Context and DirContext interfaces. The nature of the failure is described by the name of the subclass. This exception captures the information pinpointing where the operation failed, such as where resolution last proceeded to.
    •Resolved Name. Portion of name that has been resolved.
    •Resolved Object. Object to which resolution of name proceeded.
    •Remaining Name. Portion of name that has not been resolved.
    •Explanation. Detail explaining why name resolution failed.
    •Root Exception. The exception that caused this naming exception to be thrown.

  • Using Datasource with Toplink

    Hi,
    I am using toplink 10.1.3 .We are using the datasource to connect to weblogic connection pool.
    My session.xml is like this:
    - <login xsi:type="database-login">
    <platform-class>oracle.toplink.platform.database.oracle.Oracle10Platform</platform-class>
    <user-name />
    <datasource>jdbc/ds</datasource>
    </login>
    In the java DAO part,I need a physical database connection to get the ArrayDescriptor.The part of java code is below
    java.sql.Connection dbconnection=null;
    DatabaseLogin login = serverSession.getLogin();
    dbconnection=(java.sql.Connection)login.connectToDatasource(null);
    Questions:
    1.Is the above correct way to get the Physical JDBC connection from a weblogic connection pool(configured using datasource).
    2.How will the Connection released to the pool?Should i use dbconnection.close() or clientSession.release().
    Thanks

    Thanks doug for your reply.
    I am using datasource to connect to the weblogic 9.2 connection pool.
    My specific use case is this.
    I am executing a Stored procedure which will takes a Oracle user defined data type as an Input paramater.
    some steps we use in the java code for the above use case.
    --Getting the  toplink session
    ServerSession serverSession = TopLinkGenericDAO.getSession();
    clientSession = serverSession.acquireClientSession();
    --For getting the oracle user defined array
    java.sql.Connection dbconnection=null;
    DatabaseLogin login = serverSession.getLogin();
    dbconnection=(java.sql.Connection)login.connectToDatasource(null);
    oracle.sql.ArrayDescriptor descriptor = new oracle.sql.ArrayDescriptor(
    "STRING_ARRAY", dbconnection);
    oracle.sql.ARRAY arr_ORCL = new oracle.sql.ARRAY(descriptor,
    dbconnection, aIncl_Vin);
    --for executing stored procedure
    StoredProcedureCall call = new StoredProcedureCall();
    DataReadQuery dbquery = new DataReadQuery();
    call.setProcedureName(CVeITDAOConstants.INSERT_PING);
    call.addNamedArgumentValue("para1", arr_ORCL );
    dbquery.setCall(call);
    --release connection in the finally block
    finally
    clientSession.release();
    dbconnection.close();
    The above code fails when we execute it for 150 concurrent connection(using JMeter) with connection fail exception.
    Please let me know how do i release the physical jdbc connection(dbconnection) in the finally block.
    do we need to give dbconnection.close() or just by giving clientSession.release() will also release the jdbc connection.
    Thanks.

  • Where can I find how to use DataSource?

    Hi,
    I am quite new to JDBC and is writing some small database program. I find many examples use DataSource, I want to know how to use it, but cannot find the API in the docs section of java.com.
    Can anyone point me to the location of javax.sql.DataSource, or even better some examples of using DataSource?
    Also, I am using Oracle as my database, do I need to register the oracle driver first for DataSource first also?
    Any help will be approcaited.

    Hi,
    You can get the more detailed documentation at
    http://java.sun.com/j2se/1.4/docs/api/javax/sql/DataSource.html and please visit http://www.datadirect-technologies.com/download/docs/jdbc/jdbcref/usejdbc.htm for information on how to connect to database using datasources.
    Hope this helps.
    With Regards
    Gayam_Slash

  • Can  not connect datasource in weblogic server

    I have written a test class. I create datasource in weblogic server 11g(datasource name =fdbusionline jndi name = 'jdbc/fdbusionline' ) and start weblogic server. but always report the following error:
    javax.naming.NameNotFoundException: Unable to resolve 'fdbusionline'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'fdbusionline'. Resolved '']; remaining name 'fdbusionline'
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
    at weblogic.jndi.internal.ServerNamingNode_1035_WLStub.lookup(Unknown Source)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
    at com.fd.busionline.test.appinterface.impl.DataSourceTest.testConnectDataSource(DataSourceTest.java:54)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
    at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
    at oracle.jdevimpl.junit.runner.junit4.JUnit4Testable.run(JUnit4Testable.java:24)
    at oracle.jdevimpl.junit.runner.TestExecution.run(TestExecution.java:27)
    at oracle.jdevimpl.junit.runner.JUnitTestRunner.main(JUnitTestRunner.java:88)
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'fdbusionline'. Resolved ''
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
    at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    @test
    public void testConnectDataSource(){
    Connection conn = null;
    Context ctx = null;
    try{
    // Hashtable env = new Hashtable();
    // env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    // env.put(Context.PROVIDER_URL, "t3://localhost:7001");
    // env.put(InitialContext.SECURITY_PRINCIPAL, "weblogic");
    // env.put(InitialContext.SECURITY_CREDENTIALS, "!QAZ2wsx");
    Environment env=new Environment();
    env.setProviderUrl("t3://localhost:7001");
    env.setSecurityPrincipal("weblogic");
    env.setSecurityCredentials("!QAZ2wsx");
    ctx = new InitialContext();
    ctx=env.getInitialContext();
    Object obj = ctx.lookup("fdbusionline");// can not work
    Object obj = ctx.lookup("jdbc/fdbusionline"); // can not work
    DataSource ds = (DataSource) PortableRemoteObject.narrow(obj, DataSource.class);
    conn = ds.getConnection();
    Statement stmt = conn.createStatement();
    String sql = "select sysdate from dual";
    ResultSet rs = stmt.executeQuery(sql);
    while (rs.next()) {
    System.out.println(rs.getDate(1));
    } catch (Exception e) {
    e.printStackTrace();
    }finally{
    System.out.println("Test Datasource Connection");
    who can help me? Any help will be appreciated greatly

    Okay, but are you sure that the datasource is actually deployed? Does the server log or the management interface of weblogic actually report that the datasource was deployed succesfully under the name you specify? And did you double check if you don't have any name mismatches (such as a typo or an upper/lowercase mismatch)?
    I ask because the connection to the server appears to be working, but the lookup of the name gives no results - the only thing I can think of is that the resource really is not deployed even if you believe it is.
    A few observations:
    - you may want to put your JNDI credentials in a jndi.properties file in the root of the classpath in stead of hardcoding them (but you may hardcode for now as a quick test of course)
    - the correct lookup should be to "jdbc/fdbusionline", in other words you use the jndi-name.
    ctx = new InitialContext();
    ctx=env.getInitialContext();the env.getInitialContext() really is not necessary, I would remove it.

  • What's the difference between using a connection pool and a datasource

    Howdy. I figure this is a newbie question, but I can't seem to find an
    answer.
    In the docs at bea, the datasource docs say
    "DataSource objects provide a way for JDBC clients to obtain a DBMS
    connection. A DataSource is an interface between the client program and the
    connection pool. Each data source requires a separate DataSource object,
    which may be implemented as a DataSource class that supports either
    connection pooling or distributed transactions."
    In there it says the datasource uses the connection pool, but other than
    that, what is the difference between a connection pool and a datasource?

    Thanks for the info. I think it makes some sense. But it's a bit greek.
    I'm sure it'll make more sense the more I work with it. Thanks.
    "Chuck Nelson" <[email protected]> wrote in message
    news:3dcac1f5$[email protected]..
    >
    Peter,
    Here is a more formal definition of a DataSource from the Sun site
    "A factory for connections to the physical data source that thisDataSource object
    represents. An alternative to the DriverManager facility, a DataSourceobject
    is the preferred means of getting a connection. An object that implementsthe
    DataSource interface will typically be registered with a naming servicebased
    on the JavaTM Naming and Directory (JNDI) API.
    The DataSource interface is implemented by a driver vendor. There arethree types
    of implementations:
    Basic implementation -- produces a standard Connection object
    Connection pooling implementation -- produces a Connection object thatwill automatically
    participate in connection pooling. This implementation works with amiddle-tier
    connection pooling manager.
    Distributed transaction implementation -- produces a Connection objectthat may
    be used for distributed transactions and almost always participates inconnection
    pooling. This implementation works with a middle-tier transaction managerand
    almost always with a connection pooling manager.
    Does that help clarify the distinction?
    Chuck Nelson
    DRE
    BEA Technical Support

  • When is it appropriate to use DataSource (or Connection pooling)?

    Hello all,
    I'm having some design issues with my application and I'm starting to think that maybe using Connection pooling is not suited for my application. I'm using Tomcat 5.5.12 if it's any relevant..
    The architecture of our application looks like this:
    Servlets -> App Helper classes -> DB/Accessor classes
    looks like the three-tier architecture described in this document: http://www.subrahmanyam.com/articles/servlets/ServletIssues.html
    I have read on the Tomcat docs that said that using DataSource is good practice and improves efficiency since it recycles database connections. However, if the accessor/DB classes are not servlets, how can I use the DataSource facility that interacts with Tomcat?
    I would like to know whether it is a good idea to use DataSource in my case and if so, how? (since they are not servlets)
    Thanks in advance :)

    Hi. Thank you for replying.
    In the examples that I've seen that use JNDI for Database access, it seems that DataSource is always used--in other words, JNDI and DataSource always seem to be used together (in Servlets). I have not found a case where JNDI is used by itself to access the Database--perhaps I'm not looking in the right place. Could you point me to some documentation maybe?
    Thanks a lot!

  • How to use datasources to connect to database ?

    I have the following Problem
    I have two identical databases, one is the development database, the other one the production database.
    Now I need to find a way, how I can deploy an bc4j-application in local mode that way, that if the application is deployed to server 1 it connects to database 1 and if deployed to server 2 it connects to database 2.
    JDBC connection strings do not work as the connection is deployed with the application. So the application always connects to the same database.
    I thought datasources might be the solution. So I tried to define a datasource MyDS in the data-sources.xml file and specified it in the Configuration Wizard as the connection to use.
    But unfortunately this does not work and i do not know why:
    If I try to connect using the tester and using this datasource I get the following exception:
    Level #3: javax.naming.noInitialContextException
    Can anyone help me, what this means? How can I get around this using the BC4J Framework? Is there any "HowTo" Document which describes using datasources with BC4J?

    Frank,
    I've sorted this stuff out to some extent. Have a look at this thread:
    re:? How: multiple myAppWar.ear to use OC4J's data-sources.xml pooling?
    If this isn't all you need, then search on data-source.xml
    and read other threads also I may have posted helps on
    other threads so if you search on data-source.xml and my handle (curt504) it brings up all the threads that I posted to.
    Not to say I've solved all your problems, but I solved mine anyway. :)
    Good luck,
    curt

  • EBS datasource in WebLogic cluster using the EBS dbc file

    Hi All
    Please let me know if someone has successfully created EBS datasource in WebLogic cluster using the EBS dbc file.
    I have successfully created the datasource with one managed server but I am getting 'OAuth Mashaling Failure' error while adding the second managed server to this datasource.
    Thanks

    Thanks Hussein
    Here is the complete error:
    [wlst] Caused by: weblogic.common.ResourceException: weblogic.common.ResourceException: OAUTH marshaling failure
    [wlst] at weblogic.jdbc.common.internal.PooledConnectionEnvFactory.createResource(PooledConnectionEnvFactory.java:133)
    [wlst] at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1249)
    [wlst] at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1166)
    [wlst] at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:249)
    [wlst] at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1154)
    [wlst] at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:154)
    [wlst] at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:454)
    [wlst] at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:372)
    [wlst] at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:255)

  • Using Datasource in OC4J  to connect to 9iDb(ArrayIndexOutOfBoundsException

    Hi all,
    I've been encountering a certain ArrayIndexOutOfBoundsException when attempting to connect to Oracle 9i
    via a defined datasource.
    I've taken the following troubleshooting steps but to no avail:
    1. Verified username and password
    2. Verified URL by having a test class to establish a direct connection using this URL
    3. Verified that both classes12.jar and ocrs12.jar are defined in the classpath
    3. Updated classes12.jar and ocrs12.jar from the OTN to copies stipulated to be compliant with 9.2.0.1
    (this was based on a post on the net with reference to similar error messages:http://www.orafaq.net/msgboard/java/messages/1488.htm)
    It would be great if anyone could have some input on this problem.
    Thanks!
    WK
    My development environment:
    Oracle Database 9.2.0.1
    oc4j
    The following configuration and code snippets are provided for reference:
    data-sources.xml
         <data-source
              class="com.evermind.sql.DriverManagerDataSource"
              name="OraclePool"
              location="jdbc/OracleCoreDS"
              xa-location="jdbc/xa/OracleXADS"
              ejb-location="jdbc/OracleDS"
              connection-driver="oracle.jdbc.driver.OracleDriver"
              username="USER"
              password="PASSWORD"
              inactivity-timeout="30"
              url="jdbc:oracle:thin:@localhost:1521:OracleDb"
    />
    Client Code:
    InitialContext ic = new InitialContext();
    DataSource ds = (DataSource)ic.lookup("jdbc/OracleDS");
    Connection conn = ds.getConnection();
    Statement stmt = conn.createStatement();
    String strQuery = "SELECT id FROM TBL_PART";
    ResultSet rset = stmt.executeQuery (strQuery);
    Error:
    java.lang.ArrayIndexOutOfBoundsException
         at oracle.security.o3logon.C1.r(C1)
         at oracle.security.o3logon.C1.l(C1)
         at oracle.security.o3logon.C0.c(C0)
         at oracle.security.o3logon.O3LoginClientHelper.getEPasswd(O3LoginClientHelper)
         at oracle.jdbc.ttc7.O3log.<init>(O3log.java:290)
         at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:251)
         at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:252)
         at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:365)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
         at com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].sql.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:118)
         at com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].sql.DriverManagerConnectionPoolDataSource.getPooledConnection(DriverManagerConnectionPoolDataSource.java:24)
         at com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].sql.OrionPooledDataSource.getPooledConnection(OrionPooledDataSource.java:273)
         at com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].sql.PooledConnectionUsage.getPooledConnection(PooledConnectionUsage.java:21)
         at com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].sql.OrionPooledDataSource.getConnection(OrionPooledDataSource.java:145)
         at com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].sql.DriverManagerXADataSource.getAutoCommitConnection(DriverManagerXADataSource.java:226)
         at com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].sql.LogicalDriverManagerXAConnection.intercept(LogicalDriverManagerXAConnection.java:88)
         at com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].sql.FilterConnection.createStatement(FilterConnection.java:324)
         at com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].sql.FilterConnection.createStatement(FilterConnection.java:325)

    Hi WK,
    According to your stack trace, you are using a very old version of OC4J. I suggest updating to the latest, production version: 9.0.3
    Also, I seem to recall reading somewhere (I think it was in this forum), that "DataSource" is not serializable, and therefore cannot be transferred to the client.
    I use "DataSource" in my BMP entity beans to interact with the database -- this works fine. I have not tried getting a "DataSource" from a remote client, though.
    And also you may need to pass some "properties" to your "InitialContext" constructor -- depending on the type of client you are using (which I could not ascertain from your post).
    Hope this has helped you.
    Good Luck,
    Avi.

  • Help me understand JDBC connections using DataSource objects

    I'm writing a simple Java server application that accepts connections from multiple clients via RMI, connects to a SQL Server 2000 database via Microsoft's SQL 2000 JDBC driver, gets some data, and returns it to the client. The server application will handle every SQL database connection. However, it must be able to establish multiple simultaneous connections, since multiple clients may connect at the same time and request data.
    Sounds like a simple multi-threaded server that utilizes a connection pool for database connectivity, right? Well, if I want to do that, I have to register a PooledDataSource object with JNDI. My server threads that are handling requests will simply grab connections out of the pool to retrieve data (presumably).
    This seems like a fairly simple server application; however, all the information and tutorials I've read on using DataSource objects for database connections rather than DriverManager.getConnection() mention XML config files, J2EE application servers, Tomcat, WebSphere, etc. I really don't want to have to deal with all that just to get connection pooling and not have to use the DriverManager.getConnection() method.
    Is there a simple way to use DataSource objects without installing a lot of extra junk on my server?

    Thanks, diazlara. Your response was exactly what I needed to know. All the information I've read prior to this suggested that I had to have a J2EE server running, and that I had to register the DataSource object with JNDI. If you ladies and gents could take a quick look at this and let me know if I'm doing it correctly, I'd appreciate it.
    As proflux suggested, I wrote a connection manager:
    import java.sql.*;
    import javax.sql.*;
    import com.microsoft.jdbcx.sqlserver.*;
    public class SQLConnectionManager {
       private static ConnectionPoolDataSource connectionPool;
       // Initialize the connection manager
       public SQLConnectionManager() {
          init();
       // Retrieve a connection from the connection pool and return it
       public static Connection getConnection() {
          Connection connection = null;
          try {
             connection = connectionPool.getPooledConnection("myUsername", "myPassword").getConnection();
          catch (SQLException ex) {
             System.err.println("A problem occurred while getting a connection from the pool.");
             ex.printStackTrace();
          return connection;
       // Initialize the datasource and connection pool
       private static void init() {
          SQLServerDataSource mds = new SQLServerDataSource();
          mds.setDescription("MS SQLServerDataSource");
          mds.setServerName("127.0.0.1");
          mds.setPortNumber(1433);
          mds.setDatabaseName("SomeTable");
          mds.setSelectMethod("cursor");
          connectionPool = (ConnectionPoolDataSource) mds;
    }As you can see, I'm hard-coding the username and password for testing purposes. I'll incorporate a login/authentication system for any production code that I use this in.
    Once the SQLConnectionManager is created, connections can be retrieved as follows:
          Connection connection = null;
          try {
             connection = SQLConnectionManager.getConnection();
             System.out.println("** Got a SQL database connection from the pool");
             DatabaseMetaData metaData = connection.getMetaData();
             ResultSet rs = metaData.getCatalogs();
             while (rs.next()) {
                System.out.println("\tcatalog: " + rs.getString(1));
             rs.close();
             connection.close();
          catch (SQLException ex) {
             System.out.println("An exception occurred while connecting to the SQL Database:");
             ex.printStackTrace();
          }So, how does that look? I tested it out, and it seems to work just fine. Using this code, I am getting a connection from a pool, correct? I want to make sure of that. Also, are there any inherent weaknesses or flaws with this method that I need to be aware of?
    Thanks so much for all the helpful responses.

Maybe you are looking for

  • ITunes is unable to load provider date from synch service

    Hi can anyone help me with this problem, I have uninstalled ITunes and reinstalled and still comes up with "ITunes is unable to load provider date from synch service"  Hopefully some one can help me to get my iphone to synch. Michael

  • HP LaserJet P4515 Printer

    Hi ,      I am facing problem with the P4515 Printer . This Printer is attached to Postmate6 Pressure Sealer Output . The problem with the printer P4515 is that when given 200 printouts 15 pages are with papers . Suppose we give print-out one-by-one

  • FTP Adapter pickup the file meanwhile the file is transfering

    Hello, we have a follow problem: We transfer some big files manually in a ftp directory. If the adapter connect the directory concurrent as we transfer the file, he'll pick up the incomplete file and processed this. The problem is now, we get an erro

  • WGM and Airplay

    Hey, I have an ICT suite of 12 MacMinis, all with OSX 10.8.2 installed. The ICT room has an AppleTV connected to the projector so computers can project to the whiteboard without the need of trailing wires. I have the AppleTV Airplay function password

  • My HP Desjet 1050J410 crashes my word processors

    My HP Desjet 1050J410 crashes my word processers especially microsoft word 2007 and i can't print anything. i have downloaded lastest printer software from Hp but to no avail. i use XP SP 3. i can scan and make photo copies but crashes word processor