Computation-relevancy-analyzer for a12 upgrade to 2024.06

Migration
1

Hey, we want to use the computation-relevancy-analyzer as part of the a12 upgrade to 2024.06. (GetA12 Login)
But we get an error message about included models (for several models). Any ideas how to solve this problem?
On the attached screenshot, you can see my model structure.

grafik
grafik578Ă—570 57.6 KB

The log says:

$ java -jar computation-relevancy-analyzer-0.1.0-cli-tool.jar  \models

Exception in thread "main" com.mgmtp.a12.kernel.md.model.api.services.DocumentModelExpansionException: Cannot open included document model 'MetaData'.
        at com.mgmtp.a12.kernel.md.model.internal.service.ExternalDocumentModelService$DocumentModelReferenceResolverWrapper.getDocumentModel(ExternalDocumentModelService.java:221)
        at com.mgmtp.a12.kernel.md.model.internal.service.DocumentModelExpandService$IncludeExpandVisitor.handleInclude(DocumentModelExpandService.java:249)
        at com.mgmtp.a12.kernel.md.model.internal.service.DocumentModelExpandService$IncludeExpandVisitor.visitGroup(DocumentModelExpandService.java:219)
        at com.mgmtp.a12.kernel.md.model.a12internal.visitor.DocumentModelWalker.visitElementInheritance(DocumentModelWalker.java:99)
        at com.mgmtp.a12.kernel.md.model.a12internal.visitor.DocumentModelWalker.acceptElement(DocumentModelWalker.java:85)
        at com.mgmtp.a12.kernel.md.model.a12internal.visitor.DocumentModelWalker.acceptChildren(DocumentModelWalker.java:125)
        at com.mgmtp.a12.kernel.md.model.a12internal.visitor.DocumentModelWalker.visitElementInheritance(DocumentModelWalker.java:101)
        at com.mgmtp.a12.kernel.md.model.a12internal.visitor.DocumentModelWalker.acceptElement(DocumentModelWalker.java:85)
        at com.mgmtp.a12.kernel.md.model.a12internal.visitor.DocumentModelWalker.acceptChildren(DocumentModelWalker.java:125)
        at com.mgmtp.a12.kernel.md.model.a12internal.visitor.DocumentModelWalker.acceptElements(DocumentModelWalker.java:75)
        at com.mgmtp.a12.kernel.md.model.a12internal.visitor.DocumentModelWalker.acceptDocumentModel(DocumentModelWalker.java:45)
        at com.mgmtp.a12.kernel.md.model.internal.service.DocumentModelExpandService.expandInternal(DocumentModelExpandService.java:103)
        at com.mgmtp.a12.kernel.md.model.internal.service.DocumentModelExpandService.expand(DocumentModelExpandService.java:91)
        at com.mgmtp.a12.kernel.md.model.a12internal.services.DocumentModelService.expand(DocumentModelService.java:106)
        at com.mgmtp.a12.kernel.md.model.a12internal.services.DocumentModelService.expand(DocumentModelService.java:90)
        at com.mgmtp.a12.kernel.md.model.internal.service.ExternalDocumentModelService.expand(ExternalDocumentModelService.java:65)
        at com.mgmtp.a12.migration.FileBasedDocumentModelResolver.getModel(FileBasedDocumentModelResolver.java:51)
        at com.mgmtp.a12.migration.ModelLoader.load(ModelLoader.java:73)
        at com.mgmtp.a12.migration.Main.lambda$main$0(Main.java:85)
        at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
        at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
        at java.base/java.util.Iterator.forEachRemaining(Iterator.java:133)
        at java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1845)
        at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
        at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
        at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
        at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
        at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
        at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
        at com.mgmtp.a12.migration.Main.main(Main.java:73)

Thanks,
Maria

2

Hi, @maria-wintry-ice
Have you tried putting all the models in the same folder (without subfolders)?

3

Hi @malcolm-silver-ice,

thank you for your idea!

But I just tried it, because we have that problem in most insurance solutions, but unfortunately it doesn’t help to put all models in one folder. There is still the same error in the console as Maria posted above…

4

I think this is probably a bug in the path handling of the analyzer tool.

5

I think so too…
How do we proceed here? Can you create such a bug-ticket or should we do it?

6

I have created a bug ticket and will analyze the issue as soon as possible.

7

thank you! :pray:
currently we’re kind of stuck in our analysis, because we have hundreds of computations and need to find those that would now reference “not-relevant” fields…

8

Hi @maria-wintry-ice and @bianca-firm-knoll, in case you are not aware of it already: The fixed analyzer has been released with 37.1.3 and you can find it in the Artifactory.