All
Accepted answers
Nicole Aaron · Dec 4, 2017 go to post

Hi Mike, I know you already figured this out yourself but just wanted to write up some instructions for others who find this post.

The Eclipse documentation will contain separate sections for each plug-in. To filter on only the "InterSystems Atelier User Guide":

  1. Select the Scope link next to the search box
  2. Pick the radio button for "Show only the following topics"
  3. Click the New button
  4. Check the Atelier guide and give this scope a name
  5. Click OK > OK

The documentation is also available online here, where it contains only the Workbench and Atelier User Guides.

Nicole Aaron · Nov 16, 2017 go to post

This error can occur for a number of reasons. It could have to do with a firewall, a proxy server, etc. on your system. This is an Eclipse error, outside of InterSystems technologies - your best bet will probably be to Google the error.

Nicole Aaron · Nov 16, 2017 go to post

I assume that by the droppins version you mean the standalone Atelier client? Starting with the 1.1.386 release, we dropped support for the standalone Atelier client. There was an announcement in the Developer Community here.

You will need to install Eclipse OXYGEN and add the Atelier plug-in. Detailed instructions can be found in the article linked above, or on the Atelier download site, intersystems.com/atelier.

If you are still having trouble installing the Atelier plug-in, I would suggest opening a WRC case with Support (by emailing support@intersystems.com or calling 617-621-0700) to investigate what is going wrong on your system.

Nicole Aaron · Nov 15, 2017 go to post

There are currently no plans to merge the Atelier documentation with the docs for other InterSystems technologies (Caché, Ensemble, HealthShare, InterSystems IRIS Data Platform). Atelier is a separate product and will continue to have its own documentation that follows industry standards for Eclipse plug-ins.

Nicole Aaron · Oct 19, 2017 go to post

Thanks for the update, Fred. This question was answered in Fred's comment. Adding this so the post shows up as answered.

Nicole Aaron · Oct 13, 2017 go to post

I'd suggest filing a new case with Support (email support@intersystems.com or call 617-621-0700). That way an advisor can dial in and help troubleshoot your specific case. Then you or the advisor can come back to this post and give an update on the resolution.

Nicole Aaron · Oct 10, 2017 go to post

Studio's server-side source control hooks are supported in Atelier.

What version of Atelier are you using? What version of Caché? Do you have a successful connection set up to your Caché server? Are you using the Server Explorer view to look for these classes?

I would suggest opening a Support case to investigate (by emailing support@intersystems.com or calling 617-621-0700), since it would probably help for someone to dial into your system.

Nicole Aaron · Oct 2, 2017 go to post

Glad you found the source of the issue so quickly. I'm posting this as an answer so that your question will be marked as answered in the Developer Community.

Nicole Aaron · Sep 25, 2017 go to post

You can enter the arguments to pass into a Run/Debug Configuration here:

I'm not sure what you mean by the "select class file" that you are trying to pass in. Here is the method signature for %UnitTest.Manager/DebugRunTestCase:

ClassMethod DebugRunTestCase(testsuite As %String = "", testcase As %String = "", qspec As %String = "", testmethod As %String = "", ByRef userparam) As %Status

Which parameter are you trying to pass in?

Nicole Aaron · Sep 25, 2017 go to post

I added it as a comment because there is still an unanswered question (why the Server option is disabled in the Replace With menu). So I figured I'd leave the post without an answer until each of your questions has an answer.

Nicole Aaron · Sep 22, 2017 go to post

Hi John,

To answer your first question - I just looked over the development change that implemented the compare with server option. The developer commented that this has only been implemented in the Atelier Explorer context menu so far and that this feature will be coming up in the Editor context menu. I don't have a timeline for you on that.

I'll have to let someone from the development team speak to your second question. I'm not sure why the replace with server option appears and is disabled.

As a member of the Support team, I also wanted to let you know that you can absolutely file a WRC case with Atelier questions! The product options we provide are intended to find out which of our server products you are using. Feel free to ask any Atelier questions you'd prefer to keep separate from the Developer Community in the WRC (for example, if you have a question that you expect will require a lot of back-and-forth to reach a conclusion).

~Nicole

Nicole Aaron · Sep 7, 2017 go to post

Thanks for reporting this Peter. It looks like Atelier is not properly recognizing the end of a class' Query member. I found a couple other ways that this issue presents itself - a syntax error on the closing bracket of the class before you compile, and any class members following the Query are not listed in the Outline.

I logged this bug for the Atelier development team (internal reference ATL-4372).

Nicole Aaron · Aug 24, 2017 go to post

Hi Fred, I was not able to reproduce this behavior on my system. What version of Atelier are you using (Help > About Atelier)? What Caché/Ensemble/HealthShare server version (enter "write $zv" in a Caché Terminal)?

I work in the Support department, can you open a WRC case to investigate this further (email support@intersystems.com or call 617-621-0700)? Once we determine exactly what is necessary to reproduce we can post the results here in the Developer Community so this is public knowledge.

Nicole Aaron · Jun 7, 2017 go to post

The Atelier development team is actively working towards the 1.1 release. However we do not provide guaranteed timelines for the release of InterSystems products.

Nicole Aaron · Jun 1, 2017 go to post

Code completion for property parameters has not yet been implemented in Atelier. But it is on the roadmap and is planned for an Atelier 2.0 release.

Nicole Aaron · May 30, 2017 go to post

The Studio Inspector will not be implemented as-is in Atelier. However you can still view the same information in Atelier:

To see a class' properties, methods, parameters, etc. you can use the Atelier Outline view. That is shown in the answer to the DC post that Vitaliy linked to: https://community.intersystems.com/post/studio-view-inspector-atelier. Currently this shows only the members in the current class, not those that come from superclasses. A "Show Inherited" option is planned for an Atelier 1.1 release.

Nicole Aaron · May 24, 2017 go to post

You can use F3 in Eclipse to go to a declaration. This works for many of the use cases for F12 in Studio.

Nicole Aaron · May 16, 2017 go to post

Hi Shobha, here is the relevant documentation about using Ensemble with SOAP:

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…

This should give you some background about using Ensemble to send and receive SOAP messages. I would suggest reviewing this and letting us know if you have any specific questions, configuration problems, errors, etc. You can also reach out to Support or your InterSystems Sales team with more involved questions that might be easier to discuss on the phone rather than in the Developer Community.

Nicole Aaron · Apr 20, 2017 go to post

Hi Jean,

I tried out the Eclipse SQL Explorer and was able to connect to my local instance just fine. I installed the plug-in using the update site from the link you provided, http://eclipsesql.sourceforge.net/.

Then I opened the associated perspective by going to Window > Perspective > Open Perspective Other > SQL Explorer. I right-clicked in the Connections view and hit New Connection Profile. I had to select Add/Edit Drivers to add the Caché JDBC driver with these settings:

The keys were to 1) select the Extra Class Path tab and Add JARs to pick the JDBC driver from my Caché install directory and 2) to add the correct Driver Class Name, com.intersys.jdbc.CacheDriver.

Once I had that configured I selected it in the Connection Profile Wizard, entered my JDBC connection URL, jdbc:Cache://localhost:56773/SAMPLES, and selected the authentication information:

This also worked for me when I unselected "Username is not required", checked "Auto Logon" and entered my Caché credentials.

I right-clicked the connection and hit Connect. Then double-clicking the connection (listed as "Connected since <timestamp>") opened the connection in the Editor where I could enter my SQL statement:

Where are you running into problems?

Nicole Aaron · Mar 31, 2017 go to post

You can open the BPL graphical editor in Atelier by opening the class code, right-clicking anywhere on the code in the Editor and selecting "Open diagram editor".

As Joyce mentioned, there will also be a Developer Community post coming soon about the way to view the DTL/BPL graphical editors in the current version of Atelier.

Nicole Aaron · Mar 9, 2017 go to post

You can copy a whole package of classes or routines to an Atelier project. In the Server Explorer, right-click the package under the Classes or Routines tree and select Copy To Project. Pick the Atelier Project to copy to and on the next page of the wizard you should see a list of all of the classes or routines that will be copied over.

Nicole Aaron · Feb 14, 2017 go to post

That was true in older versions of InterSystems products, when cached query code was stored in routines rather than classes. A problem could occur if a query executing in one process required round trips from the client to server and a separate process purged cached queries while the client application was still using it. Development resolved this by moving the cached query code into classes - the class definition and OREF are now stored in memory until the client process is done executing the query. This makes purging cached queries safe on a live system in more recent versions.

The change was implemented starting with Caché 2010.2.0 for dynamic SQL and Caché 2012.2 for xDBC queries.

Nicole Aaron · Feb 14, 2017 go to post

I spoke with development and the fix for this bug will not be in the product until 2017.1 versions and later. (However I also haven't seen this behavior reported outside of 2014.x versions.)

Nicole Aaron · Jan 25, 2017 go to post

1. You can create a new legacy task (allows you to run COS code) in your application namespace from the System Management Portal: http://docs.intersystems.com/cache20141/csp/docbook/DocBook.UI.Page.cls…

The command to purge all cached queries in the current namespace is "do $SYSTEM.SQL.Purge()". That is described in our class reference here: http://docs.intersystems.com/cache20141/csp/documatic/%25CSP.Documatic…

2. I am checking in with development on which Caché version resolved this bug.

Nicole Aaron · Jan 18, 2017 go to post

Development did a code review and determined that this is a bug with the cached query generation code in Caché 2014.1. As far as I know we've only seen this for queries executed via xDBC.

There is a place in the cached query generation code where an error may not be properly trapped. In this case the cached query routines are not created properly, but no error is reported back. Then when Caché tries to use that cached query code to execute the query the expected methods do not exist.

The possible solutions we've come up with:

1. Create a task to purge cached queries in your application namespace - Pick a task frequency that means it will run more often than you have seen errors occur. This way you aren't stuck manually purging cached queries whenever an error pops up.

2. Get a development patch containing some fixes for your version of Caché - For this you will need to contact either your InterSystems Sales team or Support to file a WRC case. Note that our development patches do not go through our standard QD testing process. If you apply this patch you will be working with a version of our code that has not gone into any released product.

3. Upgrade your instance - This is the only long-term solution. Our cached query generation code has been rewritten in later versions of the product and this is no longer a problem.

Nicole Aaron · Dec 1, 2016 go to post

You can use the Outline view in Atelier for information about the current class' properties, parameters, class methods, etc:

There is an enhancement request to show inherited members in the Outline view which is currently planned for Atelier 1.1.

Atelier's code completion, which can be accessed by hitting ctrl+space, is also a good tool here. For example you can use code completion to quickly check the possible options for an index's keywords (with documentation):

Nicole Aaron · Nov 18, 2016 go to post

When you generate an HTML Zen Report that request is served through the web server. It looks like on your system: in the case of the IIS web server using the alias name rather than the IP address and IE 8+, some of the static files are not being served properly. I think this would be best investigated by Support in a WRC case. You can open up a new case by emailing a brief description to support@intersystems.com, or by calling the Support line at (617) 621-0700.