BPM - alert detail links incorrect

[bernie_krause]

We are having an issue with the links that are created in the email alerts.  Our systems are all clustered, with several app servers, etc - the link that gets generated in the email alert looks like this and doesn't work.  We need it to omit the ap00 and the port, then it works properly.

https://xxxxxxap00.xxxxxx.com:44300/sap/bc/gui/sap/its/webgui....blahblah

Should look like this .

https://xxxxx.xxxx.com/sap/bc/gui/sap/its/webgui... etc 

Where is Solman getting this configuration from, and how do we stop it from choosing the ap00 and the port when it creates the link?  Is this related to how the agents are installed/configured (we install at app server level, not at VIP level), or is this something that needs to be set up somewhere else in Managed System Config?  SICF?  Somewhere else?  It seems to me that it's using the app00 server as the default host, but I'm not sure where to check that configuration.

Thanks.
Bernie

[former_member45419]

Hi Bernie,

Pls refer below links for similar,

http://service.sap.com/bpm

http://service.sap.com/solutionmanagerbp

SAP Service Marketplace - Home

Regards

Nayeem

[Former Member]

Dear All,

Please let me know how to troubleshoot incident created through BPmon.

I want to create incident on every error record using badi BADI_CUSTOM_SUPNOTIF.

[Former Member]

Hi,

check the ICM full host name parameter icm/host_name_full (SAP Library - Administration of the Internet Communication Manager)

and adjust accordingly.

Thanks

Jansi

[bernie_krause]

Jansi - we already have that parameter set correctly/consistently across all our systems.  Unfortunately BPM doesn't seem to be using it.

we have SAPLOCALHOSTFULL $(SAPLOCALHOST).$(SAPFQDN) in the default profile, it also doesn't appear to be working the way we think it should.  SAPLOCALHOST is specified without the app server name (ap01 suffix). 

saplocalhost is set in the instance profile with the app server suffix, but is not fully qualified (no DN) and so should be ignored by ICM, no?

Our hosts file has all of the app servers defined as well as a high level fqdn without the ap server designations for the SID.  I've gone through the help for fqdn sequence/priority at icm/host_name_full - SAP Web Dispatcher - SAP Library, but that doesn't seem to be working correctly or I'm misunderstanding it (highly likely) .  Also went through thread http://scn.sap.com/thread/1656309 which covers the same ground without a clear resolution..

Thanks.

edit - ok, just noticed something in that BPM alert email.  The link to the solman alert inbox generates correctly, but the other 2 (one to the monitored system, the other to solman again) don't.  But..  they have different paths.  the one that works goes to default_host/sap/bc/webdynpro/sap, while the ones that are not working are going to default_host/sap/bc/solman or bc/gui... 

Are we missing some ICF service configuration??

[jolanta_gniadek]

Hi Bernie,

Do you happen to have an HTTPS service configured on the managed system?

I had some challenges when we needed to activate HTTPS service for some other purposes, but we didn't open the right port in the network for the regular users.

I'm not sure why the hostname is being changed but while generating the link BPMon is using "READ" connection, so you might take a look at the SM59 and check it there. I think I have seen a note that deals with the dipatcher problem on this connection (I would need to dig for it).

Cheers,

Jolanta

[bernie_krause]

Hmm..  we do have https configured and working. 

We did take a look at the RFC and changed it to be load balanced, but that doesn't seem to have changed anything.  I wonder if this could be part of the problem?

Server Selection and Load Balancing for HTTPS Requests

Since with End-to-End SSL HTTPS requests the SAP Web dispatcher is unable to read the URL, it can only distribute HTTPS requests in turn to the HTTPS-enabled servers in the system. This also takes into consideration the capacity of each server. To be able to process J2EE requests, each HTTPS-enabled server must have integrated the J2EE server.

The ICM of the server that receives the HTTPS request can decode the URL and then decide whether the request should be sent to the ICF or to the integrated J2EE server.

that was from Server Selection and Load Balancing Using the SAP Web Dispatcher (SAP Library - SAP Web Dispatcher)D...

Doesn't seem to explain why one Solman url forms correctly and the other doesn't though.

[bernie_krause]

And it does seem to be hitting the web dispatcher correctly, as the suffix we're seeing is rotating between the different app servers.  So something just isn't resolving, but I have no idea where to look for this.. 

[jolanta_gniadek]

Hi again,

The detail link generation to the managed system and to the alert inbox is using a different BADI to generate, hence there is a good chance that there might be a difference.

You can make a small test with the read connection - without load balancing pointing for example on the central instance and see if the host name is correct. If it is then you will have only a challenge with the port no. - I have been fighting with it a bit before and it is hard coded in the BADI that if there is HTTPS activated it will use HTTPS port - here you will have 3 solutions - switch off HTTPS (probably not an option), open port 44300 for regular users, or copy the original BADI to your own custom one and comment the lines of code that call HTTPS.

If it will work with the central instance host without load balancing, you can try again with load balancing and I'm not sure which version of SolMan you're on but take a look at the note 1826308.

Regards,

Jolanta

[bernie_krause]

Well now - that note looks might promising!!    SM7.1 sp7, St 7.10.  We'l be trying that out, thanks!!!!

[bernie_krause]

Well, the note was applied, but no love there.  We'll be looking at your other suggestions.  Any idea which bapi was affected?  Also opened an SAP "incident', see what the SAP grand poobahs come back with.

Thanks.

Bernie

[jolanta_gniadek]

Hi,

Sorry for a long reply time, I was a bit busy here. You can see the coding of the link generation in the method GET_DETAIL_INFO_URL of class CL_DSWP_BPM_ALERT_API

You can see there that the READ connection is used to get the host of the managed system and that if HTTPS service is activated then this one is used (https protocol and port number).

It's good to hear that you have some SAP guys looking at it, I hope they will be able to help you.

Cheers,

Jolanta.

[bernie_krause]

Hmm, would this be a method that you've modified?  We don't show that one in any of our structures, definitely not in that class.  We're on SM7.1, SP7.  Closest we've got is Create_shortcut_alert_details.

[jolanta_gniadek]

We're on SP10, so there can be some differences, but the method is a standard SAP:

Did you try to make a test (maybe on your D Solman) without SSL, or without load balancing on _READ connection?

There is also another note that might be relevant for you: 1930474.

Good luck!

Jolanta

[bernie_krause]

We implemented 1930474 last week with no success.  And on our non-load balanced D systems the URL works fine, but there we use http instead of https and the port is open. 

That method is the only one that's missing in our CL_DSWP* class.. 

[bernie_krause]

Jolanta - did you look at the httpurlloc table at all to maybe redirect the url?  One of our basis guys mentioned it, it's a bit out of my comfort zone. 

The Method that builds the url in sp7 is Build_Message.   It looks at smicm values, defaults to use the https url if it's active.  Our smicm table has 44300 as https port with app server fqdn - we would need to either redirect the url or recode that method to strip out the useless info.  SAP has been zero help so far.  Nice.

[bernie_krause]

SAP came back with "there is no short term solution at this time.  Thank you"...  no, thank YOU! 

Amazing.  Escalated.

[jolanta_gniadek]

Hi Bernie,

Sorry to hear that. I think the only option you have at the moment would be an implementation of BADI.

There is a piece of code called: BUILD_NOTIFICATION_LONG.txt in the note 1610494 that you could implement following the guide:

https://service.sap.com/~sapidb/011000358700000525622010E/Auto-reaction_Messages.pdf

You would have to make a small change in the code commenting the parts with:

"if sy-subrc = 0.

concatenate ls_servlist-hostname ':' ls_servlist-service

into lv_host.

lv_http = 'https'.

else."

An advantage is that you can test it on a single monitor as it requires to place the BADI filter on the monitor (a lot of work later on).

Give me a sign of you'll find ianother possibility to get rid of the https, as I was also struggling with it but in the service desk messages configuration.

Good Luck!

Jolanta