There are two types of errors in the sample that you sent, one of which has been corrected and one of which is being actively investigated. The workaround while this is under investigation is to use the graphical DTL editor in the System Management Portal.

ERROR #5001: attribute 'sourceclass' is not declared for element 'transform'

ERROR #5001: attribute 'sourcedoctype' is not declared for element 'transform'

ERROR #5001: attribute 'targetclass' is not declared for element 'transform'

ERROR #5001: attribute 'targetdoctype' is not declared for element 'transform'

These errors have been reported to the Atelier development team here at InterSystems and are being investigated. We do not have a timeline for the fix, but you can always reach out to the WRC to check in on the status of the internal report.

ERROR #5001: element 'assign' is not allowed for content model '(annotation?)'

This error has been corrected, starting with Ensemble 2017.2.1. If you are seeing this when compiling against later versions of the product please send us your version string (by clicking the About link in the top-left of the System Management Portal).

Hi Connor, I've been working with Michelle Stolwyk on this one and I do not think this is a large-scale issue with the stable Atelier repository. I just installed Java 8, Eclipse Photon, and Atelier 1.3.139 (from the stable repo https://atelier.jfrog.io/atelier/updates/stable/1.3/) on a fresh machine without any problems.

I think the issue on your system does boil down to a security/proxy problem. Here is an article I've used to help with this type of issue in the past: https://stackoverflow.com/questions/21076179/pkix-path-building-failed-and-unable-to-find-valid-certification-path-to-requ.

If you are still having trouble I would suggest reaching out to InterSystems Support (by calling +1 617-621-0700 or emailing support@intersystems.com) for help with your specific configuration. InterSystems will not be the authority on how to configure a proxy, Java certs, etc. But we can point you in the right direction and send some resources that our customers have used in the past.

Elize - I'm sorry to hear that your Atelier experience has been frustrating. I've been able to use the Atelier debugger to step through code and see variable values without any problems, and it sounds like Eduard has as well.

InterSystems provides some resources that may be helpful to you:

  1. A video on using the Atelier debugger can be found here
  2. The Atelier documentation on using the debugger is here
  3. You can always reach out to InterSystems Support to work directly with an advisor (call +1 617-621-0700 or email support@intersystems.com)

I would suggest first checking the browser you have selected in your Eclipse settings. From the preferences page, select General > Web Browser and confirm that the expected browser is selected.

Next take a look at the settings in your IE 11 browser to check the Emulation settings. (In the F12 Developer Tools make sure that the Document Mode selected there is not 7.)

If you are still having trouble I think we'll need to look into your system-specific settings, such as the operating system, exact build of IE, etc.. That would probably be best handled by InterSystems Support.

As an aside - Atelier is supported on the Eclipse Photon release, not on the 2018-12 release. I do not necessarily think this will solve the problem you are seeing now, but we have seen this cause other problems when using the Atelier plugin. So I would suggest getting a fresh install of the Eclipse Photon client here then install Atelier on this new client.

Hi Anthony - Thanks for the update, and the explanation of how you cleaned up your Eclipse perspectives. There were major, internal changes that occurred after Atelier 1.1, which can leave some of the Atelier 1.1 plugin features in this state after an upgrade. You can also clean the stale workbench data in Eclipse using the method described in the DC post here.

José filed a WRC case to look into this. José found that reinstalling everything, including Eclipse, resolved this problem. He and the Support advisor were not able to determine the root cause of this behavior before the reinstall, when the errors disappeared.

Anthony and José - The Atelier team has not been able to reproduce this, and many users have successfully upgraded to version 1.3.139. So it looks like this must be something specific to your environments. For help diving into what is going wrong on your systems, I would suggest contacting InterSystems Support (by emailing support@intersystems.com or calling +1 617-621-0700).

Can you provide more details about how you tried to enable SSL/TLS? Did you do this on the Caché server, or on the web server?

As Kyle mentioned, the first step is to use an IP and port for a web server that has HTTPS configured. If you do not know how to do this, I would suggest reaching out to your system administrators. You can also feel free to get in touch with Support or your InterSystems Sales team to discuss this in more depth.

David opened a WRC case and we are looking into the cause of this issue. I'll post the resolution here in the DC once we are done with our investigation.

======

Update 11/26/18: We were not able to get to the bottom of this, as David reached a point where he was unable to spend the time to investigate further.

This error indicates that you have a proxy/firewall blocking the Atelier installation. If you Google something like "Eclipse PKIX path building failed" you'll see a number of hits about adding the necessary certificate chain to the Java keystore. I would suggest reaching out to your network team about this. If they are not able to help, you can always reach out to InterSystems Support.