Single Sign-On

A gud link to know about Single sign-on

http://www.opengroup.org/security/sso/sso_intro.htm

InRule - Rule Engine

InRule is built entirely on the .NET platform, leveraging a component architecture that delivers unparalleled rule processing performance and flexibility. From the feature rich rule authoring environment to the optimized execution of the business rule engine, InRule unifies the domains of managed business logic and traditional systems processes.














Description:

InRule's new visual rule flow and modeling provides a graphical view of rule application elements and how they are related. Visual rule flow gives InRule users greater ability to understand where a rule application starts and ends and gives them a method for visually following the way one or more rulesets execute. Users can view and define rules through the point and click interface. Pan and zoom functionality makes it easy to navigate within large or complex applications.

Features :

• InRule's catalog services provide the ability to store, version, check-in/check-out, and set permissions on rules.


• Administrators can now view all the objects stored across multiple catalog instances and can "promote" a rule application from one catalog to another.


• InRule can be used as a Web-based Rule Management with AJAX Functionality
  Business Language Authoring and decision table controls are implemented as a set of embeddable web controls, providing greater flexibility in determining where rules can be maintained and edited


• Testing rule logic has been made even easier with irVerity, InRule's integrated testing component. Rule execution is simpler to follow with an improved layout and Watch Lists.


• Users can now define rules that are applied depending on the context in which a field is used.


• InRule's support for handling collections has been enhanced with new functions for effectively iterating over a series of items in a collection


• InRule allows users to specify rule sets to activate or deactivate based on category or metadata.


• User can choose to activate only online rules and deactivate batch rules depending on their needs


• A new Halt Ruleset function gives rule authors the capability of halting the execution of a rule with or without invoking a runtime error

Xml Web Services in Sql Server 2005

Database products are making it easier and easier to hook up Internet protocols directly to your data. Microsoft SQL Server is a case in point. While Microsoft SQL Server 2000 did allow Web data access, the process required to use the SQLXML library and a full installation of Internet Information Services. With SQL Server 2005, Microsoft has solved this issue.Now, you can have direct access to your SQL Server data from any HTTP SOAP client without any extra middleware at all - not even IIS.

Description:

Microsoft continues to bet heavily on Web Services as a backbone for service-oriented architectures, so it makes sense that they've chosen to expose SQL Server 2005 data via a Web Service. Or, to be more precise, you can create as many Native XML Web Services as you like in SQL Server 2005.

To do so, you use the new CREATE ENDPOINT statement to create HTTP endpoints. Each HTTP endpoint ties the results of a SQL Server stored procedure directly to a Web Service, providing support through the Web Services Description Language (WSDL) and Simple Object Access Protocol (SOAP) protocols for retrieving the data supplied by the stored procedure. SQL Server interfaces directly with the Windows HTTP listener process (http.sys) so that SOAP requests are routed directly to SQL Server, with no intervening middleware necessary. Similarly, SOAP responses are sent directly back to the requesting client.

Steps:
1)Create a simple Stored Procedure

CREATE PROC dbo.SalesStoreProc AS
SELECT ProductID, ProductName FROM Sales.Product

2)Creating an HTTP Endpoint

The next step is to create the HTTP endpoint. Running this SQL statement is what makes the data from the stored procedure available to SOAP clients:

CREATE ENDPOINT GetStores STATE = STARTED
AS HTTP( PATH = '/Store', AUTHENTICATION = (INTEGRATED),
PORTS = (CLEAR),
SITE = 'localhost')
FOR SOAP
( WEBMETHOD 'StoreList'
(NAME='AdventureWorks.dbo.SalesStoreProc'),
BATCHES = DISABLED,
WSDL = DEFAULT,
DATABASE = 'AdventureWorks',
NAMESPACE = 'http://AdventureWorks/Store')
GO

Key things to be noted:

• The STATE clause specifies the initial state of the endpoint. It can be started, stopped (listening but returning errors to clients) or disabled (not even listening for requests)
• The AS HTTP clause specifies the transport protocol to use. You can also specify AS TCP here.
• The PATH clause specifies the URL on the server that clients will use to reach this Web service.
• The AUTHENTICATION clause specifies how clients will authenticate themselves to the SQL Server: BASIC, DIGEST, NTLM, KERBEROS, or INTEGRATED.
• The PORTS clause specifies whether the service will listen on the CLEAR or SSL ports, or both (other clauses, not shown here, let you specify non-standard port numbers)
• The SITE clause lets you specify a hostname for the computer that will respond to requests.
• The FOR SOAP clause states that this endpoint will respond to SOAP messages. Other endpoints handle messages for Service Broker or database mirroring.
• The WEBMETHOD clause defines a Web method, mapping a method name to the name of a stored procedure
• The BATCHES clause specifies that this endpoint won't process arbitrary SQL statements.
• The WSDL clause specifies that it will provide WSDL support.
• The DATABASE clause specifies the database that contains the data.
• The NAMESPACE clause specifies the XML namespace for the messages.

Testing the Webservice:

The URL for the WSDL file (http://localhost/Store?wsdl) is determined by the CREATE ENDPOINT statement. The Web server is the server where SQLServer 2005 is installed. The PATH clause dictates the Store portion of the URL. The remainder of the URL is where SQL Server listens, by convention, for WSDL requests associated with this particular Web Service.
Thus SQL Server will accept, and respond to, standard HTTP SOAP 1.2 requests. This gives you a supremely easy way to hook SQL Server 2005 data into any sort of service-oriented architecture that you can dream up.

Microsoft Windows Small Business Server 2003

Microsoft Windows Small Business Server 2003 is the easy way for small business customers to get the power of the Windows Server operating system plus Microsoft server-based solutions for e-mail, fax, database, and security-enhanced, shared Internet access, and file/print/calendar/application sharing-all in one integrated, simplified solution at an affordable price.Windows Small Business Server 2003 helps your small business customers work smarter with fewer resources.




















Microsoft Windows Small Business Server 2003 will have the following installed
 Microsoft Windows Server 2003
 Microsoft Windows SharePoint Services V2.0
 Microsoft Exchange Server 2003
 Outlook 2003
 Microsoft Shared Fax Service
 Microsoft ISA Server 2000
 Microsoft SQL Server 2000
 Microsoft Office FrontPage 2003
 ROUTING AND REMOTE ACCESS SERVICE(RRAS)
 Mobile User/Device Support
 Shared Network Resources
 Backup and Restore
 Task Based Management

System Requirements:

• 300-megahertz (MHz) Processor
• 256 megabytes (MB) of RAM
• 4 gigabytes* (GB) of available hard disk space

Features :

• Protect key business information with an infrastructure that includes built-in firewall protection and security-enhanced remote access to help prevent unauthorized users from getting into your network.
• Keep your PCs and servers current with the latest software updates to enhance the security of your network.
• Prevent data loss by automatically backing up company information and enabling employees to retrieve accidentally deleted files and restore earlier versions of files
• Store, find and share information in one centralized location
• Provide employees with an internal Web site so they can find and share files and collaborate on group projects
• Work from virtually anywhere with remote access to business information and resources – e-mail, calendars, network files, internal Web sites and business applications
• Share resources and equipment such as Internet access, printers and fax machines
• Stay connected to your customers from virtually anywhere and anytime with remote access to business information and resources
• Manage your customer relationships more effectively with a centralized place to store and exchange information
• Use Windows Mobile-based devices to access e-mail, contacts, and calendars from virtually anywhere and at anytime
• Reduce costs and maximize limited resources

Merging Pdf

There is a gud site about Dynamic pdfs and merging 2 pdfs.

http://www.cete.com/Products/MergerForNET/

Microsoft Identity Integration Server 2003

Microsoft Identity Integration Server 2003 (MIIS 2003) provides services that make it possible to manage identity-related data from multiple, unrelated data sources. The goal of MIIS 2003 is to provide organizations with a unified view of all known identity information about users, applications, and network resources. MIIS 2003 enables you to synchronize identity information across a wide variety of identity stores, easily provision and de-provision accounts across systems, and enables self-service and helpdesk-initiated password management and reset from a Web browser. This improves productivity, reduces security risk, and reduces the total cost of ownership associated with managing and integrating identity information across the enterprise.

Microsoft® Identity Integration Server 2003 is a service that stores and coordinates identity information from multiple sources (for example, directories, databases, or formatted dump files) in an organization. With Microsoft Identity Integration Server 2003, you can combine that information into a single logical view that represents all of the identity information for a given user or resource.

An important element of MIIS 2003 is a namespace called a metadirectory. A metadirectory can integrate and synchronize information that is stored in multiple data sources including directories.

MIIS 2003 uses the metadirectory to process identity information from different data repositories such as the Microsoft® Active Directory™ directory service, a Microsoft SQL Server database, IBM® Lotus® Notes, Novell® eDirectory™, or a fixed-width text file. Every data store that provides well-known data access methods is a potential data source candidate for MIIS 2003. The different kinds of identity data systems used by MIIS 2003 are called connected data sources.

The MIIS 2003 metadirectory uses two namespaces to perform its tasks. Namespaces in this case are database-like structures containing uniquely named objects that store information during the synchronization process. The two namespaces are the connector space and the metaverse (MV), as shown in Figure 1.

The connector space is a storage area where object additions, deletions, and modifications are written before they are synchronized with the metaverse or the connected data source. A portion of the connector space is dedicated to each management agent. It is important to note that the connector space does not contain the connected data source object itself, but a shadow copy of the object that contains a subset of the object's attributes, as defined in the management agent. Not every object in a connected data source is designated for synchronization; for example, inactive employees might not be designated. For objects that are designated, some attributes might not be included because some objects contain numerous attributes that are not used at all or that might not make sense in the data sources with which the data is being synchronized.

The connection with the connected data source is not maintained continuously but only connected during communication sessions to update the connected data source or the connector space.

Management agents control the data flow between a connected data source and the metaverse. There is a management agent for each supported connected data source. The metaverse is another core component of MIIS 2003. It is a storage area that contains the aggregated identity information from multiple connected data sources. It provides a single, global, integrated view of all combined objects. These metaverse objects are based on the identity information that is retrieved from the connected data sources and a set of synchronization rules that specify how MIIS 2003 creates the metaverse objects. Metaverse objects are used to capture the aggregated data during synchronization so that data can flow to the other data source in the synchronization design.

MIIS 2003 uses a connector space and the metaverse to create an aggregated view of the identity data that is stored in multiple repositories. You can use this aggregated view to synchronize identity information across applications and platforms.
For more information about the metadirectory and concepts associated with MIIS 2003, see “Essential Concepts of Microsoft Identity Integration Server 2003” in the Technical Reference collection of the MIIS 2003 Technical Library.

Microsoft Office InfoPath 2007

InfoPath is based on Extensible Markup Language (XML). When you design a form template, InfoPath creates an .xsn file, which is a cabinet (.cab) file that contains the files necessary for the form to function, such as XML Schema Definition(XSD) and XSL Transformation (XSLT) files. When a user fills out a form in InfoPath, the data in that form is saved or submitted as industry-standard XML. However, you don't have to know anything about XML to design a form template or fill out a form. The point is that XML can make it easier for your organization to repurpose the data that it collects by using forms. For example, a single InfoPath form template for trip reports can be used to provide XML data to a customer relationship management system, a petty cash system, and a travel planning system.

Description:
InfoPath can be used to collect business data from the people whom you work with, including your colleagues, partners, suppliers, and customers. For example, you can use InfoPath to create a form template for expense reports for the people in your organization.
InfoPath form templates can be straightforward, simple form templates that are used by several people in a small workgroup. For example, a 10-person sales team can use an InfoPath form to informally collect and share information about sales calls. The data in those forms can be merged into a single summary report that is sent to management each month.
Alternatively, organizations can design highly sophisticated form templates that are connected to existing corporate databases or integrated into existing business systems. For example, the developers in your information technology department can design an InfoPath form template to manage the expense reporting process for your organization. The form template can include views and business logic features that enable different categories of users to submit the expense report, review it, approve it, and reimburse the submitter.

Usage
InfoPath can be integrated with
a) Microsoft Office Outlook
b) Share Point Server
c) Biztalk Server
d) WebServices
e) K2.Net etc.,