Biztalk Port / Orchestration Documentation

We have a great EAI setup (+ - 70 orchestrations, 200 send ports, ...). Almost none of the orchestras / ports have direct bindings. Each route is configured using filters.

Unfortunately, it's time to document the integration scenario that non-biztalk technologists understand.

I wondered if there are any tools / word -excel-visio -... templates for documenting such a scenario. There is no need to document the technical data of the orchestra / cartographic / code, as well as the message flow. (rcvport / location (with maps) β†’ orchestration (filter) β†’ sendport (s) (with filter, maps)

thank; Bart

+3
source share
3 answers
0

UML.

BizTalk Ports Interfaces . Information flow .

Enterprise Architect Sparx Systems . , , .

, . BizTalk ( ), .

0

Visio . , 10 , . . , , " ".

, - . .

, / . , , ? Visio, , ..... . , . , . .

Cloud Symbol . Visio, FTP- - .

, "MessageBox" . , Receive Port - , "MessageBox" , , , MessageBox. ( "MessageBox" , , , .

SnagIt , Word . ( , .)

, , , , . "BizTalkDocumenter" .

I sometimes use Sheets in Word to show developer artifacts and how they are connected (maps, diagrams, pipelines ...) and include a verbal description / comment for each.

I agree with HSedidin above that BPMN may be worth a try, but even that, the audience will have to learn.

There is a β€œStencil” package for BizTalk available for Vizio here: https://gallery.technet.microsoft.com/Collection-of-Visio-2013-0283d5f4 , but I have to admit that I haven't used it yet.

0
source

Source: https://habr.com/ru/post/1774043/


All Articles