Web Server Configuration
From Business Process Management, BPM and Workflow Automation Wiki | BizAgi BPMS
<keywords content="keywords">
web server configuration, web server, configuration, configuring web server
</keywords>
|
Applies for the ENTERPRISE .NET and XPRESS editions |
Contents |
Web Server Configuration
The Web Server Configuration is set in the Configuration Tab in Bizagi Studio´s Standard Menu as shown below.
This configuration defines the type of Web server that will be used for the server: ASP NET or Internet Information Services.
For a project's implementation, <b>it is recommended to use IIS</b>.
The ASP NET server has some limitations, and it is mainly used for project demos.
Using IIS
To view further information about installing the IIS, please review this article: IIS Installation over Windows XP, Windows Server 2003, Windows Vista and 7, and Windows Server 2008.
In case it is not desired to install IIS, you can still run the application by using the ASP.NET Development Server which is already installed by Microsoft's .Net Framework 2.0 SP2.
IIS Installation considerations
If the IIS is installed after the creation of a project in Bizagi (you want to switch from ASP NET to IIS), then you still need to explicitally set the IIS as the Web server in your project's configuration.
This way when Bizagi updates that the project will work with IIS, Bizagi will automatically create the web application (the work portal) for the project at the IIS Default web site.
|
Alert: Keep in mind that if you install the IIS afterwards the Microsoft .Net 2.0 SP2 Framework, then it is likely that you need to register that framework in the IIS. To do this, you may use the aspnet_regiis -i command from the framework's path (by default at "C:\Windows\Microsoft.NET\Framework\v2.0.50727\") |
Using ASP NET
The ASP.NET Development Server is a web server that runs locally on Windows operating systems. It can only serve ASP.NET web pages on the local computer and server one web application at a time (if more than one project exists the web applications of this projects can not run at the same time).
Since this configuration is useful in a Development environment where only one user may be involved and running the web application locally, it has some restrictions. In order to avoid the restrictions, IIS would be required.
The ASP.NET Development Server includes an Advanced options check box that when selected shows the option to change the port number.
Once you execute the process from Bizagi Studio, you will notice the ASP NET server running in an icon at the task bar:
ASP.NET Use Restrictions
- Only to be used by one user on a local environment (it does not publish content for access from a remote browser); for example for product testing purposes or to show in a demo.
- It is not possible to use the SMTP service configured in the IIS; this means that if the web server if ASP.NET, for Bizagi to send e-mails messages (notifications), you will require an external SMTP server.
- It will not be possible to customize changes to the Work Portal while using ASP.NET web server.
- The testing options available for the Virtualization and Replication configuration in Bizagi Studio (as shown at: Test Provider and Test Virtual Entity) will not return a success message.
- The invocation to Bizagi's web services remotely (its SOA layer) would be restricted.
- ASP.Net web server is not available for 64-bit Bizagi Enterprise projects. Projects working with Bizagi in its 64-bits version, require IIS.
Related Articles
<comments />
