SOA 與 BPM 的話題近年已被炒的沸沸揚揚，各位也已聽過很多談 SOA 與 BPM 方法與架構的研討會，但這其中卻鮮有企業導入的實例與經驗分享。而在台灣 BPM 的概念更是一再的被誤導或片斷定義。

      本次活動將不同於以往各位所參加的研討會，而將完全以企業應用的實際情境為出發。本座談特地請到遠東金士頓科技（ Kingston ） CIO / Albert Hu 從美國回台擔任座談會貴賓，分享 Kingston 連續四年被 iSuppli 評選為『世界第一的記憶體模組獨立製造商』背後的 IT 決策 － 如何利用 SOA 與 BPM 的平台達到企業內系統的整合與流程變動的敏捷度。

      美商 Ascentn 在 2007 年榮獲全球最大的研究單位 Gartner 評為微軟平台上唯一的 BPMs Cool Vendor ，並被 Kingston 採用為跨國系統的 BPM 核心平台。 Ascentn 的全球總架構工程師 / Sean Zhang 將來台灣，為各位分享海外跨國企業在 SOA 的實務應用與建置經驗。 座談會中您將會知道世界級的企業領導者例如 DELL, LOCKHEED MARTIN, CDC (Center for Disease Control), SHELL, ELBIT, NTT, TOYOTA, etc., 如何以新一代的 SOA-aligned modern BPMS 來整合資源及建制敏捷的營運流程平台以應對新一代競爭者的挑戰 。

      座談會將以精英對話的方式，由知名的微軟技術顧問 / 胡百敬擔任主持人。胡百敬是國內眾多知名大型企業的長期顧問，著作等身。是資料庫、平台開發及大型企業架構方面的專家。他會針對 SOA 與 BPM 在企業內執行的成效、成本與開發時程等企業最關心的導入實務議題來提問，並與聽眾互動。

主 題：新一代的企業IT架構 － SOA & BPM平台實務座談
時 間：2007/11/16(五)下午1:30~4:30
地 點：六福皇宮/木星廳(2F)
主持人：Microsoft 技術顧問 / 胡百敬
主講人：Ascentn CTO / Sean Zhang
來 賓：Kingston CIO / Albert Hu
對 象：台灣企業CIO與資訊相關主管
名 額：50名（場地限制、額滿為止）
主辦單位：Ascentn Taiwan
協辦單位：台灣微軟/精誠資訊
活動方式：以精英對話的小型座談，從務實的角度討論現代企業所需要的IT架構（SOA）以及敏捷度（BPM）。

報名方式：請填寫以下報名資訊傳真至02-27591336 或者 線上報名

聯絡人：林靖崴
電話：02-5581-6697#202
傳真：02-2759-1336
E-mail：john.lin@ascentn.com
網址： http://www.ascentn.com.tw

needed to build up MOSS 2007 portal that would integrate some of the existing Line Of Business (LOB) applications. We also needed to use SSO, because some of the applications weren't AD-enabled. To use SSO, you can create your own custom web part and connect to the SSO services through there.

Enabling SSO

To enable SSO, you need to start the Microsoft Single Sign-On Service in the Services-tool of Windows. You can also do this on the command-line with "net start ssosrv". Keep in mind the service needs to run under an account that has access to the SQL hosting your SSO database. For demonstrational purposes you can use administrator, otherwise create a dedicated account.

Next, go to MOSS Central Admin at http://localhost:port, where port is whatever you specified when installing MOSS. Select Operations-tab, and navigate to Manage settings for single sign-on. If you get this error:

Failed to connect to Microsoft Single Sign-on Service. To configure, please ensure the service is running.

It means your SSO service is not running. Go and doublecheck the settings on that. Then, select Manage server settings, and fill out the fields. Default values are normally ok for those fields that have been prepopulated. Click OK - the database and settings for your SSO service should now be created.

Configuring applications for SSO

Now that you have SSO running, you need to configure which applications are going to take advantage of it. Go to Manage settings for enterprise application definitions (http://localhost:port/_admin/sso/ManageApps.aspx) and click New Item. Enter a display name, application name and contact email address. The important thing here is to enter an application name that is easy to remember and describes the integrated application, such as "Asp3Tools" or "FinanceApp". Fill out rest of the fields as you see fit.

If you're wondering what the five fields under logon account information are for, you can use those to send a maximum of 5 custom fields to your LOB application upon user authentication. Normally you'd use 2, one for username and one for password. MOSS uses these field names and settings to render the authentication form dynamically for you, when logging into the the LOB application for the first time (via SSO).

Creating skeleton web part for SSO

Now that you've successfully configured SSO for MOSS, it's time to create your web part. I'll provide the basic RenderContents() -method for you that walks through the basic step when using SSO:

        protected override void RenderContents(HtmlTextWriter output)
        {
            string[] rgGetCredentialData = null;

                try
                {

                    Credentials.GetCredentials(1, "AppName", ref rgGetCredentialData);

                    ISsoProvider provider = SsoProviderFactory.GetSsoProvider();
                    SsoCredentials creds = provider.GetCredentials("AppName");
                    creds.Evidence = new System.Security.SecureString[2];

                    try
                    {
                   // your implementation of accessing the LOB app
                    }
                    catch (Exception e)
                    {
                    // catch exceptions

                    }

                }

                catch (SingleSignonException ssoex)
                {
                    if (SSOReturnCodes.SSO_E_CREDS_NOT_FOUND == ssoex.LastErrorCode)
                    {
                        string strSSOLogonFormUrl = SingleSignonLocator.GetCredentialEntryUrl("AppName");
                        output.Write("<a href=" + strSSOLogonFormUrl + ">Click here to save your credentials for the Enterprise Application.</a>");
                    }

                }

You can do a HttpWebRequest to your application, parse the HttpWebResponse and render out your application. The important thing is to use the correct application name (AppName) and catch the SSO_E_CREDS_NOT_FOUND exception for first time users. MOSS will then create the initial authentication page for you, hiding possible other authentication pages you have in your LOB system.

reference comes from http://blogs.msdn.com/jro/

So, a good start with a posting today about one of the chalanges we've been dealing with the last couple of weeks. For our customer we want to create a customized wiki definition, with some additional fields and layout. Normally you would think to copy the wiki site definition and change the onet.xml and the list dinition for the additional fields. So this is what we did, and it turns out to work ok. But changing the layout of the wiki page itself is something different...

If you dive into the Wiki content type (I used sharepoint inspector to easily see the properties), you will see that when you create a new page, the 'CreateWebPage.aspx' page is called on the layouts directory.

This page makes sure the wiki page is created and a template file is connected to it called 'wkpstd.aspx' in the DocumentTemplates directory (C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\DocumentTemplates). This page takes are of the layout of the wiki page.

So, changing this page will change the layouts of all wiki pages, which is not supported and probably not what you want to do. Therefore, you have to change the onet.xml of the wiki site difinition to mention that the template that will be used is another one. In out case a copy stored on the same directory (i.e. wkpstd_custom.aspx). In the onet.xml we've changed the wkpstd.aspx to our custom page.

<Module Name="DefaultWikiPages" List="1119" Url="$Resources:core,WikiWebLibPages_Folder;" Path="" SetupPath="DocumentTemplates">
     <File Url="wkpstd_custom.aspx" Name="$Resources:core,nav_Home;.aspx" Type="GhostableInLibrary">
       <Property Name="WikiField" Value="$Resources:core,WikiHomeContent;" />
       <NavBarPage Name="$Resources:core,nav_Home;" ID="1002" Position="Start" />
       <NavBarPage Name="$Resources:core,nav_Home;" ID="1010" Position="Start" />
     </File>
     <File Url="wkpstd_custom.aspx" Name="$Resources:core,nav_HowToUseThisWikiSite;.aspx" Type="GhostableInLibrary">
       <Property Name="WikiField" Value="$Resources:core,WikiHowToUseContent_Part1;$Resources:core,WikiHowToUseContent_Part2;$Resources:core,
WikiHowToUseContent_Part3;$Resources:core,WikiHowToUseContent_Part4;$Resources:core,WikiHowToUseContent_Part5;$Resources:core,
WikiHowToUseContent_Part6;$Resources:core,WikiHowToUseContent_Part7;$Resources:core,WikiHowToUseContent_Part8;" />
       <NavBarPage Name="$Resources:core,nav_HowToUseThisWikiSite;" ID="1010" />
     </File>
</Module>

But now the pages that are created by this site definition will have the new layout, all new created wiki pages stange enough not... So what happens? Somehow, in the CreateWebPage.aspx file, the wkpstd.aspx is 'hardcoded' used and there are two options to avoid that:

1. Create a new CreateWebPage.aspx file with your own custom code. This page will create new pages based on the new custom aspx file as a template
2. Create an eventhandler that will activate with the site definition that programatically sets the template page for each new created wiki page.

Personally I would prefer the second option, but that's up to you. Anyway learning something new everyday! Also thanks to my colleague Wouter for also researching this. :)

refernce comes from http://blogs.tamtam.nl/mart/

public string CreateTask(string SitePath, string TaskName, string AssgnTo, DateTime DueDate)

{

string ReturnVal = "";

try

{

SPSite WebApp = new SPSite(SitePath);

SPWeb Site = WebApp.OpenWeb();

SPList TaskList = Site.Lists["Tasks"];

// add a new item…

SPListItem NewTask = TaskList.Lists["Tasks"].Items.Add();

NewTask["Priority"] = "(2) Normal";

NewTask["Title"] = TaskName;

NewTask["DueDate"] = DueDate;

NewTask["Assigned To"] = Site.Users.GetByEmail(AssgnTo);

NewTask.Update();

}

catch (Exception ex){

ReturnVal += "Task not added, reason: " + ex.Message;

}

return ReturnVal;

}

Contact contact = Contact.FromName("domain\\name", SPContext.Current.Web);

if (contact.PrincipalID < 0){
    SPContext.Current.Web.AllowUnsafeUpdates = true;
    SPPrincipal p = contact.GetPrincipal(SPContext.Current.Web);
}

SPUser newUser = SPContext.Current.Web.SiteUsers[contact.LoginName];

http://msdn2.microsoft.com/en-us/library/ms551453.aspx

Oops 真是辛苦, 終於我的 KM 平台 V2.0 已經於上星期五完成了大部分約 95% 功能, 如果網友有看到這樣的訊息想要測試的可以 Mail 給我(weishoun@rstn.com) 或歡迎加入我 MSN(hilfiger1014@hotmail.com) 大家互相討論ㄅㄟ