Deployment problem, jdbc drivers( SDM)

By seeing this document i am trying to deploy the jdbc jars.
Exchange Infrastructure How-to Guides for SAP NetWeaver 2004 [original link is broken]
i have created updated aii_af_jmsproviderlib.zip file as told in the pdf.
up to 9th step it is ok for me.
when i am choosing deployment tab in sdm. it has shown one pop-up window.
it is asking about the file name and file type. But i have the file type is aii_af_jmsproviderlib.zip.
   My question is how to get sda file from the .zip file. But in this snap-shot (pdf) he is able to get the sda file. please help me from this situation.
Regards,
Deviprasad.

Hi Deviprasad,
please follow this document for deployment of JDBC/JMS adapter:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
then you will have no problem in deployment of your JDBC/JMS adapter by SDM.
Thanks,
Rajeev Gupta
Message was edited by:
        RAJEEV GUPTA

Similar Messages

  • JDBC Drivers deployment in SAP PO system

    Hi Experts,
    Could any one provide information regarding deployment of JDBC drivers in SAP PO system. As I can see one of the option in NWA (Below is the screen snap) to deploy directly driver file in to SAP PO system. Is this is the way ?? If not please show some light on this.
    Regards,
    Anusha.

    Hi Anusha
    You can use SDA maker tool to build and include JDBC driver jar file in com.sap.aii.adapter.lib.sda file. You can also get this sda file by following the steps in SAP Note 1770304.
    Ensure that the jar file is compatible with SAP JVM used in your PI system.
    After you build the sda file, deploy it using telnet or SUM.
    regards
    AKD

  • JDBC drivers for SQL Server 2008 and PI7.0

    HI,
    I have deployed the JDBC drivers (sqljdbc.jar and sqljdbc4.jar) available for the SQL Server 2008 from the microsoft website as described in the how to document for deploying and configuring JDBC and JMS adapters.
    I am running a JDBC to FIle(XML) scenario. When I go and see on the RWB CC monitoring, I get this error
    Error during database connection to the database URL 'jdbc:sqlserver://hostname:1433;databaseName=123_Nagasatya' using the JDBC driver 'com.microsoft.sqlserver.jdbc.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:sqlserver://hostname:1433;databaseName=123_Nagasatya': UnsupportedClassVersionError: com/microsoft/sqlserver/jdbc/SQLServerDriver (Unsupported major.minor version 50.0)'
    WRT to the SQL server the port 1433  is open on the host and there is no firewall on the PI server as well as the SQL Server. Both are on different machines.Any help would be greatly appreciated.
    Regards.

    Hi Sujan,
    This is the link.
    [JDBC|http://www.microsoft.com/downloads/details.aspx?familyid=c47053eb-3b64-4794-950d-81e1ec91c1ba&displaylang=en]
                                          or
    You can also use the one on the market place.
    Go to http://service.sap.com/msplatforms -> SQL Server
    get zip-file sqljdbc_12_hotfix.zip contains the sqljdbc.jar file.
    It should work.
    Please let me know if you have any questions.
    Regards.

  • Error when using JDBC drivers

    Hi ..
    We have successfully deployed the JDBC drivers but in RWB(Communication channel monitoring) ,when executing we are getting an error
    Received XI System Error. ErrorCode: EXCHANGE_PROFILE_ACCESS ErrorText:   ErrorStack: Error while reading exchange profile for system PI7 and client 001
    2006-12-05 12:33:25 Error Transmitting the message to endpoint http://sap1:8001/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: EXCHANGE_PROFILE_ACCESS:.
    <b></b><i></i>
    Any suggestions
    Thanks
    Gopal
    Message was edited by:
            Gopal krishnan
    Message was edited by:
            Gopal krishnan

    Hi..
    I did it but here i am wondering becoz my RFC connection SAPSLDAPI works fine
    But at transaction SLDCHECK..it throws an error like
    Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call returned exception code     4
    => Check whether the SLD is running!
    Summary: Connection to SLD does not work
    => Check SLD function and configurations
    But the SLD URL pops up and opens wih put any error.in a same fashion,it happens in SXMB_ADM--> integration engine config.it says connections to SLD doesnot work
    any idea to verify
    Thanks
    Gopal

  • Deploy JDBC drivers - SAP PI 7.0

    Hi guys,
    I have to deploy JDBC drivers to implement JDBC adapter in SAP PI 7.0. I've found some guides for XI 3.0 or SAP PI 7.1 but not to SAP PI 7.0. Can I apply guide for XI 3.0 or another exists?
    Best regards,
    Pablo

    Hi,
    >>>I've found some guides for XI 3.0 or SAP PI 7.1 but not to SAP PI 7.0. Can I apply guide for XI 3.0 or another exists?
    the one for 3.0 works for 7.0
    Regards,
    Michal Krawczyk

  • Problem while deploying WD application thru SDM

    Hi friends ,facing problem while deploying webdynpro application on SDM.It takes much time deployment but for the past 1 or 2 day its not working properly ..i..e error is coming while deploying WD application................................................"Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.."
    If how know how to resolve this then waiting for ur response..
    Thanx in advance
    Hanif

    Hi Hanif,
    The SDM password should be reset if it is not the same as mentioned in your Filesystem Secure Store or vice versa.
    If you have changed your administrator password, kindly do change the same in secure store as well via the config tool.
    Use the Config Tool to change the entry in secure storage as follows:
    1. Start the Config Tool.
               (Go to  <drive>:\usr\sap\<SID>\<instance>\j2ee\configtool --> configtool.bat.)
    2. Select the secure store node.
               The configuration for the secure storage in the file system appears.
    3. Select the admin/password/<SID> entry.
    4. Enter the administrator user's new password in the "Value" field and choose "Add".
    5. Choose "File" --> "Apply" to save the data.
              Note: Contrary to the message that appears, you do not need to restart the server or cluster for this change to take effect.
    6. Finally restart SDM server.
    Regards,
    Anagha

  • Problem using production version of SQL Server 2005 JDBC drivers

    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    Sabrina
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

    SabrinaL wrote:
    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    SabrinaHi. Have you done all the XA-related install for the new MS driver? (put the XA
    dll in the DBMS environment etc)? Is your DBMS on a 32-bit machine or 64-bit machine?
    Does the driver present a dll for each of those? You can also get good JDBC help
    from MS via their microsoft.public.sqlserver.jdbcdriver newsgroup.
    Joe Weinstein at BEA
    >
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

  • Problems with jdbc drivers

    I'm having problems registering jdbc drivers. I've been trying to register the microsoft Sql Server 2000 jdbc driver so that I can create a connection in my code rather than using entity beans. I've set the CLASSPATH variable to point to the driver's .jar files in the install directory with no success.
    I've connected to the database using the driver via the IDE' s Runtime and it tests ok and allows me to create a database schema ok. (I had to copy the driver files to the sun/studio5u1_se/lib/ext dir to enable this) Is there a location I can unpack the drivers .jar files which will make the driver available?
    I have also tried setting the CLASSPATH variable to point to the above mentioned directory..but that didn't work either. Can anyone help?
    These are the exception messages that I get
    java.lang.ClassNotFoundException: com.pointbase.jdbc.jdbcUniversalDriver
    at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:141)
    at Portfolio.DriverTest.getConnection(DriverTest.java:43)
    at Portfolio.DriverTest.main(DriverTest.java:102)
    Error Trace in getConnection() : com.pointbase.jdbc.jdbcUniversalDriver

    If u type in command line
    java -classpath .;<directory containing the driver>
    it executes your class file properly
    note that <directory containing the driver> is the full path to your driver. I mean, the directory that contains your driver\drivername
    eg:
    java -classpath .;c:/driver/drivername
    don�t forget to put the "dot" before semicolon. If u forget it, java won�t find your class file. your class file must be at the directory you�re executing the command
    I need to configure my sun studo ent. to locate my jdbc driver for mySQL. I don�t know where this can be made. If any of you know. please report me

  • Oracle10g Jdbc Drivers issue with EJB on Weblogic 7

    Hi there,
    We are facing a critical issue on production environment related to Oracle jdbc drivers.
    We have a J2EE application with swing client. We are using MVC framework where client calls go to stateless session bean which redirect it to specific POJO which then uses Entity Beans for persistence.
    We have following environment.
    JDK1.4.2, Weblogic 7 with SP5, Oracle10g on AIX 5.2
    Now the problem is that we were using Oracle 8 jdbc driver classes12.zip for our application. Everything was working smoothly. Recently we moved our weblogic and oracle Servers machines locations, after that movement we started to get an exception when weblogic initializing connection pool that makes connection to a different oracle10g database. Oracle supports ask us to upgrade the jdbc driver. So we moved to 10g driver ojdbc14.jar but during testing one functionality is failing with a exception where rest of application seems to be working fine. The exception occurs when we try to post a record and during the creation of a child entity bean the transactions rollback for some unknown reasons. Using the old oracle8 classes12.zip driver the same code working fine again. We have also tried the classes12.zip driver of Oracle10g but error persist. I have checked the code and deployment descriptors but they seems fine. If i comment the creation of that particular entity bean the parent bean get created successfully and transaction commit successfully. Please also note that we have not created any relation b/w both entity beans not even in the database. They both are sort of independent.
    Can any one having any idea why Oracle10g driver not working or what might be the problem with our configuration. Any help will be highly appreciated. Please see the Exception below.
    <Jan 29, 2008 6:03:10 PM PKT> <Info> <EJB> <010036> <Exception from ejbStore: javax.ejb.NoSuchEntityException: Instance
    of bean 'SecurityRatingHistoryPost' with primary key 'com.cdc.fms.server.setup.security.ratinghistory.SecurityRatingHist
    oryEntityPK@93e447fa' not found.
    javax.ejb.NoSuchEntityException: Instance of bean 'SecurityRatingHistoryPost' with primary key 'com.cdc.fms.server.setup
    .security.ratinghistory.SecurityRatingHistoryEntityPK@93e447fa' not found.
    at com.cdc.fms.server.setup.security.ratinghistory.SecurityRatingHistoryEntityBean_7x4361__WebLogic_CMP_RDBMS.__
    WL_store(SecurityRatingHistoryEntityBean_7x4361__WebLogic_CMP_RDBMS.java:2208)
    at com.cdc.fms.server.setup.security.ratinghistory.SecurityRatingHistoryEntityBean_7x4361__WebLogic_CMP_RDBMS.ej
    bStore(SecurityRatingHistoryEntityBean_7x4361__WebLogic_CMP_RDBMS.java:2012)
    at weblogic.ejb20.manager.DBManager.storeBean(DBManager.java(Compiled Code))
    at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java(Compiled Code))
    at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java(Compiled Code))
    at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java(Compiled Code))
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion: sync=weblogic.ejb20.internal.TxManager
    $TxListener@44a824cd
    Instance of bean 'SecurityRatingHistoryPost' with primary key 'com.cdc.fms.server.setup.security.ratinghistory.SecurityR
    atingHistoryEntityPK@93e447fa' not found. - with nested exception:
    [javax.ejb.NoSuchEntityException: Instance of bean 'SecurityRatingHistoryPost' with primary key 'com.cdc.fms.server.setu
    p.security.ratinghistory.SecurityRatingHistoryEntityPK@93e447fa' not found.]
    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java(Compiled Code))
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java(Compiled Code))
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java(Compiled Code))
    at weblogic.ejb20.internal.BaseEJBLocalObject.postInvoke(BaseEJBLocalObject.java(Compiled Code))
    at com.cdc.fms.server.common.ConsolidatorSessionBean_fz4673_ELOImpl.processRequest(ConsolidatorSessionBean_fz467
    3_ELOImpl.java:57)
    at com.cdc.fms.server.common.GatewaySessionBean.processRequest(Unknown Source)
    at com.cdc.fms.server.common.GatewaySessionBean_oehtlw_EOImpl.processRequest(GatewaySessionBean_oehtlw_EOImpl.ja
    va:407)
    at com.cdc.fms.server.common.GatewaySessionBean_oehtlw_EOImpl_WLSkel.invoke(Unknown Source)
    <Jan 29, 2008 6:03:10 PM PKT> <Info> <EJB> <010051> <EJB Exception during invocation from home: com.cdc.fms.server.commo
    n.GatewaySessionBean_oehtlw_HomeImpl@3e13a4aa threw exception: javax.ejb.EJBException: nested exception is: weblogic.tra
    nsaction.RollbackException: Unexpected exception in beforeCompletion: sync=weblogic.ejb20.internal.TxManager$TxListener@
    44a824cd
    Instance of bean 'SecurityRatingHistoryPost' with primary key 'com.cdc.fms.server.setup.security.ratinghistory.SecurityR
    atingHistoryEntityPK@93e447fa' not found. - with nested exception:
    [javax.ejb.NoSuchEntityException: Instance of bean 'SecurityRatingHistoryPost' with primary key 'com.cdc.fms.server.setu
    p.security.ratinghistory.SecurityRatingHistoryEntityPK@93e447fa' not found.]
    javax.ejb.EJBException: nested exception is: weblogic.transaction.RollbackException: Unexpected exception in beforeCompl
    etion: sync=weblogic.ejb20.internal.TxManager$TxListener@44a824cd
    ##################################################################

    weblogic 7? when the current production version is 10.2?
    don't play yourself. fund a project to upgrade your weblogic version.
    can't tell based on what you've posted, and I fear that the stuff you'll have to post to get an answer here will be too much. this isn't a good place to come for an answer.
    %

  • JDBC drivers not working in QA for multibye characters

    Hi,
    we have a problem with JDBC and deployed in DEV system and its works fine, but the same when we deply in QA its not working.
    the problem we are trying to use the simple select query from ORACLE DB.
    In ORACLE DB they converted the chenise char to English after that our JDBC drivers are not able to pick the multibite char.
    XI JDBC Adapter shows below error with a SELECT Query
    SELECT Query:SELECT * FROM APPS.ITEM_XI_V The Chinese character are converted to English and becomes multibye characters.
    Error:Error during conversion of query result to XML: java.sql.SQLException: Fail to convert between UTF8 and UCS2: failUTF8Conv
    Assumption is that the issue with older version of  ojdbc14.zip (JDBC Driver file)
    Reference:http://www.coderanch.com/t/299231/JDBC/java/UTF-conversion
    implement SAP Note 941317 in order to resolve the current issue.
    Note 941317 - XI / PI JDBC Adapter: Known Problems / Incompatibilities JDBC Driver Deployment. Refer to  SAP Note 831162
    after apply as per note for DEV system its works fine, but the same when we did for our QA system still the same error.
    Thanks,
    Venkat.

    Hi Gurus,
    Any idea where i am doing wrong.. in QA i am able to extract data with simple select statment with normal tables...
    Thanks,
    Venkat

  • BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)

    Hello anybody,
    learnt XA being necessary if more than one sql command in transaction, so I changed
    my entries to the following:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    Name="OracleDB"
    Password="{3DES}iKOCmvzSc6g="
    Properties="user=osv"
    Targets="osvServer"
    TestConnectionsOnReserve="false"
    URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
    <JDBCTxDataSource
    JNDIName="JNDINameOracleOSV-DB"
    Name="OracleDataSource"
    PoolName="OracleDB"
    Targets="osvServer"/>
    We set up on a database ORACLE 8.3.2.
    Now, with the non-XA-driver there was no deployment problem, but now I receive the
    following error message on the server output:
    Unable to deploy EJB: CourseDateEJB from osv.jar:
    The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
    The error was:
    XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
    start() failed on resource 'OracleDB' Unexpected error during start for XAResource
    'OracleDB': null
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.deploy(Application.java:247)
         at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
         at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
         at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Many thanks if s.b. could help me.
    Klaus

    Hi Klaus,
    if you want to implement a global transaction over two different JDBC Resource Managers
    (update on both + 2PC) they have to be both XA compliant.
    Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
    for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
    and configuring a TXDataSource with "enable two-phase commit" = true (but only one
    non-XA JDBC driver at a time can participate in a distributed transaction).
    Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
    transactions or distributed transactions without XA drivers as well (using a single
    resource manager).
    But if you want to update multiple resource managers in the same transaction using
    EJBs, this is a "global" transaction, and WL server fully supports it.
    But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
    Sergi
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    >
    Hi Sergi, hello world,
    thanks a lot for this message. So the conclusion is that I hava no chance
    at all
    to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
    a prerequisite
    for EJB are XA-transactions.
    Is this conclusion correct.
    Many thanks again
    Klaus
    "Sergi Vaz" <[email protected]> wrote:
    Hi Klaus,
    distributed transaction (XA) features require version
    Oracle8i release 8.1.6 or later of the Oracle server.
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    Hi Sergi,
    1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
    2.) I didn´t use a special driver but that that was delivered with thewls
    server
    in the package "weblogic.jar".
    Could I enable you helping me with this information?
    Best wishes
    Klaus
    "Sergi Vaz" <[email protected]> wrote:
    Hi Klaus,
    which
    1) Oracle server version (I don't think it's a 8.3.2.)
    2) Oracle JDBC driver version
    are you you using ?
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    Hello anybody,
    learnt XA being necessary if more than one sql command in transaction,so
    I changed
    my entries to the following:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    Name="OracleDB"
    Password="{3DES}iKOCmvzSc6g="
    Properties="user=osv"
    Targets="osvServer"
    TestConnectionsOnReserve="false"
    URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
    <JDBCTxDataSource
    JNDIName="JNDINameOracleOSV-DB"
    Name="OracleDataSource"
    PoolName="OracleDB"
    Targets="osvServer"/>
    We set up on a database ORACLE 8.3.2.
    Now, with the non-XA-driver there was no deployment problem, but now
    I
    receive
    the
    following error message on the server output:
    Unable to deploy EJB: CourseDateEJB from osv.jar:
    The Container-Managed Persistence Entity EJB failed while creating itsSQL
    Type Map.
    The error was:
    XA error: XAER_RMERR : A resource manager error has occured in the transaction
    branch
    start() failed on resource 'OracleDB' Unexpected error during start
    for
    XAResource
    'OracleDB': null
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.deploy(Application.java:247)
         at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
         at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
         at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Many thanks if s.b. could help me.
    Klaus

  • OAS and using JDBC-drivers from EJB

    Hi.
    I have a problem with accessing the database from EJB-components
    deployed to OAS 4.0.8. The database is 8.1.5-version. I'm trying
    to use a connection exactly like it is documented in OAS-EJB-
    documents, the connection string looks like this:
    Connection conn = DriverManager.getConnection
    ("jdbc:oracle:jts8:@ora8i");
    And this is the error that above sentence it generates:
    "Sub Protocol must be specified in connection URL".
    The DAD(ora8i) is created in OAS.
    Now, I don't even know if this uses JDBC/OCI or thin since the
    documented connection-string doesn't contain that information. I
    quess it must use OCI-drivers, at least I should use them and
    they should be installed with OAS.
    So:
    * I should use only jts-enabled JDBC-drivers when developing EJB-
    components, is this right?
    * How can I connect to the database (from OAS 4.0.8 to Oracle
    8i), the string please?
    Thanks,
    [email protected]
    null

    Hi Suresh,
    There is lot of Documentation available on this, check these links
    http://help.sap.com/saphelp_nwce10/helpdata/en/45/07d2eeea3e0485e10000000a155369/frameset.htm
    http://help.sap.com/saphelp_nwce10/helpdata/en/45/08546ff5200486e10000000a155369/frameset.htm
    Venkat.

  • So hard to deploy a JDBC driver

    My PI7.1, I use the "netwaver Administrator" CM->Application Resources to deploy the jdbc driver of postgre, it told me the deploy is OK, but the "Status" of the driver is "Unknown".
    And when I try to invloke a channel which uses this postgre JDBC driver, it throws exceptions: can not find class org.postgresql.Driver
    What should I do !!!  I grep much time in the forum but did not find any clue yet

    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1138877
    FYI~~
    Summary
    Symptom
    This note describes the procedure for deploying 3rd party drivers on PI 7.1 using JSPM.
    Other terms
    JMS, JDBC, 3rd Party, Drivers, JSPM, com.sap.aii.adapter.lib, provider.
    Reason and Prerequisites
    When connecting to 3rd party software using JDBC and JMS adapters, external drivers need to be provided.
    These 3rd party drivers need to be bundled in com.sap.aii.adapter.lib.sda provided by the adapter engine installation.
    Prior to PI 7.1 this was done using the SDM tool, however, in PI 7.1 JSPM is used to deploy com.sap.aii.adapter.lib.sda.
    This note described the steps for deployment using JSPM.
    Solution
    For the JMS Driver only
    Prepare the JMS provider file as follows:
    1. Copy the external drivers from the provider directory to a separate directory.
    For example the SonicMQ driver file is called client.jar and is located in the lib subdirectory of SonicMQ installation directory.
    2. Open the driver file with a zip program and remove the standard JMS classes. These are located in directory javax/jms.
    3. Save the modified driver file.
    For the JDBC Driver and the JMS Driver
    Add the modified driver files to the lib directory of the archive com.sap.aii.adapter.lib.sda with the help of a zip program.
    Then to modify the provider.xml file in the server directory of the archive com.sap.aii.adapter.lib.sda, proceed as follows:
    1. Extract provider.xml using a zip program and edit it as follows:
    a. For each external driver file that needs to be bundled in com.sap.aii.adapter.lib.sda, add the line <jar-name>lib/driver-jar</jar-name> in the <jars> section.
    If you want to install the SAP DB JDBC driver and the SonicMQ JMS driver, this section looks like this:
    <jars>
    <jar-name>lib/sapdbc.jar</jar-name>
    <jar-name>lib/client.jar</jar-name>
    </jars>
    b. Return the changed provider.xml to the archive.
    Make sure that the original directory server\ is retained under Path in the zip archive.
    2. Add all external driver jars that you have defined in provider.xml to the lib directory in the archive com.sap.aii.adapter.lib.sda.
    3. Use the JSPM tool to deploy com.sap.aii.adapter.lib.sda.
    a. To start JSPM, run 'go' from the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/ directory.
    b. Log on with the AS Java username and password.
    c. Select 'HotFixes' option as the package type.
    d. Place the com.sap.aii.adapter.lib.sda in Inbox directory.
    This will be mentioned in the Select Package Type dialog.
    By default this is
    <HOST>\sapmnt\trans\EPS\in.
    e. Select Next.
    f. If no applicable development component(s) are found in the Inbox directory then:
    i. Check to see if the Inbox directory is correct and has the com.sap.aii.adapter.lib.sda.
    For more information on this refer to 'Detecting and Changing the JSPM Inbox Directory' section of the JSPM documentation.
    ii. JSPM does not allow to deploy an SCA/SDA with the same version (release, SP-level, patch-level) as an already deployed component.
    In such a case, the com.sap.aii.adapter.lib.sda will not be listed in the Specify Queue dialog box.
    To force the deployment of an such SCA/SDA ignoring version rule run the 'go' command as follows:
    go -config=/jspm/forceMode=true
    -config=/jspm/deployVersionRule=updateAll
    For more information on this please refer to SAP Note 1123333.
    f. Select the hot fixes to deploy. In this case sap.com/com.sap.aii.adapter.lib and press Next.
    g. For more information about deployment procedure, refer to JSPM documentation.
    FAQs
    Q1.   Where can I find JSPM documentation?
    Ans.  Link to the JSPM User Guide on SAP Help Portal:
    help.sap.com -> Documentation -> SAP NetWeaver -> SAP NetWeaver 7.0 (2004s) -> choose a language -> SAP Library -> SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> Solution Life Cycle Management by Key Capability -> Solution Life Cycle Management by Key Capability -> Software Life Cycle Management -> Software Maintenance -> Java Support Package Manager
    Q2.   Where can I find more information on JSPM?
    Ans.  Refer to SAP Note 891983
    Q3. I am unable to see any SCA/SDA in the Specify Queue dialog box.
    OR
    I get the message "No applicable development component(s) found in the Inbox directory"
    OR
    How do I force the deployment of a component ignoring version rules ?
    Ans. Refer to SAP Note 1123333.
    Q4. Where can I find more information on the JMS Adapter?
    Ans.Refer to SAP Note. 856346.
    Q5. Where can I find more information on the JDBC Adapter?
    Ans. Refer to SAP Note. 831162
    Q6. Which external driver files do I need to bundle in the com.sap.aii.adapter.lib.sda?
    Ans. Refer to JMS and JDBC Adapter notes mentioned above.
    Q7. What are some of the things that have changed with respect to the adapter lib from XI 30 to PI 7.1?
    Ans. The library name has changed from aii_af_jmsproviderlib.sda (releases 3.0/7.0) to com.sap.aii.adapter.lib.sda (release 7.1).
    The component name has changed from com.sap.aii.af.jmsproviderlib (releases 3.0/7.0) to com.sap.aii.adapter.lib (release 7.1).
    Even the directory structure has changed. The com.sap.aii.adapter.lib.sda (release 7.1) has a lib directory in which all the external drivers need to be placed.
    This was not present in aii_af_jmsproviderlib.sda (releases 3.0/7.0) and the external drivers were placed in the root directory of the archive
    Q8. Can I use the DriverTool (provided with XI 3.0) to bundle the jars in com.sap.aii.adapter.lib.sda?
    OR
    Is there a new DriverTool for bundling the external jars in com.sap.aii.adapter.lib.sda?
    Ans. No. Due to the changes mentioned above, the DriverTool provided with XI 3.0 cannot be used to bundle external drivers in com.sap.aii.adapter.lib.sda.
    No. There is no new tool for bundling the external jars in com.sap.aii.adapter.lib.sda. This needs to be done manually as described in the steps above.

  • JDBC Drivers Issue.

    Hi All,
    I am working on PI 7.0 with JDK version 1.4.2.12 for a File to JDBC scenario.
    Here our destination Database is Oracle 8.1.7
    Now while deploying the drivers for the JDBC drivers from the following Oracle site:
    http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
    we are having following Issues:
    1. The Drivers for the Oracle database i.e availaible on the Oracle site for Oracle 8.1.7 supports only JDK version 1.2 and 1.3. So is it advisable to use these drivers?
    2. If we use any higher version of driver say 10.2.0.1.0 (Currently we are using the same) that supports the JDK version 1.4 will it be downward compatible to Oracle 8.1.7 ?
    3. Can we have two different JDK versions for the same XI servers ? Here I mean to say that can we have JDK 1.2 as well as JDK 1.4 for same XI server and if so please share the proper procedure.
    Actually all these issues arised because we are using JDBC driver 10.2.0.1.0 but we are getting problems as below:
    After every sometime say around an hour the XI server restarts automatically, but JDBC adapter services stop and do not start with the start of XI server, we have to start the services manually. So here we are considering that there could be some problem with the JDBC drivers.
    Plz provide your valuable information in these issues.
    Regards,
    Rookie.

    1. The Drivers for the Oracle database i.e availaible on the Oracle site for Oracle 8.1.7 supports only JDK version 1.2 and 1.3. So is it advisable to use these drivers?
    *If you use Oracle8.1.7 You should have Classes12.jar driver in visual admin *
    JDBC Driver: oracle.jdbc.driver.OracleDriver
    Connection: jdbc:oracle:thin:@<server IP>:<port>:<DataSource name>
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bdd6a690-0201-0010-238a-9c95a5fb6f6c
    2. If we use any higher version of driver say 10.2.0.1.0 (Currently we are using the same) that supports the JDK version 1.4 will it be downward compatible to Oracle 8.1.7 ?
    You should have OJDBC14.jar driver in visual admin if you use Oracle 10
    JDBC Driver: oracle.jdbc.driver.OracleDriver
    Connection: jdbc:oracle:thin:@<server IP>:<port>:<DataSource name>
    3. Can we have two different JDK versions for the same XI servers ? Here I mean to say that can we have JDK 1.2 as well as JDK 1.4 for same XI server and if so please share the proper procedure
    No you should have only one JDK version for same XI server.
    Also check bhavesh reply
    Re: Different Version Oracle in a SLD

  • Error while Deploying JAR file using SDM in EP system

    Hi,
    As per below mention URL for Installing and Deploying the Enrichment Controller ,I am confuguring MDM Enrichment Controller in EP system
    http://help.sap.com/saphelp_nwmdm71/helpdata/en/44/aa411ce9d57454e10000000a11466f/frameset.htm
    So, as per the Help in Step 7, its mention to deploy a specific adapter for the external enrichment service provider i.e JAR file.
    And when i am trying to deploy the *.jar file , i am getting this message in SDM:
    Summary:
    ========
      There were 1 archives selected.
      0 archives successfully loaded.
       Loading of 1 archives failed.
    Details:
    ========
    1) Error loading archive
        C:\Documents and Settings\<SDMUserID>.<EPsystemHostName>\Desktop\Adapter\MDMEnrichmentAdapter.jar
        (server side name is: C:\usr\sap\SID\JC00\SDM\program\temp\MDMEnrichmentAdapter.jar)
        com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component found in the manifest is either missing or incomplete!
    Manifest attributes are missing or have badly formatted value:
    there is no deployment descriptor declared
    (C:\usr\sap\SID\JC00\SDM\program\temp\MDMEnrichmentAdapter.jar)
    So, kindly guide me how to deploy this jar file on EP syetm or if any settings is required.
    Regards;
    Hanif
    Edited by: Shaikh Hanif on Nov 22, 2010 2:47 PM

    Hanif,
    Check this wiki's,
    http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P29
    http://wiki.sdn.sap.com/wiki/display/JSTSG/(GP)CannotDeployGPContent-WrongManifestFileAttributes
    Good Luck!
    Sandeep Tudumu

Maybe you are looking for

  • Trying to save a PDF. file as individual pages?

    I need to save only three sheets from a PDF. file so I can send it in a email.  I have no idea how to do that. You can print just one page but you can't save only that one page. PLEASE HELP!!   THANKS

  • Global temp table trigger error on Oracle AS

    we have a set of triggers that load a temp table in the before delete,update and process the table in an after statement trigger. the data that's loaded is a complaintid and when the complaintid is selected into a variable in the after statement, a N

  • Incoming fax storage on HP laserjet 1536dnf MFP

    I can't find where my incoming faxes are being stored on my computer.  I have set the faxes to be sent to computer, but I don't know where they are.

  • Want to make in app purchase

    A friend gave me her daughter's iPad and her Apple ID password. I downloaded a few free apps and want to make an in app purchase now. I signed out of her account, signed in with mine and tried it. Said the app was 'bought' with another Apple ID. So I

  • Freight forwarder in Proforma Invoice

    Hi All, In Proforma Invoice, the freight forwarder name does not appear.  Can someone tell me how to fix this issue? Thks.