My guess is that it has something to do with a recent Eclipse upgrade. Photon is Eclipse version 4.8, which is the last officially supported version for use with Atelier.

If your code base is especially large, you might want to consider creating projects like

  • site.system1.routers
  • site.system1.processes
  • site.system2.routers
  • site.system2.processes
  • site.common.routers

Keep in mind that Atelier projects don't play nicely with XML files that aren't supported by the UDL transformation engine. The community should be able to steer you in the right direction if that becomes a blocker for you.

Atelier uses this task to update its cache of your namespace(s). It might also be doing some validation. Does this task always need to be killed? 

You could try playing with your user preferences for caching and validation. Otherwise, I'd go to the WRC. I believe others have had trouble like this before in the past.

Hello Michel,

You might want to keep an eye out for some new content that the Learning Services are planning on publishing soon.

Building Custom Business Services Course

This course will be updated for IRIS for Health and includes an FTP example that will include the Attributes property. If you check out the current offering, you'll see that it consumes a file called Appointments.txt from See exercise in 3.5 (creation) and 4.3 (implementation). The video uses the File adapter, but the exercise uses FTP.

Hope this helps!

Looks to me like there is a problem with your server connection. I recommend you contact the WRC who will be able to resolve the problem quickly.

Based on the screen shot, it looks like you tried to save a MAC routine in the RemoteSystemsTempFiles project. This project is not related to Atelier in any way, but should not be blocking you from persisting your change to the file system. 

I encourage you to watch the getting started videos pointed to in other comments and to use the "Cheat Sheets" within the product itself. Go to Help > Cheat Sheets... > Atelier and click the first one. Go through them in order to get a good understanding of Atelier basics.

If after you've done this you are still having trouble, please contact the WRC who are best able to help you troubleshoot. 

Let us know what fixed the problem as an answer here as well please.

Atelier embeds the web editor accessible from the Management Portal into an Eclipse editor, so it works the same way.

The feature is supported in class files only in Atelier 1.1 and in routine files as well in Atelier 1.2. Support in CSP pages is not a high priority at this time. If this is something that you feel is a blocker or that the team should increase its priority, please contact the WRC.

Robert is correct that you need to install the terminal plugin. I would recommend using the most recent version which is available from the Eclipse release update site associated with the version of Eclipse you have installed.

If you are using Oxygen, then go to

You can find product documentation on the topic from Atelier as well. Go to Help > Help Contents > InterSystems Atelier User Guide > Tasks > Installing the Eclipse Terminal Plug-in.

Hello, Jan. It seems you are having a problem with the Java class loader. The team responsible for the Java Gateway forwarded the following suggestion. Could you please give it a try? If it doesn't help, please contact the WRC for further support.

java.lang.NoClassDefFoundError: Could not initialize class is a Java class loader error typically means that the class loader ran into an exception when trying to load (read) the class. To make sure this is not a user error, I would suggest they try to write a small Java program that simply loads the above class (use Class.forName()), they might get the same error. If not, then it’s probably something to do with the static initializer, I imagine there must be one. They should try to catch an exception in it and that should provide more info on the actual error. A good example of what can go wrong is that they might try to access the file system, right there in the static initializer, and that the path or permissions are different in their dev environment, and on the machine where they try to import the class using the Java Gateway.


To avoid these kinds of errors, we have been advocating the use of a so called ‘façade approach’, where the user makes sure to build most of the app on the Java side, hiding all sorts of things like massive dependencies, big jar files, file system dependencies etc. etc. and exposing only that small app to Cache/Ensemble via the JG