Integration with SharePoint 

Friday, January 28, 2011 12:47:00 PM

In our two previous posts we've shown you how to integrate the Budget In Brief application with the Team City, the Subversion, and the Office Live.

In this post we will show you how to integrate with Share Point in the Enterprise Environment.


Figure 1

The Budget In Brief application is configured on the Team City server, where it compiles the budget book; when the process is done, the book is checked back into the Share Point for users to review.

How to Setup the Environment  

The integration with the Share Point boils down to mapping the Document Library to the Network Drive and then to use XCOPY to copy the files around.

net use x: "https://someserver.com/somelibrary" password /user:domain\username

Note: The Budget In Brief application will work even with the mapped drive itself. However, we are doing the XCOPY to get the isolated snapshot of all data. 

Here is the example of the msbuild script where we map the library, then perform the file copy, then generate the book, and then copy the final document back to SharePoint.

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="BuildDBUnitTests" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="3.5">
<Import Project="$(MSBuildExtensionsPath)\ExtensionPack\MSBuild.ExtensionPack.tasks"/>
<Target Name="BuildDBUnitTests">
<Exec Command="net use N: &quot;https://someserver.com/ARI/ARI Use Cases&quot; password /user:domain\username"/>
<Exec Command="xcopy /EFRYI N:\ &quot;$(teamcity_build_checkoutDir)\ARI\Source&quot;"/>
<Exec Command="C:\BiB\bibc.exe &quot;$(teamcity_build_checkoutDir)\ARI&quot; &quot;$(teamcity_build_checkoutDir)\ARI\ARI_2_10.book&quot; /outputfolder &quot;$(teamcity_build_checkoutDir)\Draft&quot; /outputfile &quot;ARIUseCase&quot;"/>
<Exec Command="net use N: /Delete"/>
<Exec Command="net use N: &quot;https://someserver.com/Drafts&quot; password /user:domain\username"/>
<Exec Command="xcopy /FRY &quot;$(teamcity_build_checkoutDir)\Draft\ARIUseCase.docx&quot; &quot;N:\&quot;"/>
<Exec Command="net use N: /Delete"/>
</Target>
</Project>

That is the all the configuration that is needed.

Go to Team City and run the build as we did in the our prior blog.

Tips and Tricks

When mapping the SharePoint library, you can encounter the "System error 67 has occurred" error message, if your builder server is running on the Windows 2008 Server machine. In this case, most likely the WebClient service is not running on the server. If the service is installed, then just start it. 


Figure 2

If you can not find the service, then you need to install it.

To configure the WinClient service on the Windows 2008 Server you should install the Desktop Experience feature first.


Figure 3

When installation is done, then you can map SharePoint libraries.

Conclusion

Fully automated life cycle process run on the server: the data is stored in the Share Point; the user transparently contributes information into the Share Point Document Libraries; the Share Point ensures the safety of the valuable data and controls the access; the distributed build management and continuous integration server runs automated process; the Budget In Brief application creates the book; the Artifacts uploaded back to to the Share Point for review by the distinguished users. 

Share This Using Popular Bookmarking Services
Comments are closed on this post.

Site Map | Printable View | © 2008 - 2017 Budget In Brief | Powered by mojoPortal | HTML 5 | CSS | Design by styleshout