Connect to the open source SOFA Registry

To use the open source registry, you must configure the com.alipay.env parameter in your application. This parameter sets the operating mode for SOFA middleware clients. By default, Spring Cloud SOFA configures this parameter automatically to connect applications to the commercial SOFA middleware. To use non-commercial middleware, you must change this configuration manually.

Start the open source SOFA Registry locally

1. Download the open source SOFA Registry installation package.

2. Run the following commands to decompress and start the open source SOFA Registry.

   tar -zxvf registry-integration-fix.tgz
   cd registry-integration-fix
   sh bin/startup.sh

After you run the commands, the registry starts in the background. Check the standard output file for a message that indicates the startup status. The startup is successful if the following information appears in the output file.

Configure an application to connect to the open source SOFA Registry

Configure the following system variables in the application startup parameters:

-Dcom.alipay.confreg.url=127.0.0.1
-Dcom.alipay.env=normal
-Dspring.cloud.sofa.ldc.zone=DEFAULT_ZONE

After you complete the configuration, start the application to connect to the open source SOFA Registry.

Open source SOFA Registry FAQ

• Startup failed

  If the open source SOFA Registry fails to start, try the following steps:

  1. Delete the raftData folder in the registry-integration-fix folder.

  2. If you have multiple network cards or a configured virtual network interface, modify the JAVA_OPTS variable in the startup script. Add -Dnetwork_interface_binding=XX to specify the network card.

  3. Check if the following ports are in use. If they are, shut down the related processes: 9600, 9601, 9603, 9610, 9611, 9612, 9614, 9615, 9620, 9621, and 9622.

  4. Run the startup script again to start the registry.

Differences between the open source and commercial versions of SOFA Registry

The commercial version of SOFA Registry offers better high availability, disaster recovery, multi-region active-active deployment, and performance than the open source version. The following table compares the features of the open source and commercial versions.