This community PowerShell module created by MVP Ryan Andorfer will give you the ability to interact with Orchestrator Web Service trough PowerShell. Here is full description from the author:
A set of PowerShell cmdlets for interacting with the System Center 2012 Orchestrator web service, complete with help documentation. Supports invoking runbooks with parameters and the parameters can have html characters! This PowerShell Library contains the following functions
You can download the PowerShell module from TechNet Gallery.
The overall architecture of Service Provider Foundation is very simple. SPF have two components Web Service and Database. As the database is SQL database it can be made highly available by making SQL Cluster and putting the database there. There is no information if SQL Always On is supported but the SPF database is not a complex one and Always On should be an option. After all SPF is part of Orchestrator and Orchestrator is supported on SQL Always On. But let’s talk about how to make the Web Service highly available and scalable. The Web Service is a static application which is front for the database. So it should be easy to install to install more than one instance of the web service and just put NLB to combine them. But lets test it.
I will not show you how to install SPF as there is a great guide by Marc van Eijk here. Lets say I have 3 servers:
I’ve already installed SQL Server 2012 SP1 on SPF01. Installed SPF in SPF01 and for the SPF database I’ve used the SQL on SPF01. I’ve installed the database and SPF on the same server just because it is home lab and I didn’t want to create another server.
Next step is to populate some data in SPF in order to have some information before deploying the second SPF server. I’ve added a VMM server and associated it with Stamp. You can see that information directly in the database.
Now lets install SPF on SPF02. I’ve installed all prerequisites so I am ready to go.
For database server I am pointing SPF01 where we have SPF database already deployed.
Next Next Next
And we push Install. Installation is started.
As we are at the step of deploying the database we see message: UpdateDatabase instead of CreateDatabase.
After successful install we can query the database to see if our records are still there.
As we can see all the records are there as we left them.
Let’s add another server and another stamp from SPF02
No errors during adding. Records also show in the database.
Lets see if the records are visible from SPF01.
Both SPF01 and SPF02 are working ok.
Installing more than one SPF Web Service servers is supported scenario just not well documented.
The rest is to configure IIS and NLB the right way. There are some challenges that could be met there.