Performance issue with Documentum Contetent Services.

Question

Hi All,
This is my environment :
WebLogic Portal 8.1 SP3.
Documentum Content Services : 5.2.5.
Site Caching Services :
The WLP has been integrated with SCS (Site Caching Services) using DCS. The integration is done by creating the content Repository.
The DCS has been used to connect to SCS target and all the contents for a site has been published by using the SCS source system.Essentially, DCS has been used to fetch the metadata of the content as well as the actula content from SCS system.
As a part of DCS configuration, the DCS is connected to SCS target system DB and the IIS from where the actual files are served.
In terms of working, the DCS opena Http connection with the IIS to get the content and it returs in the form of
'com.bea.content.Node".
This has been tested in local development environment and it works fine and is reasonably fast for a portal page where it displays about 20 contents. In local environment (in one network), it takes about 8-10 seconds to retrive the content and display the same.
BUT,in different environment (ie in another network) ie Staging and Production, the PERFORMANCE is very poor. The same portal page containing about 20 contents takes about 80 seconds.
I am wondering what could be the issue for such a poor performance. In that particular network, the performance for Staging as well as Production environments are same (takes about 80 seconds).
Did anybody face this type of problem??
Can some body give some pointers for resolving this issue?
Thanks,
Prashanth Bhat.

Answer 1

Hi All,
This is my environment :
WebLogic Portal 8.1 SP3.
Documentum Content Services : 5.2.5.
Site Caching Services :
The WLP has been integrated with SCS (Site Caching Services) using DCS. The integration is done by creating the content Repository.
The DCS has been used to connect to SCS target and all the contents for a site has been published by using the SCS source system.Essentially, DCS has been used to fetch the metadata of the content as well as the actula content from SCS system.
As a part of DCS configuration, the DCS is connected to SCS target system DB and the IIS from where the actual files are served.
In terms of working, the DCS opena Http connection with the IIS to get the content and it returs in the form of
'com.bea.content.Node".
This has been tested in local development environment and it works fine and is reasonably fast for a portal page where it displays about 20 contents. In local environment (in one network), it takes about 8-10 seconds to retrive the content and display the same.
BUT,in different environment (ie in another network) ie Staging and Production, the PERFORMANCE is very poor. The same portal page containing about 20 contents takes about 80 seconds.
I am wondering what could be the issue for such a poor performance. In that particular network, the performance for Staging as well as Production environments are same (takes about 80 seconds).
Did anybody face this type of problem??
Can some body give some pointers for resolving this issue?
Thanks,
Prashanth Bhat.