go to post Nicole Aaron · May 30, 2018 I just took a quick look through some past InterSystems Support cases. I haven't seen this error reported to the WRC before.There is not an obvious/general reason for this error. I would suggest opening a WRC case to investigate this issue on your system (either by emailing support@intersystems.com or calling +1 617-621-0700).
go to post Nicole Aaron · May 29, 2018 This solution is now written up more cleanly in a Developer Community post here.
go to post Nicole Aaron · May 29, 2018 All set, John. You should see WRC 899885 when you log into the WRC application.
go to post Nicole Aaron · May 29, 2018 Hi John, yes this is still on the dev team's radar. There is a development issue filed to address it. However it is not a high priority at the moment. Let me know if you'd like me to create a WRC case in your name linked to that dev issue so that you can monitor its progress in your WRC application.
go to post Nicole Aaron · May 25, 2018 Right you are John. I sent you the wrong flag+StackOverflow page, sorry about that. The command-line flag you'll want to add is: -clearPersistedStateThis will clean persistent workbench data. Then you'll need to re-open the Atelier perspective, or the Atelier views that you use.
go to post Nicole Aaron · May 25, 2018 Hi, John - thanks for pointing this out. You'll want to run Eclipse with the -clean argument to clear all cached plug-in data. There's a good discussion about that on StackOverflow here.I'd suggest adding the clean argument by launching Eclipse from the command line (less risk than adding it to the eclipse.ini and forgetting to remove it).
go to post Nicole Aaron · Apr 20, 2018 We might have some developers on the Community using HealthShare who can give you tips here. But I think that the best way to move forward, since these are reasonably broad questions, will be to reach out to your InterSystems Sales team or Support. The answers to many of your questions will probably be better with more information about your current development process and Sales/Support can discuss the specifics with you.
go to post Nicole Aaron · Apr 6, 2018 Hi Dieter, I think that we'll need to collect some system-specific information to debug this further. The best next step will probably be to open a WRC case to investigate (by emailing support@intersystems.com or calling +1 617-621-0700).
go to post Nicole Aaron · Apr 4, 2018 I think the best next step will be to file a WRC case (by emailing support@intersystems.com or calling +1 617-621-0700). There is some system-specific info that we'd like to collect to try and debug this further.
go to post Nicole Aaron · Mar 26, 2018 I'm not sure exactly how Eclipse decides where your secure storage file should be located. I thought it had to do with where the application was installed, but after doing a bit more research I think it may be a hard-coded location. I Googled "changing eclipse secure storage location" and found this in the Eclipse documentation:http://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Freference%2Fref-securestorage-options.htm&cp=0_4_3_3
go to post Nicole Aaron · Mar 26, 2018 Your Atelier server connection information is stored in Eclipse's secure storage file. The secure storage file is shared among different workspaces created in the same Eclipse client. You can see the location of this file in your Eclipse preferences under General > Security > Secure Storage > Contents > Storage location.The location of the secure storage file depends on the directory in which Eclipse was installed. If you want a second install with an independent list of server connections, you will need to install the second Eclipse client in a new directory.
go to post Nicole Aaron · Mar 21, 2018 What exactly have you tried so far? What version of Atelier are you using? What version of Caché/Ensemble/HealthShare?I would suggest contacting the WRC (by emailing support@intersystems.com or calling 617-621-0700) to get further help on this. A Support advisor will be able to give you one-on-one help to get to the root of the problem on your system.
go to post Nicole Aaron · Mar 12, 2018 Hi Trevor, this has been reported to development (internal code ATL-3359). The ability to filter out system files in the Atelier Explorer view is currently targeted for an Atelier 1.5 release.I'll look into the Developer Community tag options. Regardless of the tag selected it never hurts to mention the build number in your post as well.
go to post Nicole Aaron · Mar 9, 2018 Currently (with Atelier 1.1.391), opening and editing class, routine and csp files are supported. The BPL and DTL graphical editors are also fully supported. Beyond that, more inclusive Ensemble support is targeted for Atelier 2.0. Keep an eye on announcements in the Atelier group in the Developer Community and Atelier release notes for information about upcoming versions.
go to post Nicole Aaron · Feb 27, 2018 Thanks for the additional information. This has been fixed in later server versions but, as John mentioned, those have not been released yet. If you need this fix now we will have to provide it in a patch kit (Adhoc). Note that our Adhocs do not go through our full suit of QD tests . You will need to contact the WRC (support@intersystems.com) to request an Adhoc.
go to post Nicole Aaron · Feb 27, 2018 This has been reported and corrected (development code CDS2960). This required a server-side change that appears in 2017.1.3, 2017.1.4 and 2017.2.2. Can you send your Caché/Ensemble/HealthShare version string so that I can confirm you do not already have a version with this fix? You can get that by clicking the About link in the top-left of the System Management Portal.
go to post Nicole Aaron · Feb 22, 2018 This should be the web server port. The PKIX error usually indicates an issue with HTTPS (such as the web server expecting HTTPS but receiving an HTTP request). The "Connection refused" message could mean that the path for the REST requests made by Atelier are not being properly served to the CSP Gateway.As Francisco mentioned, you can give this a try with the private Apache web server (by default listening on port 57772) which should be able to serve the REST requests from Atelier out of the box. That will give us a baseline of whether you can connect your Atelier client to the server.I would suggest opening a WRC case so that a Support advisor can get specifics about the web server you are using and how that is configured.
go to post Nicole Aaron · Feb 20, 2018 The Atelier team is working on this navigation feature. The Atelier Explorer and Server Explorer are scheduled to be improved with the 1.2 release (although it has not yet been implemented, so we can't guarantee the version).
go to post Nicole Aaron · Feb 17, 2018 The presentation will be available in about a week or so. It will be available on learning.intersystems.com.
go to post Nicole Aaron · Feb 14, 2018 If I understand correctly, you are looking for the DTL graphical editor within Atelier? To do this you will want to open the DTL class code, then right-click in the editor and select "Open diagram editor". You can find a previous post with more detail here:https://community.intersystems.com/post/how-edit-business-process-and-data-transformation-files-atelier
