Google


Wednesday, August 30, 2006

Deployment failed!

Moved a BizTalk project from Server A to Server B (Servers A and B each with its own SQL Server), When tried to deploy the project at Server B got the following error message: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server), Guess why?
In the properties of project - deployment, the project refered to the SQL Server on Server A, to solve the problem

right click the biztalk project > properties > configuration properties > deployment > BizTalk group > change the Server (SQL) name property to the right one

Cheers,

*[If you think that you have valuable feedback to improve the contents of this blog, please leave it as a comment here]

Monday, August 28, 2006

BTSTask replaces BTSDeploy

For BizTalk Server 2006, you use BTSTask.exe to perform BizTalk application deployment tasks. BTSDeploy is provided for backward compatibility.



Happy BizTalk dev,
Yousef

*[If you think that you have valuable feedback to improve the contents of this blog, please leave it as a comment here]

Tuesday, August 22, 2006

Macros to create file names





When creating a file (send adapter), in the send port properties (See figure 2), you specify the type File in the transport properties and you choose configure to set the File Transaport properties (See figure 1). You wonder what the %MessageID% is in the file name text box,
BizTalk server has a predefined set of macros to create the file names generated. for instance, this %MessageID%.xml generates a file with a name as the Globally unique identifier (GUID) of the message in BizTalk Server. The value comes directly from the message context property BTS.MessageID.



A number of macros are available such as:
%datetime%, %DestinationParty%, %SourceFileName%, for the full list refer to the Microsoft BizTalk Server 2006 help.

*[If you think that you have valuable feedback to improve the contents of this blog, please leave it as a comment here]

Monday, August 14, 2006

I wanna become a BizTalk developer/specialist, HOW?

3 steps,

1 - You have to posses a set of skills/expertise including (basically)

- Working experience and familiarity with Web Services and their specifications WS-*
- Working experience and familiarity with XML and its related technologies (XML schemas [XSD], XSL,...)
- Working experience and familiarity with the UML (the Unified Modeling Language), such as work flow diagrams
- Experienced in the design and development of .NET class libraries\apps
- Familiarity with the networking terminology and concepts
- Good understanding of what SOA is (if possible)

2 - READ the Microsoft BizTalk Server white papers available at
http://www.microsoft.com/biztalk/techinfo/whitepapers/default.mspx

3 - Walkthrough the BizTalk Server tutorials (really good) available at
http://www.microsoft.com/downloads/details.aspx?FamilyID=6a5f6ef4-aeb8-4d8d-a521-37333a875ce4&DisplayLang=en

4 - Try to join the BizTalk Server Team (EAI, BPA team) at the organization you're working for, and immerse your self in BizTalk through developing real world applications

Cheers,

*[If you think that you have valuable feedback to improve the contents of this blog, please leave it as a comment here]

Thursday, August 10, 2006

2 really good tech. articles

Service-Oriented Integration
The Service Interface Pattern

Enjoy a good read,
Yousef

*[If you think that you have valuable feedback to improve the contents of this blog, please leave it as a comment here]

Monday, August 07, 2006

BizTalk Silent Installation [Hussssh baby]

Hola!

I found this very useful; to initiate a biztalk server installation (setup) instance and executing it with no intervention required (No need to walk through the installation wizard). This is what the BizTalk Server 2006 installation guide calls a Silent Installation; it's just a matter of writing a simple batch file that will do the task for you.

- Use this method when installing biztalk on multiple boxes with identical configurations

** Quoted the following section from the Microsoft BizTalk Server 2006 Installation Guide for Microsoft Windows Server 2003

To perform a BizTalk Server 2006 silent installation

1. Click Start, point to All Programs, point to Accessories, and then click Command Prompt.

2. To start the silent installation, at the command prompt, type setup.exe (BizTalk's setup.exe) / , and then press ENTER.

3. Refer to the BizTalk Installation Guide (Link to it was provided in a previous post) for the command-line options that you use to install BizTalk Server 2006.

*[If you think that you have valuable feedback to improve the contents of this blog, please leave it as a comment here]