510 likes | 538 Views
Gain insights into new features and changes in BizTalk Server 2009 Beta. Learn about TAP, CTP, and upcoming releases. Explore enhanced B2B, SOA, ESB, EDI, and more. Upgrade tips included.
E N D
18:00 - ”An overview of new features and otherchanges” 19:00 - Paus, mingel, diskussioner 19:30 - ”Build & Deploy automation with Team Foundation Server 2008” 21:00 - En öl någonstans på östermalm… BizTalk Server 2009 Beta
Ochvinnarenär… Anders Zommarin
An overview of new features and otherchanges in BizTalk Server 2009 Beta Johan Hedberg mail: johan.hedberg@logica.com blog: http://blogical.se/blogs/johan im: johan@jeh.se
BizTalk Server 2009? • BizTalk Server 2006 R3 • TAP (private CTP) since early 2008 • Became BizTalk Server 2009 in september • Public CTP Q4 2008 • Release date Q2 2009
Roadmap • A new release every 2 years • 2011 (BizTalk Server “7”) on the drawing board • Prioritized areas: • Developer productivity • Enhanced B2B • Low latency and ESB • Cross-enterprise asset tracking, enterprise manageability, and industry standards (RFID) • BI / BAM • Platform capabilities (ie .NET, Windows, SQL etc.) • XLANG will continue to be BizTalk Servers orchestration technology
Focus areas • Service oriented architecture and Enterprise connectivity • Platform support • SOA and Web Services • B2B Integration • Developer productivity
Application platform • Windows Server 2008 • Hyper-V • Failover Clustering • SQL Server 2008 • SQL Server 2008 Analysis Services • .NET 3.5 SP1 • WCF Improvements etc.
WCF • WCF Adapters • .NET 3.5 bindings for Custom Adapters • Configurable transactions • Transaction Isolation Level • WCF LOB Adapters • Oracle E-Business Suite • SQL Server • And “overall improvements”
Business Activity Monitoring • SQL Server 2008 Analysis Services • Unified Dimensional Modeling (UDM) Cubes • Scalable real-time aggregations • Enhanced PerformancePoint Server 2007 integration • No clustered tables
EDI and AS2 • Enhanced support for EDI and AS2 • Multiple message attachments • Configurable auto message resend • End-to-end filename preservation • Improved reporting • Drummond re-certification for AS2 • BUGS this spring?
What about Covast? • Base EDI Adapter is removed. • Advanced B2B Pack features: • New standards for specific retail segments such as warehousing, grocery, energy, automotive and air freight; • B2B metadata management for EDI "super" interchanges, greater compatibility with SQL Server repository/Visual Studio (EDI Explorer) and new reporting capabilities; • Advanced B2B transports including new file adapters and transports and VAN connectivity; • B2B operations monitor that enables role-based viewing, end-to-end tracking/tracing and automatic archiving.
Service Registry • UDDI 3.0 • Making services discoverable • Previously a SOA tenant missing in BizTalk Server • Subscription API • Register for updates on UDDI entries • Separate install • No integration (as with RFID)
ESB Guidance 2.0 • ESB Guidance 2.0 • Improved Itinerary Processing • Modelling using DSL • Centralized storage • Pluggable resolver adapter pack • Enhanced ESB Management portal • Centralized configuration and caching • BUGS this spring?
RFID • RFID Mobile • Extended administrative tooling • Powershell • Extended operations tooling • System Center Operation Manager • Extended support for industry standards • LLDRP, TDT, TDS, WS Discovery, EPCIS
SWIFT • Enhanced support for SWIFT (Society of Worldwide Interbank Financial Telecommunication)
Host System Integration • Host Integration Server 2009 & BizTalk Adapters for Host System • WCF WebSphere MQ • WCF Service for Host Applications • Transaction Integrator • CICS, IMS, CICS HTTP, DB2, DBS/400, DB2 Universal Database, Websphere MQ
BizTalk Visual Studio projects • New project file structure • BizTalk projects are “a kind of c#” project. • Now uses MSBuild just like other projects • Projects can now contain c# classes • Upgrade will supposedly be automatic
Build Enhancements • Install contains specific “Project Build Component” • Allows building solutions on a machine that has neither BizTalk Server runtime nor Visual Studio. • Build is incremental • Team Foundation Server 2008 • MSBuild and automated builds • Session 2...
Development features • Visual Studio 2008 • Enhanced debugging • Unit testing support • Simplified property access • Static CodeAnalysis
Development features Demo
Administration • One tool! • Enhanced BizTalk Management Console • Asynchronous! • No more HAT! • The move, that began with 2004 -> 2006, is now complete. • Instead • Tracked Message Events • Tracked Service Instances • Slightly updated look and feel • New icons etc. • No EventLog
Administration Demo
Upgrade from BizTalk Server 2006 R2 • Pre-requisite: .NET 3.5 Sp1 • Install before starting upgrade • Stop all hosts, back up all databases (just in case) • Run the upgrade process • No need to re-configure • No need to re-deploy applications • Some cosmetic (presumably beta) issues
Removed features • HAT (well, not really...) • Human Workflow Service (HWS) • Business Activity Services (BAS) • Btsdeploy • If you are using this, consider transitioning to btstask. It’s been marked as deprecated since 2006. • MSMQT • Base EDI Adapter • WSE Adapter
Deprecated features • BizTalk Explorer • SOAP Adapter • Web Services Publishing Wizard • Add Web reference • SQL Adapter
BizTalk Server 2009 Beta Overview Q & A Johan Hedberg johan.hedberg@logica.com http://blogical.se/blogs/johan msn: johan@jeh.se
Build & Deploy automation with Team Foundation Server 2008 and BizTalk Server 2009 Beta Mikael Håkansson mail: mikael.hakansson@logica.com blog: http://blogical.se/blogs/mikael im: wmmihaa@hotmail.com
Agenda • The manual way • Why Automate? • Team Foundation Server 2008 • Automated Build with BizTalk 2006 • Automated Build with BizTalk 2009 • Conclusions
DB Scripts BRE Scripts Source Code Binding files The manual way… VSS BUILD TEST STAGE PROD
Demo ”The manual way”
Why Automated Build Process? Benefits: • Easier version management. • No need to manage assemblies and other resources when exporting MSI packages! • Less manual work. • Enables continuous integration!
Challenges HOGIA SvenskLön Oracle EBS
Architectural Constraints • Isolated Solutions : • No external references • Bindings file oriented • Shared components, artifacts and ports need to be handled separately from the Build Process
What is Team System? Requirement Developer Tester Architects Project Lead DBA Team Foundation Server
What is Team Foundation Server? • Work Item Tracking • Source Control • Team Build
What is Team Foundation Server? Visual Studio 2005 * Edition Visual Studio 2008 * Edition Microsoft Excel Microsoft Project Microsoft SharePoint Custom Visual Studio 2005 Team Explorer Visual Studio 2008 Team Explorer Team Foundation Server 2008
Demo Work Item Tracking & Source Control
The Automated way – BTS2006 • No support for MSBuild! • Requires Visual Studio on Build Server • Have a look at BizTalk Deployment Framework at CodePlex.
Team Build Development Configuration Build automation Feedback Deployment Inspection Testing
Demo CreateBuildType
Infrastructure Team Foundation Client Create build type Start Build/Deploy Reports Build Machine Build Agent MSBuild BizTalk TEST Build Machine Application Tier Build Agent MSBuild BizTalk STAGE Team Build Web Services Build Machine Build Agent MSBuild BizTalk PROD Data Tier Source Code Work items Team Build data
Undeploy Bindings Build & Deploy Process • Publish Build • Trigger Build • Prepare Build • Calculate Code Coverage • Get Sources Custom Tasks • Compile & Analyze • Update Work Items • Deploy Assemblies • Import Bindings • Execute Tests
TEST STAGE PROD • Undeploy Bindings • Undeploy Assembly • Import Bindings • Deploy Assemblies • Deploy Assembly Custom Tasks ApplicationBindingfiles
Demo Build & Deploy automation
Build Parameters To build a specific version: /P:GetVersion=[C|L]version Where version is the Versionspec by the following syntax: * Changeset - Version that belongs to changeset number, Eg C1234 * Label - Version that belongs to a label, EgLMyLable To perform UnDeploy, use set the Deploy parameter to false: /P:Deploy=false If you only wich to install asseblies to GAC, without deploying to BizTalk, use the GacOnly parameter. /P:GacOnly=true You may use combination of parameters: /P:GetVersion=C1234;Deploy=false (Undeploys a specific version) /P:GetVersion=C1234;GacOnly=true (Installs a specific version to GAC, without deploying to BizTalk)
Considerations • Application References • Multi server environments • No need to recompile after first successful compilation. • Building to a Group • The process is bindings file dependant • Utilizing undocumented BizTalk assemblies