altquark
Legendary Poster
I was indeed wondering when you were asking this question. Actually, JD Edwards have created and distributed a whitepaper entitled "Remote Development Using Citrix and a Windows
Terminal Server" written by Allen Jacot on 2/16/2001.
It is possible, first of all, to install Administrative Mode Terminal Services on the Deployment Server and remotely control package builds etc etc - as long as the user is the sole user on the Deployment Server. I always check to ensure that there are no other users logged in through TSAdmin.exe.
However, if you are looking for large scale remote development and the ability to promote projects and perform client-side update packages remotely (as with a larger enterprise development environment) - then read Allen's document.
In effect, the document is indeed simple in its ideas. The idea is to install oneworld for EACH development user - in their own directory. Of course this uses up significant amount of Hard Drive space (which of course is relatively cheap) - but as long as developers have their own specifications on the terminal server, they do not impact each other.
We have set this up for a customer that has outsourced much of its development to India. During the night, there are at least 25 concurrent developers on the system - and at the overlap between US Timezone and India, there can be as many as 50 developers on the Terminal Server at one time.
However, there are some caveats to Allens document.
1. The development environment should only be set up on a single Terminal Server - having users mapped across a network could cause significant delays in development, although a Gigabit connection to a common share might work well.
2. Do not push out or update the developers packages. Let the developers check out their own objects. If you need to install a new full package, then you will have to copy the package to each instance of the developers home share. This could take significant time, but is much easier than pushing to developer FAT workstations.
I will happily distribute this document if required, however there was a SAR that stated the following :
Title 5434042 REMOTE DEVELOPMENT USING CITRIX / WTS SystemH97
Document Detail Show detailed information.
Call Number 05434042
Status 900 - Closed / Complete
Product OneWorld Technical > Platform Support & CNC
Queue 111141 - OW Tech Platform Support
Reference Call (none)
Taken by Owens, James 7075911
SAR Number (none)
System Code H97 - Benchmarking/Performance
Program ID OTPTSE - Terminal Server
Release Xe
Cum Level C03
Service Pack SP20
Operating System WIN
Platform MICRO
Call Reason C - Code Change
Call From PAUL SHEARER
Customer 7050799 - Agilera, Inc.
Business Partner 7050799 - Agilera, Inc.
Date Received 2003-01-03
Date Returned 2003-01-03
Date Completed 2003-01-23
Description
<Q>
Client wants a copy of a document developed by GATS title "Remote Development
Using Citrix and a Windows Terminal Server".
<A>
Researched for the GATS contacts in the Knowledge Garden. After they verified
if this document can be shared with this BP, they forwarded a soft version of
the document to me, which I forwarded to the BP. It is important to note that
GSS does not enordse this document and will not support any problem that arises
if following the techniques in the document.
This means that although JDE is writing and distributing the document, they are not necessarily supported through GSS - if this is important, then I recommend not performing the instructions. I myself fully support Allen Jacot's document and believe it is an excellent - and probably the only method to implement remote development functionality.
Terminal Server" written by Allen Jacot on 2/16/2001.
It is possible, first of all, to install Administrative Mode Terminal Services on the Deployment Server and remotely control package builds etc etc - as long as the user is the sole user on the Deployment Server. I always check to ensure that there are no other users logged in through TSAdmin.exe.
However, if you are looking for large scale remote development and the ability to promote projects and perform client-side update packages remotely (as with a larger enterprise development environment) - then read Allen's document.
In effect, the document is indeed simple in its ideas. The idea is to install oneworld for EACH development user - in their own directory. Of course this uses up significant amount of Hard Drive space (which of course is relatively cheap) - but as long as developers have their own specifications on the terminal server, they do not impact each other.
We have set this up for a customer that has outsourced much of its development to India. During the night, there are at least 25 concurrent developers on the system - and at the overlap between US Timezone and India, there can be as many as 50 developers on the Terminal Server at one time.
However, there are some caveats to Allens document.
1. The development environment should only be set up on a single Terminal Server - having users mapped across a network could cause significant delays in development, although a Gigabit connection to a common share might work well.
2. Do not push out or update the developers packages. Let the developers check out their own objects. If you need to install a new full package, then you will have to copy the package to each instance of the developers home share. This could take significant time, but is much easier than pushing to developer FAT workstations.
I will happily distribute this document if required, however there was a SAR that stated the following :
Title 5434042 REMOTE DEVELOPMENT USING CITRIX / WTS SystemH97
Document Detail Show detailed information.
Call Number 05434042
Status 900 - Closed / Complete
Product OneWorld Technical > Platform Support & CNC
Queue 111141 - OW Tech Platform Support
Reference Call (none)
Taken by Owens, James 7075911
SAR Number (none)
System Code H97 - Benchmarking/Performance
Program ID OTPTSE - Terminal Server
Release Xe
Cum Level C03
Service Pack SP20
Operating System WIN
Platform MICRO
Call Reason C - Code Change
Call From PAUL SHEARER
Customer 7050799 - Agilera, Inc.
Business Partner 7050799 - Agilera, Inc.
Date Received 2003-01-03
Date Returned 2003-01-03
Date Completed 2003-01-23
Description
<Q>
Client wants a copy of a document developed by GATS title "Remote Development
Using Citrix and a Windows Terminal Server".
<A>
Researched for the GATS contacts in the Knowledge Garden. After they verified
if this document can be shared with this BP, they forwarded a soft version of
the document to me, which I forwarded to the BP. It is important to note that
GSS does not enordse this document and will not support any problem that arises
if following the techniques in the document.
This means that although JDE is writing and distributing the document, they are not necessarily supported through GSS - if this is important, then I recommend not performing the instructions. I myself fully support Allen Jacot's document and believe it is an excellent - and probably the only method to implement remote development functionality.