MSMQ and Biztalk

Hi, today we see the use of MSMQ and integration with biztalk (send & receive)


First step: install MSMQ on server (same or another):

1. Open the Windows Control Panel from the start menu, double-click on Add/Remove Programs and then click on the Windows Components tab to launch and display the Windows components wizard.

2. Click on Application Server and then click Details.

3. If the Message Queuing checkbox is selected it means the service is already installed and you can thus skip the rest of this section. If it is not, then you need to follow the rest of the steps below to install the message queuing service. In the Application Server dialog click on Message Queuing and then click Details.

 

4. In the Message Queuing dialog select the Core functionality checkbox and then click OK.

5. In the Application Server dialog click OK and then click Next in the Windows Components Wizard window to start installing the message queuing service.

6. When the installation of the message queuing service is complete, you need to click Finish in the Windows Components Wizard. The Message Queuing Service is now installed.

Second step: Create QUEUE ( we will create a private queue)

1.  Open the Computer Managment

 

2. Create a new private queue , set name , is transactional or none (remember this parameter)

Third step:  Biztalk , send and receive port ( if you want make a dummy orchestration )

1. the send port configure 

(set in trasport advanced tab ORDERED DELIVERY)

and configure... is

the parameter TRANSACTIONAL must egual to parameter queue.... and the destination is the name of queue.

2. Receive port is configured :

and the configure...

set oredered processing TRUE and the batch size  = 1.


Now, must you able to use MSMQ.

NOTE: it's important you remember, the message max dimension is 4 MB !! for larger message read my post "larger message queue"

bye

Using system.byte[] in map biztalk 2006

Hi
when you using a byte[] into map, you make or in script functoid or in dll .net this:
public string GETXXX(string fileurl)
byte[] content = null;
try
    {
     System.IO.FileInfo file = new System.IO.FileInfo(fileurl);
      content = System.IO.File.ReadAllBytes(file.FullName);
       }
       catch (Exception ex)
      {
       content = null; //optional , your logic ....
       System.Diagnostics.Debug.WriteLine(ex.Message); //optional
       }
return System.Convert.ToBase64String(content); //this is the code right!! into the map the destination field is a BINARY but you pass a string converted!

bye

BizTalk 2006 R2 - consume an .ASMX webservice using WCF-BasicHttp adapter

Normally when we need to consume a .asmx web service in BizTalk 2004/2006 (NOT R2) inside an orchestration, we add a web reference, which will create all the multi-part message and web port type required to consume the orchestration. You construct the orchestration and configure the SOAP adapter in the send port to consume the web service. I suppose that's the normal route any BizTalk developer will take when you are put under a circumstance to consume an .asmx webservice using WCF-BasicHttp adapter.
But when you are going to use the WCF-BasicHttp adapter, "Add Web Reference" is not going to work, and we need to take advantage of the hidden "Consume WCF Service" wizard, which comes as part of BizTalk 2006 R2. The wizard will generate required schemas, multi-part messages, orchestration port types, and also binding files for both basicHttp and custom binding. I'll put the steps here to consume a basic .asmx webservice in BizTalk 2006 R2 with WCF-BasicHttp adapter.

1. Create a blank BizTalk Project
2. Right-Click on the project and select Add->Add Generated Items->Consume WCF Service
3. Select the option "Metadata file (WSDL and XSD)", Click "Next" 
4. Open an instance of a browser and navigate to your ".asmx?WSDL" file and save it somewhere in your harddrive (Example: c:\Service.wsdl).
5. Click on the "Add" button (next step in the wizard after the one shown above), browse to the .WSDL file you saved in Step 4, Click "Next" (Accept defaults), Click "Import" and then Click "Finish" to complete the wizard.
6. Once you click "Finish" the following files will be added to your project (File name will depend on the name of the .WSDL file you selected)
   Service.BindingInfo.xml
   Service.odx
   Service_Custom.BindingInfo.xml
   Service.tempuri_org.xsd
7. Open the Service.odx file, inside the orchestration view create 2 messages as shown below
   WSRequest - Multi-part Message Type - ConsumeWebService.ConcatNameSoapIn
   WSResponse - Multi-part Message Type - ConsumeWebService.ConcatNameSoapOut
8. Right-Click on the orchestration "Port Surface", Click "Next", In the port properties page Click "Next", In the "Select a Port Type" page select "Use an existing Port Type" and select "ConsumeWebService.ServiceSoap", In port binding page select "I'll be sending a request and receiving a response." for port direction and "Specify later" for port binding. Click "Next" and then "Finish".
9. Make your orchestration logic....
10. Deploy your orchestration ..and configuring the ws port 
11. Open BizTalk Administration Console, Right-Click on the application and select "Import Binding". Browse to the auto generated binding file "Service.BindingInfo.xml" and select it. Bind your Orchestration to the correct ports and host. For the .asmx webservice logical port, select the auto generated "WcfSendPort_Service_ServiceSoap".
12. Configuring other port if present ... go!

 The point 4 and 5 are the answer!!
bye.

Cannot locate document specification because multiple schemas matched the message type

Error:
Cannot locate document specification because multiple schemas matched the message type

Resolve:
In the pipeline definition that you find at the receive location level, you may set the 'Allow Unrecognized Documents' to true.
By using this option, you wouldn't have the conflict between two namespaces 

Biztalk 2010 - new features

BizTalk Server 2010 introduces enhancements and new features in four main areas:

    * Support for the latest platforms from Microsoft including server, database and development environment.
    * Enhanced developer productivity and new application life cycle management experience for development teams.
    * New capabilities for implementing agile SOA integration solutions across heterogeneous technologies and Line of Business systems.
    * Enhanced B2B and RFID capabilities to allow the implementation of flexible end-to-end supply chain management and asset tracking solutions.

BizTalk Server 2010 introduces enhancements and new features in four main areas:   
    * Support for Visual Studio 2010
    * Support for .NET Framework 4
    * Support for Windows Server 2008 R2
    * Virtualization support with Hyper-V
    * Support for SQL Server 2008 R2  
    * Easy to use BizTalk Data Map and Line-of-Business Connectivity Workflow Foundation (WF) Activities for .NET developers
    * Seamless ability to leverage BizTalk capabilities from SharePoint 2010 Business Connectivity Service to Line-of-Business systems
    * New intuitive & intelligent Data Map and Transformation tools
    * Improved Visual Studio project and wizard-driven tools to build integration solutions with IBM Mainframe and Midrange Systems
    * Built-in components for rapid development of RFID solutions   
    * Single, comprehensive parameter settings dashboard for efficient performance tuning and streamlining deployments across environments
    * New System Center Management Pack to provide enhanced visual monitoring and diagnostics
    * Streamlined setup and live update
    * Support for SQL Server backup compression
    * Support for transparent data encryption   
    * Efficient B2B integration with scalable Trading Partner Management and advanced capabilities for complex data mapping
    * Secure FTP with new FTPS Adapter and an improved FTP Adapter
    * Adapter support for the latest application versions: SAP7, Oracle eBS 12.1, J.D. Edwards 9.0, SQL Server 2008 R2, SharePoint 2010
    * Updated industry protocol adapters
    * Enhancements to the IBM Hosts Systems Adapters


data from: 
http://www.microsoft.com/biztalk/en/us/whats-new.aspx

Biztalk 2010 - requirements

BizTalk Server Requirements

 

BizTalk Server Hardware Requirements

The following table shows the minimum recommended hardware requirements for a BizTalk Server 2010 installation on a single computer. In a production environment, the volume of traffic may dictate greater hardware requirements for your servers.

Component	Minimum Requirement
Computer and Processor	A computer with an Intel Pentium-compatible CPU that is: 1 GHz or higher for single processors 900 MHz or higher for double processors 700 MHz or higher for quad processors Hyper-Threading and Dual-Core processors are supported. The 64-bit versions of BizTalk Server require a 64-bit operating system running on an x64-based system. Computers based on CPUs that are compatible with the AMD64 (x86-64) and Extended Memory 64-bit Technology (EM64T) processor architecture are considered x64-based systems. (Standard Edition supports 64-bit operating system but not in native 64-bit execution mode) BizTalk Server is not supported on Itanium-based systems.
Memory	2 GB of RAM
Hard disk	10 GB of available hard disk space for a complete installation including the operating system and all prerequisite software. The hard disk must be NTFS formatted.
Drive	CD-ROM or DVD-ROM drive
Display	Windows Server 2008-compatible VGA or higher-resolution monitor set to 1024 x 768 pixels or greater resolution
Other	Network adapter card, and a Microsoft mouse or compatible pointing device

BizTalk Server Software Requirements

• One of the following operating systems:
  ▪ Windows Server 2008 R2
  ▪ Windows Server 2008 with Service Pack 2
  ▪ Windows 7
  ▪ Windows Vista with Service Pack 2
• Microsoft Internet Information Services (IIS) 7.0 or 7.5
• Microsoft Office Excel 2010 or 2007
• Microsoft .NET Framework 4 and .NET Framework 3.5 SP1
• Microsoft Visual Studio 2010 with Visual C# .NET. Required for BizTalk Server applications development and debugging; not required for production-only systems
• SQL Server 2008 R2 or SQL Server 2008 SP1
• SQL Server 2005 Notification Services with Service Pack 2
• The Windows SharePoint Services adapter Web service requires SharePoint Server 2010, SharePoint Foundation 2010, Windows SharePoint Services 3.0 with Service Pack 1, or Microsoft Office SharePoint Server 2007.

If you intend to install BizTalk RFID side-by-side with BizTalk Server the following software components are required in addition to the requirements listed above:

• Microsoft Message Queuing service (MSMQ)
• Microsoft Management Console (MMC) 3.0

Silverlight Developer runtime not installed

[ENG]
When I try to debug a silverlight application in VS2010 I get a message "Unable to start debugging. The Silverlight Developer Runtime is not installed. Please install a matching version."

Download from here the Silverlight for developer
http://go.microsoft.com/fwlink/?LinkID=188039



[ITA]
 Lanciando la mia applicazione web (con componenti silverlight) da VS2010 mi sono ritrovato questo errore: "Non è possibile lanciare il debug, silverlight developer runtime mancante,..."

Dopo alcune ricerche ho trovato il link per scaricare il pacchetto, che lo trovate qui:
http://go.microsoft.com/fwlink/?LinkID=188039

ciao.