Export (0) Print
Expand All

Release Notes

Connected Services Framework
The Connected Services Framework 2.5 Development Guide is applicable to the following  versions of CSF.

Connected Services Framework 2.5 Notes

New Documentation Sections

Two new sections, namely "Web services and Service Orientation" and "Connected Services Framework Architecture" have been added to the guide. These new sections detail each component and its place value in the framework, to help explain the notion of CSF as a system and network of web services.

The code samples in this guide will be synchronized with Connected Services Framework 2.5. Each Sample comes with its own ReadMe files with updated configuration details. Please use the ReadMe files to configure the samples.

CSF Session Clustering Notes:

The most critical scenario for the Session Manager and Session to handle is Failover in a clustered environment. This section shall primarily address Active-Active scenario in the cluster. The assumption is that if the application works fine with the Active-Active scenario, then it must work fine in the Active-Passive scenario.

Let us consider we have 3 active boxes clustered in such a way that they could back up each other in case of failure.

Initial Scenario

  • Session 1 is created in Box 1, IP 10.0.0.1

  • Session 2 is created in Box 2, IP 10.0.0.2

  • Session 3 is created in Box 3, IP 10.0.0.3

When each session is created, a record is created in the database to persist the state of the session. The database schema would look something like this. The session shall know which machine is the current owner at any given time. (This way we are tightly tying the session to a specific box)

SessionID

SessionManifestXML

CurrentOwner

1

<session>

10.0.0.1

2

<session>

10.0.0.2

3

<session>

10.0.0.3

When a message comes to Box 1 for Session 1 then it will be routed accordingly.

Failover Condition

Now let us consider the Failover scenario. Box 1 suddenly fails for some reason, and Box 2 takes over for it. IP Switch takes place. So now Box 2 has both 10.0.0.1 and 10.0.0.2.

When Session Manager gets a request for Session 1 in Box 2, the following steps take place in this scenario:

  1. Session Manager checks whether Session 1 is in-memory.
  2. Session 1 is not in-memory at this time.
  3. Therefore Session Manager checks the database
  • Where sessionid=1 and CurrentOwner = ’10.0.0.2’ or ‘10.0.0.1’.
  • Where sessionid=1 and CurrentOwner = ’10.0.0.2’ or ‘10.0.0.1’.
  • Message is routed through the Session.
     

Connected Services Framework Developer Edition Notes

The Developer Edition of CSF is a lean version designed to run on a single machine, so that Web services developers can get up and running quickly. Some features are not supported  in the Developer Edition. Any Sample in the guide that goes beyond the scope of Session and IDM is not applicable to CSF Developers Edition.

 Main Differences in the Developer Edition

The Developer Edition differs from the full product in the following ways:

  • Only Session Manager and Identity Manager Lite are installed in the Developer Edition. Profile Manager, Service Catalog, Service Logic, and Notification Participant are not supported.
  • IDM Lite is a scaled down version of the CSF Identity Manager (IDM). IDM Lite uses an XML file as the persistence medium, and simply stores user names and passwords in clear text.
  • Profiles are not supported in the Developer Edition.
  • The Developer Edition is limited to five active sessions.

Installing with .NET 2.0

If .NET Framework 2.0 / SQL 2005 is installed on the target computer, the IIS is set to run under ASP.NET 2.0. Please note that in this case CSF Developer Edition Installer will detect the ASP .Net 2.0 settings and will switch the "VRoot" of Session to run under .NET Framework 1.1.

SQL Server Instance Names

For the installation to run property you must have a SQL Server installed with the default settings. For SQL Server 2000 and SQL Server 2005 (non-express version) your SQL Server should not have an instance name. On SQL Server 2005 Express your installation should be with the named instance of "SQLExpress".

Database Creation Script

If you would like to change the database settings after the install and move instances you can run the following script to create the database manually.

1. Open a command window and browse to 'Program files\Microsoft CSF\CSFDeveloper\Database' or wherever the application is installed.

2. Run the following command (please adjust the file paths appropriately):

LaunchDB.exe "c:\Program files\Microsoft CSF\CSFDeveloper\Database\Scripts\SetupCSFDB.bat" "(local)\<SQL Instance Name>" CSFDB "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\CSFDB_Data.mdf" "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\CSFDB_Log.ldf" "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\CSFDB_TextImageData.ndf"

Replace <SQL Instance Name> with an appropriate SQL instance name on your server. Do not include angle brackets.

3. Manually create a database user in CSFDB as follows. Open a command window, navigate to 'Program files\Microsoft CSF\CSFDeveloper\Database' or wherever the application is installed, and run the following command:

DatabaseUpdate.exe <computer_name>\<SQL Instance Name>

For example:

DatabaseUpdate.exe computer123\SQLEXPRESS

If your SQL Server installation is a default instance (not a named instance) then simply pass the <computer_name> as in this example:

DatabaseUpdate.exe computer123


4. Verify that database user 'SessionLite' was created in CSFDB.

Software recommendations for the installation of CSF Developer Edition

Operating System

  •  Windows XP Professional. (Windows XP Home is not supported.)

  • Windows Server 2003 Standard, Enterprise and Datacenter editions are supported. (Windows Server 2003 Web Edition is not supported.)
     

Prerequisites

  •  Internet Information Services

  • Net Framework 1.1

  •  SQL Server 2000 SP3 or newer, or SQL Server 2005

  •  Microsoft Web Services Enhancements 2.0 SP3

  •  Enterprise Instrumentation Framework

Notes:

  • ASP .Net should be registered in IIS. If .Net Framework is installed before IIS then aspnet_iisreg.exe, located in the framework directory under the Windows OS directory, should be executed.
  • For Windows XP, Service Pack 2 is NOT mandatory.
  • SQL Server the authentication mode should be set to "SQL Server and Windows" and not to "Windows Only". This would be required for both Windows XP and Windows 2003.

     

Show:
© 2014 Microsoft