Friday, April 26, 2013

Workflow Manager farm for SharePoint 2013 and nopCommerce: step by step installation and configuration

First at all we see what is the Workflow Manager farm on/with SharePoint Server 2013
(Only 10$/h or 10% market price I provide Full Business Software Solution: Mobile App and Web App)


The Workflow farm consists of two components: the Workflow Manager and a service bus that
facilitates the communication among components within the farm by using the Open Authentication
(OAuth protocol). The service bus is a messaging platform that has been running in Azure for some
time that now can run on on-premises servers. The Workflow Manager uses the service bus as its core
state management and messaging layer. All communication between SharePoint and the Workflow
Manager is message based using a well-defined contract for events and management operations
happening from SharePoint into the Workflow Manager using a series of Representational State
Transfer (REST) HTTP calls. Therefore, the service bus is used for reliable message delivery and a message
broker that also keeps the message state and workflow instance state consistent.


SharePoint 2013 contains a new component known as the Workflow Services Manager, which is the
integration layer between SharePoint and the Workflow Manager. The Workflow Services Manager
connects to other SharePoint services by using the Workflow Service Application Proxy and connects
to the Workflow Manager via the Workflow Manager Client. You can install the Workflow Manager
on the same servers as SharePoint, in which case the Workflow Manager Client is automatically
installed as part of the Workflow Manager installation, known as the colocated model. You can also
install Workflow Manager on servers that do not have SharePoint installed—the federated model—in
which case you will need to install separately the Workflow Manager Client on SharePoint servers
that are responding to web requests, so that they can communicate with the Workflow Manager. You
can build a federated workflow farm to achieve high availability by joining three servers to the farm
because they work like a mirror with a witness; that is, the servers need to achieve a quorum (you can
do this with just two servers).


The Workflow Services Manager contains a number of services:

■■ Deployment This service manages workflow definitions. This is the service that deploys
workflows you create in SharePoint Designer when you click the Publish command or when in
the browser you associate a workflow template in the browser with SharePoint components,
such as lists, libraries, content types, and sites.




■■ Messaging This service takes events, such as when properties of a document change, and
sends them as messages to the Workflow Manager. This Messaging service is also exposed to
Apps. This makes it possible for Apps to have custom messages; for example, you can define a
custom message from an external application that can be sent to a workflow and you can have
a workflow that subscribes to that message.
■■ Instance This service manages workflow instances. Therefore, it is this service that is used to
obtain workflow instance status information, or if you wish to terminate a workflow instance.
■■ Interop This service invokes SharePoint 2010 workflows.
The Workflow Manager farm uses new SharePoint REST endpoints to communicate back to the
SharePoint farm by using the App model API. Therefore, SharePoint 2013 workflows use the same set
of services as Apps to complete their tasks.

All communications with the workflow farm uses either the HTTP or HTTPS protocol. On servers
within the workflow farm, within Internet Information Server (IIS) Manager, you will see one application
pool, WorkflowMgmtPool, and one site, Workflow Management Site. A Workflow Manager
server also contains the following four Windows NT services:
■■ Workflow Manager Backend
■■ Service Bus Message Broker
■■ Service Bus Gateway
■■ Windows Fabric Host Service
When a workflow farm is created, six databases are created on an SQL Server:

■■ Workflow databases:
• WFManagementDB
• WFInstanceManagementDB
• WFResourceManagemetDB
■■ Service bus databases:
• SBManagementDB
• SbGatewayDatabase
• SBMessageContainer01



Please see more detail from book Exploring_Microsoft_SharePoint_2013

Please do the steps like below to install and configure Workflow Manager farm:

1. Download WorkflowManager.exe from go.microsoft.com/fwlink/?LinkID=252092
2. Click on the WorkflowManager.exe to setup by a Web Platform Installer 4.5

3. Workflow Manager 1.0

4.  Prerequisites of installing Workflow Manager

5. Installing the Workflow Manager

6.  Application Pools before setup Workflow Manager

7. Installing Microsoft Windows Fabric

8. After have an issues of download to setup, run WorkflowManager.exe setup file again and get the installing is completed

9. Choose Configure Workflow Manager with Default Settings (Recommended)

10. List of databases before run configuration Workflow Manager

11. Type Configure Service Account and test connect to an SQL Instance then click on right continue icon

12. Configuration for Workflow Manager information

13. Summary of Workflow Manager Configuration will apply

14. Created and Configured Service Bus farm, Service Bus getway and farm management datasbase

15. Configuration progress, and also complete

16. Workflow Manager 1.0, Service Bus 1.0, Excute ASP.NET iis Registration tool and Workflow Client 1.0  were successfully installed

17. Service Bus and Workflow database were created

18. WorkflowMgmtPool and Workflow Management Site

19. Install Windows Azure SDK, PowerShell, Cross-platform Command Line Tools and nopCommerce

20. Prerequisites for Installing Windows Azure SDK, PowerShell, Cross-platform Command Line Tools and nopCommerce

21. List of Software and components need for Installing Windows Azure SDK, PowerShell, Cross-platform Command Line Tools and nopCommerce

22. Installing SQL Server Express 2008 R2 Service Pack 2

23. Default nopCommerce configuration with IIS

24. Configure a new Web Site for nopCommerce

25. nopCommerce is successful installation with database name nopCommerce696, user name default696 and password

26. Store and Database information to installation nopCommerce

27.  List of supported languages by nopCommerce

28. Default HomePage of nopCommerce

29. Search function of nopCommerce

30. My account of nopCommerce

31. Contact Us of nopCommerce

32. Home page of Administration role of nopCommerce

33. My account - Customer info of nopCommerce for Administration role

34. My account - Change password

35. Contact Us of nopCommerce

36. Shopping cart

For more information about free and 100% open source code/design/developement document, please go to nopCommerce site at http://www.nopcommerce.com/featurelist.aspx

God bless us!

Thanks God and Thanks all!

Only 10$/h or 10% market price I provide full Business Software Solution: mobile app (iOS and Android), Intranet Portal by SharePoint Online or On-Premise, Business Web App, Business Workflow, Power Bi, E-Office, Document Management, Chat system, Customer Interaction Center, Dynamics AX, Dynamics 365.

Or very happy to join your team to develop Mobile App or Business Web App.

Thank you!


Phone: +60 115 199 2689 (also on WhatsApp, Viber, Zalo)
Email or Skype: ThomasTrungVo@Hotmail.com
Gmail: SharePointTaskMaster@Gmail.com
LinkedIn: https://www.linkedin.com/in/abc365/




2 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. I can't get from the above context that nopCommerce has anything to do with SharePoint 2013 and Workflow Manager. Are you talking about the integration among them or something else? There seems to have a missing link since I expect more from what is specified in this blog post title.

    Please kindly explain if possible, thanks a lot for the valuable info.!

    ReplyDelete