presented by proactive technology sharepoint 2013 workflow configuration instructor: kim ryan
Post on 28-Mar-2015
217 Views
Preview:
TRANSCRIPT
Presented by ProActive Technology
SharePoint 2013 Workflow ConfigurationInstructor: Kim Ryan
Resources
Workflow Resource Centerhttp://technet.microsoft.com/en-us/sharepoint/jj556245.aspx
Workflow Manager Farms (Series)http://www.harbar.net/articles/wfm1.aspx
General Overview
SP2010 (Legacy) Workflow Platform • Workflow Engine ran on
same SQL Server
• Nothing extra to do
SP2010 Workflow Engine still available in
SP2013
Installs automatically
General Overview
SP2013: • All workflows you
developed for SP2010 still work
• However separate Workflow Manager is available
• Has its own SQL Server databases & configuration
General Overview
TCP or Named Pipes
General Overview
SharePoint Server 2013
Workflow Platform
General Overview
Options in SP Designer
2013
Advantages
Why have separate Workflow engine?
• Built for high-density, multi-tenancy environments• Lets you scale workflow independently of SharePoint• Built for the Cloud• 2010 still necessary for backwards compatibility• 2010 has actions not in 2013• Coordination actions let you kick off 2010 WF from 2013• Can use both WF platforms• SharePoint is first “Customer” of Workflow Manager
Advantages
Additional Benefits:
• Fully declarative authoring
• REST and Service Bus messaging
• Elastic scalability
• Managed service reliability
General Overview
General Requirementshttp://technet.microsoft.com/en-us/library/jj193451.aspx
• IIS• .NET 4 PU3 or .NET 4.5• Service Bus 1.0• Workflow Client 1.0• Windows PowerShell 3.0• Workflow Manager’s hardware requirement = 2 cores, 2Gb RAM
Prerequisites
Other basic requirements:• SQL• Server • Accounts• Certificate
s
• High Availability• Firewall
Important Note: SharePoint 2013 Workflow platform is not supported in SharePoint Foundation 2013.
Prerequisites
2 Accounts:
• Setup User Account
• Run As Account
Prerequisites
Setup User Account (http://www.harbar.net/articles/wfm1.aspx and http://technet.microsoft.com/en-us/library/jj193451.aspx)
• Setup user (configuration user) is the account used to install and configure the Workflow Manager farm
• No need to create a dedicated user account
• Must be a domain account, which is a local machine administrator of servers on which you will install and configure Workflow Manager
• Must also be a Security Administrator and Database Creator on the SQL Server instance you will be using to host the Workflow Manager related databases
Prerequisites
Setup User Account
Keep in mind:
For security reasons, the Setup account cannot be used to create a workflow based on the SharePoint 2013 Workflow platform. If you try to create a workflow based on the SharePoint 2013 Workflow platform by using SharePoint Designer 2013, you receive a warning that the list of workflow actions do not exist, and the workflow is not created. From: http://technet.microsoft.com/en-us/library/jj658588.aspx
Prerequisites
Setup User Account
Another thing to keep in mind…
The user who deploys and runs a workflow must be added to the User Profile service. Check the User Profile service application page in Central Administration to confirm that the user you are using to validate workflow installation is in the User Profile service.
http://technet.microsoft.com/en-us/library/jj658588.aspx
Prerequisites
Run As User Account (http://www.harbar.net/articles/wfm1.aspx and http://technet.microsoft.com/en-us/library/jj193451.aspx)
• The RunAs User is the service account identity of the Workflow Manager services
• Must be a domain account
• Permissions are applied when you run Workflow Manager install
NOTE ABOUT ADMIN GROUP:
• Group that contains the principals whom will administer the Workflow Manager farm • By default this will be the built in Administrators group on each server in the farm. • If you wish to have more control across a three server farm, this should be (not must be) a Domain Group and contain
the user accounts needed.
Under no circumstances whatsoever is it necessary to add SharePoint Service Accounts into this group.
Helpful to note if troubleshoot is needed later:
.NET Framework 4 Platform Update 3 or .NET Framework 4.5
Service Bus 1.0 Workflow Client 1.0 PowerShell 3.0 Instance of SQL Server 2008 R2 SP1, SQL Server
Express 2008 R2 SP1, or SQL Server 2012. TCP/IP connections or named pipes must be
configured in SQL Server Windows Firewall must be enabled Ports 12290 and 12291 must be available.
Prerequisites
Central Certificate Requirements
If you select an existing certificate, make sure the certificate:
Has a subject name, subject alternative name, and both a private and public key
Is installed in the personal store of all computers in the farm or any computer that intends to join the farm
Is Valid in with respect to the start date, end date, trust chain Has AT_KeyExchange set Can be used as a server certificate Corresponding CRL list for signing authority is present
Prerequisites
High Availability
Workflow Manager farm supports a farm of a single computer running
both Workflow Manager farm and the required Service Bus farm. If you
require high availability you must expand the farm to three (3)
computers.
Two node farms cannot guarantee high availability.
Prerequisites
Installation
1. Download Web Platform Installer
http://www.microsoft.com/web/downloads/platform.aspx
Installation
1. Download Web Platform Installer
http://www.microsoft.com/web/downloads/platform.aspx
Installation
2. In Web Platform Installer, search for Workflow and install the Workflow Manager
Installation
Note: May want to install dependencies separately
Installation
Example: Windows Fabric
Installation
Run the wizard, and then return to WPI…
Installation
Install Workflow Manager, but do not configure
Installation
Workflow Manager installation completes…
Installation
3. Install Workflow Manager updates
• Go to Microsoft Download Center and check for Workflow Manager updates:
http://www.microsoft.com/en-us/download/default.aspx
NOTE – You can find cumulative updates in the WPI as well
Installation
Search for workflow. Sort results by most recent.
Installation
4. Install Workflow Client
In the end, you’ll have Workflow Manager, Workflow Client, Service Bus, and cumulative updates for any of these – Check Microsoft Download Center
Installation
5. Verify the install
Do you have everything?
Check add/remove programsCheck installed updates
Installation
Verify the install…
Installation
Verify the install…
Installation
Command Line Option….
SAMPLES: webpicmdline.exe /? Displays help webpicmdline.exe /List:[Installed|All|Available] /XML:http://sample.com/samplefeed.xml webpicmdline.exe /Products:ASP webpicmdline.exe /Products:ASP, SQLExpress webpicmdline.exe /Products:All /Feeds:http://feedstore.com/feed1.xml, http://feedstore.com/feed2.xml - install all products from the specified feeds webpicmdline.exe /Products:All /Language:FR - install all products available in French webpicmdline.exe /Products:MyCustomProduct /Feeds:http://feedstore/MyCustomFeed.xml /Language:RU - install a product from a custom feed, Russian installer webpicmdline.exe /Products:<Title> /Log:<LogPath> /XML:<FilePath> webpicmdline.exe /Applications:Dasblog webpicmdline.exe /Applications:Dasblog@Dasblog0.app> webpicmdline.exe /Applications:Dasblog@Dasblog0.app /Products:ASP /XML:C:\webpi\webproductlist.xml /Log:DasblogScrewTurnLog.txt
Installation
Command Line Option….
Configuration
6. Run Workflow Manager Configuration
• After you have Workflow Manager installed, Workflow Manager update, and Service Bus update (Service Bus gets installed with Workflow Manager) and have verified they are all there, you are ready to run the Workflow Configuration Manager.
From: http://www.harbar.net/articles/wfm2.aspx
Configuration
Note: Configuration
Wizard generates PowerShell to perform and
execute the install
6. Select Default Settings option
Configuration
8. Complete Farm Configuration
• Service Account (Run As user from earlier)
• HTTP - > Not recommended for Production
• Remember the key you choose for the certificate!
Configuration
Workflow Manager summarizes what will happen…
Note – You can click to open text
file with PowerShell commands
Configuration
POWERSHELL: # To be run in Workflow Manager PowerShell console that has both Workflow Manager and Service Bus installed. # Create new SB Farm$SBCertificateAutoGenerationKey = ConvertTo-SecureString -AsPlainText -Force -String '***** Replace with Service Bus Certificate Auto-generation key ******' -Verbose; New-SBFarm -SBFarmDBConnectionString 'Data Source=PASRVSQL2;Initial Catalog=SbManagementDB;Integrated Security=True;Encrypt=False' -InternalPortRangeStart 9000 -TcpPort 9354 -MessageBrokerPort 9356 -RunAsAccount 'PROACTIVE\sysSharePoint' -AdminGroup 'BUILTIN\Administrators' -GatewayDBConnectionString 'Data Source=PASRVSQL2;Initial Catalog=SbGatewayDatabase;Integrated Security=True;Encrypt=False' -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -MessageContainerDBConnectionString 'Data Source=PASRVSQL2;Initial Catalog=SBMessageContainer01;Integrated Security=True;Encrypt=False' -Verbose;
Configuration
# To be run in Workflow Manager PowerShell console that has both Workflow Manager and Service Bus installed. # Create new WF Farm$WFCertAutoGenerationKey = ConvertTo-SecureString -AsPlainText -Force -String '***** Replace with Workflow Manager Certificate Auto-generation key ******' -Verbose; New-WFFarm -WFFarmDBConnectionString 'Data Source=PASRVSQL2;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False' -RunAsAccount 'PROACTIVE\sysSharePoint' -AdminGroup 'BUILTIN\Administrators' -HttpsPort 12290 -HttpPort 12291 -InstanceDBConnectionString 'Data Source=PASRVSQL2;Initial Catalog=WFInstanceManagementDB;Integrated Security=True;Encrypt=False' -ResourceDBConnectionString 'Data Source=PASRVSQL2;Initial Catalog=WFResourceManagementDB;Integrated Security=True;Encrypt=False' -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose; # Add SB Host$SBRunAsPassword = ConvertTo-SecureString -AsPlainText -Force -String '***** Replace with RunAs Password for Service Bus ******' -Verbose; Add-SBHost -SBFarmDBConnectionString 'Data Source=PASRVSQL2;Initial Catalog=SbManagementDB;Integrated Security=True;Encrypt=False' -RunAsPassword $SBRunAsPassword -EnableFirewallRules $true -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -Verbose;
Configuration Try{ # Create new SB Namespace New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'PROACTIVE\sysSharePoint','Administrator1532@PROACTIVE' -Verbose; Start-Sleep -s 90}Catch [system.InvalidOperationException]{} # Get SB Client Configuration$SBClientConfiguration = Get-SBClientConfiguration -Namespaces 'WorkflowDefaultNamespace' -Verbose; # Add WF Host$WFRunAsPassword = ConvertTo-SecureString -AsPlainText -Force -String '***** Replace with RunAs Password for Workflow Manager ******' -Verbose; Add-WFHost -WFFarmDBConnectionString 'Data Source=PASRVSQL2;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False' -RunAsPassword $WFRunAsPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -EnableHttpPort -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
Configuration
Workflow Manager Configuration Wizard progress….
Configuration
Workflow Manager Configuration Wizard finishes….
Notice option to view Log
Configuration
Example Log
Configuration
9. Check Workflow Manager Status with PowerShell
Import-Module WorkflowManagerGet-WFFarmGet-WFFarmStatus
Run PowerShell as Admin (always!)
Configuration
10. Note HTTPS Endpoint
https://PASRVSP2.Pa-Tech.com:12290
Configuration
11. Test HTTPS EndpointYou will receive a certificate error.
This is OK.
Configuration
12. Export the Certificate
1. Click the Certificate Error icon to the right of the Address Bar
2. Click View Certificates3. Click the Details tab 4. Click the Copy to File… button 5. On the Welcome to the Certificate Export Wizard
page, click Next 6. On the Export File Format page, click Next 7. In the File name text box enter c:\wfm.cer and click
Next 8. Click Finish, followed by OK twice http://www.harbar.net/articles/wfm2.aspx
Configuration
13. Create a Trust
Configuration
IMPORTANT: Watch out with this cmdlet. If the certificate file doesn’t exist it will still create a trust! Watch the output for any errors. If there are some, you will need to delete the trust before running New-SPTrustedRootAuthority again after resolving the problem.
Configuration
14. Register Workflow Service Connection
Register-SPWorkflowService -SPSite "https://intranet.pa-tech.com" -WorkflowHostUri "https://pasrvsp2.pa-tech.com:12290" Note: You CAN register the HTTP (non-Production environments) Register-SPWorkflowService -SPSite "http://pasrvsp2" -WorkflowHostUri "http://pasrvsp2.pa-tech.com:12291"
CAUTION: Watch out with this cmdlet. If this command fails the Service Application Proxy will still be created, but it will be effectively broken. Monitor the output for any errors. If
necessary, clean up the connection and re-run Register-SPWorkflowService after resolving the problem.
Configuration
15. Check Central Administration
Configuration
15. Check Central Administration
Configuration
16. FINAL STEP: Check SharePoint Designer 2013
If you see this, you’re good to
go!
© 2013 ProActive Technology, LLC
The ProActive SharePoint Team sincerely thanks you for attending this
presentation.
Thank You!
top related