Kirjojen hintavertailu – 12 903 725 kirjaa ja 27 kauppaa

Kirjailija

Kent Weare

Kirjat ja teokset yhdessä paikassa: 2 kirjaa, julkaisuja vuosilta 2011–2014, suosituimpiin kuuluu Microsoft BizTalk 2010: Line of Business Systems Integration. Vertaile teosten hintoja ja tarkista saatavuus suomalaisista kirjakaupoista.

2 kirjaa

Kirjojen julkaisuvuodet: 2011–2014.

(MCTS) Microsoft BizTalk Server 2010 (70-595) Certification Guide ()

(MCTS) Microsoft BizTalk Server 2010 (70-595) Certification Guide ()

Johan Hedberg; Morten la Cour; Kent Weare

Packt Publishing Limited
2014
nidottu
A handson certification guide with practical examples and sample questions and answers to help BizTalk developers pass the Microsoft BizTalk Server 2010 (70595) exam. If you are an intermediate level BizTalk developer who wants to pass the Microsoft BizTalk Server 2010 (70595) exam, then this book is for you. A working knowledge of fundamental BizTalk concepts around the core messaging engine and building business processes using orchestrations is assumed but not required. In addition, core knowledge of Windows Communication Foundation (WCF) and a basic understanding of Electronic Data Interchange (EDI) is recommended.
Microsoft BizTalk 2010: Line of Business Systems Integration

Microsoft BizTalk 2010: Line of Business Systems Integration

Kent Weare; Richard Seroter; Sergei Moukhnitski

Packt Publishing Limited
2011
nidottu
This book focuses on Microsoft BizTalk 2010; however, most of the concepts and explanations will apply to BizTalk 2006 R2 and BizTalk 2009. If you are an experienced BizTalk developer who wants to integrate BizTalk with Line of Business systems using practical scenarios, then this book is for you. A solid understanding of BizTalk at an intermediate level is required. This book assumes developers are comfortable creating schemas, maps, orchestrations, ports and messages in Visual Studio and configuring applications in the BizTalk Administration Console. However, experience in integrating with Line of Business systems is not necessarily required.