InfoPath and ASP.NET Development Considerations

This month at the K2 user group we did a presentation on understand the differences between InfoPath and ASP.net. This decision has been a pretty heavily debated thing in my company, even outside the scope of K2. InfoPath 2003 was pretty good but the licensing issues around it being installed on every client machine became challenging given it was part of MS Office Enterprise. Then with InfoPath 2007 they now allow for the forms to be web enabled however there are several limitations around them.

I believe InfoPath is a very strong tool which when used for the right scenario is better than ASP.net. However ASP.net allows for full control and more complex applications. NOTE that I say "applications". InfoPath itself is a "forms" product that when used with product like K2 blackpearl "applications" can be built. Using InfoPath and K2 blackpearl (or K2 blackpoint) now make development of InfoPath bearable. Then next challenge is to understand the user interface requirements and business rules that need to be implemented. Typically if the application is going to require tons of CRUD operations, grids and dynamic user interfaces InfoPath will fall flat. However if the application is just presenting some information, with some light weight CRUD operations using K2 SmartObjects, using SharePoint/InfoPath can make really strong solutions.

Here are the bullets from the presentation.

Selection Criteria:

• Worker skill set
• System integration
• Time to production
• User interface requirements
• Need to integrate with SharePoint
• Business logic & code
• Deployment

InfoPath Pros:

• Improvements over 2003 (browser option, actions are handled outside of the form, multiple form templates & views can be used).
• Quick to develop and deploy, based on XML. When I say quick; we me quick. The level of effort to create InfoPath form is significantly smaller and a wider span of designers can now build them.
• Easy to hook into most Web services.
• Disconnected / Offline use.
• InfoPath does force developers to write pretty decoupled applications in that much of the user interface rules will be captured in InfoPath and all business logic will be pushed to a business/service layer.

K2 InfoPath Pros:

• K2 allows for true business processes to be built around InfoPath instead of embedding the logic in .Net managed code, script or SharePoint server events.
• XML captured becomes part of the process and is accessible through the K2 Object/Context browsers. There is no need to build up functionality to get data and use it within the K2 process. However almost all of that has been alleviated with K2 SmartObjects.
• K2 SmartObject integration with the InfoPath form itself.
• InfoPath forms become part of the K2 project.
• Can be used in server events for XML storage.

InfoPath Cons:

• If using the InfoPath client, it must be installed on every user's computer that will participate in the workflow.
• Browser-based forms, cannot use the full set of controls that are available in the InfoPath client application (InfoPath 2007 features that are unavailable in InfoPath Forms Services and Web browser compatibility in InfoPath Forms Services).
• Browser-based forms require MOSS enterprise licensing. Just trying to use Form Services with WSS is not any cheaper from a cost perspective.
• Browser-based forms are difficult to configure for non-AD authentication (FBA).
• Browser-based forms are hard to control number of postbacks browser-based forms make to server. Things like using AJAX and Flash are not supported.
• Fully-trusted forms, difficult barrier in some environments.
• Debugging and troubleshooting is limited, can be difficult for web enabled forms.
• Hard to control look and feel, and state of controls (enabled / disabled). This is even more challenging with web enabled forms. It is very hard to make it follow corporate branding requirements when published over a public internet site.
• Event model for InfoPath is based on the XML document, not the user interface. This requires a different way of thinking when using custom code.
• Controls bound to secondary data sources can't be easily validated (InfoPath limitation).
• Little support for handling multiple languages via resource files.
• Can only be used with an InfoPath Integrated process -- can't use with a SharePoint integrated process.
• Kerberos issue still not fixed with MOSS SP1 (MS hotfix reference: KB941470 - more detail information).

K2 InfoPath Cons:

• Highly complex browser-enabled forms (lots of data connections, code behind, larger in size) may fail to convert when deployed.
• File attachments can make the form huge and cause the size of the K2 database to grow significantly.
• If you have to go into code you probably should avoid InfoPath unless you're really comfortable – forms with code not officially supported in K2 (read this for help).
• Form file left in SharePoint library (can be changed in Advanced Mode but only for client forms -- browser-enabled forms will always remain in the library).

ASP.NET Pros:

• Flexibility.
• Standard ASP.Net + Workflow.Client and SmartObject.Client namespaces, typically.
• Better control of session state for large forms or attachments.
• No Licensing considerations other than Windows Server.
• Standard debugging.
• Outside of the K2 project.

ASP.NET Cons:

• Longer development cycles.
• Custom code means more complex maintenance and management of projects.
• Outside the scope of K2 project -- must be deployed separately and kept in synch with K2 project.
• Can't be used with SharePoint integrated workflows.

InfoPath Design Considerations

• Do you need managed code? If you have lots of it, use ASP.net.
• Use ASP.NET pages for wider audience and then use InfoPath form back office business processes. It is possible in K2 to have processes that using both InfoPath and ASP.net client events.
• How many views do you need?
• Having lots of fields in a view is not a problem unless every field has a validation and conditional logic rule.
• Store data in the InfoPath form?
• Do not pollute your main data source.
• Working with required fields across views?
• Chaining multiple InfoPath forms into a single process.
• Understand Destination Plans and how XML is managed by K2?

Conclusions

Most of my K2 implementation to date has been successful InfoPath solutions. This all comes down to understanding the scope of the implementation and selecting the right tool. I know I am betraying my app dev roots when I say InfoPath is great because it is hard to get the level of control and customization you want with ASP.NET. The value proposition with InfoPath (with K2 blackpearl) is that it allows for very rapid application development and deployment with a large base of developers. Developers with a good MIS background can do this and do not require a CS background. InfoPath applications require less engineering and have a greater maintainability potential. However InfoPath forms just cannot handle complex business rules or multiple screen CRUD interfaces.

We do not that Microsoft is making a significant investment into InfoPath Forms Server in the next generation of SharePoint and MS Office. Like Excel Services, it is their first release of the technology. I am pretty confident the gap will be closed.

July 8th, 2008 User Group ASP vs InfoPath

Update 4/16/2009 - here is the recorded presentation

I will be supporting a round table discussion with the K2 User Group based in Texas on July 8th. I will be calling in J

If you want to attend in person, please contact Pattie Albright

Here is the information on the session:

Chris Geier & Mike Tally from K2 and Jason Apergis from RDA Corporation
will be doing a round table discussion on the differences, benefits, pros and cons of InfoPath and asp forms, when to use one or the other, and what works with the InfoPath client and what works with InfoPath in form services

Chris Geier will also be demonstrating a new offering from K2. K2 blackpoint is for SharePoint users that want the ability to build workflows and process-driven applications quickly – without code, without complexity.

With an easy-to-use Office-style designer, create powerful and flexible applications that increase the efficiency of your business.

K2 blackpoint, a subset of K2 blackpearl features, provides unparalleled capabilities and affordability. It also offers an upgrade path so that organizations can grow their investment and add complexity over time, if needed.
For more information, go to http://www.blackpoint.k2.com/.

Meeting Agenda: US Central Time
11-11:15 Networking/Refreshments
11:15-11:30 Announcements/Intros of New people
11:30-11:45 Tips & Tricks
11:45-12:45 Technical Presentation
12:45-1:00 Meeting Wrapup

For Virtual Attendees:

Note: please keep your phone on mute until you are ready to speak.

Audio Information

Telephone conferencing
Choose one of the following:

• Start Live Meeting client, and then in Voice & Video pane under Join Audio options, click Call Me. The conferencing service will call you at the number you specify. (Recommended)
  
• Use the information below to connect:
  Toll-free: +1 (888) 296-6500
  

  Toll: +1 (913) 227-1219
  

  Participant code: 224648
  

First Time Users:

To save time before the meeting, check your system to make sure it is ready to use Microsoft Office Live Meeting.
Troubleshooting
Unable to join the meeting? Follow these steps:

1. Copy this address and paste it into your web browser:
   https://www.livemeeting.com/cc/scna/join?id=4FM7QS&role=attend&pw=t%3A%3D2P%3BW
   
2. Copy and paste the required information:
   Meeting ID: 4FM7QS
   
   Entry Code: t:=2P;W
   
   Location: https://www119.livemeeting.com/cc/scna
   

BDC Crawl Missing Security Identifier

SOLUTION - We rebuild the SSP

Error: I ran across the interesting little error with the BDC which I did not expect. You may know that in the Share Service Provider (SSP) you need to give user permissions to the BDC. Well you may come across this error when you index a content source that is using the BDC:

The parameter is incorrect. (Could not create a security identifier for the identity 'XXX\YYY'. This identity may have been deleted.)

Symptoms: If you view the BDC content source crawl log there will be no errors however this error will be listed as an error in the Crawl Settings for search itself. This error will be created for every record that was indexed.

Cause: Well I found out that the user account in question had been deleted from Active Directory.

Resolution: To resolve the issue I had to remove the user account from the Business Data Catalog permissions as well as from all the BDC applications and entities permissions. Once I did that, run a full index, and everything will work.

Background: The first question I had was why are there no errors on the BDC content source? Knowing what I know about the BDC I suspect this is what occurred. First, there are connection errors to the BDC data source (SQL Server in this case); for instance there were no access issues to the database or the database objects that were being used in the Application Definition File (ADF). Second, knowing this I can only assume there is an error with the way the index is being built. Basically the error is in reference to the validation of Active Directory account that has permissions to the BDC application and its entities.

Deeper Dive: Digging a little deeper the following is the root of the issue. Many developers create an ADF using a tool or by hand and may not add an AccessControlList node. These nodes get added to the ADF when permissions are added in Central Administration. The AccessControlList can be added to both the LobSystem and Entity nodes.

The AccessControlList nodes must be added to the ADF prior to it being crawled. This is why if an administrator goes to Central Administration and gives a user or a group permission to the BDC, they must do a new full index of the BDC content source.

The following is an example the AccessControlList. In this example, account XXX\YYYY is being given full rights. This XML can be added to both the LobSystem and Entity node.

<AccessControlList>
  <AccessControlEntry Principal="XXX\YYYY">
    <Right BdcRight="Edit" />
    <Right BdcRight="Execute" />
    <Right BdcRight="SetPermissions" />
    <Right BdcRight="SelectableInClients" />
  </AccessControlEntry>
</AccessControlList>

Avoiding this Error: The error is occurring because the account XXX\YYYY does not exist in Active Directory account. It is recommend that permissions through a Active Directory group to minimize the occurrence of this error.

K2 blackpoint Questions and Answers

Here are some common questions that you may ask about K2 blackpoint.

Q: We already have blackpearl does blackpoint fit into the picture?

A: All the functionality in blackpoint will be rolled into blackpearl. Blackpoint is targeted toward organizations that want workflow beyond what SharePoint workflow can provide but may not need all the capabilities, such as Visual Studio and SmartObjects that blackpearl includes.

Q: Can I use blackpoint with WSS, Microsoft Forms Server and MOSS?

A: K2 blackpoint can be used with either Windows SharePoint Services v3 or Microsoft Office SharePoint Server. Microsoft Office Forms Server to provided for web-enabled InfoPath forms.

Q: Can I use SharePoint 2003?

A: SharePoint 2003 is not supported.

Q: Can I use blackpoint on a load balanced SharePoint farm?

A: Yes, K2 blackpoint can be used to provide workflow capabilities for any number of SharePoint web front-ends in a SharePoint farm.

Q: What servers in my SharePoint farm do I have to install this on?

A: The K2 blackpoint server components can be installed on a non-SharePoint server or on any of the SharePoint servers depending on how the farm is being scaled. On each SharePoint server, a set of web services is installed to facilitate communication between the SharePoint server and the K2 blackpoint server.

Q: Will I need administrative rights to install?

A: Yes, the install requires a user with local administrator rights on the server.

Q: Will this install anything on my SharePoint central administration site?

A: Yes, the K2 blackpoint install adds a tab to the Central administration site that provides access to administrative pages and tasks for managing the integration between K2 and SharePoint.

Q: Do you do solution or feature deployment?

A: Components such as our K2 web parts are deployed via solution deployment. Other components, such as our SmartObject creation capability are deployed as features and can be activated on a per site collection basis. K2 blackpoint processes are deployed to the K2 blackpoint server and do not reside directly on the SharePoint server.

Q: Can I extend the templates in K2 Studio?

A: No, existing templates in K2 Studio cannot be extended, but custom templates can be built and surfaced within the K2 Studio environment.

Q: Can I get to the code in K2 Studio?

A: No, code-level access is not available in K2 Studio.

Q: Do I have to use a process portal to manage my process?

A: Yes, K2 blackpoint makes use of Process Portals to provide access to all administrative and management tasks related to processes

Q: Microsoft says SharePoint has workflow, what does this do that it does not?

A: K2 blackpoint extends on the out-of-the-box SharePoint workflow capabilities by including a drag-and-drop Office-style process designer, functionality to manage all aspects of your SharePoint environment including lists, libraries and sites, a more in-depth set of reporting capabilities and improved task management capabilities such as delegation and redirection.

Q: Why wouldn't I just want to use built-in workflow in SharePoint?

A: SharePoint workflow provides basic process capabilities for managing documents and list items in SharePoint. However, more complex tasks, such as complex routing rules, escalations or managing lists, libraries and sites in SharePoint can be very difficult and in most cases requires a developer to write code to provide the functionality. K2 blackpoint provides all of these capabilities and more out of the box, without the need to write any code.

Q: Can't I do all this in SharePoint Designer?

A: No, many more complex tasks require a developer to write code to provide the same functionality that is included out of the box in K2 blackpoint. The K2 blackpoint comparison document compares features that are available in SharePoint Designer compared to K2 blackpoint.

Q: How does K2 blackpoint scale?

A: K2 blackpoint can be scaled to support multiple SharePoint servers. K2 blackpoint does not have to be installed no every SharePoint web front end of the farm, it is server unto itself. They can be clustered on their own dedicated resources, load-balanced, and be a highly available workflow environment.

Q: Can I upgrade to K2 blackpearl later?

A: Yes, when your workflow needs become more complex over time K2 provides the ability to easily upgrade to K2 blackpearl.

June K2 blackpoint Community Webcasts

K2 is providing some community web casts on K2 blackpoint. It is open to anyone. If you want to see it in action and ask some questions here is a place you can do it in. No upfront information needs to be provided. Just attend and check it out!

Tuesday June 17, 2008 11:00am-12:00PM CST (GMT-06)

Subject: blackpoint Webcast
Start Time: Tuesday, Jun 17, 2008 9:00 AM PDT
End Time: Tuesday, Jun 17, 2008 10:00 AM PDT
Attendee URL: https://www.livemeeting.com/cc/scna1/join?id=7CND7W&role=attend&pw=w%3B26H9%26Pd
Meeting ID: 7CND7W
Attendee Entry Code: w;26H9&Pd
Location: Live Meeting
Toll free: +1 (888) 233-7876
Toll: +1 (719) 234-7876
Participant code: 733479

June 19th meeting from 6pm – 7pm Central Time. (GMT -06)

Subject: blackpoint Webcast
Start Time: Thursday, Jun 19, 2008 4:00 PM PDT
End Time: Thursday, Jun 19, 2008 5:00 PM PDT
Attendee URL: https://www.livemeeting.com/cc/scna1/join?id=CK67B6&role=attend&pw=w%3B26H9%26Pd
Meeting ID: CK67B6
Attendee Entry Code: w;26H9&Pd
Location: Live Meeting
Toll free: +1 (888) 233-4650
Toll: +1 (719) 234-7876
Participant code: 733479

K2 blackpoint Released for SharePoint Workflow

K2 blackpoint has now been released. I have known about it but was told to keep quiet about it. Now it is out and I am extremely excited. I will make time soon to try out the beta bits that I have access to and get some information out there.

So what is K2 blackpoint? It is K2 response to providing workflow environment that power business and technical users can author workflows. It is skinned in a MS office look and feel environment. Check out the blackpoint website to get some more information. K2 blackpoint provides this perfect middle ground between K2 blackpearl and SharePoint Designer/WF workflows (comparing blackpearl to WF).

The deal is this. Building workflow in SharePoint Designer is flat out limited in scope and scalability. Building in WF requires a significant effort. Building in K2 blackpearl gets you past many of the challenges of WF however it still requires some effort and knowledge with Visual Studio. K2 blackpoint provides SharePoint users the ability to build workflows that can pretty much do anything with MOSS.

The cost of K2 blackpoint is awesome.

• $5,000 for 200 users
• $10,000 for 500 users
• $15,000 for unlimited
  

Pretty much a no brainer. I am so excited about this!

So what is the real difference between K2 blackpoint and blackpearl? I equate it to the difference between WSS 3.0 and MOSS. The comparison worksheet on blackpoint website spells it all out.

So what's in K2 blackpoint?

• A studio environment.
• Deployable on WSS 3.0 and MOSS.
• Many usability enhancements not available in Visual Studio.
• ALL of their SharePoint events (way more than what WF or SharePoint designer provide)
• InfoPath client events
• ASP.net client events
• Mail events
• Web Service events
• Process Portals (totally awesome)
• User specific task list
• Escalations, delegations
• SharePoint and workflow only SmartObjects (Workflow SmartObjects are all of the SmartObjects you get for free as part of the process definition. SharePoint SmartObjects allow you to get access to much of the data stored in SharePoint).
• New SharePoint Service Object with server side filtering and dynamic features
• ADO.net data provider for custom reports and ASP.net pages.
• Out of Office
• Extendibility
• Create custom event wizards
• Create your own reports
• Out of the box reports

So what's not in K2 blackpoint?

• Visual Studio integration (ok – had to say it)
• SmartObject Designer (You cannot create your own SmartObjects. You will have to build up or utilize existing services. The web services template or custom event wizards can be written to satisfy that. If you have data integration requirements, I would not discount want SmartObject bring to the table from the ability to create workflows in a rapid fashion.).
• K2 Workspace (this is a valuable tool and some of the functionality it provides is available by blackpoint)
• Custom report design tool that is in the K2 Workspace
• SmartForms
• SmartFunctions
• Simulation
• Code editing (Reality as workflows get complicated it is very hard to avoid writing custom code. With K2 blackpoint you are forced to create custom event wizards to implement custom code. I would not cheat and implement custom code in a web service just so you can call it from a blackpoint. As well, there are times you need to have custom code events that work with process and activity instance data. Now there is more effort to do custom code and the this should be a consideration of the scalability of the process.).
• K2 connect

I will be working up some things soon on K2 blackpoint…

Deploy Reporting Services (SSRS) Solution

Background

I needed to deploy some SSRS reports for an application we are writing and I wanted to make sure the entire application is deployable through build scripts. When working with SSRS reports I know many get accustomed to deploying using Visual Studio and that is just not an acceptable method for a production deployment. I did some research and with the help of my colleague Ray Barley I was able to the following.

The solution I have is based off the RS Utility for Reporting Services. Go here to get some good background
on it. As well, all of the code is based off of these sample scripts.

My scenario is simple I need to create a folder, then create a shared data connection and then deploy five reports. The challenge I ran into was how to deploy the .rds data connection file that in Visual Studio because I had become accustomed to that being deployed for me. We could not find anything at the moment that would deploy the file however the RS Utility allows for one to be created on the fly.

The way this works is some VB.net code is written that will call the Reporting Services web service to complete the operations that I need. The VB.net code is placed into a .rss file which can be called via command line. What we did is create three .rss files for each of the major operations we need to complete and then created a little master .cmd file that drives the whole deployment. This should be pretty re-usable for future projects.

Deploy Folder

The following code will create a folder in Reporting Services and is in a file named deploy_folder.rss.

'
' Deploy SSRS Folder
'
' Sample Command Line:
' 
' rs -i deploy_report.rss 
'    -s http://<server>/reportserver
'    -v FOLDER="Test Deploy"
'
' FOLDER name of the folder
'

Dim parentFolder As String = "AdventureWorks Sample Reports"

Public Sub Main()

    rs.Credentials = System.Net.CredentialCache.DefaultCredentials

    'Create the parent folder
    Try
        rs.CreateFolder(FOLDER, "/", Nothing)
        Console.WriteLine("Parent folder {0} created successfully", FOLDER)
    Catch e As Exception
        Console.WriteLine(e.Message)
    End Try

End Sub

Deploy Data Source Integrated
Here is the code to deploy a data source that is using Windows Integrated Security and is in a file called deploy_datasource_integrated.rss.

'
' Deploy SSRS DataSource Integrated
'
' Sample Command Line:
' 
' rs -i deploy_datasource.rss 
'    -s http://<server>/reportserver
'    -v EXTENSION="SQL"
'    -v CONN="Data Source=localhost;Initial Catalog=operationsdatamart;Connect Timeout=60"
'    -v NAME="OperationsDataMart"
'    -v FOLDER="/dev/Data Sources"
'
' CONN is the connection string
'
' FOLDER is the folder name to deploy to on the report server; it must already exist
'

Dim definition As [Byte]() = Nothing
Dim warnings As Warning() = Nothing

Public Sub Main()

  Try
    Dim definition As New DataSourceDefinition()
    definition.CredentialRetrieval = CredentialRetrievalEnum.Integrated
    definition.ConnectString = CONN
    definition.Enabled = True
    definition.EnabledSpecified = True
    definition.Extension = EXTENSION
    definition.ImpersonateUser = False
    definition.ImpersonateUserSpecified = True
    definition.Prompt = Nothing
    definition.WindowsCredentials = False

    rs.CreateDataSource(NAME, FOLDER, True, definition, Nothing)
    Console.WriteLine("Data source {0} created successfully", NAME)

  Catch e As Exception
    Console.WriteLine(e.Message)
  End Try
End Sub 

Deploy Data Source Stored

The following code is for doing a deployment of a datasource where the credentials are stored. This will support using a Windows or SQL Server account. The code is put in a file called deploy_datasource_stored.rss.

'
' Deploy SSRS DataSource Stored
'
' Sample Command Line:
' 
' rs -i deploy_datasource.rss 
'    -s http://<server>/reportserver
'    -v EXTENSION="SQL"
'    -v CONN="Data Source=localhost;Initial Catalog=operationsdatamart;Connect Timeout=60"
'    -v NAME="OperationsDataMart"
'    -v FOLDER="/dev/Data Sources"
'    -v ISWINDOWS=True/False
'    -v USER="CORPORATE\rbarley"
'    -v PASSWORD="**********"
'
' CONN is the connection string
'
' FOLDER is the folder name to deploy to on the report server; it must already exist
'

Dim definition As [Byte]() = Nothing
Dim warnings As Warning() = Nothing

Public Sub Main()

  Try
    Dim definition As New DataSourceDefinition()
    definition.CredentialRetrieval = CredentialRetrievalEnum.Store
    definition.ConnectString = CONN
    definition.Enabled = True
    definition.EnabledSpecified = True
    definition.Extension = EXTENSION
    definition.ImpersonateUser = False
    definition.ImpersonateUserSpecified = True
    definition.Prompt = Nothing
    definition.WindowsCredentials = ISWINDOWS
    definition.UserName = USER
    definition.Password = PASSWORD

    rs.CreateDataSource(NAME, FOLDER, True, definition, Nothing)
    Console.WriteLine("Data source {0} created successfully", NAME)

  Catch e As Exception
    Console.WriteLine(e.Message)
  End Try
End Sub 

Deploying a Report

Finally this is the code that will deploy a report. The code is in a file named deploy_folder.rss.

'
' Deploy SSRS Report
'
' Sample Command Line:
' 
' rs -i deploy_report.rss 
'    -s http://<server>/reportserver
'    -v PATH="C:\\Projects\\OperationsDataMart\\SSRS\\"
'    -v REPORT="WeeklyOperations"
'    -v FOLDER="/dev/WeeklyOperationsReports"
'
' PATH is the folder on the local hard drive where the report .rdl file exists.  You must use \\
'   for every backslash in the path; you must have a trailing backslash (to make this script
'   simpler)    
'
' REPORT is the file name of the report; do not include the .RDL extension
'
' FOLDER is the folder name to deploy to on the report server; it must already exist
'

Dim definition As [Byte]() = Nothing
Dim warnings As Warning() = Nothing

Public Sub Main()

    Try
        Dim stream As FileStream = File.OpenRead(PATH + REPORT + ".rdl")
        definition = New [Byte](stream.Length) {}
        stream.Read(definition, 0, CInt(stream.Length))
        stream.Close()

        warnings = rs.CreateReport(REPORT, FOLDER, True, definition, Nothing)

        If Not (warnings Is Nothing) Then
            Dim warning As Warning
            For Each warning In warnings
                Console.WriteLine(warning.Message)
            Next warning

        Else
            Console.WriteLine("Report: {0} published successfully with no warnings", REPORT)
        End If
    Catch e As IOException
        Console.WriteLine(e.Message)
    End Try
End Sub 

Running the Code

The following is a simple cmd file will create a folder, create a stored data connection using a windows account and upload five reports. Pretty simple.

set FOLDER=DemoReports

set SSRS_URL=http://localhost/reportserver

set DATA_SRC_NAME=DemoReportsConnection

set DB_CONNECTION=Data Source=localhost;Initial Catalog=Operations;Connect Timeout=60

set DB_EXTENSION=SQL

set DB_IS_WINDOWS_CONNECTION=True

set DB_USERNAME=CORPORATE\jason

set DB_PASSWORD=Pass@word1

set RDL_PATH=C:\\Demo\\Reports\\

rs -i deploy_folder.rss -s %SSRS_URL% -v FOLDER="%FOLDER%"

rs -i deploy_datasource_stored.rss -s %SSRS_URL% -v EXTENSION="%DB_EXTENSION%" -v CONN="%DB_CONNECTION%" -v NAME="%DATA_SRC_NAME%" -v FOLDER="/%FOLDER%" -v ISWINDOWS=%DB_IS_WINDOWS_CONNECTION% -v USER="%DB_USERNAME%" -v PASSWORD="%DB_PASSWORD%"

rs -i deploy_report.rss -s %SSRS_URL% -v PATH="%RDL_PATH%" -v FOLDER="/%FOLDER%" -v REPORT="DepartmentReport"

rs -i deploy_report.rss -s %SSRS_URL% -v PATH="%RDL_PATH%" -v FOLDER="/%FOLDER%" -v REPORT="ExecutiveReport"

rs -i deploy_report.rss -s %SSRS_URL% -v PATH="%RDL_PATH%" -v FOLDER="/%FOLDER%" -v REPORT="AccountingReport"

rs -i deploy_report.rss -s %SSRS_URL% -v PATH="%RDL_PATH%" -v FOLDER="/%FOLDER%" -v REPORT="FinanceReport"

rs -i deploy_report.rss -s %SSRS_URL% -v PATH="%RDL_PATH%" -v FOLDER="/%FOLDER%" -v REPORT="RollUpReport"