Dear e-Spirit team,
when there might be a use case, where the SAP Netweaver Portal environment is split up into:
- KM instances
- and non-KM instances
the "HLP-BP Navigation for FirstSpirit" might be deployed on both environments. Then, it might be helpful to separate the XML registration process:
- navigation XMLs go for non-KM instances
- search XMLs go for KM instances
Up to now, the "ActivatePortalXML" task within a FirstSpirit deployment run does call the HLP-BP webservice client, that registers the XML files. The enclosed screenshots do show these configurations currently:

The implementation creates a new native process on the operating system for calling the HLP-BP content creator client. The path for the client is being configured within the corresponding module configuration setup. The following setting is important "urlPrefixActivationClient" (display name: "Path to activation web-service client")

The problem:
- the configured bash script contains the Portal-URL where the XMLs will be registered
A possible solution:
- create a 2nd "ActivatPortalXML" action entry
- just enter FirstSpirit IDs of "portalEntryPoints" (see 1st screenshot) of type "search"
- remove "portalEntryPoints" of type "search" in the 1st "ActivatePortalXML" action configuration
- overwrite the value already available within the scheduler script context (object "context") named "urlPrefixActivationClient" in the 2nd action before method "execute()" of class "de.espirit.firstspirit.opt.portal.script.ActivatePortalXML" (reason: a second entry for "Path to activation web-service client" is not available in the Portal configuration dialog) is called.
Our question:
- is this solution valid?