jump to navigation

Microsoft Active Directory August 12, 2005

Posted by Coolguy in Microsoft Technologies.
add a comment

MSMQ August 12, 2005

Posted by Coolguy in Microsoft Technologies.
add a comment
  • MSMQ is a component of MOM (Message Oriented Middleware) in the Microsoft world.
  • It implements asynchronous communications by enabling applications to send messages to, and receive messages from, message queues.
  • Although MSMQ middleware is sold separately with MS Backoffice software suite the MSMQ client comes with every version of Microsoft Windows.
  • The current version of MSMQ is 3.0.
  • Message Queuing-T (MSMQT), also called Biztalk Server 2004 Message Queuing, is a Biztalk Server 2004 feature that enables high-performance interoperability between Message Queuing applications and Biztalk Server 2004.
  • MSMQT listens on the standard MSMQ port for messages and ensures they are delivered straight to the BizTalk Server MessageBox via a configured pipeline. It provides a subset of Message Queuing 2.0 features

Features of MSMQ

  • Provides guaranteed message delivery, efficient routing, security, and priority-based messaging.
  • Provides loosely coupled and reliable network communications services based on a messaging queuing model.
  • It can be used to implement solutions to both asynchronous and synchronous scenarios requiring high performance.
  • Applications can use MSMQ to send and process messages regardless of whether the receiving application is running or reachable over the network.

MSMQ at work

  • The process begins when a client sends messages to a queue

  • The .Net service is responsible for pushing its outgoing messages to remote destinations.
  • After the connection with the remote machine is established the message transfer takes place.
  • If required, the receiving application can send a response message back to the original requester
  • While in transit between senders and receivers, MSMQ keeps messages in holding areas, or queues.
  • These queues protect messages from being lost in transit and provide a place for receivers to look for messages when the receivers are ready to receive them.
  • Transaction services can be used with MSMQ to ensure that the transaction completes properly.


  • JMS is a specification while MSMQ is an implementation of messaging
  • MSMQ implements a “point-to-point” style messaging to the clients while JMS API specifies a “point-to-point” and “publish-subscribe” models of messaging.
  • Both can handle synchronous or asynchronous messaging.
  • Clustering and load balancing can be used in JMS when delivering messages. MSMQ messages cannot be load balanced
  • There are various 3rd party implementations of JMS from vendors like SpiritSoft and Fiorano, which provide a Bridge to communicate with MSMQ from within a Java application


  • IBM MQSeries – This has an implementation of messaging which provides a communication mechanism between applications on different platforms. There are MQSeries bridges available to communicate with JMS as well as MSMQ
  • SoniqMQ from Progress Software– A messaging solution in Java, which JMS compliant and J2EE 1.4 compatible
  • JORAM – An open source messaging solution, which is an implementation of JMS
  • Jboss Messaging – A JMS compliant messaging solution
  • Java implementations of messaging provided by WebLogic as well as Webphere








Microsoft Operations Manager 2005 August 12, 2005

Posted by Coolguy in Microsoft Technologies.
add a comment
  • MOM 2005 is an event and performance management tool for Windows Server System
  • MOM 2005 improves the manageability of your infrastructure by providing:
    Comprehensive event management
    Proactive monitoring and alerting
    Reporting and trend analysis
    System and application-specific knowledge from the experts
  • MOM’s core functionality falls into four broad areas:
    First, it collects and filters event data from managed servers. That data is filtered so you only see what is important to your servers’ health.
    Second, MOM supports processor health rules that give you alerts when specific events or performance conditions occur. There’s also an extensive knowledge base that explains the impact of certain events on performance conditions and offers advice on how to fix them.
    Third, MOM supports a robust scripting architecture, so once it alerts you to potentially damaging situations it can also take automated corrective actions like restarting a server or changing a configuration value. Finally, MOM provides full reporting to give you an enterprise-wide view of your IT infrastructure’s health and operations

MOM Management Packs

  • MOM management packs provide built-in, product-specific operations knowledge for a wide variety of your server applications
  • Management packs contain rules for monitoring a comprehensive array of server health indicators and creating alerts, often preemptively, when problems are detected or reasonable thresholds are exceeded that require administrator intervention.
  • This powerful monitoring capability is augmented by in-depth knowledge base content, prescriptive guidance, and actionable tasks that can be associated directly with the relevant alerts included in the management packs
  • Administrators can then act to prevent or correct situations, such as degraded performance or service interruption, maintaining service availability with greater ease and reliability
  • To provide the best possible management for applications, Microsoft encourages application providers, who have the sophisticated knowledge associated with their own applications, to supply management packs for their applications
  • That way, they can embed the necessary operational intelligence to aid the administrator or operator.
  • Management packs for Microsoft applications are developed directly by the individual product teams in conjunction with Microsoft Consulting Services and Microsoft Product Support Services, combining the best of development, deployment, and troubleshooting knowledge.
  • In addition, there are a wide range of non-Microsoft application and hardware management packs that enable MOM to manage far more than the Microsoft components of your IT infrastructure

Architecture and work flow

Edition – Pricing

  • The estimated retail price of a MOM 2005 server license is $729 per server. A MOM server license need to be obtained for each MOM server implemented in the MOM environment. (MOM server is not available individually in retail, and is sold with a minimum of 10 OML pack. MOM server plus 10 OML estimated retail price is $6,099).OML stands for Operations Management License
  • MOM 2005 Workgroup Edition manages only up to 10 devices due to a built-in technical limitation. Importantly, this restriction includes virtual as well as physical machines
  • Customers have to re-purchase their MOM 2005 licenses for all monitored devices at the time they decide to add the 11th managed device.


  • Nagios
  • mon
  • Angel
  • spong
  • HP OpenView
  • CA Unicenter TNG
  • Novell’s ManageWise / ZenWorks
  • Big Brother
  • MRTG
  • Zabbix [zabbix.com]
  • argus



BizTalk Server 2004 August 12, 2005

Posted by Coolguy in Microsoft Technologies.
add a comment
  • Tool to integrate systems.
  • It supports the goal of creating business processes that unite separate applications into a coherent whole
  • A business process is a set of actions that together meet some useful business need.
  • It connects diverse applications, and then to graphically create and modify business processes that use the services that those applications provide
  • BizTalk Server 2004 is built completely around the .NET Framework and Microsoft Visual Studio® .NET.

Usage scenarios

  • BizTalk Server is used for application integration in the following scenarios:
  • Connecting applications within a single organization commonly referred to as enterprise application integration (EAI). (70 percent of BizTalk deployments are for EAI)
  • Connecting applications in different organizations, often called business-to-business (B2B) integration

BizTalk Server engine

  • Engine works only with XML documents internally
  • Whatever format a message arrives in, it is always converted to an XML document after it is received.
  • Similarly, if the recipient of a document cannot accept that document as XML, the engine converts it into the format expected by the target application.


  • A message is received through a receive adapter.
  • An adapter is an implementation of a communication mechanism, such as a particular protocol.
  • BizTalk Server 2004 provides built-in adapters, and adapters have been created for popular applications such as SAP.
  • A developer can determine which adapters to use in a given situation, or can create custom adapters for specific needs.
  • E.g’s of Adapters:
    SOAP adapter.
    BizTalk Message Queuing adapter.
    File adapter
    HTTP adapter
    SMTP adapter
    SQL adapter.
    Base EDI adapter.
    FTP adapter


  • Processing of the message can involve multiple steps, and it is performed by a message pipeline.
  • Incoming messages are processed through a receive pipeline, while outgoing messages go through a send pipeline
  • A developer can also create custom pipelines by using the Pipeline Designer tool.


  • After a message has passed through an adapter and a receive pipeline, the business process must determine where it should go.
  • A message is most often targeted to an orchestration, but it is also possible for a message to go directly to a send pipeline, using the BizTalk Server 2004 engine purely as a messaging system
  • In either case, messages are matched with their destinations through subscriptions
  • For example, an orchestration might create a subscription that matches all messages of the type “Invoice”, or all messages of the type “Invoice” received from Woodgrove Bank, or all messages of the type “Invoice” received from Woodgrove Bank that are for more than $10,000.


  • Enables you to create a business process graphically.
  • Tools available are:
    BizTalk Editor: Creating Schemas using XSD
    BizTalk Mapper: Mapping Between Schemas using XSLT transformations Orchestration Designer: Its used to defining business processes.
  • Some of the tasks available include Receive,Send,Port, Decide. Loop. Construct Message. Transform. Parallel Actions. Scope. Message Assignment
  • Ultimately, the group of shapes that you define in BizTalk Server 2004 becomes just a standard .NET assembly

Business Rule Engine

  • Enables more business-oriented users to directly create and modify sets of business rules.
  • These rules are created by using a tool called the Business Rule Composer, and then executed directly by the engine. This technology is new in BizTalk Server 2004.
  • The change takes effect immediately. And while orchestrations are typically created and maintained by developers, business rules are readable enough to be modified by business analysts without the need to involve more technical people
  • Additional features in Biztalk server 2004 include:
    Enterprise Single Sign-On Business Activity Monitoring


  • Are used to support specific industries and scenarios
    HL7: Messaging solution for patient information within and between healthcare systems HIPAA : Health Insurance Portability and Accountability Act
    SWIFT: Financial institutions

User Roles

  • Three roles are necessary to create and maintain BizTalk Server 2004 applications.
    · Business analyst.
    · Developer.
    · Administrator.

Editions and Licensing

  • Enterprise Edition: Unlimited CPU’s, unlimited number of internal applications and external trading partners
  • Standard Edition: Single CPU and integration with up to 10 applications and 20 trading partners, no fail over and scalability
  • Partner Edition: Integration with up to three applications and three trading partners.
  • Developer Edition: Designing, developing, and testing purposes
  • BizTalk Server 2004 requires Microsoft SQL Server and Microsoft Windows Server 2003 to install.
  • BizTalk Server require one production license for each processor


  • webMethods
  • BEA
  • OpenEAI
  • Tibco
  • SeeBeyond
  • Vitria




Citrix MetaFrame Presentation Server August 11, 2005

Posted by Coolguy in Microsoft Technologies.
add a comment
  • Citrix MetaFrame Presentation Server is a technology that can allow remote users to connect to applications that are actually installed on a remote computer.
  • This is useful for users who are unable to run various Windows programs on their PCs, or people who use many PCs and need to use a common instance of a program across all their computers.
  • Programs are run on thin client server and the user interface is displayed on the user’s machine. This system is called ‘Thin Client’ because the client PC does not need to have the resources needed to run the full program, only the user interface, so can be a lower specification (thin) PC.
  • These Presentation Servers let users connect any client device to any application running on the presentation server (terminal server).
  • Citrix clients are available for Windows, Mac, various flavors of UNIX, and even EPOC handheld devices.
  • There is a UNIX version of Presentation Server so you can run UNIX and Java applications on a terminal server while accessing them from Windows clients.


  • Citrix Presentation Server uses ICA (Independent Computing Architecture) protocol, for transmitting keystrokes, mouse movements, and screen updates between thin clients and the presentation server
  • Users can use various connections including dial-up and ISDN connections to access the applications. Figure shows the various connection types ICA can support
  • Citrix ICA has the ability to separate application logic from the user interface. On the client, users see and work with the application’s interface, but 100 percent of the application executes on the server.
  • ICA is the Citrix counterpart of Microsoft’s Remote Desktop Protocol (RDP). Table compares both of these protocols

    Client Support



    Windows 95/98/NT/2000/XP



    Windows for Workgroups 3.11



    Windows 3.1




    Windows CE











    Web browser



Editions and Licensing

  • Citrix Presentation Server is the world’s most widely deployed presentation server for centrally deploying and managing applications,
  • Latest version of Citrix Presentation Server is 4.0.Its due to be released in the second quarter of 2005 and will be available in three editions, Enterprise, Advanced and Standard.
  • Citrix Presentation Server, Citrix Access Gateway and Citrix Password Manager are bundled together as Citrix Access Suite
  • Suggested retail prices of MetaFrame Presentation Server 3.0 are:
    Enterprise $400 per user
    Advanced $345 per user
    Standard $290 per user


  • Other server based computing products in market are:
  • Tarantella’s Secure Global Desktop
    Terminal Services in Windows Server 2003
    Thinpath from NCD
  • Bear Paw is the next release of Terminal Server (the set of technologies currently known as “Terminal Services”). Microsoft is enhancing this component, making it almost a standalone app in its own right.
  • Citrix clients do not actively use their own resources to access such infrastructures, rather, just to view the remote session over an optimised protocol.
  • As such, the Citrix Metaframe servers perform the basic I/O, memory management and redirection services on behalf of a number of client sessions. In order to achieve this, the Citrix servers illustrate a linear increase of memory resources according to the number of clients connecting to sessions


BizTalk performance stats February 23, 2005

Posted by Coolguy in Microsoft Technologies.
add a comment