[Dubbo practice] Dubbo + Zookeeper + Spring Integrated Application-Dubbo implements distributed services based on Zookeeper (2), dubbozookeeper

[Dubbo practice] Dubbo + Zookeeper + Spring Integrated Application-Dubbo implements distributed services based on Zookeeper (2), dubbozookeeper
Dubbo is integrated with Zookeeper and Spring

 

Dubbo uses the full spring configuration method to transparently access the application without any API intrusion to the application. You only need to use spring to load Dubbo configurations. Dubbo is loaded Based on Spring Schema extension.

 

I. Installing zookeeper in standalone Mode

 

1, download zookeeper registration center,: http://www.apache.org/dyn/closer.cgi/zookeeper/ download unzip to enter E: \ zookeeper-3.3.6 \ zookeeper-3.3.6 \ bin,

Double-click zkServer. cmd to start the registry service.

ZkServer. sh [Linux] Or zkServer. cmd [Windows]

 

2. Before you execute the startup script, you need to configure several basic configuration items. The Zookeeper configuration file is under the conf directory, which contains zoo_sample.cfg and log4j. properties, you need to change zoo_sample.cfg to zoo. cfg, because Zookeeper will find this file as the default configuration file at startup. The following describes in detail the meaning of each configuration item in this configuration file.

 

 

 

• TickTime: This is the interval between the Zookeeper server or between the client and the server to maintain the heartbeat, that is, each tickTime sends a heartbeat.

• DataDir: the directory where Zookeeper stores data. By default, Zookeeper stores log files that write data in this directory.

• DataLogDir: As the name implies, it is the directory where Zookeeper stores log files.

• ClientPort: the port connecting the client to the Zookeeper server. Zookeeper listens to this port and accepts access requests from the client.

 

After configuration, zookeeper listens to port 2181 of the local machine.

After these configuration items are configured, you can start Zookeeper now. After starting Zookeeper, check whether Zookeeper is in the service, you can run the netstat-ano command to check whether the clientPort number you configured is in the listening service.

 

Ii. Service Provider

 

Define a service interface: (this interface must be packaged separately and shared with the service provider and consumer)

1. Package com. unj. dubbotest. provider;
3. Import java. util. List;
5. Public interface DemoService {
7. String sayHello (String name );
9. Public List getUsers ();
11. }

 

 

Implement interfaces on the service provider: (hide implementations on the service consumer)

1. Package com. unj. dubbotest. provider. impl;
3. Import java. util. ArrayList;
4. Import java. util. List;
6. Import com. unj. dubbotest. provider. DemoService;
8. Public class DemoServiceImpl implements DemoService {
10. Public String sayHello (String name ){
11. Return "Hello" + name;
12. }
14. Public List getUsers (){
15. List list = new ArrayList ();
16. User u1 = new User ();
17. U1.setName ("hejingyuan ");
18. U1.setAge (20 );
19. U1.setSex ("f ");
21. User u2 = new User ();
22. U2.setName ("xvshu ");
23. U2.setAge (21 );
24. U2.setSex ("m ");
27. List. add (u1 );
28. List. add (u2 );
30. Return list;
31. }
32. }

 

Declare the exposure service with Spring Configuration:

1. <? Xml version = "1.0" encoding = "UTF-8"?>
2. <Beans xmlns = "http://www.springframework.org/schema/beans"
3. Xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns: dubbo = "http://code.alibabatech.com/schema/dubbo"
4. Xsi: schemaLocation = "http://www.springframework.org/schema/beans
5. Http://www.springframework.org/schema/beans/spring-beans.xsd
6. Http://code.alibabatech.com/schema/dubbo
7. Http://code.alibabatech.com/schema/dubbo/dubbo.xsd
8. ">
10. <! -- Specific implementation bean -->
11. <Bean id = "demoService" class = "com. unj. dubbotest. provider. impl. DemoServiceImpl"/>
13. <! -- Provider application information for dependency calculation -->
14. <Dubbo: application name = "xs_provider"/>
16. <! -- Use the multicast broadcast registration center to expose the service address -->
17. <! -- <Dubbo: registry address = "multicast: // 224.5.6.7: 1234"/> -->
19. <! -- Use the zookeeper registration center to expose the service address -- that is, the IP address and port number of the server where zookeeper is located -->
20. <Dubbo: registry address = "zookeeper: // 192.168.24.213: 2181"/>
22. <! -- Expose services on port 20880 using dubbo protocol -->
23. <Dubbo: protocol name = "dubbo" port = "20880"/>
25. <! -- Declare the service interface to be exposed -->
26. <Dubbo: service interface = "com. unj. dubbotest. provider. DemoService"
27. Ref = "demoService"/>
29. </Beans>

Load the Spring configuration, start the service (or build the project as a web project, configure spring startup in web. xml, and then throw it to tomcat to provide the service ):

1. Package com. unj. dubbotest. provider. impl;
3. Import org. springframework. context. support. ClassPathXmlApplicationContext;
5. Public class Provider {
7. Public static void main (String [] args) throws Exception {
8. ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext (
9. New String [] {"applicationContext. xml "});
10. Context. start ();
11. System. in. read (); // to ensure that the service is always on, use the congestion of the input stream to simulate
12. }
13. }

3. service consumers

Use Spring configuration to reference remote services:

1. <? Xml version = "1.0" encoding = "UTF-8"?>
2. <Beans xmlns = "http://www.springframework.org/schema/beans"
3. Xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns: dubbo = "http://code.alibabatech.com/schema/dubbo"
4. Xsi: schemaLocation = "http://www.springframework.org/schema/beans
5. Http://www.springframework.org/schema/beans/spring-beans.xsd
6. Http://code.alibabatech.com/schema/dubbo
7. Http://code.alibabatech.com/schema/dubbo/dubbo.xsd
8. ">
10. <! -- Consumer Application name, used to calculate dependencies. It is not a matching condition. Do not use the same name as the provider. -->
11. <Dubbo: application name = "hjy_consumer"/>
13. <! -- Use the zookeeper registration center to expose the service address -->
14. <! -- <Dubbo: registry address = "multicast: // 224.5.6.7: 1234"/> -->
15. <Dubbo: registry address = "zookeeper: // 192.168.24.213: 2181"/>
17. <! -- Generate a remote service proxy and use demoService like a local bean -->
18. <Dubbo: reference id = "demoService"
19. Interface = "com. unj. dubbotest. provider. DemoService"/>
21. </Beans>

 

Call service test:

1. Package com. alibaba. dubbo. demo. pp;
3. Import java. util. List;
5. Import org. springframework. context. support. ClassPathXmlApplicationContext;
7. Import com. unj. dubbotest. provider. DemoService;
9. Public class Consumer {
11. Public static void main (String [] args) throws Exception {
12. ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext (
13. New String [] {"applicationContext. xml "});
14. Context. start ();
16. DemoService demoService = (DemoService) context. getBean ("demoService ");
17. String hello = demoService. sayHello ("hejingyuan ");
18. System. out. println (hello );
20. List list = demoService. getUsers ();
21. If (list! = Null & list. size ()> 0 ){
22. For (int I = 0; I <list. size (); I ++ ){
23. System. out. println (list. get (I ));
24. }
25. }
26. System. in. read ();
27. }
29. }

Test results:

 

Appendix: Dubbo Management page

 

Need to download: war package for dubbo-admin-2.5.3

: Http://download.csdn.net/detail/u013286716/7041185

 

The procedure is as follows:

 

1. Replace the content of the ROOT folder that comes with tomcat/webapps (that is, replace the tomcat startup homepage), decompress the downloaded war package to webapps/ROOT, and replace it directly.

 

Note: jdk does not use 1.8. This experiment uses 1.6.

 

2. start tomcat and access ip: 8080 or use localhost: 8080 if it is local.

Enter the username and password, which can be viewed in the dubbo. properties file under E: \ apache-tomcat-7.0.6-dubbo \ webapps \ ROOT \ WEB-INF, such:

 

3. Access http: // 192.168.24.213: 38080/

 

 

 

4. Start our service providers and consumers.

 

 

Overall description:

Zookeeper (Registry) is deployed on 213 of machines, and service providers and consumers run on 215 of machines, of course, we can also deploy service providers and service consumers on different machines.

 

 

 

Source code source: http://minglisoft.cn/technology

Add QQ: 2042849237