cancel
Showing results for 
Search instead for 
Did you mean: 

SRM 7.0 catalog EP is not working.

Former Member
0 Kudos

Hi Masters .

We are upgrade srm 5.0 to srm 7.0 the catalog in srm 5.0 working ok. but in SRM 7.0 no. I Know the process change because the portal is requiered. when user made click in Catalog link nothing happens show the next error .

Maybe is necessary make steps post instalation to MDM server and Portal.

In Portal system administration when executes test to MDM Catalog show me the next message

any Idea to fix the problem

thanks in advances.

Accepted Solutions (1)

Accepted Solutions (1)

timea_geczi
Employee
Employee
0 Kudos

Hi Oscar,

this has most probably nothing to do with MDM.

Please check SAP note 1643978 - Catalog link does not open catalog. I think this will resolve the issue.

Regards,

Timea

Former Member
0 Kudos

Hi Timea

thanks for your reply. review of note 1643978 and the settup is correct in my system,

but debuging a found the problem is the Hook_url parameter is truncated on the return value

in run time. look like this.

http://hostname:50000/irj/portal?NavigationTarget=pcd:portal_content/com.sap.pct/specialist/com.sap....

the value is truncated is not complete. 

1.- I have another questions my web services is in standard structure call in srm 7.0 is changed because in srm 5.0 it was in integrated structure call ?

2.- the parameter useportalnavigation is requiered ? 

thanks in advances.

timea_geczi
Employee
Employee
0 Kudos

Hi Oscar,

regarding your questions:

1. yes, in SRM 7.0 only the standard call structure can be used (see SAP note 1287412),

2. the parameter UsePortalNavigation can be used, if portal and MDM are installed on the same Web Application Server - it is than triggering absolute navigation instead of navigation by the hook url.

Regards,

Timea

Former Member
0 Kudos

Hi timea.

Thanks for your support .

the WAS is not the same for those aplications MDM and Portal so the parameter is not requiered.

the problem persist in URL value hook_url. what can i review to fix the problem.

best regards.

timea_geczi
Employee
Employee
0 Kudos

Hi Oscar,

are you using webdispatcher or other reverse proxy? If yes, check top 6 of SAP note 1723534.

Regards,

Timea

(P.S. It would be nice if you could award points for the useful answers... )

Former Member
0 Kudos

Thanks again Timea.

 

we are using proxy reverse.  so the top is not my case. but the top 5 I think maybe is the possible fix the problem.   the note 1456724 hook_url delete. what do you think about that note is correct.

thanks.

timea_geczi
Employee
Employee
0 Kudos

Hi Oscar,

no, I don't think that note 1456724 is relevant for your case. When you click on the catalog link to open the catalog, these function modules are not called at all. These are only called during cross-catalog search and catalog validation (SC creation from Old Shopping Carts).

I think that the issue is with the settings of your reverse proxy. Please recheck the settings with your basis colleagues. Following wiki site might help you:

http://wiki.sdn.sap.com/wiki/display/BSP/Using+Proxies

I would suggest you to create a HTTPWatch trace to see, what is happening (the details of the traffic can be seen only with the professional version).

If it's really an issue with the reverse proxy, I'm afraid I will not be able to help you further...

Regards,

Timea

Former Member
0 Kudos

Hi Timea.

an apology four my delay.

but finally the problem was resolve  the SP leven of components JAVA MDM CONNECTOR and JAVA API. because we had diferents levels of components so. we downgrade the appropiate components and Catalog is download very good.

thanks for your support.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Oscar,

please check the NWA monitoring for more details when you call the catalog in the shopping cart.

URL for the NWA monitoring: http://<J2EE_SERVER>:PORT/nwa

Do you see more information in the monitoring? connection error? ...

Regards,

Florian