Skip to Content

Hi folks,

 

I’d like to share with you steps that you may use in your test ME system in case you need to redeploy VMJDBC driver:

 

  1. Login to NW textconsole.
  2. Run command “add dbpool” – this will add more commands to console.
  3. Run command “REMOVE_DATA_SOURCE VMJDBC”. If NW says it cannot remove driver because it is not deployed – it is OK
  4. Run command “DEPLOY_JDBC_DRIVER VMJDBC <PATH TO SQLJDBC.jar>/sqljdbcX.jar” [the name\version of the file must be according to the installation guide]
  5. After it is deployed restart NW.
  6. Go to NWA.
  7. Open Configuration Management.
  8. Open Infrastructure.
  9. Open Application Resources.
  10. Find “VMJDBC” record and select it.
  11. Look at Settings parameter “Filename” – it should end with “sqljdbcX.jar” [should end with the name of the file from step 4]

 

In case of production system, please, follow strictly the installation guide, upgrade guide and correction Notes. Do not play with your production as I do sometimes with my test system 🙂

 

Br, Alex.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Sergiy Katerinich

    The simplest way to renew the existing VMJDBC driver of SAP ME is as follows:

    1. stop me~ear application and wait until all SAP ME related applications are stopped (if they are running, the system will not let you delete the driver);
    2. in Application Resources, search for “VMJDBC” and check JDBC DataSource tab if any of resources using the driver has green status.
    3. if all resources are grey or red, then click “Delete Selected Resource” button for the driver;
    4. create the driver again following the instructions from SAP ME Component Installation guide.
    (0) 
    1. Tim Drury

      Sergiy: true, however just yesterday I was trying to switch my VMJDBC from Oracle to SQL Server.  I undeployed ME, MECTC, etc.  I undeployed all db pools.  Restarted the Java instance.  I could _not_ delete the VMJDBC entry and it was pointing to a non-existent Oracle driver jar.  Following Alex’s steps solved the issue.

      (0) 

Leave a Reply