We've had that same question and although it does not appear that the
users have corrupted any objects I believe there is still a risk. Chances
are that if a user is accessing an object in the persistent objects
tables, they will lock it only long enough to load it into Cache and then
release the lock. I highly doubt that this lock would last long enough
for the eGen to time out on the record so like I said - the chance of
corruption should be minimal. Just be sure to clear your caches after
your eGen is done so that the users get the updated specs.
What we have done to be SURE there is no chance of corruption is use our
Save Location as an alternate space for the eGen. We have a save location
that we use for development which is essentially a complete spare set of
specs which includes persistent objects tables. (See "Creating a Save
Location" document on KG)
During Production: The users are logging in to JPD and the OCM's are
pointing F989998 and F989999 to COPD9
- When we want to eGen we point the eGen machine's JDBj.INI file to COSV9,
- eGen JPD9 into COSV9
- When the eGen is done we have a set of OCM mappings for PD9 and JPD9
that point to COSV9 that are inactive.
- We Activate the four COSV9 OCM entries, Deactivate the four COPD9 OCM
entries for the persistent objects tables
- Clear the JDBJ Caches in SAW and voila! The users are all now pointing
to the new tables and there was NO web down time.
We don't care if the fat clients refresh their OCM's because they don't
look at the F989998 and F989999 tables anyway. So why change those
OCM's? Just in the interest of completeness and if you, as a CNC, ever
use UTB to have a look into them you want to be sure you are looking at
the right tables.
The next time we eGen we use COPD9 and reverse the whole process
effectively flip-flopping between the two sets of persistent objects. Just
check your OCM and JDBj.INI before each eGen to be sure you use the right
set.
Regards,
Gerald.
tiefenbs <
[email protected]>
Sent by:
[email protected]
07/18/2005 11:53 PM
Please respond to
JD Edwards=AE EnterpriseOne
To
[email protected]
cc
Subject
Generating Objects with users accessing objects on Web server
When generating objects do we need to lock out users from the web server
so that users do not access the objects while thgey are being generated.
Most we can get from people so far is that it SHOULD be ok, but have heard
that if a user accesses a object as it is being generated it may corrupt
it. We have done testing and it does seem to be ok, but can any one
confirm this for us.
EP One 8.10, Tools Release: 8.93.N1 Fat Client, Citrix XE and Portal.
Windows Server 2003, SQL 2000, Create Print, Olapworks