Skip to main content

Red Hat JBoss BPM Suite - 使用SSH 操作 GIT 專案




原作: Red Hat JBoss BPM Suite - access GIT project using SSH
===============================================================================

自從上週Red Hat JBoss BRMS 與 Red Hat JBoss BPM Suite v6 專案正式發表後,這是我最常被問到的問題。

本文會用JBoss BPM Suite 當作主要的範例,JBoss BRMS 做法上也是一樣的。 所以下面的解答適用在兩個產品上。

因為這次開發跟部署的儲存庫底層都改成GIT了。

如果我們仔細點看一下JBoss BPM Suite 的架構,可以看到聯結商業使用者和開發團隊的儲存庫就是一個GIT 的儲存庫。

JBoss BPM Suite architecture

一般的流程會有一個商業分析師使用 JBoss BPM Suite 網路的GUI 工具中的 Model designers (模型設計), process designers (流程設計), 和不同的 rule designer (規則設計) 設計內容,並將其整合成一個專案。開發者在以上的工作做完或是在同時的時候開發應用程式,並同時幫忙商業分析師。

以前我們在測試跟使用Beta版的時候,我們用的是沒有安全機制的 GIT 通訊協定, 所以你可以不用認證就將內容clone 跟 push 到儲存庫裡。所以看起來會像下面的 Generic Loan Demo 範例,複製一個只能讀的專案到本地端。






$ git clone git://localhost/bpms-generic-loan

Cloning into 'bpms-generic-loan'...
remote: Counting objects: 266, done
remote: Finding sources: 100% (266/266)
remote: Getting sizes: 100% (213/213)
remote: Compressing objects:  51% (110/212)
remote: Total 266 (delta 22), reused 133 (delta 19)
Receiving objects: 100% (266/266), 47.97 KiB, done.
Resolving deltas: 100% (54/54), done.

現在正式的產品出來以後,就不能這樣隨便沒有認證就把你的變動 push 到上面去。

如果你試著把變動push 上去後,你就會看到以下的錯誤. 
$ git push

fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

要正確執行專案的 clone 與 push,現在必須要透過SSH 通訊協定才可以了,一樣使用 Generic Loan Demo 範例: 


透過安全認證複製專案

$ git clone ssh://erics@localhost:8001/bpms-generic-loan

Cloning into 'bpms-generic-loan'...

The authenticity of host '[localhost]:8001 ([127.0.0.1]:8001)' can't be established.
DSA key fingerprint is 62:c2:c5:4c:22:3a:dd:8e:24:34:bf:3f:16:e7:3c:73.
Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '[localhost]:8001' (DSA) to the list of known hosts.
Authenticated with partial success.
Password authentication

Password: bpmsuite   <<<<< enter-password-here

remote: Counting objects: 266, done
remote: Finding sources: 100% (266/266)
remote: Getting sizes: 100% (213/213)
remote: Compressing objects:  51% (110/212)
remote: Total 266 (delta 22), reused 133 (delta 19)
Receiving objects: 100% (266/266), 47.97 KiB, done.
Resolving deltas: 100% (54/54), done.

透過安全認證複製更新專案變動


$ git push

Authenticated with partial success.
Password authentication

Password: bpmsuite   <<<<< enter-password-here

Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 282 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: Resolving deltas: 100% (2/2)
remote: Updating references: 100% (1/1)
To ssh://erics@localhost:8001/bpms-generic-loan
   f789a22..659ef75  master -> master


希望這篇文章有助於你探索和拓展你對JBoss BPM Suite 知識,同時在上開發自己的BPM項目。

Comments

Popular posts from this blog

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.


2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.


So, now we know …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.



And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

jboss-devstudio-9.0.0.GA-installer-eap.jar
double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.


And select JBoss Fuse Development for the plugin,


Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …