I just wanted to share a couple other Atelier tools I find useful that have some similar functionality to the Studio Inspector. The first is the Atelier Outline View. This shows the currently defined members of a file (parameters, properties, methods, etc):

The second tool is the Quick Outline, which you access using cmd+O on Mac or ctrl+O on Windows. The first time you hit cmd+O/ctrl+O you will see a list of members defined in the current class:

You can then hit cmd+O/ctrl+O again to show the inherited members, along with which class each member comes from. The inherited members show up in a lighter gray font instead of black:

You can also start typing in this box to narrow down the list:

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.

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?

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).

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.

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


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.

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?

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.

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):

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.

When you try to start Atelier with the wrong version or bitness of Java installed, you will see that error pop up. There are a few things you can check when this occurs:

1. In an OS command prompt, enter “java –version” to display something like:

java version "1.8.0_51"

Java(TM) SE Runtime Environment (build 1.8.0_51-b16)

Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

This shows the version and the bitness of the Java version installed on your machine. So this can help make sure you are meeting a couple of requirements:

A. You need the Java JDK or JRE version 1.8 (JDK for Mac, JRE for other platforms)

B. The bitness of Java must match the bitness of your Atelier client. I’ve seen that a 64-bit install indicates that it is 64-bit in the "java –version” output. But for a 32-bit version of Java, no bitness is listed in the "java –version” output.

2. Check your JAVA_HOME environment variable. Make sure that if this is set that it is pointing to your Java JDK/JRE with the correct version and bitness.

On a Mac,  you can check the location of your Java 1.8 home directory with the Terminal command: /usr/libexec/java_home -v 1.8. On a Windows machine, you can enter this in a Command Prompt: where java.