xECM Integration

Hi Experts,

I have few questions regarding xECM. We are using CS 16.2.4 and AC 16.2.2 with ELS installed on AC

We are running batches from OTDP->Doc Pipeline->SAP/AS->CS. The flow of documents from Doc Pipeline is fast but BW that has to be created from SAP to CS is very slow.

Does it have to do anything with what we define in logical ports and connection details in Maintain Extended ECM?
Currently one node URL is defined for each of the Logical ports. Does LB URL has to be defined to give high availability?

Thanks,

Find more posts tagged with

Comments

Appu Nair

Your workspaces creation creates multiple objects in Livelink . If you take a look at one workspace template you will be able to find out 1) How many objects 2)what operations like metadata, renaming etc .All if these is done by Oscript code which can be measured by looking at performance logs of content server a.k.a livelink . Typically xecm operations require a CS architecture with a number of front ends under a LB Appliance and a highly performance database.if your xecm is a small operation it might suffice

Bryan Gerlach

Some of this could also be due to the object types and relationships you are trying to map across into CS. We had a performance issue with Equipment creation that after some trial and error, found that the related objects was the major cause. Since we were using a canned property provider, we modified it to remove the relationships we weren't ready to use and cut the time to create by 60%. OT support helped track down the problem areas in the slow down.