Disabling OL In Xe/ERP8.0

Hi List


It has just come to my notice, that by a setting in the jde.ini file, developers can access, the old OL and bypass the OMW altogether.


This has recently led to problems, like corruption of specs.


Does anyone know, how to disable the use of OL in XE/ERP8.0, even if the particular setting has been made in jde.ini.


Thanks


Yogi
Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com
Buy the best in Movies at http://www.videos.indiatimes.com
Now bid just 7 Days in Advance and get Huge Discounts on Indian Airlines Flights. So log on to http://indianairlines.indiatimes.com and Bid Now !



Dep Svr: ERP 8.0, Win2K AS, SP19.1
Data Svr: Oracle, Sun
Ent Svr: ERP 8.0, SUN

You can lock down the P9860 in Security Workbench.

DeRay Scholz
CNC / DBA
[email protected]
dj Orthopedics, LLC

I have been unable to test this but I have heard that running the application P99999 (Terminate Developers that use OL) will address this issue.

And you can find that object in the special \B666 pathcode, under daemons and other special tools.

db

You can do this by securing the P9860 and other applications from the group and or users that you do not want to have access. In te past, I secured this from *PUBLIC to keep all people out.

Andy

Yes you should sucure it. But, that will not keep a bright developer out of it. They'll just copy it to another name to avoid the security.

you have to secure it from the workbench, then i guess you have also to try to check it out from the server to your workstation, and get the token....(from the omw)...i guess it will be hard for any devil....sorry developer to make a copy from it (in case you have a very tide OMW rules)...what you think?????

Do you need the token to copy an object? I've not found that to be an issue. Is that an OWM rule you set up?

"bright" is one word for that developer. i have a few other things to call that developer; something like "unemployed" comes to mind.
Dave