In my last Blog entry i showed an example for AMUSE using Embedded Devices. You can have a look here. Today i will give you some extra information.
It is also possible to start the executable which is deployed on the mobile device as standalone application/statemachine.
When starting the application (either on the mobile or on the pc), without using Enterprise Architect, the statemachine will be executed within the application.
Our Partner company from the UK Dunstan Thomas will be conducting a Webinar on “LieberLieber AMUSE” in collaboration with us.
Register now:
To register you interest for this webinar please email us with your name, company, telephone number and email address along with the title of the webinar you wish to register for. We’ll then send you login details for the webinar on the week prior to the event. Register your interest here.
Unavailable on the day?
As before for those of you unable to attend any of our webinars, don’t worry, all of our webinars are available for download from the Dunstan Thomas site.
.
Introduction
The goal of this entry is to show how a flight booking process with different web services and a mock-up GUI can be simulated and verified with AMUSE. The focus is on the orchestration of the web services, which are part of the flight booking process. In a next step it would be interesting to generate BEPEL out this state machine.
Today I want to show how we can use “Enterprise Architect” and the LieberLieber “Amuse” Plug-In to integrate “ASP.NET Mvc Web Application” into a flowchart.
Here you can see the final solution.
To download the video click here.
If you haven’t seen my previous posts please check out “LieberLieber AMUSE – Using Statemachines to Build Winforms flows” and “LieberLieber AMUSE – Using Statemachines and ASP.NET WebServices”.
Ok, first of all have a look at the Asp.net Mvc Solution.
As you can see I added an AuthenticationController (provides the controller methods), AuthenticationService (provides the authentication logic) and AuthenticationViewModel (provides the view model for the web form) to the solution.
Wir freuen uns, dass SparxSystems LieberLieber AMUSE geprüft hat uns in die 3rd Party Tool Liste aufgenommen hat! (und das sowohl auf der australischen als auch auf der deutschen Seite).
Somit ein weiterer Meilenstein in der LieberLieber AMUSE Erfolgsgeschichte!
Today I want to show how we can use Enterprise Architect and the Amuse Plug-In to integrate a “classic” ASP.net WebService (asmx) into a flowchart.
In this example I will use the project from my last example (“LieberLieber AMUSE – Using Statemachines to Build Winforms flows“) and extend this solution to use a ASP.NET-Authentication-WebService.
1. First we will add to the existing .NET solution a new project from the type “ASP.NET Web Service Application” and call it “AMUSEAuthenticationWebService”.
2. Change the name from “Service1.asmx” to “AuthenticationService.asmx”.
3. Now we add another project from type “Class Library” and call it “AMUSEAuthenticationLogic”.
4. Change the name of the class file from “Class1.cs” to “Authentication.cs”.
5. Copy now the “ValidateUser”-method from “AMUSEAuthenticationService”-project to the “AMUSEAuthenticationLogic”-project.
6. Now we build the solution and add the “AMUSEAuthenticationLogic.dll”, as reference, to the “AMUSEEAuthenticationWebService” project.
7. Now we can change the class name and method name from the “AuthenticationService.asmx.cs”:
Class name: AuthenticationService
Method name: ValidateUser(string username, password) and call the “ValidateUser” method from the “AMUSEAuthenticationLogic”
(weiterlesen…)
Today I want to show that you can use Enterprise Architect and the AMUSE – Add-In to integrate Windows Forms and existing Class Libraries and not only for embedded solutions.
In this example we are going to create a simple authentication workflow. Here you can see the final solution.
To download the video click here.
To download the project files click here.
First of all have a look at the 3 different Windows Forms and the class library.
I build one solution which contains 2 different projects. One project contains the Windows Forms and one contains the Authentication service.
