Hello Catrina; Generally speaking any server-side update of data will have disruptive effects on client sessions.
<<If users are in Oracle hierarchies in TopBraid Live and we want to refresh the workspace, what happens to the TopBraid Live sessions?>> Workspace refresh will have the same impact on Oracle back-ends as the below. For liveCache, any changes made outside of TBL invalidates the write-through cache and cannot be known by the cache. Therefore changes made to Oracle RDF outside of TBL require that the cache be explicitly re-generated through a TBL reset. <<Will the cache refresh without interfering with processes that are running and querying the data?>> In principle, if the only changes occurring in the workspace is to files that are under TBL server control, then scripts and sessions should run without disruption. But if any file changes outside of TBL control (i.e. some other software changing files in the TBL workspace), then there is a potential for inconsistencies in sessions and the execution of scripts from files changing in midstream. It would be highly recommended to clear all sessions before refreshing the workspace, particularly if files have changed, as running scripts could end up working on stale data files. <<What repercussions should we be aware of?>> The main set of repercussions is the danger that client-side data and in-process scripts will start with data that is rendered stale (invalid) by the workspace refresh. I.e. the data previously served is different after the workspace refresh, causing inconsistencies in the data. The advice, that is given for any client-server architecture, is that changes that are not controlled by server software (e.g. back-door data changes followed by workspace refresh) require that all sessions are cleared before performing a refresh that modifies data. -- Scott On Dec 9, 10:14 am, Catrina <[email protected]> wrote: > Our TopBraid Live is configured with the cacheAll enabled. If users > are in Oracle hierarchies in TopBraid Live and we want to refresh the > workspace, what happens to the TopBraid Live sessions? The workspace > refresh that I refer is through TopBraid Live -> TopBraid Live Server > Administration -> Refresh Workspace. > > Is it safe to refresh the workspace while users are in the Oracle > hierarchies and running SPARQLMotion scripts that run queries against > the hierarchies? > > I notice that when a refresh occurs, all of the Oracle rdf models are > closed and reopened. I see this from our tomcat logs: > [TopBraid Info] org.topbraid.eclipsex: Opening Oracle Model: GSI_DEV > (8) > [TopBraid Info] org.topbraid.eclipsex: Related info: path=/live/ > user=hieruser > [TopBraid Info] org.topbraid.eclipsex: Closing Oracle Model: GSI_DEV > (7) > [TopBraid Info] org.topbraid.eclipsex: Related info: path=/live/ > user=hieruser > > Will the cache refresh without interfering with processes that are > running and querying the data? What repercussions should we be aware > of? > > Thanks, > Catrina -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
