From MdsWiki
| Revision as of 16:00, 16 November 2016 (edit) Twf (Talk | contribs) (→Older builds can be found below) ← Previous diff |
Revision as of 16:04, 5 September 2017 (edit) Jas (Talk | contribs) Next diff → |
||
| Line 4: | Line 4: | ||
| ==== Java Applications ==== | ==== Java Applications ==== | ||
| MDSplus for Windows no longer includes the Java Run-time Environment in the installation kit. To run the Java applications (jScope and Traverser) provided with the MDSplus installation, you will need to also install either a Java Run-time Environment (JRE) or the Java Development Kit (jdk). These kits can be found on at http://www.oracle.com. Be sure to install either a JRE or a JDK kit found in "Downloads for developers". The download on the Oracle site entitled "Java for your computer" provides only the browser support for Java and is not sufficient to run the Java applications provided with MDSplus. | MDSplus for Windows no longer includes the Java Run-time Environment in the installation kit. To run the Java applications (jScope and Traverser) provided with the MDSplus installation, you will need to also install either a Java Run-time Environment (JRE) or the Java Development Kit (jdk). These kits can be found on at http://www.oracle.com. Be sure to install either a JRE or a JDK kit found in "Downloads for developers". The download on the Oracle site entitled "Java for your computer" provides only the browser support for Java and is not sufficient to run the Java applications provided with MDSplus. | ||
| + | ==== MDSIP over SSH ==== | ||
| + | MDSIP connection strings optionally contain a protocol clause, preceding the hostname. For example: | ||
| + | ssh://user@host-ip-address/ | ||
| + | These can be used in mdsconnect calls, in thick-client tree specifications and in distributed client subtree search paths. To use ssh as the mdsip transport under windows an ssh client must be installed that supports windowless connections. Putty [http://www.putty.org/] will work, but SecureCRT will not. If using putty, follow the steps for setting up an ssh key without password, and installing its public part in your authorized_keys on the host computer you are connecting to. Put the private part of the key in some secure location on your PC. Then create a script called ssh.bat someplace in your PATH containing something equivalent to: | ||
| + | "C:\Program Files\putty\plink" -i full-file-spec-of-your-id_rsa.ppk %1 | ||
| + | You should then be able to define thick client trees: | ||
| + | w7x_path ssh://your-account@mds-trm-1.ipp-hgw.mpg.de:: | ||
| + | In your system environment variables. Or to mdsconnect | ||
| + | mdsconnect('ssh://your-account@mds-trm-1.ipp-hgw.mpg.de') | ||
| + | |||
| === Installation Kits === | === Installation Kits === | ||
| The following table lists the latest MDSplus kits for Microsoft Windows systems. If you are using a 64-bit Windows distribution then install the 64-bit version of MDSplus otherwise install the 32-bit version. You should not need to install a 32-bit version on a 64-bit version of windows. | The following table lists the latest MDSplus kits for Microsoft Windows systems. If you are using a 64-bit Windows distribution then install the 64-bit version of MDSplus otherwise install the 32-bit version. You should not need to install a 32-bit version on a 64-bit version of windows. | ||
Revision as of 16:04, 5 September 2017
Contents |
Special Configuration Steps
Java Applications
MDSplus for Windows no longer includes the Java Run-time Environment in the installation kit. To run the Java applications (jScope and Traverser) provided with the MDSplus installation, you will need to also install either a Java Run-time Environment (JRE) or the Java Development Kit (jdk). These kits can be found on at http://www.oracle.com. Be sure to install either a JRE or a JDK kit found in "Downloads for developers". The download on the Oracle site entitled "Java for your computer" provides only the browser support for Java and is not sufficient to run the Java applications provided with MDSplus.
MDSIP over SSH
MDSIP connection strings optionally contain a protocol clause, preceding the hostname. For example:
ssh://user@host-ip-address/
These can be used in mdsconnect calls, in thick-client tree specifications and in distributed client subtree search paths. To use ssh as the mdsip transport under windows an ssh client must be installed that supports windowless connections. Putty [1] will work, but SecureCRT will not. If using putty, follow the steps for setting up an ssh key without password, and installing its public part in your authorized_keys on the host computer you are connecting to. Put the private part of the key in some secure location on your PC. Then create a script called ssh.bat someplace in your PATH containing something equivalent to:
"C:\Program Files\putty\plink" -i full-file-spec-of-your-id_rsa.ppk %1
You should then be able to define thick client trees:
w7x_path ssh://your-account@mds-trm-1.ipp-hgw.mpg.de::
In your system environment variables. Or to mdsconnect mdsconnect('ssh://your-account@mds-trm-1.ipp-hgw.mpg.de')
Installation Kits
The following table lists the latest MDSplus kits for Microsoft Windows systems. If you are using a 64-bit Windows distribution then install the 64-bit version of MDSplus otherwise install the 32-bit version. You should not need to install a 32-bit version on a 64-bit version of windows.
There are currently three flavors of MDSplus builds:
| Flavor | Description |
|---|---|
| Stable | Stable builds are updated less frequently but tend to be more robust and well tested. No new features are added to the stable builds until they have been tested thoroughly by users of the Beta or Alpha distributions. |
| Alpha | Alpha builds are updated frequently and represent builds of the head of the git repository. New features (and bugs) can appear at any time. You should not use the Alpha kits on any production system. |
The following are the latest builds. If you are upgrading from a 6.x release of MDSplus you will need to first manually deinstall your installed version before installing a 7.x version. This is because the installation utility used has changed in 7.0 and does not recognize pre-7.0 installations.
Below is the last 6.x version created: