<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://code.msdn.microsoft.com/rss.xsl"?><rss version="2.0"><channel><title>OBA Sample Application Kit for PeopleSoft</title><link>http://code.msdn.microsoft.com/obapsftsak/Project/ProjectRss.aspx</link><description>This page provides developers with guidance on how they can integrate PeopleSoft with Office, specifically Outlook 2007 and MOSS 2007. </description><item><title>UPDATED WIKI: Home</title><link>http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=Home&amp;version=8</link><description>&lt;div class="wikidoc"&gt;
Office Business Application (OBA) Sample Application Kit for PeopleSoft&lt;br /&gt; &lt;br /&gt;So, you're probably asking yourself: what is OBA, and why should I care?? OBAs are essentially a new breed of composite application that you build using the Office Platform. OBAs at their essence are made up of three major pieces: i) the LOB system (e.g. SAP, PeopleSoft, or Dynamics), ii) A customized Office client (e.g. custom task pane using Visual Studio), and iii) SharePoint customizations (e.g. Business Data Catalog (BDC)) Web part. The value of OBAs derives from the fact that by building them you can integrate specific parts of the LOB systems in your organization directly into the Office interface that your information workers use on a daily basis--think Sales data integrated into Excel 2007 which enables you to use the native functionality of Excel and a customized Excel client to read/write data. This same idea applies to the SharePoint environment, where developers can also create views into data using different service-bound Web parts. The net for OBA development is that if your orgamization uses Office in their daily operations and you're not building OBAs, then you're missing an opportunity to leverage your existing infrastructure (as opposed to building and supporting separate LOB applications). &lt;br /&gt; &lt;br /&gt;For more information on OBA, I would suggest the following resources: &lt;br /&gt; &lt;br /&gt;1. Six Office Business Applications (MS Press) or Programming Microsoft Office Business Applications (MS Press). &lt;br /&gt;2. Overview of an OBA: http://msdn2.microsoft.com/en-us/library/bb614538.aspx. &lt;br /&gt;3. Overview of OBA Solution Patterns: http://msdn2.microsoft.com/en-us/library/bb614541.aspx. &lt;br /&gt;4. My blog (http://blogs.msdn.com/steve_fox/) where I've listed out some additional resources to check out. &lt;br /&gt; &lt;br /&gt;So, with the above in hand what is this OBA Sample Application Kit for PeopleSoft? &lt;br /&gt; &lt;br /&gt;In many cases, developers don't have the knowledge on how to programmatically integrate Office applications with LOB systems. What this kit provides is guidance on how you can integrate with Web services that have been generated from within PeopleSoft and then consume those services within a .NET and managed code environment. The OBA Sample Application Kit for PeopleSoft (one in a series of kits) includes a whitepaper, installation document, source code, and client-side binaries (server-side (MOSS) code is discussed in the documents how to deploy) for you to use and learn how you integrate PeopleSoft programmatically into your Office system. &lt;br /&gt; &lt;br /&gt;The goal of the kit is to provide developers with some information on how they can go ahead and learn how to programmatically integrate PeopleSoft with Office (specifically Outlook 2007 and MOSS 2007), thus providing you with specific knowledge around Visual Studio Tools for Office (VSTO) - a component technology within Visual Studio 2008 that enables you to build Office solutions, the MOSS 2007 BDC and the integration with Web services, and more generically the use of Web services developed using PeopleTool within .NET and the Visual Studio IDE. &lt;br /&gt; &lt;br /&gt;I hope you enjoy the kit, and if you're looking for something on SAP integration, check out the OBA Sample Application Kit for SAP: http://code.msdn.microsoft.com/obasapsak.&lt;br /&gt; &lt;br /&gt;Steve&lt;br /&gt; &lt;br /&gt;PS There was an issue with the source code download--empty zip file noted on 04/20/08. I've uploaded the bits again, so this problem should now be resolved. Apologies for the inconvenience.&lt;br /&gt;
&lt;/div&gt;</description><author>Steve_Fox</author><pubDate>Tue, 08 Jul 2008 17:05:26 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: Home 20080708P</guid></item><item><title>UPDATED WIKI: Home</title><link>http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=Home&amp;version=7</link><description>&lt;div class="wikidoc"&gt;
Office Business Application (OBA) Sample Application Kit for PeopleSoft&lt;br /&gt; &lt;br /&gt;So, you're probably asking yourself: what is OBA, and why should I care?? OBAs are essentially a new breed of composite application that you build using the Office Platform. OBAs at their essence are made up of three major pieces: i) the LOB system (e.g. SAP, PeopleSoft, or Dynamics), ii) A customized Office client (e.g. custom task pane using Visual Studio), and iii) SharePoint customizations (e.g. Business Data Catalog (BDC)) Web part. The value of OBAs derives from the fact that by building them you can integrate specific parts of the LOB systems in your organization directly into the Office interface that your information workers use on a daily basis--think Sales data integrated into Excel 2007 which enables you to use the native functionality of Excel and a customized Excel client to read/write data. This same idea applies to the SharePoint environment, where developers can also create views into data using different service-bound Web parts. The net for OBA development is that if your orgamization uses Office in their daily operations and you're not building OBAs, then you're missing an opportunity to leverage your existing infrastructure (as opposed to building and supporting separate LOB applications). &lt;br /&gt; &lt;br /&gt;For more information on OBA, I would suggest the following resources: &lt;br /&gt; &lt;br /&gt;1. Six Office Business Applications (MS Press) or Programming Microsoft Office Business Applications (MS Press). &lt;br /&gt;2. Overview of an OBA: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614538.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614538.aspx&lt;/a&gt;. &lt;br /&gt;3. Overview of OBA Solution Patterns: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614541.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614541.aspx&lt;/a&gt;. &lt;br /&gt;4. My blog (&lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fblogs.msdn.com%2fsteve_fox%2f&amp;amp;referringTitle=Home"&gt;http://blogs.msdn.com/steve_fox/&lt;/a&gt;) where I've listed out some additional resources to check out. &lt;br /&gt; &lt;br /&gt;So, with the above in hand what is this OBA Sample Application Kit for PeopleSoft? &lt;br /&gt; &lt;br /&gt;In many cases, developers don't have the knowledge on how to programmatically integrate Office applications with LOB systems. What this kit provides is guidance on how you can integrate with Web services that have been generated from within PeopleSoft and then consume those services within a .NET and managed code environment. The OBA Sample Application Kit for PeopleSoft (one in a series of kits) includes a whitepaper, installation document, source code, and client-side binaries (server-side (MOSS) code is discussed in the documents how to deploy) for you to use and learn how you integrate PeopleSoft programmatically into your Office system. &lt;br /&gt; &lt;br /&gt;The goal of the kit is to provide developers with some information on how they can go ahead and learn how to programmatically integrate PeopleSoft with Office (specifically Outlook 2007 and MOSS 2007), thus providing you with specific knowledge around Visual Studio Tools for Office (VSTO) - a component technology within Visual Studio 2008 that enables you to build Office solutions, the MOSS 2007 BDC and the integration with Web services, and more generically the use of Web services developed using PeopleTool within .NET and the Visual Studio IDE. &lt;br /&gt; &lt;br /&gt;I hope you enjoy the kit, and if you're looking for something on SAP integration, check out the OBA Sample Application Kit for SAP: http://code.msdn.microsoft.com/obasapsak.&lt;br /&gt; &lt;br /&gt;Steve&lt;br /&gt; &lt;br /&gt;PS There was an issue with the source code download--empty zip file noted on 04/20/08. I've uploaded the bits again, so this problem should now be resolved. Apologies for the inconvenience.&lt;br /&gt;
&lt;/div&gt;</description><author>Steve_Fox</author><pubDate>Tue, 08 Jul 2008 17:04:48 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: Home 20080708P</guid></item><item><title>UPDATED WIKI: Home</title><link>http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=Home&amp;version=6</link><description>&lt;div class="wikidoc"&gt;
Office Business Application (OBA) Sample Application Kit for PeopleSoft&lt;br /&gt; &lt;br /&gt;So, you're probably asking yourself: what is OBA, and why should I care?? OBAs are essentially a new breed of composite application that you build using the Office Platform. OBAs at their essence are made up of three major pieces: i) the LOB system (e.g. SAP, PeopleSoft, or Dynamics), ii) A customized Office client (e.g. custom task pane using Visual Studio), and iii) SharePoint customizations (e.g. Business Data Catalog (BDC)) Web part. The value of OBAs derives from the fact that by building them you can integrate specific parts of the LOB systems in your organization directly into the Office interface that your information workers use on a daily basis--think Sales data integrated into Excel 2007 which enables you to use the native functionality of Excel and a customized Excel client to read/write data. This same idea applies to the SharePoint environment, where developers can also create views into data using different service-bound Web parts. The net for OBA development is that if your orgamization uses Office in their daily operations and you're not building OBAs, then you're missing an opportunity to leverage your existing infrastructure (as opposed to building and supporting separate LOB applications). &lt;br /&gt; &lt;br /&gt;For more information on OBA, I would suggest the following resources: &lt;br /&gt; &lt;br /&gt;1. Six Office Business Applications (MS Press) or Programming Microsoft Office Business Applications (MS Press). &lt;br /&gt;2. Overview of an OBA: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614538.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614538.aspx&lt;/a&gt;. &lt;br /&gt;3. Overview of OBA Solution Patterns: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614541.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614541.aspx&lt;/a&gt;. &lt;br /&gt;4. My blog (&lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fblogs.msdn.com%2fsteve_fox%2f&amp;amp;referringTitle=Home"&gt;http://blogs.msdn.com/steve_fox/&lt;/a&gt;) where I've listed out some additional resources to check out. &lt;br /&gt; &lt;br /&gt;So, with the above in hand what is this OBA Sample Application Kit for PeopleSoft? &lt;br /&gt; &lt;br /&gt;In many cases, developers don't have the knowledge on how to programmatically integrate Office applications with LOB systems. What this kit provides is guidance on how you can integrate with Web services that have been generated from within PeopleSoft and then consume those services within a .NET and managed code environment. The OBA Sample Application Kit for PeopleSoft (one in a series of kits) includes a whitepaper, installation document, source code, and client-side binaries (server-side (MOSS) code is discussed in the documents how to deploy) for you to use and learn how you integrate PeopleSoft programmatically into your Office system. &lt;br /&gt; &lt;br /&gt;The goal of the kit is to provide developers with some information on how they can go ahead and learn how to programmatically integrate PeopleSoft with Office (specifically Outlook 2007 and MOSS 2007), thus providing you with specific knowledge around Visual Studio Tools for Office (VSTO) - a component technology within Visual Studio 2008 that enables you to build Office solutions, the MOSS 2007 BDC and the integration with Web services, and more generically the use of Web services developed using PeopleTool within .NET and the Visual Studio IDE. &lt;br /&gt; &lt;br /&gt;I hope you enjoy the kit, and if you're looking for something on SAP integration, check out the OBA Sample Application Kit for SAP: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fcode.msdn.microsoft.com%2fobasapsak&amp;amp;referringTitle=Home"&gt;http://code.msdn.microsoft.com/obasapsak&lt;/a&gt;.&lt;br /&gt; &lt;br /&gt;Steve&lt;br /&gt; &lt;br /&gt;PS There was an issue with the source code download--empty zip file noted on 04/20/08. I've uploaded the bits again, so this problem should now be resolved. Apologies for the inconvenience.&lt;br /&gt;
&lt;/div&gt;</description><author>Steve_Fox</author><pubDate>Tue, 08 Jul 2008 17:03:24 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: Home 20080708P</guid></item><item><title>UPDATED WIKI: Home</title><link>http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=Home&amp;version=5</link><description>&lt;div class="wikidoc"&gt;
Office Business Application (OBA) Sample Application Kit for PeopleSoft&lt;br /&gt; &lt;br /&gt;So, you're probably asking yourself: what is OBA, and why should I care?? OBAs are essentially a new breed of composite application that you build using the Office Platform. OBAs at their essence are made up of three major pieces: i) the LOB system (e.g. SAP, PeopleSoft, or Dynamics), ii) A customized Office client (e.g. custom task pane using Visual Studio), and iii) SharePoint customizations (e.g. Business Data Catalog (BDC)) Web part. The value of OBAs derives from the fact that by building them you can integrate specific parts of the LOB systems in your organization directly into the Office interface that your information workers use on a daily basis--think Sales data integrated into Excel 2007 which enables you to use the native functionality of Excel and a customized Excel client to read/write data. This same idea applies to the SharePoint environment, where developers can also create views into data using different service-bound Web parts. The net for OBA development is that if your orgamization uses Office in their daily operations and you're not building OBAs, then you're missing an opportunity to leverage your existing infrastructure (as opposed to building and supporting separate LOB applications). &lt;br /&gt; &lt;br /&gt;For more information on OBA, I would suggest the following resources: &lt;br /&gt; &lt;br /&gt;1. Six Office Business Applications (MS Press) or Programming Microsoft Office Business Applications (MS Press). &lt;br /&gt;2. Overview of an OBA: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614538.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614538.aspx&lt;/a&gt;. &lt;br /&gt;3. Overview of OBA Solution Patterns: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614541.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614541.aspx&lt;/a&gt;. &lt;br /&gt;4. My blog (&lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fblogs.msdn.com%2fsteve_fox%2f&amp;amp;referringTitle=Home"&gt;http://blogs.msdn.com/steve_fox/&lt;/a&gt;) where I've listed out some additional resources to check out. &lt;br /&gt; &lt;br /&gt;So, with the above in hand what is this OBA Sample Application Kit for PeopleSoft? &lt;br /&gt; &lt;br /&gt;In many cases, developers don't have the knowledge on how to programmatically integrate Office applications with LOB systems. What this kit provides is guidance on how you can integrate with Web services that have been generated from within PeopleSoft and then consume those services within a .NET and managed code environment. The OBA Sample Application Kit for PeopleSoft (one in a series of kits) includes a whitepaper, installation document, source code, and client-side binaries (server-side (MOSS) code is discussed in the documents how to deploy) for you to use and learn how you integrate PeopleSoft programmatically into your Office system. &lt;br /&gt; &lt;br /&gt;The goal of the kit is to provide developers with some information on how they can go ahead and learn how to programmatically integrate PeopleSoft with Office (specifically Outlook 2007 and MOSS 2007), thus providing you with specific knowledge around Visual Studio Tools for Office (VSTO) - a component technology within Visual Studio 2008 that enables you to build Office solutions, the MOSS 2007 BDC and the integration with Web services, and more generically the use of Web services developed using PeopleTool within .NET and the Visual Studio IDE. &lt;br /&gt; &lt;br /&gt;I hope you enjoy the kit, and if you're looking for something on SAP integration, check out the OBA Sample Application Kit for SAP: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fcode.msdn.microsoft.com%2fobasapsak&amp;amp;referringTitle=Home"&gt;http://code.msdn.microsoft.com/obasapsak&lt;/a&gt;.&lt;br /&gt; &lt;br /&gt;Steve&lt;br /&gt; &lt;br /&gt;PS There was an issue with the source code download--empty zip file noted on 04/20/08. I've uploaded the bits again, so this problem should now be resolved. Apologies for the inconvenience.&lt;br /&gt;
&lt;/div&gt;</description><author>Steve_Fox</author><pubDate>Tue, 08 Jul 2008 17:02:06 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: Home 20080708P</guid></item><item><title>UPDATED WIKI: Home</title><link>http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=Home&amp;version=4</link><description>&lt;div class="wikidoc"&gt;
Office Business Application (OBA) Sample Application Kit for PeopleSoft&lt;br /&gt; &lt;br /&gt;So, you're probably asking yourself: what is OBA, and why should I care?? OBAs are essentially a new breed of composite application that you build using the Office Platform. OBAs at their essence are made up of three major pieces: i) the LOB system (e.g. SAP, PeopleSoft, or Dynamics), ii) A customized Office client (e.g. custom task pane using Visual Studio), and iii) SharePoint customizations (e.g. Business Data Catalog (BDC)) Web part. The value of OBAs derives from the fact that by building them you can integrate specific parts of the LOB systems in your organization directly into the Office interface that your information workers use on a daily basis--think Sales data integrated into Excel 2007 which enables you to use the native functionality of Excel and a customized Excel client to read/write data. This same idea applies to the SharePoint environment, where developers can also create views into data using different service-bound Web parts. The net for OBA development is that if your orgamization uses Office in their daily operations and you're not building OBAs, then you're missing an opportunity to leverage your existing infrastructure (as opposed to building and supporting separate LOB applications). &lt;br /&gt; &lt;br /&gt;For more information on OBA, I would suggest the following resources: &lt;br /&gt; &lt;br /&gt;1. Six Office Business Applications (MS Press) or Programming Microsoft Office Business Applications (MS Press). &lt;br /&gt;2. Overview of an OBA: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614538.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614538.aspx&lt;/a&gt;. &lt;br /&gt;3. Overview of OBA Solution Patterns: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614541.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614541.aspx&lt;/a&gt;. &lt;br /&gt;4. My blog (&lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fblogs.gotdotnet.com%2fsteve_fox%2fdefault.aspx&amp;amp;referringTitle=Home"&gt;http://blogs.gotdotnet.com/steve_fox/default.aspx&lt;/a&gt;) where I've listed out some additional resources to check out. &lt;br /&gt; &lt;br /&gt;So, with the above in hand what is this OBA Sample Application Kit for PeopleSoft? &lt;br /&gt; &lt;br /&gt;In many cases, developers don't have the knowledge on how to programmatically integrate Office applications with LOB systems. What this kit provides is guidance on how you can integrate with Web services that have been generated from within PeopleSoft and then consume those services within a .NET and managed code environment. The OBA Sample Application Kit for PeopleSoft (one in a series of kits) includes a whitepaper, installation document, source code, and client-side binaries (server-side (MOSS) code is discussed in the documents how to deploy) for you to use and learn how you integrate PeopleSoft programmatically into your Office system. &lt;br /&gt; &lt;br /&gt;The goal of the kit is to provide developers with some information on how they can go ahead and learn how to programmatically integrate PeopleSoft with Office (specifically Outlook 2007 and MOSS 2007), thus providing you with specific knowledge around Visual Studio Tools for Office (VSTO) - a component technology within Visual Studio 2008 that enables you to build Office solutions, the MOSS 2007 BDC and the integration with Web services, and more generically the use of Web services developed using PeopleTool within .NET and the Visual Studio IDE. &lt;br /&gt; &lt;br /&gt;I hope you enjoy the kit, and if you're looking for something on SAP integration, check out the OBA Sample Application Kit for SAP: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fcode.msdn.microsoft.com%2fobasapsak&amp;amp;referringTitle=Home"&gt;http://code.msdn.microsoft.com/obasapsak&lt;/a&gt;.&lt;br /&gt; &lt;br /&gt;Steve&lt;br /&gt; &lt;br /&gt;PS There was an issue with the source code download--empty zip file noted on 04/20/08. I've uploaded the bits again, so this problem should now be resolved. Apologies for the inconvenience.&lt;br /&gt;
&lt;/div&gt;</description><author>Steve_Fox</author><pubDate>Tue, 22 Apr 2008 20:08:48 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: Home 20080422P</guid></item><item><title>UPDATED RELEASE: OBA Sample Application for PeopleSoft, v. 1.0 (Apr 07, 2008)</title><link>http://code.msdn.microsoft.com/obapsftsak/Release/ProjectReleases.aspx?ReleaseId=845</link><description>In this release, you&amp;#39;ll find four major deliverables--each of which is intended to help the developer understand how they can programmatically integrate PeopleSoft with Microsoft Office technologies and applications. Specifically, you&amp;#39;ll find&amp;#58; &lt;br /&gt;&lt;br /&gt;1. A technical whitepaper that provides an overview of the sample application kit.&lt;br /&gt;2. An installation guide, which walks you through how to recreate the environment.&lt;br /&gt;3. A walkthrough document, which takes you through the end-user experience of the solution in the kit.&lt;br /&gt;4. Some sample code to get you started--at least for the client side bits &amp;#40;Outlook 2007&amp;#41;.&lt;br /&gt;&lt;br /&gt;Please note that these items are unsupported and are intended only for instructional use. &lt;br /&gt;&lt;br /&gt;</description><author></author><pubDate>Tue, 22 Apr 2008 19:57:15 GMT</pubDate><guid isPermaLink="false">UPDATED RELEASE: OBA Sample Application for PeopleSoft, v. 1.0 (Apr 07, 2008) 20080422P</guid></item><item><title>UPDATED WIKI: Home</title><link>http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=Home&amp;version=3</link><description>&lt;div class="wikidoc"&gt;
Office Business Application (OBA) Sample Application Kit for PeopleSoft&lt;br /&gt; &lt;br /&gt;So, you're probably asking yourself: what is OBA, and why should I care?? OBAs are essentially a new breed of composite application that you build using the Office Platform. OBAs at their essence are made up of three major pieces: i) the LOB system (e.g. SAP, PeopleSoft, or Dynamics), ii) A customized Office client (e.g. custom task pane using Visual Studio), and iii) SharePoint customizations (e.g. Business Data Catalog (BDC)) Web part. The value of OBAs derives from the fact that by building them you can integrate specific parts of the LOB systems in your organization directly into the Office interface that your information workers use on a daily basis--think Sales data integrated into Excel 2007 which enables you to use the native functionality of Excel and a customized Excel client to read/write data. This same idea applies to the SharePoint environment, where developers can also create views into data using different service-bound Web parts. The net for OBA development is that if your orgamization uses Office in their daily operations and you're not building OBAs, then you're missing an opportunity to leverage your existing infrastructure (as opposed to building and supporting separate LOB applications). &lt;br /&gt; &lt;br /&gt;For more information on OBA, I would suggest the following resources: &lt;br /&gt; &lt;br /&gt;1. Six Office Business Applications (MS Press) or Programming Microsoft Office Business Applications (MS Press). &lt;br /&gt;2. Overview of an OBA: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614538.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614538.aspx&lt;/a&gt;. &lt;br /&gt;3. Overview of OBA Solution Patterns: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614541.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614541.aspx&lt;/a&gt;. &lt;br /&gt;4. My blog (&lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fblogs.gotdotnet.com%2fsteve_fox%2fdefault.aspx&amp;amp;referringTitle=Home"&gt;http://blogs.gotdotnet.com/steve_fox/default.aspx&lt;/a&gt;) where I've listed out some additional resources to check out. &lt;br /&gt; &lt;br /&gt;So, with the above in hand what is this OBA Sample Application Kit for PeopleSoft? &lt;br /&gt; &lt;br /&gt;In many cases, developers don't have the knowledge on how to programmatically integrate Office applications with LOB systems. What this kit provides is guidance on how you can integrate with Web services that have been generated from within PeopleSoft and then consume those services within a .NET and managed code environment. The OBA Sample Application Kit for PeopleSoft (one in a series of kits) includes a whitepaper, installation document, source code, and client-side binaries (server-side (MOSS) code is discussed in the documents how to deploy) for you to use and learn how you integrate PeopleSoft programmatically into your Office system. &lt;br /&gt; &lt;br /&gt;The goal of the kit is to provide developers with some information on how they can go ahead and learn how to programmatically integrate PeopleSoft with Office (specifically Outlook 2007 and MOSS 2007), thus providing you with specific knowledge around Visual Studio Tools for Office (VSTO) - a component technology within Visual Studio 2008 that enables you to build Office solutions, the MOSS 2007 BDC and the integration with Web services, and more generically the use of Web services developed using PeopleTool within .NET and the Visual Studio IDE. &lt;br /&gt; &lt;br /&gt;I hope you enjoy the kit, and if you're looking for something on SAP integration, check out the OBA Sample Application Kit for SAP: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fcode.msdn.microsoft.com%2fobasapsak&amp;amp;referringTitle=Home"&gt;http://code.msdn.microsoft.com/obasapsak&lt;/a&gt;.&lt;br /&gt; &lt;br /&gt;Steve&lt;br /&gt;
&lt;/div&gt;</description><author>Steve_Fox</author><pubDate>Wed, 09 Apr 2008 15:55:31 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: Home 20080409P</guid></item><item><title>UPDATED RELEASE: OBA Sample Application for PeopleSoft, v. 1.0 (Apr 07, 2008)</title><link>http://code.msdn.microsoft.com/obapsftsak/Release/ProjectReleases.aspx?ReleaseId=845</link><description>In this release, you&amp;#39;ll find four major deliverables--each of which is intended to help the developer understand how they can programmatically integrate PeopleSoft with Microsoft Office technologies and applications. Specifically, you&amp;#39;ll find&amp;#58; &lt;br /&gt;&lt;br /&gt;1. A technical whitepaper that provides an overview of the sample application kit.&lt;br /&gt;2. An installation guide, which walks you through how to recreate the environment.&lt;br /&gt;3. A walkthrough document, which takes you through the end-user experience of the solution in the kit.&lt;br /&gt;4. Some sample code to get you started--at least for the client side bits &amp;#40;Outlook 2007&amp;#41;.&lt;br /&gt;&lt;br /&gt;Please note that these items are unsupported and are intended only for instructional use. &lt;br /&gt;&lt;br /&gt;</description><author></author><pubDate>Mon, 07 Apr 2008 22:44:06 GMT</pubDate><guid isPermaLink="false">UPDATED RELEASE: OBA Sample Application for PeopleSoft, v. 1.0 (Apr 07, 2008) 20080407P</guid></item><item><title>CREATED RELEASE: OBA Sample Application for PeopleSoft, v. 1.0 (Apr 07, 2008)</title><link>http://code.msdn.microsoft.com/obapsftsak/Release/ProjectReleases.aspx?ReleaseId=845</link><description>In this release, you&amp;#39;ll find four major deliverables--each of which is intended to help the developer understand how they can programmatically integrate PeopleSoft with Microsoft Office technologies and applications. Specifically, you&amp;#39;ll find&amp;#58; &lt;br /&gt;&lt;br /&gt;1. A technical whitepaper that provides an overview of the sample application kit.&lt;br /&gt;2. An installation guide, which walks you through how to recreate the environment.&lt;br /&gt;3. A walkthrough document, which takes you through the end-user experience of the solution in the kit.&lt;br /&gt;4. Some sample code to get you started--at least for the client side bits &amp;#40;Outlook 2007&amp;#41;.&lt;br /&gt;&lt;br /&gt;I&amp;#39;ve also uploaded an OBA Overview deck that will help you become more familiar with OBAs in general.&lt;br /&gt;&lt;br /&gt;</description><author></author><pubDate>Mon, 07 Apr 2008 22:43:09 GMT</pubDate><guid isPermaLink="false">CREATED RELEASE: OBA Sample Application for PeopleSoft, v. 1.0 (Apr 07, 2008) 20080407P</guid></item><item><title>UPDATED RELEASE: OBA Sample Application Kit for PeopleSoft, v. 1.0 (Mar 27, 2008)</title><link>http://code.msdn.microsoft.com/obapsftsak/Release/ProjectReleases.aspx?ReleaseId=739</link><description>In this release, you&amp;#39;ll find four major deliverables--each of which is intended to help the developer understand how they can programmatically integrate PeopleSoft with Microsoft Office technologies and applications. Specifically, you&amp;#39;ll find&amp;#58; &lt;br /&gt;&lt;br /&gt;1. A technical whitepaper that provides an overview of the sample application kit.&lt;br /&gt;2. An installation guide, which walks you through how to recreate the environment.&lt;br /&gt;3. A walkthrough document, which takes you through the end-user experience of the solution in the kit.&lt;br /&gt;4. Some sample code to get you started--at least for the client side bits &amp;#40;Outlook 2007&amp;#41;.&lt;br /&gt;&lt;br /&gt;I&amp;#39;ve also uploaded an OBA Overview deck that will help you become more familiar with OBAs in general.&lt;br /&gt;&lt;br /&gt;Note&amp;#58; These are early drafts of the documents &amp;#40;as of 03&amp;#47;30&amp;#47;08&amp;#41;, so there may be future iterations on these. </description><author></author><pubDate>Tue, 01 Apr 2008 18:58:44 GMT</pubDate><guid isPermaLink="false">UPDATED RELEASE: OBA Sample Application Kit for PeopleSoft, v. 1.0 (Mar 27, 2008) 20080401P</guid></item><item><title>UPDATED WIKI: Home</title><link>http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=Home&amp;version=2</link><description>&lt;div class="wikidoc"&gt;
Office Business Application (OBA) Sample Application Kit for PeopleSoft&lt;br /&gt; &lt;br /&gt;So, you're probably asking yourself: what is OBA, and why should I care?? OBAs are essentially a new breed of composite application that you build using the Office Platform. OBAs at their essence are made up of three major pieces: i) the LOB system (e.g. SAP, PeopleSoft, or Dynamics), ii) A customized Office client (e.g. custom task pane using Visual Studio), and iii) SharePoint customizations (e.g. Business Data Catalog (BDC)) Web part. The value of OBAs derives from the fact that by building them you can integrate specific parts of the LOB systems in your organization directly into the Office interface that your information workers use on a daily basis--think Sales data integrated into Excel 2007 which enables you to use the native functionality of Excel and a customized Excel client to read/write data. This same idea applies to the SharePoint environment, where developers can also create views into data using different service-bound Web parts. The net for OBA development is that if your orgamization uses Office in their daily operations and you're not building OBAs, then you're missing an opportunity to leverage your existing infrastructure (as opposed to building and supporting separate LOB applications). &lt;br /&gt; &lt;br /&gt;For more information on OBA, I would suggest the following resources: &lt;br /&gt; &lt;br /&gt;1. Six Office Business Applications (MS Press) or Programming Microsoft Office Business Applications (MS Press). &lt;br /&gt;2. Overview of an OBA: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614538.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614538.aspx&lt;/a&gt;. &lt;br /&gt;3. Overview of OBA Solution Patterns: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2flibrary%2fbb614541.aspx&amp;amp;referringTitle=Home"&gt;http://msdn2.microsoft.com/en-us/library/bb614541.aspx&lt;/a&gt;. &lt;br /&gt;4. My blog (&lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fblogs.gotdotnet.com%2fsteve_fox%2fdefault.aspx&amp;amp;referringTitle=Home"&gt;http://blogs.gotdotnet.com/steve_fox/default.aspx&lt;/a&gt;) where I've listed out some additional resources to check out. &lt;br /&gt; &lt;br /&gt;So, with the above in hand what is this OBA Sample Application Kit for PeopleSoft? &lt;br /&gt; &lt;br /&gt;In many cases, developers don't have the knowledge on how to programmatically integrate Office applications with LOB systems. What this kit provides is guidance on how you can integrate with Web services that have been generated from within PeopleSoft and then consume those services within a .NET and managed code environment. The OBA Sample Application Kit for PeopleSoft (one in a series of kits) includes a whitepaper, installation document, source code, and client-side binaries (server-side (MOSS) code is discussed in the documents how to deploy) for you to use and learn how you integrate PeopleSoft programmatically into your Office system. &lt;br /&gt; &lt;br /&gt;The goal of the kit is to provide developers with some information on how they can go ahead and learn how to programmatically integrate SAP with Office (specifically Outlook 2007 and MOSS 2007), thus providing you with specific knowledge around Visual Studio Tools for Office (VSTO) - a component technology within Visual Studio 2008 that enables you to build Office solutions, the MOSS 2007 BDC and the integration with Web services, and more generically the use of Web services developed using PeopleTool within .NET and the Visual Studio IDE. &lt;br /&gt; &lt;br /&gt;I hope you enjoy the kit, and if you're looking for something on SAP integration, check out the OBA Sample Application Kit for SAP: &lt;a href="http://code.msdn.microsoft.com/obapsftsak/Wiki/View.aspx?title=http%3a%2f%2fcode.msdn.microsoft.com%2fobasapsak&amp;amp;referringTitle=Home"&gt;http://code.msdn.microsoft.com/obasapsak&lt;/a&gt;.&lt;br /&gt; &lt;br /&gt;Steve&lt;br /&gt;
&lt;/div&gt;</description><author>Steve_Fox</author><pubDate>Fri, 28 Mar 2008 13:16:32 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: Home 20080328P</guid></item><item><title>CREATED RELEASE: OBA Sample Application Kit for PeopleSoft, v. 1.0 (Mar 27, 2008)</title><link>http://code.msdn.microsoft.com/obapsftsak/Release/ProjectReleases.aspx?ReleaseId=739</link><description>In this release, you&amp;#39;ll find four major deliverables--each of which is intended to help the developer understand how they can programmatically integrate PeopleSoft with Microsoft Office technologies and applications. Specifically, you&amp;#39;ll find&amp;#58; &lt;br /&gt;&lt;br /&gt;1. A technical whitepaper that provides an overview of the sample application kit.&lt;br /&gt;2. An installation guide, which walks you through how to recreate the environment.&lt;br /&gt;3. A walkthrough document, which takes you through the end-user experience of the solution in the kit.&lt;br /&gt;4. Some sample code to get you started--at least for the client side bits &amp;#40;Outlook 2007&amp;#41;.&lt;br /&gt;&lt;br /&gt;Note&amp;#58; These are early drafts of the documents &amp;#40;as of 03&amp;#47;30&amp;#47;08&amp;#41;, so there may be future iterations on these. </description><author></author><pubDate>Thu, 27 Mar 2008 20:43:06 GMT</pubDate><guid isPermaLink="false">CREATED RELEASE: OBA Sample Application Kit for PeopleSoft, v. 1.0 (Mar 27, 2008) 20080327P</guid></item></channel></rss>