Actually
There is a method of performing development on a Terminal Server - which is a recommended method created by a JDE whitepaper written by Alan Jacot entitled "Remote Development Using Citrix and a Windows Terminal Server"
Of course, under the new KG3 - I spent about an hour looking for this whitepaper to no avail, so cannot provide a link right now.
However, the text is as follows :
In order to perform remote development through OneWorld® you need to ensure that you have the proper hardware. You will need to have at least the minimum requirements for a terminal server. You can find these on J.D. Edwards’ web site. You will also need additional disk space requirements. Since each remote development user will need their own path code, which is roughly 2.5 Gigabytes each.
Number of Users
Due to the higher impact of development work the number of users that you will be able to have on a single machine will be lower then a “normal” terminal server. Generally a terminal server can support 40 production users. You should be able to support 15 concurrent remote developers per terminal server.
Deploying a Package to the Remote Development Terminal Server
To deploy a package to the server you will need to use the add/remove programs application located in the control panel. This is the standard procedure for deploying a package to a terminal server. The only difference with a remote development server is that you need to manually copy the B7 directory into different directories.
Installing the OneWorld® package to the terminal server. Go to start/settings/control panel.
Double click on the add/remove programs icon. This will take you into the add/remove programs window. The example below is from a machine running Windows 2000, but Windows NT® is very similar.
Press the add new programs button. This will bring up a screen that asks you where you would like to install the software from. In windows 2000 press the floppy/CD-ROM button. Then press the browse button and find the OneWorld® client Install directory on your deployment server. You will need to have a mapped network drive to your deployment server.
Select the setup.exe in the OneWorld® client install directory on your deployment server. This will take you into the standard OneWorld® client installation. This will create a B7 directory, containing the OneWorld® client software, on your terminal server.
Directory Structure
In order to successfully accomplish remote development, on a windows terminal server, you must ensure that each remote developer has their own set of OneWorld® specifications. This means that developers will have their own path code or path codes, and system directory. What you need to do is create a directory with same name as the each of your remote developers’ Windows NT® logon. You then need to copy the contents of the B7 directory into this new directory. You will then have a directory similar to the example given below. You are doing this so that each remote user has their own OneWorld® specifications to work against and thus development work will not corrupt the server.
Example Directory Structure
Jacotall
PY7333
Bin32
Data
Include
Lib32
Make
Obj
Res
Source
Work
Spec
System
JDE.INI
Now that each remote developer has his or her own directory structure you now need to let the OneWorld® software know to use this directory structure. The way that a windows terminal server works with OneWorld® is that the JDE.INI file under the WINNT directory is copied into each users’ windows directory under the profile of each terminal server user. This is the JDE.INI file that you will need to modify for each user and ensure that it is kept up to date. You will need change the INSTALL section of each remote developer’s JDE.INI file to point the OneWorld® software to the correct directory structure on the windows terminal server. An example is shown below.
INSTALL
B7=D:\Jacotall
OWDEVELOPER GROUP
One of the final steps in creating a remote development server is creating a local user group named OWDEVELOPER. This local group is what enables the OneWorld® development tools on the terminal server, such as Forms Design Aid (FDA). The OneWorld® software is coded to look for this group if your remote developer’s NT login is a part of this local group then they will be able to use the OneWorld® design tools. This is why you need to add your remote developers’ NT login into this group.
Common Questions and Answers
Question:
Is Citrix a requirement for setting up a remote development terminal server?
Answer:
No, Citrix is not a requirement for setting up a remote development terminal server. However, the Citrix software does greatly enhance the performance of terminal servers and thus it is recommended that you use Citrix when setting up a remote development windows terminal server.
Question:
Does J.D. Edwards have any clients currently using remote development with through a windows terminal server?
Answer:
Yes, J.D. Edwards does have clients who have successfully implemented and are currently using remote development through a windows terminal server.
Hope that all helps. Sorry I couldn't find the link.