|
Prerequisites
Software Installation
As noted, the CCS has
two main capabilities, namely invitation of participants (and
accepting / rejecting the invitation), as well as configuration of
the infrastructure. The two respective tasks will be elaborated here
in more detail.
a)
Inviting Contractors
Though the CCS can principally be used to
generate custom invitations and according configuration information,
it is actually designed to receive information about the potential
providers to invite, as well as specific configuration information
from an external selector / discovery service (or in the case of
BREIN, from the VIM) using the “invite” function (see below).
The user has the option to select the most
suitable contractor out of the list of selected providers and
inspect the invitation details. He can then send the invitation to
the respective provider’s CCS.
The provider can inspect these invitations
anytime in his local CCS and accept or reject the invitation. By
accepting the invitation, the CCSes will trigger the configuration
process according to the workflow defined using the Windows Workflow
Foundation (see Defining and executing configurations).
Prerequisites
The Contract Commitment
Support needs Windows Server 2003 / XP or higher and the .NET
Framework 3.5 or higher.
Installation
The Contract Commitment
Support ships with its own installation file (see below) – however,
if the code is altered by the user, we generally recommend using the
Visual Studio environment (note that the express editions are free).
Nonetheless, all code can also be compiled from the command line
tool using MSBuild which ships with the .NET Framework:
MSBuild.exe ContractCommitmentSupport.sln
To install the CCS
using the setup tool, just execute
CCS_Setup.msi and follow the
instructions on the screen. The installer allows you to select
whether you want to install the client side, service provider side
or both CCS components.
Note that the client
side CCS will, by default, register itself at the URI
·
http://localhost:80/BREIN/CCSClient
whilst the service
provider side CCS will register at
·
http://localhost:80/BREIN/CCSSP
In addition, the CCS
exposes two workflows as web services, which are registered at
·
http://localhost/WWF/ServiceProviderConfigWFService
and
·
http://localhost/WWF/CustomerConfigWFService
respectively.
The Contract Commitment
Support is actually an application and not a standalone Web service
– accordingly, the application has to be started in order to make
the interface available over the Internet.
a)
Defining and executing configurations
In the current version of the CCS, configuration
workflows have to be compiled with the CCS in the form of a linked
library. In the long run, any Windows Workflow Foundation based
process compiled as a library can be dynamically selected for
execution. In order to change the configuration workflow in the
current version, the CCS source code has to be opened in Visual
Studio (2008 or higher) in order to adapt the respective workflow
(Customer or Service Provider side). Note that any interfaces can be
invoked and that cross CCS information can be exchanged, e.g. to
align the security setup. As the two workflows should be adjusted to
each other, it is however recommended to retain the overall workflow
and just deselect steps, respectively change the interfaces.
The respective files are called
ServiceProviderWF.cs (in project Service_ ProviderConfigurationWF)
and CustomerWF.cs (in project Customer_ ConfigurationWF)
respectively.
After (re)compilation, the CCS can be used as
before.
|
