webMethods

webMethods

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.  Unable to Build & Upload Model in Designer 7.1.2

    Posted Thu January 03, 2013 02:55 PM

    One of my colleagues is getting the following error upon Build & Upload for a new ProcessModel:

    Build of process "BeP_OtC_BIS_deliverCustomerOrder_inBIS" started at Thu Jan 03 15:06:20 CET 2013 
    Checking database for prior build and upload of process: "BeP_OtC_BIS_deliverCustomerOrder_inBIS" version: "1"
    Retrieving previous build information for process: "BeP_OtC_BIS_deliverCustomerOrder_inBIS" version: "1"
    Error: Failed to retrieve previous build information for process "{0}" version: "{1}". Please make sure that the database is configured properly.
    null
    at java.io.ByteArrayInputStream.<init>(Unknown Source)
    at com.webmethods.process.generator.process.receipt.util.ProcessGenerationReceiptManager.parseBytes(ProcessGenerationReceiptManager.java:152)
    at com.webmethods.process.generator.process.receipt.util.ProcessGenerationReceiptManager.getPreviousGenerationReceipt(ProcessGenerationReceiptManager.java:131)
    at com.webmethods.process.generator.process.receipt.util.ProcessGenerationReceiptManager.getPreviousGenerationReceipt(ProcessGenerationReceiptManager.java:117)
    at com.webmethods.process.generator.ProcessModelGenerator.readGeneratedComponentsFromGenerationReceipt(ProcessModelGenerator.java:424)
    at com.webmethods.process.generator.ProcessModelGenerator.generateModel(ProcessModelGenerator.java:255)
    at com.webmethods.process.generator.ProcessModelGenerator.generateModel(ProcessModelGenerator.java:463)
    at com.webmethods.process.generator.actions.GenerateProcessAction.run(GenerateProcessAction.java:269)
    ... 30 more
    Error: Build of process "BeP_OtC_BIS_deliverCustomerOrder_inBIS" failed. Please check the log file for more information.
    java.lang.NullPointerException
    at com.webmethods.process.generator.ProcessModelGenerator.setOldLogicalToPhysicalMapList(ProcessModelGenerator.java:1265)

    I have checked the LogicalServer settings, the JDBC-Pool Settings and the Designer settings several times. All of them are correct and working.
    Except for the Build & Upload.
    I have checked also the Proxy Settings of the Designer but even this did not help.

    Any Ideas?


    #webMethods
    #webMethods-BPMS
    #BPM


  • 2.  RE: Unable to Build & Upload Model in Designer 7.1.2

    Posted Thu January 03, 2013 03:46 PM
    1. Check in Windows > Preferences - if Process Audit has been configured to point either to Logical name of IS or directly thru’ DB URL?

    2. This DB should have process audit tables created in it. Use DB Configurator to check if this exist or not.

    3. If tables exist, and still you see this error, drop and recreate those tables again, and check if build success…

    HTH
    -Senthil


    #webMethods-BPMS
    #BPM
    #webMethods


  • 3.  RE: Unable to Build & Upload Model in Designer 7.1.2

    Posted Thu January 03, 2013 04:40 PM
    1. Process Audit is configured to the logical Name of IS.
    2. Tables exist (I have done the creation myself).

    Unfortunately I cannot recreate the tables as we already have deployed nearly the complete application to the IS. The affected ProcessModel is the first new one for this instance.


    #webMethods
    #BPM
    #webMethods-BPMS


  • 4.  RE: Unable to Build & Upload Model in Designer 7.1.2

    Posted Fri January 04, 2013 03:11 AM

    When you say, deployed the complete application, do you mean ‘n’ number of process models, and packages etc., or just packages and TN assets etc., Reason being, IS assets (packages, config files), and TN objects are not related with PRT tables. It just holds info about the process model… If you dont have any other process model deployed, and this is the first one, you can try that…

    On the other hand, just to make sure if tables exist, run dbConfigurator by choosing the category ‘catalog’ instead of create/drop etc., This will show all the installed tables from the db url that you provide…

    If problem still persists, increase the logging level and try to capture more info… You can also analyze the designer log files…

    -Senthil


    #webMethods
    #BPM
    #webMethods-BPMS


  • 5.  RE: Unable to Build & Upload Model in Designer 7.1.2

    Posted Fri January 04, 2013 11:13 AM

    I can do selects on these tables (I am currently working on a support incident with SAG for another issue related to these tables) in the DB directly. DB-Schema has been created using “PRODUCT - IntegrationServer” from DC_7.1.2_Fix7. This contains also Process tables (PE and Audit).
    Additionally we have modified the audit/schemas/wMProcess.xml as described in a Knowledgebase Article in Empower:

    • Modify PROCESSKEY from 64 to 255 Chars
    • empty WmRepository4
    • restart IS to reload the Auditing Schemas.

    I have deployed normal packages in one set, and the models and their impl-packages in another set. (Splitted into several Deployments for packaging reasons).

    I have checked the log-files myself:

    Here is the StackTrace (is shown in the “Build Report”-Tab in the Designer also):

    !MESSAGE Error in Generation: java.lang.NullPointerException
    at com.webmethods.process.generator.ProcessModelGenerator.setOldLogicalToPhysicalMapList(ProcessModelGenerator.java:1298)
    at com.webmethods.process.generator.ProcessModelGenerator.generateModel(ProcessModelGenerator.java:266)
    at com.webmethods.process.generator.ProcessModelGenerator.generateModel(ProcessModelGenerator.java:469)
    at com.webmethods.process.generator.actions.GenerateProcessAction.run(GenerateProcessAction.java:253)
    at com.webmethods.process.generator.actions.GenerateProcessAction.run(GenerateProcessAction.java:82)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
    at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
    at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
    
    !ENTRY com.webmethods.sc.eclipse.logging 4 0 2013-01-04 13:38:47.277
    !MESSAGE Error in Generation: java.lang.NullPointerException
    at com.webmethods.process.generator.ProcessModelGenerator.setOldLogicalToPhysicalMapList(ProcessModelGenerator.java:1298)
    at com.webmethods.process.generator.ProcessModelGenerator.generateModel(ProcessModelGenerator.java:266)
    at com.webmethods.process.generator.ProcessModelGenerator.generateModel(ProcessModelGenerator.java:469)
    at com.webmethods.process.generator.actions.GenerateProcessAction.run(GenerateProcessAction.java:253)
    at com.webmethods.process.generator.actions.GenerateProcessAction.run(GenerateProcessAction.java:82)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
    at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
    at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

    #webMethods
    #webMethods-BPMS
    #BPM


  • 6.  RE: Unable to Build & Upload Model in Designer 7.1.2

    Posted Mon January 07, 2013 10:57 AM

    After finding the following thread [url]wmusers.com this leads to the following Empower KB Article:
    [url]https://empower.softwareag.com/sl24sec/SecuredServices/KCFullTextASP/viewing/view.asp?KEY=083812-866743&DSN=PIVOTAL&DST=TCD&QUERY=1736911&SessionID=636091255&HL=1[/url]

    IMO the commandline generator for Designer 7.2 (buildAndUpload*.bat) and 2 caf-sql-plugins are also affected:

    • com.webMethods.caf.shared.sql_*
    • com.webMethods.caf.sql.data.ui_*
    • Check the MANIFEST.MF and the plugin.xml (if present) of those plugins for references to sl53_cj*.jar

    #webMethods
    #webMethods-BPMS
    #BPM


  • 7.  RE: Unable to Build & Upload Model in Designer 7.1.2

    Posted Tue January 08, 2013 01:30 PM

    After exchanging the jars and modifying the files as described in the Empower KB-Article 1736911, the Designer is no longer able to connect to the database at all.
    neither with the IS-parameters nor with the directly given parameters.

    connection to the server has been checked with telnet and this works.

    In the Designer Log there is the following error message:
    java.lang.ClassCastException: org.eclipse.core.internal.resources.File

    Any ideas?


    #webMethods-BPMS
    #BPM
    #webMethods