Here's what I recommend (assumes you are using Server Manager extension as well; can be done without it but you'll have to edit JSON in a file):
In Server Manager's tree, expand the namespaces of your server.
Clock the "eye" icon on the %SYS row. This will add another root folder to your VS Code workspace. The folder uses the `isfs-readonly` scheme to access the namespace directly.
In VS Code's Explorer (not ObjectScript Explorer), expand that folder and drill down to find the class you want.
Assuming you want to use this multi-root workspace again, use "Save Workspace As..." from the File menu. If you don't, you'll be prompted when you exit VS Code and given a choice of saving or discarding.
Good video. One tip I have is that at 4:18 it advises using a command to add second and subsequent folders to a multi-root workspace. Instead I recommend clicking on the InterSystems Tools icon in the Activity Bar, then using the Servers tree (contributed by the Server Manager extension) to find your server and namespace, then clicking the pencil button (Edit Code in Namespace). This adds an isfs entry to your workspace. The eye button alongside it will add an isfs-readonly entry instead.
Indeed you can do the whole of the workspace creation from that tree. With nothing open in VS Code (no folder, no workspace) click all the pencils or eyes you want. To name and save your workspace use "Save Workspace As..." from the File menu. If you haven't done that by the time you close the VS Code window you will be prompted to save or discard the as-yet-untitled workspace. So if you just wanted to browse a server speculatively you can use an untitled workspace and discard it when you exit.
May I suggest you edit the post and change the language at the top of the CodeSnippet elements so they're set to JavaScript instead of ObjectScript? Or if you prefer, ask me and I'll do it using my DC Moderator powers.
In the intersystems.servers object in your settings JSON you can add a pathPrefix property within the webServer object of your connection definition. In your example:
Turns out it wasn't hard to add this. Download and install 1.8.2-beta.2 if you want to try it out.
Only the editable file gets coloured, not the preview. It may be possible to address that, but would require more work than I have time for at the moment.
Instead of adding the %All role to the /terminalsocket web app I suggest you add %DB_IRISLIB which should be sufficient to solve your issue.
My guess is, this environment used to give public %DB_IRISLIB:R but then someone tightened security by removing this, around the time you upgraded WebTerminal.
UnknownUser is normal for the /terminalsocket session.
Does the problem also occur if you start from an incognito/InPrivate instance of your web browser?
Previously you reported that WebTerminal is working OK on another of your InterSystems environments. Is this still the case? Is that one using 4.9.5 yet?
For the one that fails to make the websocket connection I suggest you use F12 in your browser to open Developer Tools, and make sure network tracing is active before you go to the /terminal/ URL to open a WebTerminal. Look at the network trace messages, and compare them to equivalent messages from a different web browser session that connects successfully to WebTerminal on your other environment.
I'm not clear whether WebTerminal ever worked on this InterSystems instance, e.g. with WebTerminal 4.9.3.
Maybe also worth checking what the InterSystems security audit log is showing around the time you fail to connect with WebTerminal. You may need to turn this auditing on, and perhaps enable it for some additional event types.
As long as the XML import compiled the classes, there's nothing else you need to do in order to benefit from the update.
I suggest you stop using WebTerminal for at least 15 minutes, then check in Portal's Web Sessions page (under System Operation) that no /terminalsocket sessions remain.
Next, launch a WebTerminal. Confirm it reports being version 4.9.5. Check that the Web Sessions page shows one /terminalsocket entry. Now close your WebTerminal browser. Refresh the Web Sessions page. The /terminalsocket entry should no longer be there.
WebTerminal 4.9.5 is now available. After updating to this you should no longer see /terminalsocket web sessions hanging around for 15 minutes after WebTerminal browser windows have been closed.
When comparing between an environment that works and the one that doesn't, did you also check the settings of the /terminalsocket application? If not, please do that.
go to post
Here's what I recommend (assumes you are using Server Manager extension as well; can be done without it but you'll have to edit JSON in a file):
Assuming you want to use this multi-root workspace again, use "Save Workspace As..." from the File menu. If you don't, you'll be prompted when you exit VS Code and given a choice of saving or discarding.
go to post
Good video. One tip I have is that at 4:18 it advises using a command to add second and subsequent folders to a multi-root workspace. Instead I recommend clicking on the InterSystems Tools icon in the Activity Bar, then using the Servers tree (contributed by the Server Manager extension) to find your server and namespace, then clicking the pencil button (Edit Code in Namespace). This adds an isfs entry to your workspace. The eye button alongside it will add an isfs-readonly entry instead.
Indeed you can do the whole of the workspace creation from that tree. With nothing open in VS Code (no folder, no workspace) click all the pencils or eyes you want. To name and save your workspace use "Save Workspace As..." from the File menu. If you haven't done that by the time you close the VS Code window you will be prompted to save or discard the as-yet-untitled workspace. So if you just wanted to browse a server speculatively you can use an untitled workspace and discard it when you exit.
go to post
How intriguing Rob.
May I suggest you edit the post and change the language at the top of the CodeSnippet elements so they're set to JavaScript instead of ObjectScript? Or if you prefer, ask me and I'll do it using my DC Moderator powers.
go to post
It won't necessarily be the instance name, depending on how the external web server has been set up.
go to post
Documentation at https://intersystems-community.github.io/vscode-objectscript/configurati... has now been updated to include this information.
go to post
In the intersystems.servers object in your settings JSON you can add a pathPrefix property within the webServer object of your connection definition. In your example:
"intersystems.servers": { ... "server1": { "webServer": { "host": "localhost", "port": 443, "scheme": "https", "pathPrefix": "/instance1" } }, ... }go to post
Please open an issue at https://github.com/intersystems-community/vscode-objectscript/issues
Screenshots can be pasted from clipboard direct into GitHub.
Thanks.
go to post
Interesting. Based on doc at https://docs.intersystems.com/healthconnectlatest/csp/documatic/%25CSP.D... the common attribute of all the faultily-displaying properties is that they are calculated. Does that hold true for the ones not shown in your screenshot?
go to post
Turns out it wasn't hard to add this. Download and install 1.8.2-beta.2 if you want to try it out.
Only the editable file gets coloured, not the preview. It may be possible to address that, but would require more work than I have time for at the moment.
go to post
Were you logged in as a user with the %All role when you clicked the update link in WebTerminal?
go to post
I haven't seen this problem.
The GitHub source of this method doesn't seem to check the status of its ParseStream call before trying to read the stream:
Maybe your upgrade procedure went wrong. I suggest you download the XML distribution and import it again.
go to post
One way is to use my webterminal-vscode extension in conjunction with the WebTerminal package.
go to post
An example is shown in https://community.intersystems.com/post/use-serenji-debug-your-rest-serv...
go to post
The Serenji VS Code extension from George James Software supports direct backend debugging of REST endpoints in Caché and InterSystems IRIS.
The debugging features of Serenji require an activation key. We provide free 30-day keys upon request.
John Murray
Senior Product Engineer
George James Software
go to post
Maybe you need to sign up on the Columnar Storage Early Access Program at https://gs2022.isccloud.io/#early-access
go to post
Instead of adding the %All role to the /terminalsocket web app I suggest you add %DB_IRISLIB which should be sufficient to solve your issue.
My guess is, this environment used to give public %DB_IRISLIB:R but then someone tightened security by removing this, around the time you upgraded WebTerminal.
Such a change ought to show up in the audit log.
go to post
UnknownUser is normal for the /terminalsocket session.
Does the problem also occur if you start from an incognito/InPrivate instance of your web browser?
Previously you reported that WebTerminal is working OK on another of your InterSystems environments. Is this still the case? Is that one using 4.9.5 yet?
For the one that fails to make the websocket connection I suggest you use F12 in your browser to open Developer Tools, and make sure network tracing is active before you go to the /terminal/ URL to open a WebTerminal. Look at the network trace messages, and compare them to equivalent messages from a different web browser session that connects successfully to WebTerminal on your other environment.
I'm not clear whether WebTerminal ever worked on this InterSystems instance, e.g. with WebTerminal 4.9.3.
Maybe also worth checking what the InterSystems security audit log is showing around the time you fail to connect with WebTerminal. You may need to turn this auditing on, and perhaps enable it for some additional event types.
go to post
As long as the XML import compiled the classes, there's nothing else you need to do in order to benefit from the update.
I suggest you stop using WebTerminal for at least 15 minutes, then check in Portal's Web Sessions page (under System Operation) that no /terminalsocket sessions remain.
Next, launch a WebTerminal. Confirm it reports being version 4.9.5. Check that the Web Sessions page shows one /terminalsocket entry. Now close your WebTerminal browser. Refresh the Web Sessions page. The /terminalsocket entry should no longer be there.
go to post
WebTerminal 4.9.5 is now available. After updating to this you should no longer see /terminalsocket web sessions hanging around for 15 minutes after WebTerminal browser windows have been closed.
This should help with license starvation issues.
go to post
When comparing between an environment that works and the one that doesn't, did you also check the settings of the /terminalsocket application? If not, please do that.