Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SAP xECM Integration Issue

Status
Not open for further replies.

rkbgrid

Technical User
Oct 17, 2011
1
GB
Hi OpenText and SAP Gurus,

This is my 1st post in this forum. Please pardon me if anything i said wrong or against the rules of forum.

I have an issue with SAP to xECM integration. Currently we are using Extended ECM 9.8 Solution presented by OpenText. We have OpenText Content server 9.7.1, Archive Server 9.7 with other bunch of OpenText Suite products. We are using SAP ECC as leading application for our implementation. After all the configuration and setting up of the servers and application, we came across few issues, out of which high priority issues is outlined below.

We are facing one issue of Business Objects and Business workspace declaration in SAP which need to be reflected back in Livelink and vice versa.

As to make it better understanable, I have created one word file which is attached with this thread.

Please go through it and any help/input/suggestion would be highly appreciable.

Issue 1: When you go to a SAP object (example shown here is a billing document accessed via transaction VF03) and click on Business References, it gives a list of business references. However, when you click on one of the business references, it does not show any details. A blank HTML window is opened.





Clicking on any one of the above gives the following window:


Issue 2: After adding a business workspace in Content Server and mapping it to a SAP object, you go back to SAP, access the relevant SAP object and try to Display Business Workspace. It gives a blank window with a text at the bottom:





Regards
RKB
 
in any case you need on the livelink server to put logs which is like this
DEBUG=2
[options]
WantLogs=TRUE
WantLAPILogs=True

then after putting this on all instances or for debugging isolate it on the machine where the RCS is configured to talk to livelink.I mean from your RCS you have pointed to livelink to make the connection

Then on the RCS box(if you have a separate RCS box) or on the archive server which is your RCS stack you should bump up RCS logging thru the MMC (ot administration client). This would tell you why the page is rendered blank.The point of bumping up the RCS log is to accertain the return results of webservices calls that the RCS java stack makes.It is a client to livelink at this point.what if the SAP calling user cannot see a category definition(in your xECM they are called ELIB types) .Also what is the modus operandi of a sap user to livelink user,SAP SSO login ticket or impersonate user or Dir Svcs with IWA on IIS.

BTW when you click the page and the blank page occurs and you see a trace log file then send it to livelink support and let them figure out the script crash.

that is how I would check the plumbing and business rules of this "lot of moving parts " product suite.You need a good understanding of the architectural elements to do 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,Livelink ECM Champion 2010
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top