Verifying Java SCS with enqueue replication

Edit online

You must verify that your SAP system runs without problems with the virtual host name and the replication server. You can start and stop the SCS services manually. This topic presents the steps and commands how to achieve this.

First, you must activate the VIPA under z/OS® UNIX System Services or the IP alias under Linux®. Under z/OS UNIX, use the moddvipa command as root user:
```
moddvipa -p tcpip -c 10.101.5.195 (if this is the IP address of ha1scsv)
```
Manually start the SCS01 instance as <sid>adm:
```
startsap r3 SCS01 ha1scsv
```
Verify that all processes are running correctly with sapcontrol:
```
sapcontrol -nr 01 -function GetProcessList
```
The output must show that all processes have a GREEN status, similar to the output example shown in Starting and stopping the ASCS.
Manually start the enqueue replication server as <sid>adm on another machine after you have activated the Java™ ERS VIPA there:
```
startsap r3 ERS11 ha1jersv
```
Verify that the replication process is running correctly with sapcontrol:
```
sapcontrol -nr 11 -function GetProcessList
```
The output must show that all processes have a GREEN status, similar to the output example shown in Starting and stopping the ASCS.

Verify manually afterward that the SAP SCS is running correctly. Use the utility enqt that SAP provides. Run as <sid>adm:

enqt pf=/usr/sap/HA1/SYS/profile/HA1_SCS01_ha1scsv 97

The output is similar to:


---REQ-----------------------------------------------------------------------------------
EnqId:          EnqTabCreaTime/RandomNumber    = 06.09.2015 00:06:19  1125957979 / 8563
ReqOrd at Srv:  TimeInSecs/ReqNumberThisSec    = 09.09.2015 13:45:43  1126266343 / 1
-----------------------------------------------------------------------------------------

where EnqId is the unique identifier of the enqueue server and its enqueue table.

In addition, run:

enqt pf=/usr/sap/HA1/SYS/profile/HA1_SCS01_ha1scsv 20

The output is similar to:

J2E <interna $service.e X ejb/CreateEmptyImageBean
J2E <interna $service.e X ejb/FinishImageBean
J2E <interna $service.j X
Number of selected entries: 3

This shows the current enqueue table entries.

Use the ensmon utility to check whether the replication server has successfully connected to the Java stand-alone enqueue server. For example, run:

ensmon pf=/usr/sap/HA1/SYS/profile/HA1_SCS01_ha1scsv

From the main menu select:

1: Dummy request . The dummy request is run successfully.
2: Get replication information. This returns the information that Replication is enabled in server, repl. server is connected Replication is active and displays the statistics lists.

Stop the enqueue server and the message server manually. Move the VIPA to the system, where the replication server is started and start the SCS instance there. The replication server must stop itself after the enqueue table has been rebuilt.

Run:

enqt pf=/usr/sap/HA1/SYS/profile/HA1_SCS01_ha1scsv 20

again. If it displays the same output as it did before you stopped the enqueue server, you verified that replication works.

Note: As described in Adapt the Java property ms.reconnect.timeout, a Java application server stops and restarts if it can reconnect to the Java message server within the time that is defined by property ms.reconnect.timeout. If your manual failover takes longer than your timeout setting, adapt that property for manual failover tests.