WSAD 5.1 & WSCallbackHandler - Websphere

This is a discussion on WSAD 5.1 & WSCallbackHandler - Websphere ; We are in the process of upgrading from WSAD 5.0(2?) to WSAD 5.1 We are running some batch applications on the server. These have to pass along authentication information to the server and the system that was setup worked fine ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: WSAD 5.1 & WSCallbackHandler

  1. WSAD 5.1 & WSCallbackHandler

    We are in the process of upgrading from WSAD 5.0(2?) to WSAD 5.1

    We are running some batch applications on the server. These have to pass
    along authentication information to the server and the system that was
    setup worked fine in WSAD 5.0 but failes in 5.1

    It will not compile and gives the following errors in the task list:

    Error The import com.ibm.websphere.security.auth.callback cannot be
    resolved

    and also:

    Error WSCallbackHandlerImpl cannot be resolved or is not a type

    It turns out that the package/class in 5.0 was in wssec.jar In 5.1 the
    package/class DOES NOT EXIST.

    So what changed between the two versions? Is there a different way to do
    this?

    The line in question is this:

    try {
    lc = new LoginContext("ClientContainer",new
    WSCallbackHandlerImpl(parms[0],"usnt",parms[1]));
    }
    catch (LoginException le) {

    etc.

    Thanks,

    - Bret

  2. AS400 from WSAD5.1.1

    Hi All,
    Can i talk to AS400 databse using WSAD5.1.1 (i need to talk to the
    databse using datasource object is that possible).

    when i connect i get the following exception
    [19/02/04 10:58:31:781 NZDT] 410deafe ExceptionUtil E CNTR0020E:
    Non-application exception occurred while processing method "x" on bean
    "BeanId(SampleApp#SampleData.jar#DataReader, null)". Exception data:
    COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0612E Invalid
    parameter number. SQLSTATE=S1093
    at
    COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throwPa ramIndexError(Unknown
    Source)
    at COM.ibm.db2.jdbc.app.DB2PreparedStatement.setObjec t(Unknown Source)
    at COM.ibm.db2.jdbc.app.DB2PreparedStatement.setObjec t(Unknown Source)
    at
    com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement. setObject(WSJdbcPreparedStatement.java:1066)
    at
    com.olasme.framework.sql.intercept.PreparedStateme ntInterceptor.setObject(PreparedStatementIntercept or.java:373)
    at
    com.olasme.framework.sql.SimpleStatement.statement Set(SimpleStatement.java:152)
    at
    com.olasme.framework.sql.SimpleStatement.prepareQu alifier(SimpleStatement.java:222)
    at
    com.olasme.framework.sql.SelectStatement.prepareSt atement(SelectStatement.java:185)
    at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerD elegate.java:455)
    at com.ibm.rmi.iiop.ORB.process(ORB.java:402)
    at com.ibm.CORBA.iiop.ORB.process(ORB.java:1685)
    at com.ibm.rmi.iiop.Connection.doWork(Connection.java :2173)
    at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl. java:64)
    at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.ja va:95)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:593)
    com.olasme.framework.research.WorkerSystemExceptio n: Cannot prepare
    statement (null); nested exception is: COM.ibm.db2.jdbc.DB2Exception:
    [IBM][JDBC Driver] CLI0612E Invalid parameter number. SQLSTATE=S1093
    at
    com.olasme.data.manager.ejb.DataReaderBean.findByI d(DataReaderBean.java:80)
    at
    com.olasme.data.manager.ejb.EJSRemoteStatelessData Reader_c2be3553.findById(EJSRemoteStatelessDataRea der_c2be3553.java:22)
    at
    com.olasme.data.manager.ejb._EJSRemoteStatelessDat aReader_c2be3553_Tie.findById(_EJSRemoteStatelessD ataReader_c2be3553_Tie.java:192)
    at
    com.olasme.data.manager.ejb._EJSRemoteStatelessDat aReader_c2be3553_Tie._invoke(_EJSRemoteStatelessDa taReader_c2be3553_Tie.java:88)
    at
    com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHa ndler(ServerDelegate.java:602)
    at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerD elegate.java:455)
    at com.ibm.rmi.iiop.ORB.process(ORB.java:402)
    at com.ibm.CORBA.iiop.ORB.process(ORB.java:1685)
    at com.ibm.rmi.iiop.Connection.doWork(Connection.java :2173)
    at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl. java:64)
    at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.ja va:95)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:593)

    Any Help would be appreciated Much

    Thnx
    Sudhakar


  3. Re: AS400 from WSAD5.1.1

    Sudhakar wrote:
    > Hi All,
    > Can i talk to AS400 databse using WSAD5.1.1 (i need to talk to the
    > databse using datasource object is that possible).
    >
    > when i connect i get the following exception
    > [19/02/04 10:58:31:781 NZDT] 410deafe ExceptionUtil E CNTR0020E:
    > Non-application exception occurred while processing method "x" on bean
    > "BeanId(SampleApp#SampleData.jar#DataReader, null)". Exception data:
    > COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0612E Invalid
    > parameter number. SQLSTATE=S1093
    > at
    > COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throwPa ramIndexError(Unknown


    > Any Help would be appreciated Much
    >
    > Thnx
    > Sudhakar
    >


    Check the DB2 for AS400 docs - it takes a different driver on the Java
    side than the other DB2's.

    Ken


  4. Re: AS400 from WSAD5.1.1

    Hi Ken,
    I'm Using WSAD5.1.1 on Windows 2000 and using DB2Connect Enterprise
    Editon with DB2 Workgroup Server Unlimited Edition to look up AS400
    database. The driver class i use is

    "COM.ibm.db2.jdbc.DB2XADataSource"

    Any Help
    Sudhakar

    Ken Hygh wrote:

    > Sudhakar wrote:
    >
    > > Hi All,
    > > Can i talk to AS400 databse using WSAD5.1.1 (i need to talk to the
    > > databse using datasource object is that possible).
    > >
    > > when i connect i get the following exception
    > > [19/02/04 10:58:31:781 NZDT] 410deafe ExceptionUtil E CNTR0020E:
    > > Non-application exception occurred while processing method "x" on bean
    > > "BeanId(SampleApp#SampleData.jar#DataReader, null)". Exception data:
    > > COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0612E Invalid
    > > parameter number. SQLSTATE=S1093
    > > at
    > > COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throwPa ramIndexError(Unknown

    >
    >
    > > Any Help would be appreciated Much
    > >
    > > Thnx
    > > Sudhakar
    > >

    >
    > Check the DB2 for AS400 docs - it takes a different driver on the Java
    > side than the other DB2's.
    >
    > Ken
    >



  5. Re: AS400 from WSAD5.1.1

    Sudhakar wrote:
    > Hi Ken,
    > I'm Using WSAD5.1.1 on Windows 2000 and using DB2Connect Enterprise
    > Editon with DB2 Workgroup Server Unlimited Edition to look up AS400
    > database. The driver class i use is
    >
    > "COM.ibm.db2.jdbc.DB2XADataSource"
    >
    > Any Help
    > Sudhakar
    >
    > Ken Hygh wrote:
    >


    No, sorry - I don't have an AS400 anywhere near me. Maybe someone else
    can help...

    Ken


  6. Re: AS400 from WSAD5.1.1

    About 18 months ago, the driver to use for the AS/400 database was part of
    the "AS/400 toolkit", and not the normal DB2 driver. Things may have
    changed since then. If not, you want to search the IBM i-Series server
    web site for the toolkit. It will point you at an open source project
    whose name I forget. (18 months is a long time in WebSphere!)

+ Reply to Thread