In reference with an earlier question of problems with extended notifications (HTTP error 403)

[Mike Pokraka]

Hi Stefaan,

As mentioned previously, these BSP's are used internally. You may not use
internet/BSP functionality, but the message is HTML. To generate it, SAP
uses the built in webserver to avoid reinventing the wheel.

Think of it as rendering it out to a webpage which the system then reads
and plonks into an email, all of which happens internally. A bit like the
old BTCI technology.

Hope that helps,
Mike


On Fri, March 20, 2009 4:16 pm, Stefaan Vermeulen wrote:
> Hi,
>
> Previously I encountered via the possible logs & SWN test program just a
> message that no messages were sent.
> Altough the config. was confirmed to be OK by some users of this group.
> I had some more time to get to the bottom of it (debug SWN_SELSEN_TEST).
>
> Last time I stranded at the error from call function SWN_CALL_BSP that
> gave
> an error.
> Since I do not use BSP I didn't put to much attention to it.
>
> I went a bit deeper into it and saw that the function is used to call up a
> service I presume to create a message content.
> I found a OSSnote 603624  related to http client 403 forbidden error.
> Since I'm on a new ECC6 in development it is possible that these services
> are not all set to active, what indeed is the case, I could check with
> /nSICF.
>
> */default_host/sap/bc/bsp/sap/swn_message1*
>
> My question is 3 way's; Can someone conform this that even without using
> BSP, this service has to be active?
> What does this service exactly do  ?
> Is it enough to activate only this service
>
> Kr,Stefaan.
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>