BizTalk真是太強了~
偶然間看到,BizTalk也可以跟Cloud base的Salesforce CRM連接喔~
http://seroter.wordpress.com/2009/10/11/orchestrating-the-cloud-part-ii-creating-and-consuming-a-salesforce-com-service-from-biztalk-server/
推薦這個部落格: 1
可以快速幫助了解CRM如何幫助企業強化競爭力.
https://rc.crm.dynamics.com/rc/2011/en-us/on-prem/5.0/video_resources.aspx
內容主要有:
Get started
Getting started with Microsoft Dynamics CRM
Add Personnel to Microsoft Dynamics CRM
Account basics
Understanding contacts
Configure and customize
Tailor Microsoft Dynamics CRM for your business needs
Personalize Microsoft Dynamics CRM for yourself
Get data into Microsoft Dynamics CRM
Using duplicate detection
Data migration overview
Optimize productivity
Sharing and assigning records
Organize and track all your activities
Organize and centralize articles for your business
Use Goal Management
Routing your work with queues
Optimize business processes with workflows and dialogs
Create a simple workflow
Ceate a dialog
Improve customer service
Improve customer service with contracts
Getting started with cases
Simplify scheduling with services
Reach out to your customers
Getting started with leads
Winning sales with opportunities
Getting started with campaigns
Boost sales with a quick campaign
Target the right customers with marketing lists
Manage products and orders
Working with products and the product catalog
Set up your product catalog
Working with quotes, orders, and invoices
Concurrent Users* | Average Response Time | Web Requests | Business Transactions | Average SQL Server Utilization | Average CRM Server Utilization |
150,000 | .4 seconds | 5.5 M/hr | 703,080/hr | 39.6% | 42% |
數據來源:
http://technet.microsoft.com/en-us/library/hh204514.aspx
之前一直搞不懂,為何BizTalk要出一個這麼難用的ESB Toolkit東東.今天看了這篇文章後,稍微有點了解了.其實之前我們一直覺得在BizTalk理所當然的開發方式,如:建Send port, Receive Port, Publishing Web Service....等,在建構以SOA為主的架構上,實作上其實是有困難的.
這篇文章點出了到底BizTalk其實是個什麼東西,而有了ESB Toolkit後,他可以解決以前那些問題.
http://www.dotnetspider.com/resources/39068-Case-for-ESB-Toolkit-Why-do-we-need-it.aspx
底下是一個國外網站提出20個升級到CRM 2011的理由,可以參考看看.
20 Reasons to Upgrade to Microsoft Dynamics CRM 2011
http://www.opsvault.com/20-reasons-to-upgrade-to-microsoft-dynamics-crm-2011/
微軟先幫你安裝好了.
只要準備好Hyper-V環境後,下載完此vhd,再掛載上去即可歐
http://www.microsoft.com/download/en/details.aspx?id=13624
This section lists the operating system and software requirements for the Microsoft Dynamics CRM Web client.
The following operating systems are supported for the Microsoft Dynamics CRM Web client:
- Windows 7 (all versions)
- Windows Vista (all versions)
- Microsoft Windows XP Professional SP3
- Microsoft Windows XP Home SP3
- Windows XP Media Center Edition SP3
- Microsoft Windows XP Tablet SP3
In addition, the Microsoft Dynamics CRM Web client requires one of the following Internet Explorer Web browser versions:
- Internet Explorer 8
- Internet Explorer 7
To use Microsoft Dynamics CRM with Microsoft Office integration features, such as Export to Excel and Mail Merge, you must have one of the following installed Microsoft Office versions on the computer that is running the Microsoft Dynamics CRM Web client:
- Microsoft Office 2003 SP3
- 2007 Microsoft Office system SP2
- Office 2010
Note: Microsoft Windows 2000 editions are not supported for installing and running the Microsoft Dynamics CRM Web client.
http://technet.microsoft.com/en-us/library/gg554677.aspx
Slide上的圖片.

顯示在CRM系統上的圖形.

這........該不會是作假吧!!!!
經過一番的找尋,原來是有眉角的.
雖然一開始剛設定好的Pie Chart是2D的沒錯,但是可以透過匯出匯出圖表的功能,將2D的Pie Chart匯出成xml.

打開xml後,進行以下修改.
1. 找到ChartType屬性,從Pie改成doughnut
2. 將Area3DStyle屬性,從false改成true
然後再透過Import Chart將該xml匯入到CRM,之後就可以看到3D的Pie Chart囉~
不過這個做法有個後遺症,就是無法進行DrillDown的動作.看來只有基本的那幾種圖形才提供drilldown的功能. 因此最後還是乖乖的改回2D的圖形. .......殘念~
因為Windows 2008 R2的IIS已經是7.5了,已經不像是IIS6那樣直接Add WebService Extension就好了,需要比較繁瑣的步驟進行一些設定,才能將BTSHTTPReceive.dll啟用.
設定步驟如下:
執行IIS管理員

新增應用程式(請注意:此步驟是在尚未安裝RosettaNet Accelerator的情況下)

設定別名與實際路徑


成功建立BTARTNHTTPReceive應用程式

新增應用程式集區

修改應用程式集區,進階設定。

設定識別為Administrator

設定ISAPI及CGI限制
新增,設定路徑為C:\Program Files (x86)\Microsoft BizTalk Server 2010\HttpReceive\BTSHTTPReceive.dll
再新增一筆,路徑指到C:\Program Files (x86)\Microsoft BizTalk Server 2010\HttpReceive64\BTSHTTPReceive.dll
設定處理常式對應
選擇右上角”新增指令碼對應”。

指到執行檔C:\Program Files (x86)\Microsoft BizTalk Server 2010\HttpReceive\BTSHTTPReceive.dll
點選要求限制,點選”指令動詞”Tab,輸入動詞指令為POST。
按下是(Y)。

再輸入一筆是指到C:\Program Files (x86)\Microsoft BizTalk Server 2010\HttpReceive64\BTSHTTPReceive.dll
選擇剛建立的BTSHTTPReceive項目,設定編輯功能權限,然後勾選執行。
對另一個BTSHTTPReceive64項目也進行同樣的動作。

瀏覽BTARNHTTPReceive裡面的BTSHTTPReceive.dll。
當看到此畫面即表示設定完成。

http://msdn.microsoft.com/en-us/library/ee377036(v=BTS.70).aspx
根據此篇文章測試的結果,單純增加BizTalk Server的數量,並無法完全的提升BizTalk處理訊息的Throughput(吞吐量).
因為當今天處理訊息的瓶頸是在SQL Server時,增加BizTalk的個數只會讓SQL更疲於應付多一台BizTalk的request罷了,在處理訊息的速度上是完全得不到提升的.
文章當中,針對另一個影響Performance的要素MessageBox進行scale-out,從測試數據上看來,這樣反而可以獲得更大的效能提升.
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 |
- Dec 2011(1)
- Nov 2011(2)
- Oct 2011(1)
- Sep 2011(1)
- Aug 2011(1)
- Jul 2011(5)
- Jun 2011(1)
- May 2011(6)
- Apr 2011(2)
- Mar 2011(5)
- Feb 2011(1)
- Dec 2010(1)
- Nov 2010(2)
- Oct 2010(4)
- Sep 2010(2)
- Aug 2010(6)
- Jul 2010(3)
- Mar 2010(1)
- Feb 2010(1)
- Nov 2009(2)
- Oct 2009(1)
- Sep 2009(1)
- Jul 2009(2)
- Jun 2009(2)
- May 2009(1)
- Apr 2009(1)
- Mar 2009(1)
- Feb 2009(4)
- Jan 2009(1)
- Dec 2008(2)
- Oct 2008(1)
- Aug 2008(2)
- Jul 2008(3)
- Jun 2008(2)
- May 2008(2)
- Mar 2008(1)
- Oct 2007(2)
- Sep 2007(1)
- Aug 2007(1)
- Dec 2006(1)
- Oct 2006(1)
- Sep 2006(3)
- Aug 2006(2)
- Jul 2006(3)
- Jun 2006(2)
- Apr 2006(3)
- Mar 2006(2)
- Feb 2006(1)
- Jan 2006(3)
- Dec 2005(3)
- Nov 2005(1)
- Oct 2005(3)
- Sep 2005(8)
- Aug 2005(2)
- Jul 2005(5)
- Jun 2005(3)
- May 2005(10)




