Quantcast
Channel: BizTalk Server 2010 Documenter
Viewing all 27 articles
Browse latest View live

Created Feature: Output documentation for use in a difference check [23]

$
0
0
Is there anyway to output documentation for use in a difference check, e.g. as an XML file?

I'd like to be able to export the _"documentation"_ of an application from say the TEST and STAGING environments, and then use a diff tool, e.g. Beyond Compare, so we could check through any differences between the two _"versions"_ of the application

Cheers,
SteveC.

New Post: Output documentation for use in a difference check

$
0
0
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.

Created Issue: Documenter reporting host instances for WCF-Custom receive locations incorrectly [24]

$
0
0
Generally, a great tool, thanks to everyone for their hard work and contributions.

Today, I ran into an issue where the tool incorrectly reported all my WCF-Custom endpoints as being hosted by the default application (in this case, BizTalkServerApplication) rather than what is configured and shows in AdminConsole.

I know there is a known BizTalk issue whereby all dynamic ports get hosted by the default application regardless of your setting in code. Just wondering if there's a similar issue with WCF-Custom, or if this is actually a BizTalk Documenter bug. Thanks!

New Post: Documenter reporting host instances for WCF-Custom receive locations incorrectly

$
0
0
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.

New Post: Documenter reporting host instances for WCF-Custom receive locations incorrectly

New Post: Orchestration filter expression

Commented Feature: Output documentation for use in a difference check [23]

$
0
0
Is there anyway to output documentation for use in a difference check, e.g. as an XML file?

I'd like to be able to export the _"documentation"_ of an application from say the TEST and STAGING environments, and then use a diff tool, e.g. Beyond Compare, so we could check through any differences between the two _"versions"_ of the application

Cheers,
SteveC.
Comments: Are you looking for code differences or configuration differences? If it is configuration differences have a look at utility https://biztalkdeployutil.codeplex.com/ There is also a code to deployed difference tool out there that I can look for if that's what you are after. I've also added this as a feature task for the new BizTalk Server 2013 Documenter. https://biztalk2013documenter.codeplex.com/workitem/1855

New Post: Output documentation for use in a difference check


Created Unassigned: Error Generating Documentation Filter XML is malformed [25]

$
0
0
I have used BTS 2006 without any issues, today I downloaded the 2006-2010 version for a BTS 2K10 platform. When I run it I get an error message box as follows: (Full error snapshot in the attached image

The Filter XML is malformed (quite often caused by the binding being reformatted and putting whitespace in front of the filter XML)
<?XML version="1.0".....utf-16>
<Filter xmlns......>
<Group>
<Statement Property="ErrorReport.FailureCode" Operator="6" />
</Group>
<Group>
<Statement Property="Microsoft.Practices.ESB.ExceptionHandeling.Schemas.Property.FaultCode" Operator="6" />
</Group>

Thanks in advance

Commented Unassigned: Error Generating Documentation Filter XML is malformed [25]

$
0
0
I have used BTS 2006 without any issues, today I downloaded the 2006-2010 version for a BTS 2K10 platform. When I run it I get an error message box as follows: (Full error snapshot in the attached image

The Filter XML is malformed (quite often caused by the binding being reformatted and putting whitespace in front of the filter XML)
<?XML version="1.0".....utf-16>
<Filter xmlns......>
<Group>
<Statement Property="ErrorReport.FailureCode" Operator="6" />
</Group>
<Group>
<Statement Property="Microsoft.Practices.ESB.ExceptionHandeling.Schemas.Property.FaultCode" Operator="6" />
</Group>

Thanks in advance
Comments: I just wanted to add that the application Microsoft.Practices.ESB is not used and it is not running. I get this error even when I try to document an assembly

New Post: Duplicate Addition Detected

$
0
0
I am using documenter BizTalk.Utilities.Documenter.Setup.msi (for BTS2K10).
It works fine for almost all applications except one when I run it to document it, I get the following error
DUPLICATE ADDITION DETECTED : Cannot add duplicate items to collection. Attempted to add item name : Provider QName.

Thanks for your help

New Post: Using command line

$
0
0
Hi,

I'm trying to use the documenter from the command line, but even if I use /def, I don't get generated documentation.

What could be wrong and how do I get more information of what's wrong?

Thanks in advance!
Lex

New Post: BizTalk Documenter 2010 : Index and Search Tab

$
0
0
Hi,
I have tested BizTalk Documenter 2010, it is a great tool. But I can't figure out how to add an Index and a Search Tab in the chm file. Can you explain me how to do that please ?
Best regards
Minh Quang

Reviewed: BizTalk 2010 Documenter V1.1.0.0 (Mar 16, 2015)

$
0
0
Rated 4 Stars (out of 5) - That is a great tool that help me a lot. I have a suggestion : it would be great to add an Index and a Search tab in the chm file by looking a keywords thesaurus list for example.

Commented Unassigned: Error Generating Documentation Filter XML is malformed [25]

$
0
0
I have used BTS 2006 without any issues, today I downloaded the 2006-2010 version for a BTS 2K10 platform. When I run it I get an error message box as follows: (Full error snapshot in the attached image

The Filter XML is malformed (quite often caused by the binding being reformatted and putting whitespace in front of the filter XML)
<?XML version="1.0".....utf-16>
<Filter xmlns......>
<Group>
<Statement Property="ErrorReport.FailureCode" Operator="6" />
</Group>
<Group>
<Statement Property="Microsoft.Practices.ESB.ExceptionHandeling.Schemas.Property.FaultCode" Operator="6" />
</Group>

Thanks in advance
Comments: It sounds like the version of BizTalk Documenter you are using is the one from this https://biztalk2013documenter.codeplex.com/ project, as that warning does not exist in this version. A filter on one of your ports is malformed (and will actually not be working as expected). This is usually occurs when you've editing a Binding File in Visual Studio and it's reformatted that segment. The Binding File will still successfully be imported, however the Filter will not actually show up when you look at it in BizTalk Administration Console, nor will it actually work. It is strange however that is is occurring on one of the ESB Ports for which you are unlikely to have imported the bindings. Run the BizTalk Documenter telling it only to document specific applications rather than everything.

New Post: Duplicate Addition Detected

Commented Issue: Documenter reporting host instances for WCF-Custom receive locations incorrectly [24]

$
0
0
Generally, a great tool, thanks to everyone for their hard work and contributions.

Today, I ran into an issue where the tool incorrectly reported all my WCF-Custom endpoints as being hosted by the default application (in this case, BizTalkServerApplication) rather than what is configured and shows in AdminConsole.

I know there is a known BizTalk issue whereby all dynamic ports get hosted by the default application regardless of your setting in code. Just wondering if there's a similar issue with WCF-Custom, or if this is actually a BizTalk Documenter bug. Thanks!
Comments: Yes, that is a known bug with this version of Documenter, see https://biztalk2010autodc.codeplex.com/workitem/16 Please download the latest version of Documenter from https://biztalk2013documenter.codeplex.com/ It should be fixed there

Edited Issue: Documenter reporting host instances for WCF-Custom receive locations incorrectly [24]

$
0
0
Generally, a great tool, thanks to everyone for their hard work and contributions.

Today, I ran into an issue where the tool incorrectly reported all my WCF-Custom endpoints as being hosted by the default application (in this case, BizTalkServerApplication) rather than what is configured and shows in AdminConsole.

I know there is a known BizTalk issue whereby all dynamic ports get hosted by the default application regardless of your setting in code. Just wondering if there's a similar issue with WCF-Custom, or if this is actually a BizTalk Documenter bug. Thanks!

New Post: BizTalk Documenter 2010 : Index and Search Tab

Updated Wiki: Home

$
0
0

Updated version (18/Sep/2014)

Due to some issues with source control in this CodePlex solution that are still have to be resolved and wanting to release the new BizTalk 2013 Documenter, Mark Brimble and Colin Dijkgraaf have released a new version of BizTalk Server 2010 documenter download along with the BizTalk Server 2013 documenter and it's code in a new Codeplex Project at BizTalk Server 2013 Documenter    Please download the appropriate version from there as this code base is no longer being updated.

 

Overview
Having recently become involved in BizTalk I was happy to find the BizTalk Server 2006 Documenter but unfortunately it did not run correctly in  the environment that I was using.  
I have spent some time modifying, fixing and enhancing the application for use in the environment I use in my work.  The project now includes modified files from the BizTalk OM project and the SSO Config project. It has been compiled in Visual Studio 2010 and tested on BizTalk 2010 running on Windows Server 2008 R2.  Having now used it to successfully document the environments in my workplace I thought I should offer the installation files and source code to those who may find it useful as I found the original BizTalk Server 2006 Documenter


Project Description
I have not removed any of the functionality of the original project. In this edition I have concentrated on the GUI and the compiled help functionality.  So the description remains the same as it did for the BizTalk Server 2006 Documenter, with the following fixes/enhancements:

  • GUI modified to resemble more of a wizard, step by step style.
  • Fixed, click through functionality on Orchestration diagram
  • Transformations added to Orchestration Code Elements page including input and output message(s).
  • New click through functionality on above transformations
  • Fixed, object descriptions pulled through into documentation (Code Elements page)
  • Added, SSO integration. Will now document SSO applications
  • Fixed, Documents exported BizTalk configuration file (xml)
  • Enhanced, can now include additional HTML documentation by selecting folder it is held in. These documents appear under 'Additional Notes'. Any file called titlePage.htm will replace the default title page.

Known Issues

  • Will not run successfully if a .chm file is open of the same name and path of the one you are trying to create.
  • Needs to be run on the actual server you are documenting.
  • Word documentation is incomplete (I have not done any work on this side of things yet).
  • Rules Engine documentation not tried or tested.
  • See  BizTalk Server 2006 Documenter for other issues.


Viewing all 27 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>