WSRP consuming SAP EP problem with consumer agent

[Former Member]

hi folks,

I set up a WSRP producer (JBoss) which provides content for other WSRP-compliant portals around.

Although I does not need registration, I set it up for SAP EP 2004s (SP13) and I ran into trouble with the consumer agent string sent by SAP EP.

WSRP recommends sending this:

The consumerAgent value MUST start with "productName.majorVersion.minorVersion" where "productName" identifies the product the Consumer installed for its deployment, and majorVersion and minorVersion are vendor-defined indications of the version of its product. This string can then contain any additional characters/words the product or Consumer wish to supply. 

In my case the String is SAP_EP_SP6 whereas the portal is "indeed" SAP EP 2004s (SP13) which might resolve to SAP EP 7 SP13.

Does anyone have a clue on where to set this string within portal?

Thanks for your help!

regards,

Christian

[Former Member]

Did SAP or anyone else ever respond to this? We'd like to do the same thing over here, but this issue is causing us a problem (and it looks like there may be another one that will bite us if we can figure this one out http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138878#4138878).

Anyone get this to work with Liferay (that's our next option to look at)?

[Former Member]

Hi Jason,

that was my post on JBoss forums, although it didn't help too much. Some SAP employee send us a fix - a dirty hack in fact - to get it working but after patching the portal it didn't talk WSRP to Oracle portal anymore.

The fix from Jboss was not tested we simply couldn't trust the setup (Jboss talking to SAP EP and vice-versa) anymore and opted for doing a completely different thing (no portal standards).

Next thing that will cause problems in your scenario will be SAP logon tickets that are simply too much for neighboring portals from other vendors... As a result of my experiences I can just say "hands off" and wait for netweaver ce, which will - hopefully - include JSR168 support.

Good luck!

regards,

Christian

[Former Member]

Wait for CE? Lol, that's what we're using Same issues still, very sad. I'm trying some fixes from JBoss (basically they've included some config to loosen some of their validations. I'll post my findings here.

[Former Member]

For those that are interested JBoss Portal 2.6.6 (not release) or higher should include configuration to run in a less strict mode (Consumer agents, locale string, etc). I successfully have a portlet being served up from JBoss Portal and being consumed in SAP EP in Netweaver CE 7.1.

[Former Member]

This problem has its origin in SAPs weak implementation of the WSRP 1.0 standard from OASIS and others (here JBoss Portal) strict implementation of standards...

The consumer MUST send a consumer agent string containing following a special layout which is "Product.Majorversion.Minorversion" whereas SAP sends stuff like "SAP_EP6_SP09" as consumer agent, although in my case this had to be "SAP_EP7_SP13" or according to WSRP-standard "SAP.EP7.SP13".

I opened a ticket at SAP and gonna sleep on until NetWeaver CE comes on.

regards,

Christian