The Primary Application Container provides the runtime environment for Verj.io Applications, or to put it another way, it is the component that end users directly interact with.
It also powers your automated business logic and is functionally equivalent to the Verj.io On-Premises environment’s workflow component with the same Verj.io Version.
Applications
Requests from end users are internally routed through to the Service Plan's Application Containers, which respond as defined by the application.
New applications, and changes to existing applications, can be deployed to a Service Plan’s Application Filesystem via the Studio. Application Containers automatically load these updates, making them available to new end users.
Processes
New Workflow Processes and changes to existing Processes can be deployed to a Service Plan from the Studio. These updates are automatically loaded by the Primary Application Container and made available to all new Workflow Jobs.
Composition
All Service Plans come with one Primary Application Container.
The configuration of the Service Plan determines various attributes of the Primary Application Container, including the amount of memory available to it.
Troubleshooting
The Studio’s Visual Debugger can remotely connect to an Application Container and help troubleshoot your application.
Application and workflow logs can be viewed in the logging section of the Cloud Portal. Reports on the Application Containers' performance and resources can be generated in the Cloud Portal’s statistics page.
Controlling Primary Application Containers
The Primary Application Container can be restarted or stopped in the Service Plan details page of the Cloud Portal.