Verifying the installation

To verify the setup for the ERS replication operation, the SAP system is started and a manual failover of the ABAP SAP Central Services (ASCS) and standalone Enqueue Replicator Server (ERS) occurs. First, the ASCS instance fails over from the first node to the second node. Then, the ASCS instance fails over from the second node back to the first node.

Ensure that the following prerequisites are met before you verify the installation:
  • All ASCS, ERS, primary application server, and additional application server instances are stopped.
  • You have the authority to perform all steps as a <sid>adm user.
  1. Start the ASCS instance on the first node and the ERS instance on the second node.
    1. Start the ERS instance on the second node by using the following commands: 
      
ifconfig <interface_name> <ERS_IP_alias> netmask <IP_netmask> alias up
startsap r3 ERS<ID>
    2. Start the ASCS instance and the primary application server instance on the first node by using the following commands: 
      
ifconfig <interface_name> <ASCS_IP_alias> netmask <IP_netmask> alias up
startsap r3 ASCS<ID>
startsap r3 DVEBMGS<ID>
    3. Start the additional application server instance on the second node by using the following command: 
      startsap r3 D<ID>
    4. Check the replication status for each ERS instance on the second node by using the ensmon (ENSA) utility or the enq_admin (ENSA2) utility.
      • To check the replication status by using the ensmon utility, run the following command: 
        ensmon pf=/usr/sap/<SID>/ERS<ID>/profile/<SID>_ERS<ID>_<node2>
        Select the task Get replication information. An output that is similar to the following example is displayed:
        .
..Replication is enabled in server, replication server is connected. 
Replication is active...
      • To check the replication status by using the enq_admin utility, run the following command:
        enq_admin --replication_state pf=/usr/sap/<SID>/SYS/profile/<SID>_ASCS<ID>_<ASCS_HOSTNAME>
        An output that is similar to the following example is displayed: 
        
Enqueue Server 2

Replication-State = ON
2019-03-19  01:17:09;  OK;  'Replication State';  Response=294 usec
    5. Verify whether you can start all application servers successfully.
      • Log on to the primary application server for Advanced Business Application Programming (ABAP) by using the SAP graphical user interface (GUI).
      • Log on to the additional application server for ABAP by using the SAP GUI.
      • Log on to the primary application server for Java™ by using a web browser. The default address is http://node1:5<ID>00/index.html.
      • Log on to the additional application server for Java by using a web browser. The default is address is http://node2:5<ID>00/index.html.
  2. Change the direction of replication from the second node to the first node. Start the ASCS instance on the second node and the ERS instance on the first node.
    1. Stop the additional application server instance on the second node by using the following commands: 
      
stopsap r3 ERS<ID>
stopsap r3 D<ID>
ifconfig <interface_name> <ERS_IP_alias> delete
    2. Stop ASCS, ERS, and primary application server instances on the first node by using the following commands: 
      
stopsap r3 DVEBMGS<ID>
stopsap r3 ASCS<ID>
ifconfig <interface_name> <ASCS_IP_alias> delete
    3. Start ASCS IP instances on the second node by using the following commands: 
      
ifconfig <interface_name> <ASCS_IP_alias> netmask <IP_netmask> alias up
startsap r3 ASCS<ID>
    4. Start ERS instances on the first node by using the following commands: 
      
ifconfig <interface_name> <ERS_IP_alias> netmask <IP_netmask> alias up
startsap r3 ERS<ID>
    5. Check the replication status for each ERS instance on the second node by using the ensmon (ENSA) utility or the enq_admin (ENSA2) utility.
      • To check the replication status by using the ensmon utility, run the following command: 
        ensmon pf=/usr/sap/<SID>/ERS<ID>/profile/<SID>_ERS<ID>_<node2>
        Select task Get replication information. An output that is similar to the following example is displayed:
        .
..Replication is enabled in server, replication server is connected. 
Replication is active...
      • To check the replication status by using the enq_admin utility, run the following command:
        enq_admin --replication_state pf=/usr/sap/<SID>/SYS/profile/<SID>_ASCS<ID>_<ASCS_HOSTNAME>
        An output that is similar to the following example is displayed: 
        
Enqueue Server 2

Replication-State = ON
2019-03-19  01:17:09;  OK;  'Replication State';  Response=294 usec
    6. Start the primary application server instance on the first node by using the following command: 
      startsap r3 DVEBMGS<ID>
    7. Start the additional application server instance on the second node by using the following command: 
      startsap r3 D<ID>
    8. Verify whether you can start all application servers successfully.
      • Log on to the primary application server for ABAP by using the SAP graphical user interface (GUI).
      • Log on to the additional application server for ABAP by using the SAP GUI.
      • Log on to the primary application server for Java by using a web browser. The default address is http://node1:5<ID>00/index.html.
      • Log on to the additional application server for Java by using a web browser. The default is address is http://node2:5<ID>00/index.html.
After successful verification, all ASCS, ERS, primary application server, and additional application server instances must be stopped and the virtual IP addresses must be deactivated.