Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Transcript of Outsystems Workshop
Provides all the logging and monitoring information for applications, integration adapters, web services, timer and all other application resources Service Center Life cycle management system Agile Platform is made up of the following components:
Platform Server Agile Platform The tool enables the modeling of Web 2.0 User Interfaces, Business Logic, Databases, Integration Components and Web Services, Security Rules and Scheduling activities. Service Studio 1- validates de eSpace OML file
2- creates a new version of the application in Metadata Database
3- takes the OML file and all its dependencies and generates a standard .NET or J2EE aplication
4- through the Deployment Service deploys the aplication onto Application Server
5-Updating the database model 1-Click-Publish Button
The visual model of an application assembled in Service Studio is stored as an OML (Outsystems Markup Language) file. Each one of these files is called an eSpace. Service Studio 1-Click Publish mechanism in action: Service Studio 2-Platform’s version control service
A developer decides to publish
He may receive notifications about what has been changed by others.
The information about what has changed is obtained directly from the central version control service – Server Environment
He merge and quickly combine everyone´s changes Extending the Platform and integration with other systems
Integration Studio is a desktop environment used to:
Integrate external applications
Integrate external databases
Extend the Agile Platform with extra functionality
Clients with Java, COM or .NET APIs can use Integration Studio's discovery wizards. Integration Studio 1- Integration Studio introspects the methods exported by the library of code
2- guides the developer in creating the methods signatures that will be visible for Service Studio developers.
A C# source wrapper file with the signatures is generated
3- The C# source wrapper file is compiles into code
4- The complete package (assembly) is published on the Platform
5-The assembly is stored in the Metadata Database
(An equivalent process is used for Java
environments (scenario B).) B - Java environment A - .NET environment Integration Studio The Web Application Server (WAS) - For .Net deployments the WAS is IIS. For Java deployments the WAS is JBOSS
Deployment Service - works in tandem with the Deployment Controller Service and
ensures that the compiled applications are installed and deployed on each Front-End Server.
Scheduler Service - Manages the timely execution of scheduled jobs resulting from the compilation of Timer
objects inside Service Studio.
Log Service - Provides extensive, asynchronous logging services to store performance and error audit events
generated by all running applications. 1- Front-end servers – A Platform Server installation can have several front-end servers Plataform Server 2- Deployment server
Compiles eSpace OML files
Generates the .NET or J2EE application code
generates the SQL Script to update and migrate the Runtime database
Deployment Controller Service
Invokes the OutSystems Compiler and database update script
coordinates the deployment of the generated application, across all front-end servers
Updates the runtime database Plataform Server 3- Database server
Stores all application data
The Platform uses the native session management services of the corresponding WAS stack (.Net or Java).
This is where the Agile Platform stores application versions, platform users, security configuration policies, etc
Contains the processed logs generated by the execution of all web applications supported by the Platform Typical virtual or physical machine allocation for 3 environments (in dashed lines). Development Environment
Quality Environment - Quality is used by Testers and Business Users.
Production Environment - read-only access accounts for development/maintenance teams to access analytics information on
performance and application errors The Platform Server can be configured with different physical architectures to cope with different scalability, performance, reliability, and security requirements. Development, Quality and Production environments The unified console for managing an infrastructure and its environments (Platform Servers), deployment of applications, IT users, and security across all infrastructure. LifeTime LifeTime gives:
full visibility of all applications across all environments in infrastructure
the exact version of each application running in Development, Quality Assurance, or Production environments
an instant snapshot of any application inconsistencies between environments
allows drill down and identify the exact details to correct LifeTime eSpace layers eSpace layers and Objects Users Database Database Services Database Database