Unfinished configuration of "IDES ERP 6.0 Including Enhancement Package 7 on SAP ASE 15.7"

[frank_vanoverloop2]

Hi,

we recently deployed an instance of the solution "IDES ERP 6.0 EhP7" on AWS.

Login is possible but some functions seems to indicate that the set up is not completed yet.

For instance, DBACOCKPIT returned following error :

"The host http://vhcalabaci.wdf.sap.corp .... does not exist. Please check the spelling or your access to the Internet."

Looks like it is still configured for the Walldorf intranet. 

This is more or less confirmed when looking in some configuration files on the virtual server :

hosts file:

     contains also references to "wdf.sap.corp"

instance profiles (DEFAUL, ASCS, PAS)  :

     SAPFQDN=wdf.sap.corp

Can you investigate and propose a correct set up?

I did not want to change the configuration settings since there may be other configurations that need to be adjusted.

Thanks in advance for your feedback,

Frank Van Overloop

[manfred_stein]

Hi Frank

Looks like some factory setting survived our clean up activities

As a first resort, can you try to enter vhcalbaci.wdf.sap.corp into your local host file on your desktop and report the result to me?

Reconfiguring the app server to use another domain is not difficult but requires some expertise. Not sure how familiar you are with such changes, but judging from your comments would not surprise me if you are up to the little challenge.

Would help me to get the clean up done via our solution settings for subsequent instantiations.

Thanks in advance, Manfred

[frank_vanoverloop2]

Hello Manfred,

Since we have just started with CAL this is still on restricted access so there is some freedom for prototyping and consultancy towards SAP 😉 .

I will check with the owner if I can activate the instance to make the changes on OS and SAP level and test; Then get back to you with the results.

If I remember correctly I used “dummy.nodomain” with another instance type.

Anyway, it will help having a consistent approach for this – the hosts file on our workstations is protected against local changes and some might frown if we ask to  add lines with “wdf.sap.corp” .

Presumably it also needs to be secured that the host names are unique among CAL solutions.

Perhaps it is – I did not check all “Getting started” guides.

Since I am not familiar with ASE I need a hint where to make network configuration settings, if needed (something like tnsnames.ora for Sybase). Might take less time than wandering around in a bunch of Google links.

Regards

[manfred_stein]

Hi Frank

Thanks for your immediate reaction. Looks like we forgot to instruct our deployment script to change to dummy.nodomain.

Just a few additional remarks

- Tying into a real customer network is rather difficult, so we tend to add frontend servers and simulate a small shielded network area for our trial solutions. Not available for your current solution and perhaps not really useful for what you have in mind.

- If the dummy.nodomain helps you in the first place, my expection is that we do not need to do more than modify the profile setting and make sure that the /etc/hosts file on the SAP server is maintained accordingly. I am not the ASE expert but have access to quite a bit of expertise in the backend if my guess that ASE will not care proves to be wrong. If it gets too much, probably easier to scratch the instance and bring up a new one once we have fixed our solution settings wrt domain name.

I have reached out to a colleague who has written the automation (incl handling of SAP autostart server stop and resume) and with his feedback we should be able to move you over quickly to a non-SAP specific domain name.

- Getting you unique server names may actually be some back and forth among the 3 of us, so why don't we take the discussion over to private mail and not bore the SCN users with our tech intructions. Will send you my coordinates via direct message.

Manfred

[frank_vanoverloop2]

Hello,

I tested 2 changes :

- put entries for wdf.sap.corp in my local hosts file

- put entries for dummy.nodomain + adjust /etc/resolv.conf

System start is OK, but access to dbacockpit is still behaving weird.

The html version fails at the start -
Impossible to connect to the URL http://vhcalabaci.dummy.nodomain:0/sap/bc/webdynpro/sap/dba_cockpit?<etx>. The server responded with: Can't assign requested address.

i can go into the sapgui interface for DB02 but most of the interesting menu options are greyed out - so I can't retrieve the info.

In some of the screens in DB02 I find reference to a server wdflbmd16124 - a DB test connection to this server fails (of course). Tried to enter this name asa alias in the hosts file but that did not solve this issue. On the other hand, abaadm seems to have the correct environment info for the local ASE (since the database starts). Looks some config settings between user env and gui are not in sync.

But I miss ASE skills to figure out where I need to correct this.

Mixed feelings about this installation - it looks like the application part will work - but having this confusing setup might still give surprises at later stages.

So I hope your team works on a clean version of this image and will deploy is soon.

Regards

Frank

[ventsislav_ivanov2]

Hello Frank,

Thanks you for the valuable feedback. We will follow-up on it.

For tracking the solution update you can create support ticket under BC-VCM-VAP.

Best Regards,

Ventsislav

[ventsislav_ivanov2]

Hi Frank,

We addressed some of your points above and released an update of the appliance.

Rest of the points we'll try to address with next version of this appliance.

Changes include wdf.sap.corp is not used as default domain name.

For DBA cockpit - we added default setup of reverse proxy so you can access it:

http://<instance ip>:8080/sap/bc/webdynpro/sap/dba_cockpit?<etx>

This way you will not have to change the content of your .hosts file

You can re-create your instance now to see the changes.

Best Regards,

Ventsislav