What is the licensing story with on-premises SF deployment?
Will it included with a Windows Server license?
The Service Fabric standalone installer for Windows Server is currently in preview and thus not supported for production deployments. At this point, there is no plan to charge a license fee for the installer when it GAs but that is subject to change.
Related
Since I struggle to install the Hyperledger Fabric and Composer development environments locally on my Windows 10 machine I would like to know if it's possible to deploy a .bna file imported from the online Playground to the IBM Cloud or if I need the entire local installation.
I didn't find recent information about this but it appears that it was not possible on february 2017 but it may have changed.
If you have a IBM bluemix account, you can follow this instruction:
Deploying Hyperledger Composer Business Network to IBM Blockchain Platform Enterprise Plan on IBM Cloud. https://ibm-blockchain.github.io/platform-deployment/
a .bna file can only be deployed on a 'running' hyperledger-composer, may it be local or the online playground.
if you want to us it locally, here are the complete installation steps(with prerequisites).
after that, you can deploy your exported .bna file locally.
If you want to deploy it locally, then you have no option but to do all the above installations!
Hope this helps you!
I am planning to deploy Odoo Community POS for my electronics store. I want this installation to be done on on-premises and in the cloud. Like my store operators can use the software on both offline/ online modes depending on the availability of the internet connection. While doing operations offline, I want the data to be auto-synced on the availability of internet. In the start, I will be having a standard Odoo Community version installation but I might build some features and add custom models too.
Which deployment option will suit me more? http://www.odoo.com/documentation/10.0/setup/install.html#setup-install-source
Is there any possibility to have an Odoo Community edition hybrid deployment (on-premises and cloud at the same time).
Is this possible to make database auto-sync for both on-premises and cloud databases?
At work, I'm in the process of installing Windows Azure Pack: Web Sites in a VMWare ESXi lab environment. I have little available RAM and hard drive space on the ESXi.
I originally thought I would be able to do this without spending too much resources. The Azure Pack Express variant is advertised as if it only requires one machine with 8 GBs of RAM. However, after completing the first installation, I discovered that the Azure Pack: Web Sites extension requires no less than 7 different server roles installed on 7 different machines, each with Windows Server 2012 R2. I need a separate Cloud Controller, Cloud Management Server, Cloud Front End, Cloud Publisher, Cloud Shared Web Worker, Cloud Reserved Web Worker and Cloud File Server.
I have no way of freeing up that much resources. In the installation guide for Windows Azure Pack, they "advice" me to use separate VMs for each role, but they don't say explicitly that it won't work. Is it because multiple server roles on one machine will strain resources, or is it because the roles are incompatible and will make the system malfunction? In my case, the Azure Pack will only be used for penetration testing by a single user, so I imagine resources should not be a problem.
I'm not a web administrator, and I'm in over my head on this task. If anyone could give me some advice before I proceed on this, that would be much appreciated.
TLDR: Will there be a critical conflict if I install seven server roles on one machine, or will there just be a strain of resources?
If I were to setup IBM Bluemix local, what are the operating systems that can support the Bluemix software?
Been trying to look for answers in the internet but always end up frustrated because I can't find any answer. Even Bluemix site did not mention what is the OS requirement in setting up Bluemix.
Bluemix Local is not a software product that you can install in your own operating system. It runs in your environment but it is still a subscription.
The Bluemix Local install is only performed by IBM and it is an automated deployment of many virtual servers. It is also a managed offering, meaning that you don't have access to the operating system on those virtual machines. All the maintenance tasks are executed by IBM through a secure connection and a mechanism called Relay.
I guess you probably saw this link before, but the infrastructure requirements are described here: https://console.ng.bluemix.net/docs/local/index.html#localinfra
I think you may need Bluemix Support team to help you build the Bluemix local environment, Bluemix local is a cloud platform as a service that need to build on your infrastructure as a service.
What is the difference between "App fabric workflow service" and "Workflow manager 1.0"
Both used to host workflows. For me workflow manager looks good because it is scalable, we can create workflow hosting farm using multiple servers.
will "Workflow manager" replace "appfabric workflow"? for new project what to select?
This is a tough one.
AppFabric Workflow Services (actually WCF workflow services) are hosted in WorkflowServiceHost, but to be honest, we can see that AppFabric workflow hosting is not really evolving much. Especially in combination with BizTalk tools (adapter & mapper) through BizTalk AppFabric connect, it is nice to build some things.
Workflow Manager is the technology that was shipped with SharePoint Server 2013, together with Service Bus for Windows Server. To be honest, it is a V1, but this will probably be the technology that will be evolved (especially since SharePoint is the biggest customer of this technology ;))
The nice thing about Workflow Manager is that it is built to be cloud-ready (isolation, scalability, security...). You also have the concept of the Trusted Surface (http://msdn.microsoft.com/en-us/library/windowsazure/jj193509(v=azure.10).aspx) This allows you to sandbox customization.
So, my bet would be: if your product/platform is a long term thing, go for Workflow Manager, but live with the V1 concepts, or ignore the Trusted Surface sandboxing.
If you build it for shorter term, go for AppFabric still.
Hope this helps
Jurgen Willis (http://blogs.msdn.com/b/workflowteam/archive/2012/10/24/announcing-the-release-of-workflow-manager-1-0.aspx) when announcing Workflow Manager 1.0 answered this question.
A major difference between them is that the AppFabric (for Workflows) is supposed to be for hosting Workflow Services based on WorkflowServiceHost(WFSH). Meaning that the workflows in AppFabric are all services and expect to be invoked as services consuming and exposing WCF Soap Services.
But the Workflow Manager can host any type of Workflow including services. You can have workflows initiated that does not receive or send any messages, but only does DB transactions.
Some follow up I found.
App Fabric is going to be discontinued according to this:
http://blogs.msdn.com/b/appfabric/archive/2015/04/02/windows-server-appfabric-1-1-ends-support-4-2-2016.aspx
And Sharepoint Server 2016 relies on App Fabric:
https://redmondmag.com/articles/2015/05/12/sharepoint-2016-and-infopath.aspx
Workflow Manager 1.0 was shipped with Sharepoint Server 2013 as mentioned previously in this thread. Does that mean that Workflow Manager is also discontinued or will it come as a version 2.0 when Sharepoint Server 2016 is released? Any other information about where all this is going is very welcome.
The question:
will "Workflow manager" replace "appfabric workflow"? for new project
what to select?
still seems unanswered to me.
Windows Workflow Foundation is such a great and potent framework, and it is troublesome if you don't have an on premise host system like AppFabric you can rely on.
Sam Vanhoutte is right:
Cons of workflow manager is that it really is a a V1 product, the two main issues that I ran into when using it were:
Workflows hosted in Workflow Manager are expected to be declarative: adding your own custom code can be tricky, documentation is not extensive.
Workflow manager does not allow you to force persistence of a workflow state easily. There is some mention that delay activities will persist state, however, the Persist Activity is explicitly not supported. I have run into cases while building workflows where the same activity is executed multiple times because of a problem in the hosting environment configuration or because an exception in a custom code activity crashes the host instead of suspending the workflow as it does when using AppFabric.
If you have the time to put in to learn the platform and deal with V1 issues I would definitely choose workflow manager, if you have experience with hosting in AppFabric be prepared for significant differences.
Windows fabric or service fabric are the ones which are used to form service bus cluster ring. Service fabric is used in sb1.1 with tls1.2 support version. The previous versions use windows fabric.
App fabric is not used by workflow manager. It is used by sharepoint.