Object Importer/Object Exporter

[JennieBee]

I need to take folder structures with permissions and cats/atts from 1 Livelink test instance and have them input into a Training and a Production instance. We are very new to Livelink, and the documentation doesn't tell me what a control file is, how to output the data to store all the file names/perms/cats/atts, and how to bring it back in. 9 pages, saying you need a log file, destination file, and control file, but not explaining how to export the data is killing me. (sorry for the whining!)

I have been backed into a corner of doing this export/import in a matter of 2 days time, and we have no one in house who knows livelink but me, and I am just learning as I go. Please, please help me if you can!

LL 9.7.1

 

[mikepycroft]

Here is the process I use. Works Ok for normal folders and documents. Issues with with workflows & form templates.

Moving Livelink Objects using XML Export and Import

Ref: Section 13 of the Livelink ECM System Administration manual.

Objective:

To move the contents of a folder, workflow, form template, forms and webreports from the sandpit environment into the live one.

Method:

1. To create the export xml the following suffix needs to be added to the system URL. Where the objid is the object to be exported such as a folder or document.
Scope = sub – includes all sub documents
Content=base64 – is the actual contents of the documents

System URL:
http://systemName/livelink/llisapi.dll
Suffix:
?func=ll&objId=153104&objAction=xmlexport&viewType=1&scope=sub&nodeInfo&attributeinfo&nodeinfo&versioninfo=all&content=base64

2. Cut and paste the suffix onto the system url and the xml export file will appear in the browser. Save this file to the server.



3. On the server log in using an admin account and go to the admin.index pages.

4. To create the import URL add the following suffix to the system URL. Where the objid is the location where you want to import the items and the filename is the location and file name of the export file.
NOTE: This needs to be done on the server.

?func=admin.xmlimport&filename=d:\tmp\Proceduers.xml&objid=35452

 

[appnair]

I wish I could write something out to help you but it is all very clearly explained in the manaul under the module directory.

For eg

First on the instance of data to be exported,RDP into that livelink server,I usually do it on the Admin server.

Create preferably somewhere a folder called OE.For parctical purposes make it a share if there is more than one livelink OE involved.Underneath it create three folders called Working,Log and Destination.

Then log into livelink and thru func=admin.index and find the link called OE admin.

Now under Configure
Enter these:
Working:\\machinename\OE\Working\
Log:\\machinename\OE\Working\
Destination:\\machinename\OE\Working\
Advanced
Objects Per Batch:1000

Click the manaual object Export

Add a log file name like temp.log

In the control file copy this code and save as xml

<?xml version="1.0" encoding="UTF-8"?>
<export>
<node>
     <location>Enterprise</location>
     <docstorage>\\machinename\OE\Destination\</docstorage>
</node>
</export>

See if that works.You are then supposed to take the resultant file and the folder to the target and consume it with OI similar stuff.It is there in the manaual.Not sure if permissions will come or not.Also cats/atts of first sytem has to be created intarget system using xml export/import as well.I usuallu have a excle worksheet that has all the permissions written and I use it on the target system.


Also cloning systems is all possible,you will need to follow some documentation for that.


Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[appnair]

Addendum settings of OI
On the traget server for OI click and create the tables
2Configure similarly create folders and replcate like this
Control File: \\machinename\OI\Upload\
Working: \\machinename\OI\Upload\
Log: \\machinename\OI\Upload\

only essential stuff shown.

Now bring the folder that you obtained from the other server
and a txt file(which is actually an xml) file to this server.

Edit the text file in notepad replace all aoccurences of

\\machinename\OE\Destination to

wherver you can store the folder for eg I change that to
\\machinename\E$\OI

Essentially all we are doing is telling the target server where to find the acataul data file.OE has given you a big folder structure alaready.


Run it you will get a bunch of errors like Groups are not therr cataegories are not there that kind.Once those anomalies are mitigated you will get a full replica





Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[appnair]

BTW a cut and paste error ocurred

Working:\\machinename\OE\Working\
Log:\\machinename\OE\Working\
Destination:\\machinename\OE\Working\

It should read as

Working:\\machinename\OE\Working\
Log:\\machinename\OE\Log\
Destination:\\machinename\OE\Destination\

Similarly on the OI

Control File: \\machinename\OI\Upload\
Working: \\machinename\OI\working\
Log: \\machinename\OI\Log\


It acataully is a very good piece of code/module and once you get the grasp of things dwelve into its syntaxa nd you acn start pulling in external documents.OE is a new module
OI has been there for almost 5 ,6 yrs hence used for legacy data migration


Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair