nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there any database implemented inside teamsite

pranav

Hi,

i was wondering about the management of internal data used by teamsite for its own use.

Howcome Teamsite is managing its internal information ?.
Is there any database which is embeded with teamsite ?

-Pranav
TS 6.1 with SP2 on Windows 2000(with SP4)

Edited by pranav on 06/24/05 05:31 AM (server time).

Find more posts tagged with

Comments

iwovGraduate

What kind of internal data/information are you talking about?
TeamSite keeps the internal information in a backing-store which is basically a file-system based repository.

nipper

Yes there is an emedded DB deep inside TS. You cannot get to it. It is not an Oracle/SQL like DB.

This keeps all the information about versions, files, etc. Why do you need to know ?

pranav

Why do you need to know ?

Few days back i was trying to remove workflows from my system, all the workflows.So, i simply deleted the workflow directory(all the steps i got from support center), inside iw-store directory.It worked perfectly fine and when i restarted the teamsite server again all tasks were gone.
Now my question is>>
I was wondering, how teamsite is keeping the information about each workflow job and the tasks ?
>Similarly, when i am storing files in different branches , how these informations are getting stored ?

-Pranav

stefanmaier

Hi,
my understanding is, that the directory /iw-store/workflow is a complete store, not the /iw-store directory itself.
E.g. you see the store like your other stores with "iwstat".
If you delete the whole directory /iw-store/workflow, you delete the whole store.
After restarting TS, it recognizes that there's no workflow store and creates a new one.

If you are talking about storing files in different branches, you're talking about a little piece of information inside of one store.
To understand how this little piece of information is stored, the backing store programmers should give some information :-),
'cause we have no official interface to look into a backing store and we can't edit some information there.

Can anybody give some feedback, if my understanding is right?

Regards
Stefan

pranav

Hi,
You have given me real good informations , thanks !! .But my mind generated one new query..

>>If iwstore/workflow is an individual store then this means if i create 5-6 new stores (like default) then all the workflows related to these stores and their respective branches will get stored in this single workflow floder /iwstore/workflow . am i right ?
If i am right then , if say tomorrow i delete one or two stores from the teamsite then what will happen to all those workflows which are still residing in the workflow folder.

-Regards,
Pranav

Adam Stoller

I believe the answer is - only delete the entire workflow store when you want to delete all traces of all workflows for all stores; and only delete a secondary store when you either know there aren't (or don't care if there are) any workflows associated with that store. It would be cleaner to determine which active tasks have areavpath's associated with the store targeted for deletion; determine those tasks' jobids; delete those jobs; then delete the store.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com