Skip to Content
0

SAP Solution Manager on AWS, unable to resolve domain

Jul 10, 2017 at 09:52 AM

128

avatar image

Hi All,

We have just installed SAP Solution Manager 7.2 ABAP + JAVA Stack on our AWS instance.

First we had issues with Hostname not supporting SAP standards so we changed that and completed our installation with Non Domain option.

However during out Post configuration we now unable to proceed as the BSP's requires FQDN and our domain is unable to resolve.

We get error - "Cannot resolve Hostname.domain by name" Domain name appears to be us-east-x.xxx.internal.

After updating param icm/host_name_full = Host.us-east-x.xxx.internal says "Page cannot be displayed"

http://Host.us-east-x.xxx.internal:50000/sap/public/myssocntl?sap-client=100

How can we add alias to the domain name, should that be taken care by AWS support team.

Also what is the procedure to open the access to AWS SAP systems from internet. (have asked my network team to check this https://archive.sap.com/discussions/thread/3376395)

Regards,

Rupali S

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Bartosz Jarkowski Jul 10, 2017 at 11:50 AM
0

Can't you just add the hostname to /etc/hosts? You can use ping to verify

Best regards

Bartosz

Show 3 Share
10 |10000 characters needed characters left characters exceeded

Hi Bartosz,

I have already maintained the host file entry, but still its unable to resolve the domain name.

Without the FQDN, SOLMAN_SETUP opens with URL http://Host:50000/sap/public/myssocntl?sap-client=100

but fails once I click on System Preparation. Is there a way that ICM can completely ignore FQDN and just work with short hostname ?

As I had seen in the prereq - "You have installed the SAP Solution Manager and satisfied the following configuration prerequisites:

  • The license key is installed.
  • The profile parameter /ICM_HOST_NAME_FULL or SAPLOCALHOSTFULL is set.
  • The Transport Management System (TMS) is configured.
  • The connection to the SAP backend system exists and works.
  • The SAP Solution Manager Java instance is up-to-date."

slmn-bsp.jpg

host.jpg

Regards,

Rupali S

slmn-bsp.jpg (74.8 kB)
host.jpg (20.1 kB)
0

Did you maintain the /etc/hosts entries also on your local computer where you execute SOLMAN_SETUP? Because for me the message clearly says the host cannot be found, so I don't think it's the SolMan issue.

Can you verify the settings by pinging Host.us-east-x.xxx.internal? Please do it from Solution Manager OS as well as from computer you are going to run SOLMAN_SETUP ?

Best regards

Bartosz

0

Hi Bartosz,

I have arranged to add system details in my local host file.

In the meanwhile back on AWS my Network team has given a new alias but we still get Page Cannot be displayed on SOLMAN_SETUP.

aws-domainissue.jpg

Regards,

Rupali S

0
Rupali Sutar Jul 17, 2017 at 05:24 AM
0

Hi,

Although not fully, but issue has been sorted with respect to FQDN, I tried to open respective ports (Inbound/Outbound Ports). We still have JAVA config to finish, and some JAVA stack URL end up with RABAX 503 error during SOLMAN_SETUP.

Also some URL work without FQDN (i.e. SLD) and some work with FQDN, its little confusing to understand the right configuration :-)

Thanks All,

Regards,

Rupali S

Share
10 |10000 characters needed characters left characters exceeded