IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  MWS instance doesnt start

    Posted Tue December 16, 2008 07:19 AM

    Hi All ,
    Stuck with this error while trying to start new MyWebmethods Server(7.1.1) instance.
    java.io.IOException: [wm-cjdbc36-0039][SQLServer JDBC Driver][SQLServer]Invalid
    object name ‘MWS_CONFIG’.

    All steps mentioned at WM Install guide(Pg83 - pg95) and MWS Admin Guide (Pg43 - pg50) were carefully read and implemented and Database Component Configurator used for creating and connecting to the database,but the MWS server instance doesnt start.
    It seems MWS_CONFIG is a table but it is not being created for some reason.
    Several new instances were created and MWS uninstalled and reinstalled but the problem persists

    Environment: WM 7.1.1
    Database : Sql Server 2005
    Could someone please help us with this.
    Thanks & Best Wishes


    #MWS-CAF-Task-Engine
    #webMethods-BPMS
    #webMethods


  • 2.  RE: MWS instance doesnt start

    Posted Tue December 16, 2008 07:23 AM

    Log of error message :

    C:\webMethods7\MWS\bin>mws -s w6 run
    JAVA_HOME: C:\webMethods7\jvm\win150
    MWS_HOME: C:\webMethods7\MWS
    No registered exception delegate
    java.io.IOException: [wm-cjdbc36-0039][SQLServer JDBC Driver][SQLServer]Invalid
    object name ‘MWS_CONFIG’.
    at com.webMethods.rtl.locator.DBConfigLocator.getLocationStream(DBConfig
    Locator.java:58)
    at com.webMethods.rtl.locator.ClusterConfigLocator.getLocationStream(Clu
    sterConfigLocator.java:59)
    at com.webMethods.rtl.locator.StreamLocatorFactory.getLocationStream(Str
    eamLocatorFactory.java:110)
    at com.webMethods.rtl.util.FileUtil.getInputStream(FileUtil.java:199)
    at com.webMethods.rtl.util.FileUtil.loadPropertiesFile(FileUtil.java:422
    )
    at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.loadSyste
    mProps(DefaultPhaseProvider.java:212)
    at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initializ
    ePhases(DefaultPhaseProvider.java:70)
    at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializ
    ePhases(ClusterPhaseProvider.java:27)
    at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:868)
    at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:827)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.webMethods.portal.system.start.Main.start(Main.java:131)
    at com.webMethods.portal.system.start.Main.main(Main.java:48)
    —> Nested exception
    java.io.IOException: [wm-cjdbc36-0039][SQLServer JDBC Driver][SQLServer]Invalid
    object name ‘MWS_CONFIG’.
    at com.webMethods.rtl.locator.DBConfigLocator.getLocationStream(DBConfig
    Locator.java:58)
    at com.webMethods.rtl.locator.ClusterConfigLocator.getLocationStream(Clu
    sterConfigLocator.java:59)
    at com.webMethods.rtl.locator.StreamLocatorFactory.getLocationStream(Str
    eamLocatorFactory.java:110)
    at com.webMethods.rtl.util.FileUtil.getInputStream(FileUtil.java:199)
    at com.webMethods.rtl.util.FileUtil.loadPropertiesFile(FileUtil.java:422
    )
    at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.loadSyste
    mProps(DefaultPhaseProvider.java:212)
    at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initializ
    ePhases(DefaultPhaseProvider.java:70)
    at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializ
    ePhases(ClusterPhaseProvider.java:27)
    at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:868)
    at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:827)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.webMethods.portal.system.start.Main.start(Main.java:131)
    at com.webMethods.portal.system.start.Main.main(Main.java:48)
    [POP.001.0002] A “java.io.IOException” occurred with the Message “[wm-cjdbc36-00
    39][SQLServer JDBC Driver][SQLServer]Invalid object name ‘MWS_CONFIG’.”
    java.io.IOException: [wm-cjdbc36-0039][SQLServer JDBC Driver][SQLServer]Invalid
    object name ‘MWS_CONFIG’.
    at com.webMethods.rtl.locator.DBConfigLocator.getLocationStream(DBConfig
    Locator.java:58)
    at com.webMethods.rtl.locator.ClusterConfigLocator.getLocationStream(Clu
    sterConfigLocator.java:59)
    at com.webMethods.rtl.locator.StreamLocatorFactory.getLocationStream(Str
    eamLocatorFactory.java:110)
    at com.webMethods.rtl.util.FileUtil.getInputStream(FileUtil.java:199)
    at com.webMethods.rtl.util.FileUtil.loadPropertiesFile(FileUtil.java:422
    )
    at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.loadSyste
    mProps(DefaultPhaseProvider.java:212)
    at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initializ
    ePhases(DefaultPhaseProvider.java:70)
    at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializ
    ePhases(ClusterPhaseProvider.java:27)
    at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:868)
    at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:827)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.webMethods.portal.system.start.Main.start(Main.java:131)
    at com.webMethods.portal.system.start.Main.main(Main.java:48)
    Shutting down…
    Shutdown complete.
    C:\webMethods7\MWS\bin>


    #webMethods-BPMS
    #webMethods
    #MWS-CAF-Task-Engine


  • 3.  RE: MWS instance doesnt start

    Posted Tue December 16, 2008 09:11 AM

    MWS_Config as far as I am aware is a table that only came into existence in 7.1.2. I would check the database and also check the scripts used to create the database components, as either you are trying to run a 7.1.2 MWS against 7.1.1 database components or vice versa…

    thanks,

    Donald


    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS


  • 4.  RE: MWS instance doesnt start

    Posted Wed December 17, 2008 02:08 AM

    yes, as suggested by Donald. seems like you are running different instance of MWS over different instance of DB.

    please check this for upgrading your database component.

    Migrate My webMethods Server Data

    1. Go to the My webMethods Server_directory\server\default\config directory and make
      sure the mws.db.xml file exists.
    2. On the machine on which you installed the Database Component Configurator, go to
      the webMethods_directory\common\db\bin directory and open a command window.
    3. Migrate the My webMethods Server database component by running this command:

    dbconfigurator.{bat|sh} –a migrate –d {oracle|sqlserver|db2luw} –c MyWebMethodsServer –v latest –l db_server_URL –u existing_db_user –p password –fv 20

    1. Make sure the MWS_CONFIG and MWS_CONTENT tables exist in the 7.1.2 My
      webMethods Server database component.
    2. Start My webMethods Server.

    #webMethods-BPMS
    #webMethods
    #MWS-CAF-Task-Engine


  • 5.  RE: MWS instance doesnt start

    Posted Wed December 17, 2008 07:09 AM

    Donald and Lion ,
    You are both spot on.
    The problem was due to different versions of Database Component configurator and MWS. In this case ,
    Database Component configurator was 7.1.1 and MWS was 7.1.2.

    Mws_config table used by MWS 7.1.2 is created only by Database Component configurator 7.1.2.
    So installed Database Component configurator 7.1.2 which created the database components and MWS 7.1.2 started without a glitch.

    Thanks a bunch Donald and Lion for your inputs.

    Thanks & Best Wishes,


    #webMethods-BPMS
    #webMethods
    #MWS-CAF-Task-Engine