MSMQ30NewFeaturesMSMQ30新特點6、露凝無游氛，天高風景澈。7、翩翩新來燕，雙雙入我廬，先巢故尚在，相將還舊居。8、吁嗟身后名，于我若浮煙。9、陶淵明（約365年—427年），字元亮，（又一說名潛，字淵明）號五柳先生，私謚“靖節”，東晉末期南朝宋初期詩人、文學家、辭賦家、散文家。漢族，東晉潯陽柴桑人（今江西九江）。曾做過幾年小官，后辭官回家，從此隱居，田園生活是陶淵明詩的主要題材，相關作品有《飲酒》、《歸園田居》、《桃花源記》、《五柳先生傳》、《歸去來兮辭》等。10、倚南窗以寄傲，審容膝之易安。MSMQ30NewFeaturesMSMQ30新特點MSMQ30NewFeaturesMSMQ30新特點6、露凝無游氛，天高風景澈。7、翩翩新來燕，雙雙入我廬，先巢故尚在，相將還舊居。8、吁嗟身后名，于我若浮煙。9、陶淵明（約365年—427年），字元亮，（又一說名潛，字淵明）號五柳先生，私謚“靖節”，東晉末期南朝宋初期詩人、文學家、辭賦家、散文家。漢族，東晉潯陽柴桑人（今江西九江）。曾做過幾年小官，后辭官回家，從此隱居，田園生活是陶淵明詩的主要題材，相關作品有《飲酒》、《歸園田居》、《桃花源記》、《五柳先生傳》、《歸去來兮辭》等。10、倚南窗以寄傲，審容膝之易安。NewFeaturesofMessageQueuinginWindows.NETServer2003ShaiKarivProgramManagerMSMQMicrosoftCorporationNewFeaturesofMessageQueuinginWindows.NETServer2003ShaiKarivProgramManagerMSMQMicrosoftCorporationBeforeWeStart…Win06:Tips&Tricks,latertoday!MSMQbackground:MSMQ1.0inWindowsNT4.0MSMQ2.0inWindows2000Platformintegration:AD,Clustering,MMCAdd-onserviceslikeTriggersMSMQ3.0inXPand.NETServer2003Internetmessaging1-to-manymessagingIntegratingTriggers,extendingAdminAPISystem.MessagingAgendaReliable1-NMessagingDistributionListsReliableMulticastReliableInternetMessagingMessagingOverSOAP/HTTPFirewallsandLoadBalancingAdminAPIDeploymentandStorageTriggersDistributionLists

OverviewSoftware“fan-out”Pub/SubprimitivesEnd-to-endsemanticsforDeliveryguaranteesSecurityTransactionsImplementation:1-1“internally”DistributionLists

PublicDLsRegisteredinActiveDirectoryLeverageADGroupobjectProgrammableviaADSIcallsManageableviaADMMCsnap-insNewformatname:DL=<GUID>ElementscanbeotherDLsDimdestasNewMSMQDestinationdest.FormatName=“DL=<GUID>”Message.SenddestDistributionLists

PrivateDLsClient-managed“DL”:ListofformatnamesIncludingnewformatnames:DL,HTTPNon-discoverableDimdestasNewMSMQDestinationdest.FormatName=“DIRECT=OS:host1\q”,”PRIVATE=…”Message.SenddestDistributionLists

TransactionsIdenticaltoqueuetransactionsMultipletransactionstosameDL:In-OrderdeliveryIfsentfromthesamecomputerNoin-orderguaranteeformessagessenttodifferentDLsEvenifDLscontainthesamequeuesDistributionListsAgendaReliable1-NMessagingDistributionListsReliableMulticastReliableInternetMessagingMessagingOverSOAP/HTTPFirewallsandLoadBalancingAdminAPIDeploymentandStorageTriggersReliableMulticast

OverviewHardware“fan-out”:EfficientsendtomultiplerecipientsExposeandleverageIPmulticastMSMQprovidesoffline,persistencyProvidebuildingblocksforPub/SubScenario:real-timemarketdatapush(financialsector)Protocol:PragmaticGeneralMulticastReliableMulticast

PGM:PragmaticGeneralMulticastJointMicrosoft/CiscoeffortPublicspecificationCiscoroutersprovideoptimizationReliablemulticasttransportReceivereithergetsalltransmissionandrepairdataOrabletodetectunrecoverabledatalossMembersmayjoin/leaveatanytimePGMDataFlow

PGMhostsendsamulticastpacketSenderReceiverSR=MulticastODATARRRRPGMDataFlow

Arecipientsends(unicast)NAKUnicastNAKSenderReceiverSRRRRRPGMDataFlow

RoutermulticastsNCFinLANSenderReceiverSR=MulticastODATARRRRPGMDataFlow

RouterunicastsNAKbacktosenderSenderReceiverSRRRRRPGMDataFlow

SendermulticastsrepairdataSenderReceiverSR=MulticastODATARRRRReliableMulticast

ConfigurationandSecurityReceiverconfiguration:Newqueueproperty:MulticastAddressAqueuecanjoinonemulticastgroupSenderconfiguration:MaxsendrateMaxtimetherepairdataisavailableSecurity:ExistingauthN/authZ(perqueue)EncryptiononlyatapplicationlevelReliableMulticast

ProgrammingmodelReceiverside:Newqueueproperty:MulticastAddresscanbesetprogrammatically…WhencreatingthequeueorlateronSenderside:Newformatname:MULTICAST=<IP>Noadditionalend-to-endsemanticsDimdestasNewMSMQDestinationdest.FormatName=“MULTICAST=<address:port>”Message.SenddestReliableMulticastAgendaReliable1-NMessagingDistributionListsReliableMulticastReliableInternetMessagingMessagingOverSOAP/HTTPFirewallsandLoadBalancingAdminAPIDeploymentandStorageTriggersReliableWebMessaging

GoalsSameprogrammingmodelUseHTTPastransportSOAP-basedprotocolSecuremessagingacrossfirewallsSupportNetworkLoadBalancingReliableWebMessaging

ProgrammingmodelOpenqueue,sendmessageQueuecanbeHTTP-addressedNewformatname:

DIRECT=HTTPS://host/MSMQ/qOpenqueue,receivemessageNewmessagepropertiesleverageSOAPsupportSoapHeader,SoapBodySoapEnvelope,CompoundMessageReliableWebMessaging

SOAPReliableMessagingProtocolSRMP:Specificationforgeneral-purposereliablemessagingPublishedspecificationExtensionofWS-RoutingImplementedbyMSMQ3.0SOAPheaderisusedtoprovideend-to-endinformationneededforreliablemessagingSRMPMessageElementsWS-Routing:pathPropertiesServicesStreamReceipts:DeliveryCommitmentStreamSOAPBodySecuritySOAPHeaderSOAPBodySRMPPath,Propeties<SOAP-ENV:Headerxmlns=/srmp

xmlns:rp="/rp/“><rp:pathSOAPENV:mustUnderstand=“1”><rp:action>MSMQ:Message</rp:action><rp:to>server/something</rp:to><rp:id>uuid:2288926ac3fd49c-e7d5-4354-ba8d-3e13fc6f677c</rp:id><rp:relatesTo>uuid:2288926ac3fd49d-e7d5-4354-ba8d-3e13fc6f677c</rp:relatesTo></rp:path><propertiesSOAP-ENV:mustUnderstand="1“><expiresAt>20380119T031407</expiresAt><sentAt>20010509T130502</sentAt></properties></SOAP-ENV:Header>SRMPServices<servicesSOAP-ENV:mustUnderstand="1"><durable/><deliveryReceiptRequest><sendTo>/receipts</sendTo></deliveryReceiptRequest><commitmentReceiptRequest><sendTo>/deliverydone</sendTo><negativeOnly/></commitmentReceiptRequest></services>SRMPStreams<streamSOAP-ENV:mustUnderstand="1"><streamId>uuid:84b9f5d0-33fb-4a81-b02b-5b760641c1d6</streamId><current>1</current><start><sendReceiptsTo>sender/streamAcks/</sendReceiptsTo></start></stream>

<streamSOAP-ENV:mustUnderstand="1"><streamId>uuid:84b9f5d0-33fb-4a81-b02b-5b760641c1d6</streamId><current>7</current><previous>5</previous></stream>SRMPExtensibility

MSMQsupportforextensibilityMSMQcreatestheSRMPelementsWhendestinationformatnameisURLReceive-sideapplicationscanaccessthemessageasXMLdocumentSoapEnvelope,CompoundMessageSend-sideapplicationscanextendtheSOAPmessageSoapHeader,SoapBodyInternetMessaging/SRMPReliableWebMessaging

RedirectingSRMPmessagesHTTPrequestscanberedirectedSRMPmustsupportredirectionRedirectingSRMPmessagesrequiresstoreandforwardMSMQ3.0supportsstore,redirectandforwardUsingXMLfilesfor“mapping”MessagecontentdoesnotchangeReliableWebMessaging

Mappingfile<from>External(known)nameofthedestination<to>Localresolutionforthedestination<redirections><redirection><from>https://z/msmq/orders</from><to>https://server1/msmq/q1</to></redirection></redirections>ReliableWebMessaging

RoutingSRMPmessagesEnterprise:MSMQusesActiveDirectoryfordynamicroutingMSMQdoesnotuseActiveDirectorytoresolveDIRECTformatnameRedirectmappingallowsconnectionlessSRMPmessagingUsefulforworkgroupmodeaswellReceiverSenderMSMQhostMappingtableInternetMessaging/MappingAgendaReliable1-NMessagingDistributionListsReliableMulticastReliableInternetMessagingMessagingOverSOAP/HTTPFirewallsandLoadBalancingAdminAPIDeploymentandStorageTriggersSecureWebMessaging

RequirementsDonotallowdirectTCPsessionsfromInternettoIntranetDonotexposenamesofinternalresources:computers,queuesDonotstoresensitivedataoncomputersintheDMZDonotforwardunauthenticatedmessagesfromDMZtoIntranetSecureWebMessaging

TopologyInternetDMZFirewallFirewallHTTPProxyMSMQServerhttps://my_company/ordersAuthenticateMapStoreForwardhttps://ic/msmq/InQueuehttps://your_company/acksIntranet<sendReceiptsTo>my_company/receipts</sendReceiptsTo>MSMQClientReliableWebMessaging

NLBOverviewNetworkloadbalancingsolutions:Hardware(e.g.CiscoLocalDirector)DNSround-robinWindowsNetworkLoadBalancingNLBassumesstate-lessservicesSeamlessforlowQoSmessagingappsSpecialsolutionrequiredforhighQoSmessagingappsReliableWebMessaging

NLB:LowQoSmessagingNLBNode1My_MSMQ_AppNode2My_MSMQ_AppNode3My_MSMQ_AppNLBClusterDIRECT=HTTP://NLB_URL/MSMQ/q1orDIRECT=TCP:<NLB_IP>\q1(worksalsoonWindows2000)ReliableWebMessaging

NLB:HighQoSmessagingNLBNLBClusterMSMQClient1App_inqueueMSMQClient2App_ordersNode1Q1->client1\q1Q2->client2\q9Node2Q1->client1\q1Q2->client2\q9Node3Q1->client1\q1Q2->client2\q9AgendaReliable1-NMessagingDistributionListsReliableMulticastReliableInternetMessagingMessagingOverSOAP/HTTPFirewallsandLoadBalancingAdminAPIDeploymentandStorageTriggersAdminAPI

OverviewProgrammablecontrolofMSMQobjects:MSMQserviceApplicationqueuesInternaltransmissionqueuesLocalandremoteCOMobjectmodelAdd-onavailableforMSMQ2.0AdminAPI

ExtensiontoexistingobjectsMSMQApplicationextensionsincludes:ActiveQueuesPrivateQueuesDirectoryServiceServerIsConnectedUsedQuotaConnectDisconnectMachine(canmanageremotehosts)MSMQQueueextension:PurgeAdminAPI

NewobjectsMSMQManagement:baseclassforoutgoingandtargetqueuesMachineFormatNameMessageCountQueueType(private,public,…)MSMQOutgoingQueueManagementNextHops(routinginfo)EodGetSendInfo(transactioninfo)EodResend(transactionalprotocol)PauseResumeMSMQQueueManagementUsedQuotaEodGetReceiveInfo(transactioninfo)AdminAPI

CodeexamplePauseanoutgoingqueueon“RemoteMachine”,inspectitscontentandresumeit.DimqmgmtasNewMSMQManagementqmgmt.InitMachine:=“RemoteMachine”,PathName:=“TargetMachine\q”DimoutqmgmtasMSMQOutgoingQueueManagementSetoutqmgmt=qmgmtoutqmgmt.PauseMsgBox“messagesinq:”&outqmgmt.MessageCountoutqmgmt.ResumeAgendaReliable1-NMessagingDistributionListsReliableMulticastReliableInternetMessagingMessagingOverSOAP/HTTPFirewallsandLoadBalancingAdminAPIDeploymentandStorageTriggersStorage&Deployment

EnterprisedeploymentSimplifyMSMQrequirementsinActiveDirectoryenvironment:NoMSMQserversondomaincontrollersMSMQclientsaccessActiveDirectorydirectlyviaLDAPOldrequirementsstillapplyforNT4.0andWindows2000clientsStorage&Deployment

NodeploymentonDCSenderRecipientMSMQAnyDomainControllerExistence&AuthenticationOpenqueueonrecipientforsendStorage&Deployment

UnlimitedstorageProblem:MSMQ1.0/2.0messagestore:2GBlimitationWin64doesn’tsolveGoal:liftthe2GBlimitImplementation:ExtendthecurrentMSMQpropr