Workflow notifications through Web Dispatcher

Tue Jan 12 05:36:00 EST 2010

G'Day,

There's nothing unusual about your setup (other than users connecting
directly to the central instance?!!??), so option 3 should be valid, but
sounds like there may be a bug.

Might be worthwhile asking OSS.

Cheers,
Mike

On Tue, January 12, 2010 10:03 am, POURNARAS KONSTANTINOS wrote:
> Hello all,
>
> I have a problem with the e-mail messages created through Workflow
> Notifications. The productive landscape is a central instance under which
> two application servers reside; <sapp1> and <sapp2>. The fully qualified
> names for these servers is <sapp1.company.com> and <sapp2.company.com>.
> Users connect to the central instance through Citrix, and eventually get
> assigned to one of the instances. When a workflow notification is created,
> the links use the fully qualified server names in port 8000; so, the links
> start with <http://sapp1.company.com:8000/...> or
> <http://sapp2.company.com:8000/...>.
>
> The problem is that all HTTP traffic is served through Web Dispatcher at
> <http://sapwebdisp:8100/...>, so all HTTP requests should start as such.
>
> I have attempted to fix this in the following ways:
>
> 1.	Setting the icm hostname to sapwebdisp; this would work on a landscape
> with one instance, but not on the aforementioned landscape with two
> instances. Even the Web Dispatcher would not respond, but emails generated
> had the proper links and HTTP references.
>
> 2.	Creating an entry in HTTPURLLOC table; this seems to generate proper
> URLs by testing class CL_SWN_URL_GENERATOR, but actual message generation
> through SWN_SELSEN still uses the fully qualified name of the initiating
> instance. This is kept though, as CL_SWN_URL_GENERATOR is used by other
> parts of my workflows to send information messages.
>
> 3.	Setting WG_HOST; in transaction SWNCONFIG -> General Settings ->
> WG_HOST is set as <http://sapwebdisp:8100/sap/bc/gui/sap/its/webgui/>.
> This gives me correct links in the body of the emails generated, so I have
> an operating solution. The problem here is that HTML formatting is lost,
> due to the fact that the message source still contains references to the
> fully qualified name of the server, e.g.  <html><head><title></title><base
> href=" sapp1.company.com "â€¦>.
>
> Maybe you have an alternative solution to propose? It seems that the only
> problem remaining with my solution (points 2 and 3) is the reference of
> the fully qualified name in the message source; can that be altered
> somehow with customizing or parameter settings?
>
>
>
> Best regards,
> Evangelos Pournaras
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>