To check if your SAP Java System is running, open the JSMON command line tool. Enter the values for JSMON’s SERVER1_AS_DETAILS and SERVER1_AS_NUM parameters. In the output of the JSMON, you should see the number of active server nodes and services. If the number is zero, the AS Java instance is not running.
During this process, you can check whether the SAP Java instance is running by entering the name of the SAP database in the command line. It should be present in the rh1_sap_database_group. If the SAP database instance is running, the RSJava-ApplicationServices resource agent is part of the group. You can also check if it is running using the pcs status command.
In addition, the ERS and FS resource agents are part of the AS Java instance. If both of them are running, the AS Java instance is running. If the FS has failed, you can check if it is running by viewing its status in the System Status dialog. You will need administrator privileges to access this dialog. To find out if the AS Java instance is currently running, you can perform a connection check.
Next, check if your SAP HANA instance is running. You can use the pcs-monitor to see if your SAP HANA server is running. You can also run a pcs-monitor to monitor the failover process. This will show you whether the cluster is running on a single node or in clusters. During the failover process, you must use a sysrq-trigger to monitor the process.
To check if your SAP HANA cluster has successfully failed, you should run the crm-monitor. This command will show you if the cluster is running on both nodes. Then, you should run a pc-monitor to find out if your SAP server is down. If the SAP HA interface is down, you should use a separate RS for each instance.
You can also run pc-monitor. This will show you if the AS Java instance is running on a node. The RSJava-monitor will be able to tell you if the ASJava instance is running. However, this command will not tell you if the ASJava is up or not. After the failure, you can continue to monitor your system.
When you run pc-monitor, you can also see if the ASJA is up and running on both nodes. If it is, you will see that the RSJava cluster has started. If the RSJ server is up, it will start up in a separate node. If the cluster is up and running, it will have an RSJ-trigger configured to monitor the failover process.
If you are unsure whether or not the SAP-SUSE-Cluster-Connector is running, you can use the rh2_ascs20 filesystem as the host to test the cluster’s availability. Then, pcs-monitor will tell you the RSJ-configure filesystem’s clone status. This means that the SAP-SUSE-Cluster-Adapter is running and is available on the target host.
The first thing to do to test the SAP-SUSE-Cluster-Connector is to install the RH2_ASC20 resource agent. This resource agent is used to create a PAS instance. The RH1_PAS_D01_group is the FS and ERS of the cluster. Then, you need to use pcs_mon to test whether or not the SAP-SUSE-Cluster-connector is running.
In a dual stack SAP system, the AS Java instance is managed remotely by a user in the SAP System. In a dual-stacked SAP system, this user must be created in the SAP ABAP user management administration console and the AS Java instance. The role must be assigned to the SAP_JAVA_NWADMIN_CENTRAL_READONLY, the ERS and ASJA-Java are linked to each other via SPI for SAP.
The next step to check if your SAP ABAP instance is running is to log into SAP PI. In a normal SAP environment, you should have administrator access to the system. You must be able to login as root to the SAP ABAP ES and JAVA. If you do not have administrative privileges, you must access the backend server to check for the SAP ABAP application.