IS 6.1 build 132: 2005-02-28 12:29:06 CET [ISS.0096.0001C] J


How can I find out what caused the issue?

2005-02-28 12:29:06 CET [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ProcessAudit functional alias, check configuration.?

I’m going to configure webMethods IS 6.1 to use MySQL server with MySQL Connector/J driver (mysql-connector-java-3.1.7-bin.jar), but it looks IS doesn’t like it.


Hi Jacek,

Unfortunately MySQL is not one of the database that we support for the platform pools - specifically for the ProcessAudit. Refer to the install guide that accompanies the installation - PlatformInstallGuide.pdf, Chapter 3, Software requirements.

The supported database vendors for the various components defined in the resource pools are:

  • Oracle
  • SQL Server 2000
  • DB2


I do know that MySQL is not on the list of the supported DBs, but the point is whether it’s possible to run it at all or not. Does it mean that having the JDBC compliant driver isn’t enough to run it in IS?

I can’t understand the error message I’m getting while trying to run MySQL as the database for ProcessAudit:

java.sql.SQLException: Cannot load connection class because of underlying exception: ‘java.lang.SecurityException: Prohibited package name: java.sql’.
at com.mysql.jdbc.NonRegisteringDriver.connect(
at java.sql.DriverManager.getConnection(
at java.sql.DriverManager.getConnection(
at wm.server.jdbcpool.testPool(
at java.lang.reflect.Method.invoke(Native Method)
at com.wm.util.template.Reporter.invoke(
at com.wm.util.template.InvokeToken.eval(
at com.wm.util.template.TemplateToken.evalChild(TemplateToken.wm.server.jdbcpool:testPool

but hey, it looks the error was generated by the MySQL driver nor IS.

It looks as if the game were not over :wink:

And the reason of the previous troubles has finally been found and sorted out. Hurraay!

webMethods 6.1 build 132 seems to work with MySQL 4.1.10 via MySQL Connector/J 3.1.7.

The reason was the JVM version IS used and the database URL (but I think it’s less important).

Now, the issue is with the tables that WmPRT package expects in the database. It however should be much easier as I guess it’s documented somewhere what tables to create depending on a database type - Oracle, DB2 or MS SQL Server.

IS_HOME is the home directory of Integration Server
WM_HOME is the home directory of WebMethods 6.x (that’s where IS_HOME, Broker, Modeler and some other directories are)

Here’s what I did to get MySQL running. What I mean saying ‘running’ is that it’s now possible to test the MySQL pool in the JDBC Pools panel. It at least gives me: “Test of ProcessAudit successful”.

%IS_HOME%\config\jdbc\driver\MySQL.xml is as follows:

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

    MySQL Connector/J 3.1.7

%IS_HOME%\config\jdbc\pool\MySQLPool.xml looks like this:

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

    commented out due to security reasons
    MySQL Pool

The MySQL JDBC driver is applied to IS CLASSPATH in %IS_HOME%\bin\server.bat:

set APPENDCLASSES=C:\apps\mysql-connector-java\mysql-connector-java-3.1.7-bin.jar

And the most important point is that IS has to be running with Java 1.4. Otherwise java.sql.Savepoint class won’t be found - it’s not available in 1.3 which is the IS default JVM version.

So, instead of running IS with the default JVM (it’s in %IS_HOME%\jvm):

java version “1.3.1”
Java™ 2 Runtime Environment, Standard Edition (build 1.3.1)
Classic VM (build 1.3.1, J2RE 1.3.1 IBM Windows 32 build cn131-20021107 (JIT enabled: jitc))

IS should be run with that one (it’s in %WM_HOME%\jvm\win142):

java version “1.4.2”
Java™ 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot™ Client VM (build 1.4.2-b28, mixed mode)

In order to do it, %IS_HOME%\bin\server.bat (on MS Windows) has to be changed:

rem SET JAVA_DIR=C:\apps\webMethods6\IntegrationServer\jvm
SET JAVA_DIR=C:\apps\webMethods6\jvm\win142

Start up IS and have fun! :slight_smile:

Going to create the tables for WmPRT…

In order to create the tables for WmPRT one needs to run the scripts:

  • create_processaudit_6-1-5_Oracle.sql
  • create_prt_6-1_Oracle.sql

with the following changes:

  • Replace VARCHAR2 to VARCHAR
  • Add the size of the column in some indexes

The scripts are in %WM_HOME%\common\db\scripts\create

Having done this, WmPRT doesn’t complain at startup anymore (but it doesn’t certainly mean that everything is fine).