SAP Netweaver 7.31 Upgrade

[Former Member]

Dear Experts,

I did the Portal upgrade from 7.0 to 7.31 in MSCS environment. I uninstalled the dialog instance in second node.

Whenever i moved the SAP SCS to node 2 and the server node started in node 1, am not able to access the portal via the virtual hostname.

I have explained the scenario below.

Physical hostname: physical

Virtual hotname: virtual

Scenario1:

SCS: Node1 and Java Server: Node1

http://virtual:<port>/irj/portal - working

Scenario2:

SCS: Node2 and Java Server:Node1

http://virtual:<port>/irj/portal - Not working

http://physical:<port>/irj/portal - Working.

Please help me to solve the issue.

Regards,

Raja. G

[Former Member]

Hello Raja,

The virtual hostname availability depends on the MSCS resource type  'IP Address'. It should be part of the SAP Cluster group ( which contains SCS or ASCS ). So when you failover the SAP Cluster group then  the virtual hostname / IP Address also moves along with it.

Can you check if the  'IP Address' cluster resource types is part of the SAP Cluster group. If not then you need to include it.

More MSCS configuration details can be found in the section 'High availability with Microsoft Cluster Services' in Installation guide.

https://service.sap.com/instguidesnw73

Regards,

Mudasir.

[Former Member]

Hi,

The cluster is working fine. The problem is with URL only.

To make it clear installed the additional application server instance in node2 and moved the resource to node2 then the URL is fine. However when i shutdown the node2 instance again the http://virtual:<port>/irj/portal didnt worked.

So now wherever the SCS is running one application server has to run to recognize the virtual hostname URL but that should not be in real case.

Please clarify whether the web dispatcher is mandatory for the clustered portal system. Also let me know why the physical hostname URL is working in the clustered environment?

Regards,

Raja. G

[Former Member]

Hi Raja,

Webdispatcher is an optional component. Its not mandatory for clustered portal to work.

To clarify how it works ( How url picks up the virtual IP Hostname ) : The virtual IP is a  Cluster resource and whenever you failover the cluster group, the virtual IP points to the server it is running on. The hostname is mapped to this virtual IP Address ( maintained in hosts file ) so as long as the virtual IP cluster resource is running the url works fine.

Why physical hostname is working :?? Coz physical hostname is not a part of the cluster & it doesn't changes when you failover the cluster.

Can you attach the screenshots of the cluster groups & resources running for your systems so that we can investigate more

Regards,

Mudasir.

[Former Member]

Hi Mudasir,

I have clustered SAP an Oracle in MSCS and i have CI in node1 and DI in node 2. Please let me know the web dispatcher is needed for the load balancing for this scenario.

Regards,

Raja. G

[Former Member]

Hi Raja,

To explain in a simple way.

Yes, the web-dispatcher would be required for  load balancing in your scenario.

Reason : The virtual hostname seems to be part of Cluster package of SCS only so whenever you move SCS, the virtual hostname points to the Node 2.

There are more than a way to load balance however the web dispatcher might be the easiest way to achieve it.

Hope it helps.

Regards,

Mudasir.

[Former Member]

Hi Mudasir,

I will install and config the web dispatcher and comeback to you.

Regards,

Raja. G

[Former Member]

Hi Raja,

Did upgraded ERS instance on both nodes?

[Former Member]

Hi Srini,

Yes, the ERS is upgraded in both the nodes.

Regards,

Raja. G

[Former Member]

Hi Raja,

SCS also updated?

anyway you can check.

//virtual host opening for both nodes.

go to run :

//virtual hosname/