Home › Forums › Business Model › BI Models › Unable to Publish model
Tagged: Business Models
- This topic has 8 replies, 2 voices, and was last updated 9 years ago by ashutosh.
-
AuthorPosts
-
-
November 10, 2015 at 8:43 am #391ashutoshParticipant
Hi All,
I am unable to publish model. I have validated the project and there are no errors. I have added a new message and trying to test it. When I am trying to publish my model it doesnt do anything.
Setps that I am following to publish:
–> Click on Model Library
–> Click on Publishwhen I click publish it starts doing something but after that it just gets still.
I am attaching the screen shot for reference. I am not getting any warnings or error messages.
Please let me know if am missing something or how can I check what issue is there.
Regards,
Ashutosh0Attachments:
You must be logged in to view attached files. -
November 11, 2015 at 1:58 pm #396Ed ShawKeymaster
The fact that you aren’t getting warnings or error messages may be a good thing.
Typically, publish is not a noisy process. Once you press Model Library/Publish… it should:
1. take a bit of time doing some some validation
2. display a File/Save dialog to confirm the location and filename (based on the settings of your publish and out folders from preferences – typically something like d:/work/out/publish).
3. After pressing the Save button, there should be a status in the lower right corner of studio that says something like Publishing “Finance”: (35%)
3b. if you are re-publishing the same version, you may be prompted to overwrite and existing file.
4. If you look at the console view, you should see some output. What you are waiting for is for the status message in the right hand corner to disappear and for the console to output something like
BUILD SUCCESSFUL
Total time: 1 minute 20 secondsThere is no dialog that says you are done. You can close the Model Library at any time and the process will continue until completed. To check that it succeeded look at the console output and you can also check for a new or updated jar file in your published folder.
By the way, if you have added a new message and want to test it you likely do not need to publish your model. You can test it by running your server console.
0 -
November 11, 2015 at 4:05 pm #398ashutoshParticipant
Thank you for the response Ed.
There are some issues with the publishing of model. I followed, and I know the steps that you described above. As you described:
Step 1 happens in my system but Step 2 never happens (i.e. giving a pop up for saving the file.) Can I check any internal logs as to why I am not getting the file save dialogue option?
And About the message that I was trying to parse I figured it out. It was a problem with scheme code and now its working fine.
I was getting the below error and that is the reason I thought maybe I have to publish the model with my new message (RBC_Client) which I created for test purpose. Now everything is fine except the publish part.
12345678910Error: Unknown message "RBC_Client" in repository "rbccwm".at nexj.core.meta.xml.XMLMetadata.getMessage(XMLMetadata.java:2881)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:597)at nexj.core.scripting.JavaMethod.invoke(JavaMethod.java:226)at integration.lambda(library:integration:127)at scheme.loop(syslibrary:scheme:1470)at integration.lambda(library:integration:125)Regards,
Ashutosh0 -
November 11, 2015 at 5:03 pm #400Ed ShawKeymaster
Asutosh,
Glad you’ve solved your message metadata issue. I guess you had the wrong name or hadn’t restarted your running server so it wasn’t aware of the new metadata – yes?
To see what’s going on with your publish, try looking at the following. In your workspace where you keep your models (mine is called “d:/work/models” – some people prefer a folder called “ws”) look for a folder called “.metadata”. In that folder you may find a file called “.log”. That fill may contain some helpful output. It is the log file that NexJ Studio uses to output warnings and errors.
You can delete it and retry your publish if you want to eliminate any “old noise”. Otherwise, just look for the latest entries in the file and see what they say.
0-
November 11, 2015 at 5:47 pm #402ashutoshParticipant
Thanks Ed.
I got the error message from the .log file.
Now I am getting error in starting the minimum console and its not getting started. I will investigate on this and come back.
Error from the log file:
1234567891011121314151617181920212223242526272829303132!ENTRY com.nexjsystems.nexjstudio 4 0 2015-11-11 16:15:05.633!MESSAGE Build error occurred.!STACK 0java.lang.NullPointerExceptionat nexj.core.meta.integration.format.object.ObjectMessagePartMapping.buildDependentMsgPartsMap(ObjectMessagePartMapping.java:1061)at nexj.core.meta.integration.format.object.ObjectMessagePartMapping.buildDependentMsgPartsMap(ObjectMessagePartMapping.java:1085)at nexj.core.meta.integration.format.object.ObjectMessagePartMapping.buildDependentMsgPartsMap(ObjectMessagePartMapping.java:1030)at nexj.core.meta.integration.format.object.ObjectMessagePartMapping.refer(ObjectMessagePartMapping.java:1119)at nexj.core.meta.integration.Message.resolveReferences(Message.java:610)at nexj.core.meta.integration.Message.resolveReferences(Message.java:606)at nexj.core.meta.integration.Message.resolveReferences(Message.java:606)at nexj.core.meta.integration.Message.resolveReferences(Message.java:584)at nexj.core.meta.integration.Message.resolveReferences(Message.java:356)at nexj.core.meta.xml.XMLMetadataLoader.load(XMLMetadataLoader.java:1880)at nexj.core.meta.xml.DefaultXMLMetadataLoader.B(DefaultXMLMetadataLoader.java:13)at nexj.core.meta.xml.DefaultXMLMetadataLoader$1.load(DefaultXMLMetadataLoader.java:26)at nexj.core.meta.DynamicMetadataLoader.load(DynamicMetadataLoader.java:143)at nexj.core.meta.xml.DefaultXMLMetadataLoader.load(DefaultXMLMetadataLoader.java:21)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:597)at nexj.eclipse.model.repository.DescriptorInstanceModel.loadMetadata(DescriptorInstanceModel.java:5466)at nexj.eclipse.controller.RepEditorAppController.loadMetadata(RepEditorAppController.java:1353)at nexj.eclipse.controller.RepEditorAppController.loadMetadata(RepEditorAppController.java:1303)at nexj.eclipse.controller.RepEditorAppController.loadMetadata(RepEditorAppController.java:1297)at nexj.eclipse.controller.RepEditorAppController$9.run(RepEditorAppController.java:1457)at nexj.eclipse.controller.RepEditorAppController.validateRepository(RepEditorAppController.java:1496)at nexj.eclipse.controller.RepEditorAppController$21.run(RepEditorAppController.java:3287)at nexj.eclipse.controller.RepEditorAppController$JobProgressMonitorDialog.run(RepEditorAppController.java:5454)at nexj.eclipse.controller.RepEditorAppController$JobProgressMonitorDialog$2.run(RepEditorAppController.java:5490)at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)0-
November 12, 2015 at 3:40 pm #404Ed ShawKeymaster
This looks like a metadata issue – i.e. incorrect code in your project. Could you confirm where you are at with this. Are you still having difficulty publishing? Thanks.
0-
November 14, 2015 at 5:05 pm #406ashutoshParticipant
Today I created a new project with the latest code and everything works fine only I am thing is I am not able to publish the model. When I checked the logs in the dir, I am getting below error in it.
How can we check what is not set in the environment as validating the project dont give any error.
Error:
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778!SESSION 2015-11-14 16:57:14.744 -----------------------------------------------eclipse.buildId=M20130204-1200java.version=1.6.0_26java.vendor=Sun Microsystems Inc.BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_USCommand-line arguments: -os win32 -ws win32 -arch x86!ENTRY com.ca.harvest.cmsdk 4 0 2015-11-14 16:58:10.062!MESSAGE Failed to initialize CA SCM CMSDK. Please ensure that all required components are installed.!STACK 0java.lang.UnsatisfiedLinkError: no liblber in java.library.pathat java.lang.ClassLoader.loadLibrary(ClassLoader.java:1738)at java.lang.Runtime.loadLibrary0(Runtime.java:823)at java.lang.System.loadLibrary(System.java:1028)at com.ca.harvest.cmsdk.CmsdkPlugin.preloadWin32Libs(CmsdkPlugin.java:54)at com.ca.harvest.cmsdk.CmsdkPlugin.start(CmsdkPlugin.java:41)at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)at java.security.AccessController.doPrivileged(Native Method)at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:263)at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:469)at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395)at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)at java.lang.ClassLoader.loadClass(ClassLoader.java:247)at com.ca.harvest.cm.CmPlugin.(CmPlugin.java:19)at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)at java.lang.reflect.Constructor.newInstance(Constructor.java:513)at java.lang.Class.newInstance0(Class.java:355)at java.lang.Class.newInstance(Class.java:308)at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:167)at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:679)at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:263)at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:469)at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395)at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:464)at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)at java.lang.ClassLoader.loadClass(ClassLoader.java:247)at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:340)at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1212)at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:273)at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52)at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:269)at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition$1.run(LightweightDecoratorDefinition.java:124)at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)at org.eclipse.core.runtime.Platform.run(Platform.java:857)at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.internalGetDecorator(LightweightDecoratorDefinition.java:120)at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:251)at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)Regards,
Ashutosh0
-
-
-
-
November 12, 2015 at 4:08 pm #408ashutoshParticipant
Hi Ed,
Still I am not able to publish the model. when I validate I don’t get any error in the studio.
Even I cehcked the .log file for the validation but did not see any logs written when validation was happending.
Screenshot attached for validtion.
Regards,
Ashutosh Singh0 -
November 16, 2015 at 2:21 pm #394Ed ShawKeymaster
Ashutosh,
It looks like your environment is missing a reference to CA Harvest. I think this is an Eclipse Plugin Library that is specific to the configuration of your customer environment. NexJ doesn’t ship or use Harvest. Can you check with your CA representative to determine what might be wrong?
Thanks,
Ed
1
-
-
AuthorPosts
- You must be logged in to reply to this topic.