Livelink XML Export & Import

We have a customer who wants to upgrade from LL 9.7.1 to Content Server. Can we use LL XML Export & Import to perform this?

I need feedback on the below points..

Any limitation regarding object types (Projects, Tasklist, Forms…. etc). Does it work with all object types in LL by default?
Any limitation on the size or number of objects that can be exported or imported?
Can we use it to migrate contents from one LL instance to another? Will it migrate Workflows as well?
Any other limitations in using this XML feature?
Is the version available for 9.7.1 (export) & Content server (import)?

Regards,

Dominic.

Find more posts tagged with

Comments

Kevin_Bailey

How many objects are you talking about?

On Oct 26, 2011, at 4:53 AM, "eLink Entry: LAPI Forum" <lapi@elinkkc.opentext.com> wrote:

Livelink XML Export & Import Posted by dcarvalho@itqan.ae (Carvalho, Dominic)On 10/26/2011 04:49 AM

We have a customer who wants to upgrade from LL 9.7.1 to Content Server. Can we use LL XML Export & Import to perform this? I need feedback on the below points.. Any limitation regarding object types (Projects, Tasklist, Forms…. etc). Does it work with all object types in LL by default? Any limitation on the size or number of objects that can be exported or imported? Can we use it to migrate contents from one LL instance to another? Will it migrate Workflows as well? Any other limitations in using this XML feature? Is the version available for 9.7.1 (export) & Content server (import)? Regards, Dominic.
[To post a comment, use the normal reply function]
Forum: LAPI Forum
Content Server: Knowledge Center

Shivaram Padmanabhan

Do you want to upgrade or migrate? If your plan is to upgrade, then why XML export\import and why not the normal upgrade process

Dominic_Carvalho

There's been a slight mistake on my part for mentioning a LL upgrade, but I just got the actual requirement as stated below.

The customer has many LL instances at different locations. The main central instance has been replicated across each location. These locations are all project-specific and so some of these projects have been completed, so the instance is no longer required, but the data needs to be imported into the central instance before shutting it down. That's why the need of XML Export & Import. Certain queries from the customer are attached, for which we need answers. The main concern is the retention of permissions, audit, renditions & even generations. Within LL, we would be dealing with Projects & Folder objects with loads of documents. Also, what core factors are to be looked upon before creating a test environment?

Thanks in advance.

Appu_Nair

As Kevin is suggesting one usually does XMEXPORT by using the browser,now in most cases when you do xmlexport on a huge hierarchy the livelink server thread is building this to show you a response file on your browser. IIS has a time out of say 900 secs in most places, and if the process takes more than that then your browser who is at the mercy of the webserver will time out.If you refresh it starts from scratch thereby starting this vicious cycle.Having said that both lapi and oscript can programmatically do this for you so can products such as Object Importer/Exporter and its many enhancement packages as well.Excellent migration tools such as Global Cents takes the guess work/programming out of this equition as well.I use OE/OI to do most of these things.