本文說明了如何定製化JHipster-Registry，增加訊息匯流排功能。
實現的效果就是修改配置中心的檔案後，通過訊息佇列主動推送給微服務而無需重啟微服務，實現配置內容熱載入。

1 整體規劃

1.1 拓撲架構

1.2 基礎設定

1.3 相關元件

2 JHipster Registry定製

2.1 下載原始碼

Github上下載jhipster-jhipster原始碼。
https://github.com/jhipster/jhipster-registry/releases

2.2 提交到GitLab

儲存到本地Gitlab原始碼庫

2.3 配置檔案定製

pom.xml

<dependency>
     <groupId>org.springframework.cloud</groupId>
     <artifactId>spring-cloud-starter-bus-amqp</artifactId>
</dependency>
<dependency>
      <groupId>org.springframework.boot</groupId>
     <artifactId>spring-boot-starter-actuator</artifactId>
</dependency>
 

application.yml

management:
    security:
        enabled: false
    context-path: /management       # 訊息匯流排的url，這個字首要加在 /bus/refresh 前面

application-prod.conf

spring:
   rabbitmq:
        host: rmqha_proxy
        port: 56729
        username: guest
        password: guest
        publisher-confirms: true     # 生產者訊息確認
        addresses: rmqha_proxy       # 客戶端訪問server地址, 作為傳送者，配置和host一致

2.4 專案構建

在安裝了jdk，maven, yarn，nodejs的centos7伺服器上執行命令

yarn && yarn install    #前端資源配置生成
mvn -Pprod clean package dockerfile:build   #專案構建並打包成docker映象，版本號為3.0

2.5 服務啟動

docker service create --name base-registry --replicas 1 --network mycloud_base-overlay --constraint node.labels.mycloud.node.type==worker --constraint node.labels.mycloud.node.env==dev --env SPRING_PROFILES_ACTIVE=prod,git --env JHIPSTER_SECURITY_AUTHENTICATION_JWT_SECRET=gdd904a2dffb3eaf28a318b49e0ab986cc51012k --publish 8761:8761 dtr.devops.mycloud.com/common/jhipster-registry:3.0

可通過如下url訪問
http://<IP>:8761

3 客戶端服務定製

3.1 建立專案

通過jhipster生成一個微服務，名為my-client。

3.2 提交到GitLab

儲存到gitLab庫[email protected]:root-cloud/mycloud-monitor.git

3.3 配置檔案定製

pom.xml

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-web</artifactId>
</dependency>
<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-eureka</artifactId>
</dependency>
<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-bus-amqp</artifactId>
</dependency>
<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-actuator</artifactId>
</dependency>

application-prod.yml

eureka:
    instance:
        prefer-ip-address: true
    client:
        service-url:         # 指向eureka伺服器
            defaultZone: http://admin:${jhipster.registry.password}@base-registry:8761/eureka/       

spring: 
   rabbitmq:
        host: rmqha_proxy
        port: 56729
        username: guest
        password: guest
        publisher-confirms: true         # 生產者訊息確認
        addresses: rmqha_proxy       # 客戶端訪問server地址, 作為傳送者，配置和host一致

bootstrap-prod.yml

spring:
    cloud:
        config:
            fail-fast: true
            retry:
                initial-interval: 1000
                max-interval: 2000
                max-attempts: 100
            uri: http://admin:${jhipster.registry.password}@base-registry:8761/config       # 指向配置伺服器
            # name of the config server's property source (file.yml) that we want to use
            name: mq-client
            profile: rd # 注意這裡是rd分支，springcloud-config.git上的rd分支
            label: master # toggle to switch to a different version of the configuration as stored in git
jhipster:
    registry:
        password: admin

MyClientApp.java

@(JHipster)RefreshScope     # 加上這個註解 
public class MyClientApp {
    ......
}

3.4 新增測試程式碼

application-prod.yml

application:
    domain: http://yourcompany.com/2017        # 增加一個配置項

ApplicationProperties

@ConfigurationProperties(prefix = "application", ignoreUnknownFields = false)
public class ApplicationProperties {
    private String domain = "http://default";
    public String getDomain() {
        return domain;
    }
    public void setDomain(String domain) {
        this.domain = domain;
    }
}

TestResource.java

@RestController
@RequestMapping("/management")
public class TestResource {
private final ApplicationProperties appProperties;

   @GetMapping("/mq/property")
    @Timed
    public ResponseEntity<String> getproperty() {
        return ResponseUtil.wrapOrNotFound(Optional.ofNullable(appProperties.getDomain()));
    }
}

3.5 專案構建

在安裝了jdk，maven, yarn，nodejs的centos7伺服器上執行命令

$ mvn -Pprod clean package dockerfile:build   #專案構建並打包成docker image

3.6 服務啟動

docker service create --name mq-client-mysql --replicas 1 --network name=mycloud_base-overlay,alias=mq-client-mysql --constraint node.labels.mycloud.node.type==worker --constraint node.labels.mycloud.node.env==data --env MYSQL_ROOT_PASSWORD=my-secret-pw --publish 32781:3306 dtr.devops.mycloud.com/common/mysql:5
docker service create --name my-client-app --replicas 1 --network mycloud_base-overlay --constraint node.labels.mycloud.node.type==worker --constraint node.labels.mycloud.node.env==dev --env SPRING_PROFILES_ACTIVE=prod,swagger --publish 18081:8081 dtr.devops.mycloud.com/yourcompany/my-client:1.0

可通過如下url訪問
http://<IP>:18081

4 測試效果

4.1 第1次查詢配置項

http://<IP>:18081/management/mq/property

http://yourcompany.com/2017      # 返回值

4.2 修改配置項

application:
    domain: http://yourcompany.com/2018        # 把2017改成了2018

4.3 第2次查詢配置項

http://<IP>:18081/management/mq/property

http://yourcompany.com/2017      # 返回值沒有改變

4.4 通知訊息匯流排

$ curl -X POST http://<IP>:8761/management/bus/refresh

4.5 第3次查詢配置項

http://<IP>:<port>/management/mq/property

http://yourcompany.com/2018      # 返回值已經更新為2018