go to post Daniel Kutac · May 30, 2017 Safeena,you do not invoke web methods directly. You need to create a client class by consuming a WSDL file that your service exposes. There is a wizard that guides you through the process of client creation. Apart to client class itself the wizard also generates all data types used by a web service. Please consult documentation here.There are some other option when using Ensemble but I suggest you follow the link above.
go to post Daniel Kutac · May 22, 2017 what benchmark? populating the data or retrieving populated data? I think the speed of data population is not that important, comparing the standard populate or cos faker. What would be important is ability of the tool to mimic real data at maximum possible extent (e.g. values distribution).
go to post Daniel Kutac · May 17, 2017 Oh, now I see. I'm using Microsoft Edge as default browser and it displays them OK. Chrome is the troublemaker.I'll see what can I do to fix it.
go to post Daniel Kutac · May 11, 2017 Lasse, can you be more specific please? I'll be happy to add more information, but I need to know what are you missing.Thank you!
go to post Daniel Kutac · Mar 15, 2017 Thomas,Hope I understood your question correctly, if not then let me know.In general, when dealing with XML VDoc documents (files), you need to create a production that uses services based onEnsLib.EDI.XML.Service.FileService, operations based on EnsLib.EDI.XML.Operation.FileOperation and a routing process - EnsLib.MsgRouter.VDocRoutingEngine. There is no need to do any coding, just supply parameters in the production diagram.You may need to provide DocSchemaCategory setting for a service, for this, you need to import the XML Schema, using Import button at Ensemble->Interopeate->XML->XML Schema Structures page.for actual routing, you need to design a rule, and supply path to the document element/attribute that's used to decide where the rule sends document to. I prefer using XPATH expressions for this.An example of routing rule contents is here:<ruleDefinition alias="" context="EnsLib.MsgRouter.VDocRoutingEngine" production="tzp.dasta.router.Production"><ruleSet name="" effectiveBegin="" effectiveEnd=""><trace value="Document.{/dasta/is/ip/lo/loi/@material}"></trace><rule name=""><constraint name="source" value="Dasta3Zadanka"></constraint><constraint name="msgClass" value="EnsLib.EDI.XML.Document"></constraint><constraint name="docCategory" value="ds030101"></constraint><when condition="Document.{/dasta/is/ip/lo/loi/@material}="B""><send transform="" target="Dasta3Biochemie"></send><return></return></when><otherwise><send transform="" target="Dasta3Mikrobiologie"></send><return></return></otherwise></rule></ruleSet></ruleDefinition>You can create a VDOC document from a persistent (any, not only persistent) object, as long as it extends also from %XML.Adaptor. First, you serialize your object instance to XML stream or string, and then using ImportFromString/ImportFromLibraryStream (or other - see online reference for EnsLib.EDI.XML.Document class) method you instantiate a VDoc document.HTH.Dan
go to post Daniel Kutac · Mar 6, 2017 May others find it useful:I created a small dummy java class that implements public static String evaluate() method (with 1 to 5 arguments for my needs), compiled it and made a jar file.replaced original references to java:com.intersys.xsltgateway.XSLTGateway by my faked ones (Atelier refactor, easy...) in all used XSL stylesheets.Then I supplied this dummy jar file into a list of external JAR files to the OrangeVolt XSL run configuration. It all worked fine and I eventually received transformed document (with dummy data in places of original isc:evaluate calls).Just need to remember to put back pointer to original callback handler class before deploying transformation to Cache server.
go to post Daniel Kutac · Mar 3, 2017 Thank you all for replies,a few clarifications:1. I can run the transformation from Cache, using %XML.XSLT2.Tranformer class (and supplying an instance of Cache callback class), this works fine.2. when there are no isc:evaluate callbacks in the XSL stylesheet, then Atelier runs transformation fine, too.So, Jamie is right.PS: this is not an important issue, but I was looking forward to see Eclipse's user friendly debugger in action. But I can live with that limitation, understanding why it is so.
go to post Daniel Kutac · Feb 27, 2017 hmm, I see...in that case, can the procedure of creating index be more automated? You know I'm a lazy programmer :)
go to post Daniel Kutac · Feb 27, 2017 Michael,wouldn't it be enough just to define datatype that has Getter and Setter methods implemented that perform the encryption/decryption on the fly and transparently for you?Dan
go to post Daniel Kutac · Jan 19, 2017 Istvan, what if I have a habit of putting all XSL stylesheets into XDATA blocks?
go to post Daniel Kutac · Dec 27, 2016 Excellent job!it took me a little while, though, to figure out all dependencies, namely PYTHON that was not mentioned in the github instructions and fresh enough node.js.But now everything works as expected now.One wish: please add a button that would navigate back to the System Management Portal or open the dashboard in a new tab/window.
go to post Daniel Kutac · Dec 16, 2016 Thanks to Alexander, he found the potential bug (or a feature), the calculated measure definition shall not have "shared storage" selected!Dan
go to post Daniel Kutac · Dec 16, 2016 Alessandro,I'm trying to follow your example on Cache 2016.2.1. but with no luck. Respectively, when I drag and drop pivot table rows and columns, I always get "no result" in the (single) cell.However, when using the MDX supplied, it works fine. Looking at generated MDX when using drag'n'drop, the MDX looks completely different.What am I doing wrong? Dan
go to post Daniel Kutac · Dec 9, 2016 for me personally, the greatest benefit of custom SQL queries is that you don't need any (persistent) data, you can just generate it on the fly, either computing them or bringing from any arbitrary external system. Dan
