To import user and group information from a text file, you can:
use the Import
action:
/action=import&FileName=textfile.txt
configure a task using the ogs_text
library:
to replace all the information in the OmniGroupServer repository with the information in the text file, set GroupServerIncremental=False
. In this case, you should also set the TextFile
parameter, to specify the path of the file that contains the information:
[Text] GroupServerLibrary=ogs_text GroupServerIncremental=false TextFile=C:\Autonomy\OmniGroupServer\TextDir\mydata.txt
to configure incremental updates from text files, set GroupServerIncremental=True
. In this case, do not set the TextFile
parameter. Instead, set the TextDirectory
parameter to the path of the directory that contains the text files:
[Text] GroupServerLibrary=ogs_text GroupServerIncremental=TRUE TextDirectory=C:\Autonomy\OmniGroupServer\TextDir
Each text file written to the directory must have a file name in the format <RepostoryName>_<Index>
, where
<RepositoryName>
|
is the name of the repository. |
<Index>
|
is a number that counts up from 0, and specifies the order of the updates. For example, the changes listed in Text_0 are processed first, and then the changes in Text_1 , and so on. OmniGroupServer stores the index of the last processed file in a file named <RepositoryName>_LastProcessed . |
Whether you use the import
action or set up a task in the OmniGroupServer configuration file, the text files must be constructed as described in Construct the Text File
|