Test and Deployment
In this section, you will learn how to test, deploy, and run your application on the platform.
Testing and Deploying an Application
The main steps involved in testing and deploying your application are:
- During development, the application is tested by launching its web interface, process, connector, or composite API in Test mode. In Test mode, the role concept is applied, but only the executing user gets test results. The executing user is the one with the Designer role.
- When launching a process, a process request is started. Use the Process Console for monitoring process requests. You can open the Process Console after launching the process, or via a process report.
- When you have updated the process or fixed errors, you can relaunch or edit it. You can restart it from the point of failure.
- As soon as your development test phase is over, you usually save your work by creating a new version of the project and running this version in Acceptance mode. In Acceptance mode, the role definition specifies which users are authorized to access the application.
- During the Acceptance phase, you collect feedback from the user tests. You can then include required fixes in the version currently running in Acceptance mode, or in a new project version.
- After completion of the Acceptance phase, you deploy the Acceptance version in Live mode.
- In Live mode, you can either fix issues on a copy of the Live version, or in the Live version itself by patching it. For patching the Live version, you set it to Test mode, change the included resources, and set it back to Live.
For details about testing, deploying and running an application, refer to:
- Version & Lifecycle Management
- Process Console
- Deployment in the Lifecycle Guide for the Advanced IDE
- Using Internal Parameters to control the execution mode and version in the Lifecycle Guide for the Advanced IDE
- Run in the Lifecycle Guide for the Advanced IDE
For details about monitoring the execution of an application, refer to:
- Monitoring and Debugging the Execution State of Process Requests
- Monitoring the Processing of Emails
As soon as you have created the web interface and process for the sample application, you can launch it in Test mode.
To test the web interface, proceed as follows:
- Open the Sample Expense Request project, go to Web Interfaces and launch the Expense Request web interface in Test mode by choosing Launch in the Actions menu. If you have already created different versions of the web interface, you can choose the version to be launched.
- Test all steps of the workflow implemented in the web interface.
- Check all screens implemented in the web interface.
- Check the notification emails that are sent.
To test the process, proceed as follows:
- Open the Sample Expense Request project, go to Processes and launch the Expense Request process in Test mode by choosing Launch in the Actions menu. If you have already created different versions of the process, you can choose the version to be launched.
- The Process Console helps you identify errors within the process.
To deploy the sample application, proceed as follows:
- Pick users the users involved in acceptance testing and assign them the required roles.
- Create a new version of the Sample Expense Request project according to your versioning policies.
- Include all relevant resources in the new version.
- Select the versions of included subprojects.
- Save the new project version.
- Select this version when launching a web interface or process. When launching the web interface or process, you can specify either Acceptance or Live mode for deployment.
Running an Application in Debug Mode
For details, refer to Running an application in Debug mode in the Lifecycle Guide for the Advanced IDE.