Skip to Content
avatar image
Former Member

JDBC driver deployment in J2EE 7.10 SP1

At attempt of installation additional JDBC the driver on J2EE version 7.10 SP1, occurs incorrect installation.

1. JDBC JAR localtion is incorrect

2. JDBC driver in status 'Unknown'

I try to deploy JAR with NWA and telnet.

Any comment's? Can somebody give me any solution to fix that bug?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    avatar image
    Former Member
    Jun 19, 2007 at 05:38 PM

    Hello everybody,

    I'm facing the (probably) same problem trying to install an additional driver and datasource on 7.05 SP0. So here is some more detailed information:

    1. Deployed driver via telnet with the following results:

    - driver is shown in nwa but status is ‘unknown’

    - Filename in nwa points to: C:\usr\sap\CE1\J01\j2ee\cluster\server0\.\temp\dbpool\_MyOJDBC\ojdbc.jar but the archive actually is located at C:\usr\sap\CE1\J01\j2ee\cluster\bin\ext\MyOJDBC\ ojdbc.jar

    2. Deployed DataSource via telnet with result: MyTestDataSource is shown in nwa with status ‘fully available’

    So for so good. But after restarting the instance the DataSource is shown with status ‘Not available’!?

    Here’s what server_00.0.log says:

    #1.5 #0019B9125D7B00100000000200000AEC02A9303D899F2F71#1182273949460#/System/Server##com.sap.engine.services.telnet.core.TelnetProxy.run()#Administrator#33####2eb97f501e8311dc86e60019b9125d7b#Application [13]##0#0#Info#1#com.sap.engine.services.telnet.core.TelnetProxy#Java###User connected.#1#Administrator#

    #1.5 #0019B9125D7B001A0000000000000AECFFFFFFFFFFFFFFFF#1182274040835#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###The session id 113 is associated with correlator id -1. Use this correlator id to filter the trace and log messages.#

    #1.5 #0019B9125D7B001A0000000100000AECFFFFFFFFFFFFFFFF#1182274040835#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###++++++++++++++ Starting deployment ++++++++++++++#

    #1.5 #0019B9125D7B001A0000000200000AECFFFFFFFFFFFFFFFF#1182274040835#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Archives specified for deployment are: #

    #1.5 #0019B9125D7B001A0000000300000AECFFFFFFFFFFFFFFFF#1182274040835#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###C:
    usr
    sap
    CE1
    J01
    j2ee
    cluster
    server0
    temp
    dbpool
    MyTestDataSource.xml.sda#

    #1.5 #0019B9125D7B001A0000000400000AECFFFFFFFFFFFFFFFF#1182274040835#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Start loading archives ...#

    #1.5 #0019B9125D7B001A0000000500000AECFFFFFFFFFFFFFFFF#1182274040851#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Archives are loaded.#

    #1.5 #0019B9125D7B001A0000000600000AECFFFFFFFFFFFFFFFF#1182274040851#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Error Handling Action: 'UndeploymentAction', Error Handling Strategy: 'OnErrorStop'.

    Error Handling Action: 'DeploymentAction', Error Handling Strategy: 'OnErrorStop'.

    Error Handling Action: 'PrerequisitesCheckAction', Error Handling Strategy: 'OnErrorStop'.

    Version Handling Rule: 'UpdateAllVersions'.

    Deployment Strategy: 'normal deploy strategy'.

    Life Cycle Deployment Strategy: 'bulk deploy strategy'.

    There are no batch filters specified.#

    #1.5 #0019B9125D7B001A0000000700000AECFFFFFFFFFFFFFFFF#1182274040866#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Warning#1#com.sap.engine.services.deploy#Plain###Property for application name is not specified. Setting display name from application.xml as application name.#

    #1.5 #0019B9125D7B001A0000000900000AECFFFFFFFFFFFFFFFF#1182274040866#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Warning#1#com.sap.engine.services.deploy#Plain###Property for provider name is not specified#

    #1.5 #0019B9125D7B001A0000000B00000AECFFFFFFFFFFFFFFFF#1182274040882#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.deploy#Plain###BcaClassFinder.addResources Can not open zip fileC:
    usr
    sap
    CE1
    J01
    j2ee
    cluster
    server0
    temp
    deploy
    work
    deploying
    MyTestDataSource.xml.sda1182274040851
    MyTestDataSource.xml it is not a valid zip archive#

    #1.5 #0019B9125D7B001A0000000C00000AECFFFFFFFFFFFFFFFF#1182274040882#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###The batch for session id 113 will be executed with normal parallelism strategy.#

    #1.5 #0019B9125D7B001A0000000D00000AECFFFFFFFFFFFFFFFF#1182274040913#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.deploy#Plain###BcaClassFinder.addResources Can not open zip fileC:
    usr
    sap
    CE1
    J01
    j2ee
    cluster
    server0
    temp
    deploy
    work
    deploying
    MyTestDataSource.xml.sda1182274040882
    MyTestDataSource.xml it is not a valid zip archive#

    #1.5 #0019B9125D7B001A0000000E00000AECFFFFFFFFFFFFFFFF#1182274041179#/System/Server/Configuration##com.sap.engine.core.configuration#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Warning#1#com.sap.engine.core.configuration#Plain###ValueEntry: trim performed on ConfigEntry: \#~comp_elem#

    #1.5 #0019B9125D7B001A0000001300000AECFFFFFFFFFFFFFFFF#1182274041991#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Deployment has finished with result: The status of the deployed SDUs is Success.

    Additional information:

    #

    #1.5 #0019B9125D7B001A0000001400000AECFFFFFFFFFFFFFFFF#1182274041991#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Unlocking the Deploy.#

    #1.5 #0019B9125D7B001A0000001500000AECFFFFFFFFFFFFFFFF#1182274041991#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#33####55d0f5301e8a11dcc5a00019b9125d7b#1 Telnet unknown Tue Jun 19 19:25:49 CEST 2007##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Deployment has finished#

    And finally my data-source.xml:

    <?xml version="1.0" encoding="utf-8"?>

    <!DOCTYPE data-sources SYSTEM 'data-sources.dtd'>

    <data-sources>

    <data-source>

    <data-source-name>MyTestDataSource</data-source-name>

    <driver-name>MyOJDBC</driver-name>

    <init-connections>1</init-connections>

    <max-connections>10</max-connections>

    <max-time-to-wait-connection>60</max-time-to-wait-connection>

    <expiration-control>

    <connection-lifetime>600</connection-lifetime>

    <run-cleanup-thread>60</run-cleanup-thread>

    </expiration-control>

    <sql-engine>vendor_sql</sql-engine>

    <jdbc-1.x>

    <driver-class-name>oracle.jdbc.driver.OracleDriver</driver-class-name>

    jdbc:oracle:thin:@ xxxx.xxxx.xxxx.com:1528:YYYYY

    <user-name>xxxxx</user-name>

    <password>xxxxx</password>

    </jdbc-1.x>

    </data-source>

    </data-sources>

    Any ideas?

    Best regards,

    Helge

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 28, 2007 at 10:07 AM

    I am also experiencing the same issue.

    I have tried to locate the config that points to the temporary location so I could correct it manually, but I have been unable to find this in the database tables or the file system.

    However, if I create a datsource based on the driver installation it will actually work and show as "Fully Available" until the server is restarted when it becomes "Not available"

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 26, 2007 at 11:38 AM

    Hi friends,

    This is just a visualization problem and will be fixed in next releases.

    After deployment driver is available and can be used for DataSource creation.

    After restart also drivers and DataSources are usable but their status is unknown for the UI. You can use them without any problems.

    Best regards,

    Nikolai.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 12, 2007 at 07:08 AM

    Hi Dedevich,

    unfortunately I can not give a solution - but a comment: Although the wrong driver location and the status 'unknown' are displayed, the driver (in our case) can be used by our CustomDataSource.

    Regards,

    Helge

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 02, 2009 at 10:40 PM

    == 7.10 and later ==

    If you have trouble to follow the following instructions use mc. with mc you can handle the archive like a normal directory. or you can unzip the archive and zip it again when you are finished adding your jdbc drivers.

    1. get com.sap.aii.adapter.lib.sda. you find it in directory DATA_UNITS\JAVA_J2EE_OSINDEP_J2EE_INST on your SAP NetWeaver 7.10 PI Java installation DVD.

    2. add your jdbc driver to directory lib in this archive

    3. edit server/provider.xml in this archive

    <?xml version="1.0"?>
     <provider-descriptor>
      <display-name>XPI Adapter Library</display-name>
      <component-name>com.sap.aii.adapter.lib</component-name>
      <provider-name>sap.com</provider-name>
      <references>
        <reference type="library" strength="strong" provider-name="sap.com">engine.j2ee14.facade</reference>
      </references>
      <jars>
        <jar-name>lib/com.sap.aii.adapter.lib_api.jar</font></jar-name>
        <jar-name>lib/mysql-connector-java-5.1.10-bin.jar</jar-name>
      </jars>
     </provider-descriptor>

    4. copy your archive com.sap.aii.adapter.lib.sda to /usr/sap/trans/EPS/in

    5. Deploy the archive with JSPM<br>

    ./go "-config=/jspm/forceMode=true" "-config=/jspm/deployVersionRule=updateAll"

    choose hotfix

    example for mysql

    jdbc archive: mysql-connector-java-5.1.10-bin.jar

    JDBC Driver: com.mysql.jdbc.Driver

    connection String: jdbc:mysql://<hostname>:<DB-Port (Default:3306)>/<Datenbank Name>

    Edited by: Andreas Oelkers on Oct 3, 2009 12:42 AM

    Add comment
    10|10000 characters needed characters exceeded