Deck for introduction IT Admins to NSB and what they need to know to support the product

1. NServiceBus for Admins

2. Integration Framework Patterns 2

3. Broker App App Broker App App App

4. Bus App App Bus Bus App App Bus Bus

5. Messaging Patterns

6. Publish & Subscribe Subscriptions Publisher Subscriber Bus Subscriber Subscriber Bus Bus

7. Bus Request & Response Client Response Bus Request Bus

8. Distributor Work Management Distributor Worker Bus Worker Worker Bus Bus

9. Saga(Workflow) State Persistence Main Business Process Sub Process 3 Bus Sub Process 1 Sub Process 2 Bus Bus

10. Gateway Site 2 Site 1 Server Client HTTP Gateway Gateway

11. Messaging/Integration Framework Selection Criteria Features Publish/Subscribe Work Distribution Long Running Business Workflows Lives on existing infrastructure Low Learning Curve Actively supported Cost Effective

12. Selected Framework NServiceBus Open Source Feature Rich Built on MSMQ, MSDTC, and .NET

13. NServiceBus Architecture

14. Required Software MSMQ MSDTC NSB Bits .NET Framework 3.5 SP1 RDBMS Subscription Storage Very small, SQL Server will do

15. Monitoring PerfMon Counters NSB “Critical Time” – how long has the oldest message been sitting in the queue Logs SCOM MSMQ Error Queue

16. Logging Configurable & managed by the developer Includes standard mechanisms Files Event Log Database Custom…

17. Installation NServiceBus.Host.exe [/install (installs as a Windows Service) [/serviceName] (name in the registry) [/displayName] (display name in Mgr) [/description] (description in Mgr) [/instance] (another named instance) [/startManually] (don’t start the service) [/username] (account it runs as) [/password] (password of above user) [ProfileName] (name of the profile to use)

18. Profiles Modifies host behavior on startup Logging Subscription Storage Can Create Custom Profiles OOTB Profiles Lite: Console app, verbose logging, memory subscription storage Integration: Console app, informational logging, MSMQ subscription storage Production: Windows Service, error logging, database subscription storage

19. Uninstallation NServiceBus.Host.exe [/uninstall [/serviceName] [/instance]]

20. Application Level MSMQ Configuration <MsmqTransportConfig InputQueue="client“ Queue messages are being received on ErrorQueue="error“ Queue error messages are sent to NumberOfWorkerThreads="1“ Number of threads used to process messages MaxRetries="5“ Max number of times to try and process a message />

21. Subscription Storage Configuration <MsmqSubscriptionStorageConfig Queue="subscriptions" /> Queue to look for subscriptions <DBSubscriptionStorageConfig> <NHibernateProperties> <add Key="connection.provider" Value="NHibernate.Connection.DriverConnectionProvider"/> <add Key="connection.driver_class" Value="NHibernate.Driver.SqlClientDriver"/> <add Key="connection.connection_string" Value="Server=.;Database=nservicebussubscriptions;Trusted_Connection=True;"/> <add Key="dialect" Value="NHibernate.Dialect.MsSql2005Dialect"/> </NHibernateProperties> </DBSubscriptionStorageConfig>

22. Tools ReturnToSourceQueue.exe Replays messages to the queue they came from Runner.exe Validates and fixes MSMQ installations Starts MSDTC if necessary Installs NSB performance counters

23. Running in a Cluster You need to add the .NET Framework feature or application server role to the member servers You need to add both a MSDTC and a MSMQ resource to the cluster (MSMQ will require that you have MSDTC) After adding the Generic Application for NServiceBus.Host.exe, you will need to go in and modify the properties of the generic application to check the "Use Network Name for computer name" box so that NServiceBus points to the cluster name for using MSMQ not to the member server that is currently running it.

24. Questions?

25. Pub/Sub Mechanics Publisher Subscriptions Outbound Inbound ReturnToSourceQueue.exe Subscriber1 Subscriber2 Errors Inbound Outbound Outbound Inbound Inbound