If you upgrade from a NetWeaver-based system with the SAP SUM tool, be aware that SUM can upgrade the system, it’s configuration, and the profiles, but is not able to change the configuration in Failover Cluster! SWPM 2.0 installs and configures this automatically. To be able to do this, the ASCS profile must contain the (virtual) hostname of the Enqueue Replicator instance.įor more information on how to configure new Enqueue Server 2 and Enqueue Replicator instances, visit the SAP Help Portal. Lesson learned: The Enqueue Server 2 connects to the Enqueue Replicator. The main difference of the new concept is that now the Enqueue Server 2 starts a connection to the Enqueue Replicator and initiates the replication of the lock table. Here are two example screens:ĮRS instance (#10) in a Failover Cluster (now clustered like the ASCS!): The executables are “enq_server.exe” (Enqueue Server 2) and “enq_replicator.exe” (Enqueue Replicator). SWPM 2.0 uses the new executables and concept for S/4 HANA 1809 installations or higher. Lesson learned: The ERS connects to the Enqueue Server. In this configuration, the ERS instance which does not run on the same host where the ASCS instance is running connects to the Enqueue Server and starts the replication of the lock table. Here are two example screens:ĪSCS instance (#00) in a Failover Cluster:ĮRS instance (#10) in a Failover Cluster (installed on each cluster node locally): NetWeaver-based systems use the two executables “enserver.exe” (Enqueue Server) and the “enrepserver.exe” (Enqueue Replication Server). You will learn the differences to the old Enqueue Replication Server (ERS) and the changes in the operations concept. In this blog, I will show you the new Enqueue Server 2 in conjunction with the new Enqueue Replicator.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |