Terminal Server-- Create/Modify Versions?

We have OneWorld Xe SP19.1, Update 6.
The majority of our clients work through Terminal Server (TSE). We have seen that the TSE clients can make a copy of a version and check it in to the server. But the TSE clients can't check out an existing version from BV or from OMW.

Is this a limitation of TSE, or do we have something configured incorrectly? What limitations do we have in TSE as far as checking in/out, creating new versions, etc.?

Thanks in advance.
--
Tim in Barcelona

Tim,

Numerous posts on this topic. First off, you DON'T want users having the
ability to check in/out things on a terminal server, especially on
production WTS boxes...the chance for spec file corruption is too great.

With that said, yes, there is a built in limitation on the WTS platform
that prohibits the checkout/in process. This limitation can be
de-activated. You can also set up a WTS so that full development can
occur if you so desire.

If you need the document, let me know, I can e-mail it to you.

Regards

________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com

Hi Tim,

Yes that is a limitation of TSE. By design JDE does
not allow check-outs on a TSE box because that is a
development function which is not supported on TSE.
You are allowed to create versions and check them in
as you noticed but that's it. You can not check it
out again unless you go to a standard fat client.

Happy New Year!
--- timallen <[email protected]> wrote:
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=47365


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Tim, Haven't seen you lately on Tool Time lately, but did love the SANTA 2
movie!!

Seriously though... We have seen this also after going from B7332 to XE last
year or maybe in one of the newer SP. Apparently it is a design decision by
JDE to try and control versions. To modify versions, JDE want you to use
OMW using a FAT client. I never did figure out how the code determines that
the user is a TSE but it is buried deep in there somehow.





Tom Crawford

Right : it's a limitation of TSE clients. TSE Clients can't get or check out any objects previously checked in but they can create some objects : I'm sure that's true for versions and report templates but I don't know if you can create for instance applications or other objects with TSE. There are some papers on KG that will inform you more.

There's a paper fix on KG for this. I can't remember the name.

There is also a change in jde.ini. Add line OWDEVELOPER=TRUE under [DEBUG] section.

and i know one way should work:

create a local group on ur computer named :'owdeveloper', and add ur logon ID in it,
logoff and logon again ,
it should work now.

bee

Hi

I would also like to get the copy of that document. Would Appreciate it.

Thanks,
Manoj G Kidiyoor
[email protected]

Xe SP 20, SUN Oracle 8.1.7

That will not work after SP17.1

it works fine on 18.1 and 19.1 as well as SP20 ! Used it today on 19.1 with no issues !

Just ensure that you spell it correctly....

I was referring to creating the owdeveloper local group and I forgot that we were talking only about version development and not full development.

Thanks for correcting my error.