Introduction

The standard procedure for deploying the bpm”online "cloud" application is as follows:

1. Use the free trial registration page at bpmonline.com to create your trial bpm'online site. During the trial, you can familiarize yourself with the main features of the application. After the trial period is complete, the demo version can be transferred to the primary bpmonline site.
2. Contact a bpm'online sales manager to deploy a new application on the cloud or transfer an existing application to the bpm'online data center Bpm'online staff will perform the transfer.

When creating bpm'online cloud applications, certain limitations apply. Compliance with these requirements is critical for successful deployment.

Primary limitations

The use of SQL Agent is restricted

Tasks (Jobs) and other actions performed by SQL Agent cannot be created. The bpm'online task planner must be used instead.

The use of DB Mail is restricted

Email notifications must be sent via bpm'online platform features.

The use of Extended Stored Procedure is restricted

All logic must be implemented either through standard stored procedures on T-SQL, or through the use of the application server features.

The use of DBMS user names is restricted

Database users are not created within the DBMS on the bpm'online site. Domain users and domain authentication are used instead.

Modifications to Web.config are restricted

All required parameters must be stored as bpm'online system settings.

Binding to server and DBMS IP addresses is restricted

Server IP addresses may be changed. Therefore, any binding to any specific IP address will become invalid after such change. Always use domain names.

Installing additional software is restricted

No additional software can be installed on bpm'online servers.

Working with file system is restricted

Working with the application and DBMS server file system is restricted by OS access rights. Access to files is available through FTP and HTTP protocols.

Third-party applications cannot be run on server

Running third-party applications is restricted by OS access rights. All business logic must be implemented as part of the bpm'online application.

Database must be deployed on SQL Server 2016

To ensure compatibility with bpmonline site cloud infrastructure, the application database provided by customers must be created on SQL Server 2016.

The application must support both HTTP and HTTPS protocols

The use of logic that supports only one protocol is restricted. Instead, current application protocol must be defined.

The application must work with access rights of a regular user

The use of functions that require administrator access rights is restricted.

The application must work as a user without a profile

On the bpm'online site, the users are created without profiles or the ability to actually log in to OS.

Additional recommendations for partners

• Set the partner name as the "Maintainer" system setting.
• In the UsrPrefix system setting, specify a partner-specific prefix. For example, if the partner name is "FineSolution", the UsrPrefix could be "FS".
• The partner solution must not use replacing modules. Only schemas may be replaced.
• Server logic must be concentrated in C# classes and called where needed.
• The public API for server classes and client schemas must be covered by unit-tests.
• All required data, scripts, and libraries must be bound to packages.
• Development must be performed with the use of SVN and all packages must be committed to the repository.