Does HLP-BP support SAP Ajax Framework Page (AJP)?

[king]

Dear HLP FirstSpirit community,

currently, we wonder whether the HLP-BP does support:

- the Ajax Framework Page (AJP) components

- in SAP NW 7.02 (EHP2), SP6

The AJP components currently provided on SAP NW 7.02:

- com.sap.portal.nav.afp.dynnavigation 7.0206.20110224153033.0000

- com.sap.portal.nav.afp.helperservice 7.0206.20110224153033.0000

- com.sap.portal.nav.afp.pagetoolbar 7.0206.20110224153033.0000

- com.sap.portal.navigation.afp.dtn 7.0206.20110224153033.0000

- com.sap.portal.navigation.afp.layout 7.0205.20100907122632.0000

- com.sap.portal.navigation.afp.masthead 7.0206.20110224153033.0000

- com.sap.portal.navigation.afp.menu 7.0206.20110224153033.0000

- com.sap.portal.navigation.afp.resources 7.0206.20110224153033.0000

- com.sap.portal.navigation.afp.servlet 7.0206.20110224153033.0000

- com.sap.portal.navigation.afp.setup 7.0206.20110224153033.0000

- com.sap.portal.navigation.afp.tln 7.0206.20110224153033.0000

- com.sap.portal.navigation.afp.widgets 7.0206.20110224153033.0000

Important note: the AJP is not provided by default in SAP NW 7.02. But it might be set as default framework page by configuration. Starting with SAP NW 7.30 AFP will be delivered automatically.

                                               

sap.com	com.sap.portal.navigation.afp.dtn	null (7.0206.20110224153033.0000)	SAP AG	SAP AG	20110310164533	null/null
sap.com	com.sap.portal.navigation.afp.layout	null (7.0205.20100907122632.0000)	SAP AG	SAP AG	20110310164533	null/null
sap.com	com.sap.portal.navigation.afp.masthead	null (7.0206.20110224153033.0000)	SAP AG	SAP AG	20110310164534	null/null
sap.com	com.sap.portal.navigation.afp.menu	null (7.0206.20110224153033.0000)	SAP AG	SAP AG	20110310164535	null/null
sap.com	com.sap.portal.navigation.afp.resources	null (7.0206.20110224153033.0000)	SAP AG	SAP AG	20110310164536	null/null
sap.com	com.sap.portal.navigation.afp.servlet	null (7.0206.20110224153033.0000)	SAP AG	SAP AG	20110310164957	null/null
sap.com	com.sap.portal.navigation.afp.setup	null (7.0206.20110224153033.0000)	SAP AG	SAP AG	20110310164537	null/null
sap.com	com.sap.portal.navigation.afp.tln	null (7.0206.20110224153033.0000)	SAP AG	SAP AG	20110310164538	null/null
sap.com	com.sap.portal.navigation.afp.widgets	null (7.0206.20110224153033.0000)	SAP AG	SAP AG	20110310164539	null/null

[stefan_brauneis]

Hi Holger,

in SAP NetWeaver Portal AFP is currently NOT supported by the HLP BP for FirstSpirit.

Acutally we have tested it and it does not work with the HLPFS-NavigationConnector because of some new Properties of the NavigationNodes the AFP is requesting and using.

These are:

• INavigationConstants.IS_LEAF_ATTR
• com.sap.portal.navigation.IsBusinessSuite

I will come back to this thread when we have a planing when we will implementing these properties and have tested this on AFP.

This is on one side bundled to the testing on EhP 2 and SAP NetWeaver Portal 7.3 as these are the two releases which contain the AFP currently.

Best regards,

Stefan Brauneis

[stefan_brauneis]

Hi all,

just to finalize this for everyone (Holger already knows):

SAP NetWeaver Portal Ajax Framework Page is now supported by the HLP BP for FirstSpirit in EhP 2.

That means you can use the BP for FirstSpirit with the Standard Ajax Framework Page which comes with SAP NetWeaver 7.02.

The new properties have been implemented and we have tested it successfully.

If you would like to use the BP for FirstSpirit with AFP in your SAP NetWeaver Portal please ask for the latest version of the BP for FirstSpirit via the e-Spirit Helpdesk

Best regards,

Stefan Brauneis

[hbroens]

Does the latest HLP Business Package support NetWeaver 7.3 portal in general?

Kind regards,

Hilco Broens

[stefan_brauneis]

Hi Hilco,

SAP NetWeaver Portal 7.3 is not yet supported!

We are currently working on the migration and I will post a message here as soon as it will be released.

We are currently supporting SAP NetWeaver Portal 7.0 EhP 2 (or 7.02) which also includes the Standard SAP AJAX-Framework-Page.

Best regards,

Stefan Brauneis

[hbroens]

Hi Stefan,

Thanks for the information!

Cheers, Hilco

[hbroens]

Hi Stefan,

Any news on the roadmap for HLP BP?

Kind regards,

Hilco Broens

[king]

Dear HLP,

after having deployed HLP-BP 4.11 to a SAP NW 7.30 instance using the AjaxFrameworkPage, we always get the following message when clicking to a HLP-BP specific navigation node:

Before, we guaranteed, that the:

• NavigationConnectorService
• NavigationManagerService
• NavigationService

have been configured properly. Additionally, the navigation XML resources have been registered successfully.

When we analyze the requests using HTTPwatch, we observe:

• a hashed navurl-value is sent as a POST parameter within the 1st request, here: navurl://4f3860f072fb457e495c639bce018b9a
• usage of Short-URLs is activated in SAP NW 7.30 (allows a mapping of "Short URLs" to "Full URLs" where the HLPFS prefix gives the central SAP navigation connector the information which concrete connector to use - here the custom navigation connector provided by HLP. The "Short URL"-iView gives a concrete mapping for the "Full URL":
  
  

  Short URL	Full URL
  4f3860f072fb457e495c639bce018b9a	HLPFS://wcms_c_Bosch_20GlobalNet/...

• the last AFP-servlet call contains another requested navurl compared to the one initially requested. Details see the following to screenshots that document the 1st and the last HTTP request:
  
  
  

We are not quite sure, what provokes that initial error. Maybe you can see a hint?

[kannewischer]

Hi all,

yesterday Stefan found out how to solve this problem. It was due to a combination of the property value "UsePcdLaunchUrl=true" in the GenericCreatorService and a missing "end user" flag for users assigned to the PCD structure "Portal content-> Content Provided by Other Vendors-> End User Content->HLP BP FIRSTspirit-> Pages". More information on the UsePcdLaunchUrl can be found in the HLP BP "Installation and Update" documentation in chapter 3.5.2.

So if anybody has a similar issue, there are two ways how to fix it:

1) Set the property UsePcdLaunchUrl in the GernericCreatorClient to false (if you don't need it)

• To to this log in to the nwa as administrator and go to "Configuration -> Infrastructure -> Application Modules"
• search for de.hlp.pct.fsintegration and select the corresponding entry
• select GenericCreatorService below Web Module Details
• scroll down to Portal Service Details, find the UsePcdLaunchUrl property and change it's value to false
• click the save button
• finally you should restart GenericCreatorService and NavigationManagerService, switch to the corresponding view with the button "More Actions -> View corresponging to Application"

2) Set the end user flag

• In the PCD go to "Portal content-> Content Provided by Other Vendors-> End User Content->HLP BP FIRSTspirit"
• Right-click on "Pages" and select "Open -> Permissions" and select the "End User" checkbox for the users available here

Best Regards

Tim