Before running the importer, you should have installed the pi-nuxeo-marketplace-x.x.x-mp.zip package into Nuxeo.
You should also have logged into the Nuxeo GUI, and created a workspace called 'Patricia' and a folder named 'Documents' in 'Patricia' workspace.
Change nuxeo.conf file and make JVM parameters are set properly. For example:
JAVA_OPTS=-Xms1024m -Xmx2048m -XX:MaxPermSize=2048m -server -Dfile.encoding=UTF-8 |
References:
Also execute the following (if needed) in the Patricia database:
update PAT_DMS_SETTINGS set DMS_SETTING_VALUE='false' where DMS_SETTING_KEY='file.import.completed' |
The files to be imported must be accessible by the Nuxeo server. In order for the importer to have access to the files, you must mount or copy the old Patricia (P:) file share onto the nuxeo machine. It's more reliable to copy the files to the Nuxeo server instead of mounting.
Example mount command: linux (dom=YOURWINDOMAIN may not be needed):
mount -t cifs //server_ip_address/Patricia -o user=username,pass=mypass,dom=YOURWINDOMAIN /mnt/Patricia Example mount command: MS Windows
net use p: \\server_ip_address\\patricia
|
Download pi-nuxeo-importer.zip from here: pi-nuxeo-importer.zip
After the pi-nuxeo-importer.zip is downloaded, unzip it to a folder, e.g: $HOME/pi-nuxeo-importer/
Edit config.py file, and change parameters according to the Nuxeo server information.
The first step is to create top level Nuxeo folders, for example:
by simply using a script:
cd ~/pi-nuxeo-importer python create_folders.py |
In this step, we run a script to generate import URLs in a text file.
cd ~/pi-nuxeo-importer python generate_urls.py |
In this step, we run a script to import documents by using the URLs text file generated in previous step.
cd ~/pi-nuxeo-importer python import_urls.py |
You can access the logs via the following command. You can also just use a web browser to accessing: http://127.0.0.1:8080/nuxeo/site/fileImporter/log.
cd ~/pi-nuxeo-importer python log_monitor.py |
You will know that the import is finished when the content of the log remains static, and ends with an import summary referencing 'SimonWatch' toolset, on the console.
After the import is finished, the import finalization operation should be started (or, it will be run automatically at midnight).