ProcessMIX Guide
  • Platform Overview
    • Introduction
    • Platform Purpose
    • Main Concepts
      • Organization Structure
      • Visual Language
      • Project Development Environment (IDE)
      • Deployment and Integration
      • Administration and Troubleshooting
    • First Steps
    • Change Log
      • 5.0.0
      • 5.0.5
      • 5.0.5.1
      • 5.0.5.2
      • 5.0.5.3
      • 5.0.5.4
  • Language Reference Guide
    • Overview
    • Data Structures and Types
      • Core Types (pdk.core)
      • Dictionary (pdk.asset.dictionary)
      • Scorecard (pdk.asset.scorecard)
      • Blockchain (pdk.blockchain)
      • Exceptions (pdk.ex)
      • Input/Output (pdk.io)
      • JSON Web Token (pdk.jwt)
      • Networking (pdk.net)
      • HTTP (pdk.net.http)
      • SOAP/Web Services (pdk.net.soap)
      • XML/DOM (pdk.net.xml)
      • S3 (pdk.s3)
      • SQL (pdk.sql)
      • Postgres (pdk.db.postgre)
      • Util (pdk.util)
      • Default Data Structure Field Values
    • Flows
      • Variables
        • Local Flow Variables
        • Node Variables
      • Flow Node Types
        • Core Nodes
          • In
          • Out
          • Assign
          • If
          • Switch
          • Iterator
          • Function Call
          • Subflow
          • Raise Exception
          • Exception Handler
          • Validator
        • Connector Nodes
          • Database Begin Transaction
          • Database Commit Transaction
          • Database Rollback Transaction
          • Database Query Executor
          • EVM Blockchain Functions
          • EVM Blockchain Smart Contract Functions
          • REST Service Executor
          • SOAP Service Executor
          • S3 Connector
          • SMB Connector
      • Expressions
      • Built-In Functions
        • Expression functions
          • pdk.util.Any
          • pdk.util.Array
          • pdk.util.Blockchain
          • pdk.util.Cast
          • pdk.util.Codec
          • pdk.util.Crypto
          • pdk.util.Date
          • pdk.util.File
          • pdk.util.Json
          • pdk.util.JWT
          • pdk.util.Map
          • pdk.util.Math
          • pdk.util.String
          • pdk.util.Util
        • Node functions
          • pdk.flow.Any
          • pdk.flow.Array
          • pdk.flow.File
          • pdk.flow.JsonArray
          • pdk.flow.JsonObject
          • pdk.flow.HttpRequest
          • pdk.flow.HttpResponse
          • pdk.flow.Logger
          • pdk.flow.Map
          • pdk.flow.Xml
            • pdk.flow.xml.XmlAttr
            • pdk.flow.xml.XmlElement
            • pdk.flow.xml.XmlNode
            • pdk.flow.xml.XmlDocument
            • pdk.flow.xml.XmlDocumentType
            • pdk.flow.xml.XmlDOMConfiguration
            • pdk.flow.xml.XmlDOMImplementation
            • pdk.flow.xml.XmlProcessingInstruction
            • pdk.flow.xml.XmlTypeInfo
            • pdk.flow.xml.XmlCharacterData
            • pdk.flow.xml.XmlText
            • pdk.flow.xml.XmlNamedNodeMap
          • pdk.node.BlockchainEth
          • pdk.node.S3
          • pdk.node.Smb
      • Exceptions
        • Checked Exceptions
        • Runtime Exceptions
    • Assets
      • Dictionary
      • Decision Table
      • Scorecard
      • PMML
    • Connectors
      • DB Connector
        • Prepared Query
        • Dynamic Query
        • Query input parameters
        • Stored Procedure
      • REST Connector
      • SOAP Connector
      • S3 Connector
      • SMB Connector
      • EVM Blockchain Connector
    • Global Variables
    • Appendices
      • Overview of Database Transactions
      • Reserved Words
  • Project Development Environment (IDE)
    • Project Explorer Panel
    • Flow Builder
    • Flow Node Editor
    • Data Structure Builder
    • Connector Builders
      • REST Connector Builder
      • SOAP Connector Builder
      • DB (Database) Connector Builder
      • EVM Blockchain Connectors Builder
      • S3 Connector Builder
    • Asset Builders
      • Dictionary Builder
      • Decision Table Builder
      • Scorecard Builder
      • PMML Asset Builder
    • Global Variables Panel
    • Expression Editor
    • Project Deployment and Execution
    • Cron Expression Generator
    • Test Helper
    • Debugging the Project
    • DB transactions
    • Team Collaboration Tools
      • Version Control
      • Conflict Resolver
    • Selectors
    • Error Panel
    • Local History
  • Home and Administration Guide
    • Organization and Subscription
    • Organization Team
    • Repositories and Projects
    • Environments
    • Deployments
    • Database Provisioning
    • Roles and Permissions
  • Logs and Troubleshooting
    • Request/Call Logs
    • Deployment Logs
    • Application Logs
  • Appendix: Example Project
    • Risk Mitigation Solution
Powered by GitBook
On this page
  • How to work with the Environment?
  • How to work with Deployments?
  • How to work with Internal databases?
  • How to work with Request logs?
  • How to work with Deploy logs?
  • How to work with Application logs?
  1. Home and Administration Guide

Environments

Environments — is the HOME section of the application, where you can access information about the available environments based on your subscription plan. You can view and manage your deployments, and

PreviousRepositories and ProjectsNextDeployments

Last updated 11 months ago

How to work with the Environment?

To go to the Environments section, click the Environments tab on the left top panel. Now you have access to the list of available Environments to work with.

Three types of environments are available in the app:

  1. Development. This type of environment can not be deleted. All IDE deployments can only be directed to this environment.

  2. Testing. Test environments often mirror the production environments but with some key differences. To simulate the production environment more accurately, for example, the testing environment may have different hardware and software configurations. This helps QA teams execute thorough functional, performance, and regression testing by mimicking real-world conditions. Additionally, it is possible to use other Kubernetes clusters; this feature is configured when deploying an application to your server before starting to use it. The system administrator responsible for deploying the application to servers can modify this feature. Testing is done before the software is deployed to the production environment to help find and fix any problems.

  3. Production. A software application’s deployment and use by end users occurs in a production environment. It is the real-world context where the software program operates.

At the top of the panel, you can see information about the environment, including:

  • Environment name.

  • Environment type.

  • Allocated slot number. These slots are allocated from the total pool of slots to all environments.

  • Free slots. These slots are available for creating new deployments.

While creating an organization, the Owner defines the number and types of environments needed. This section displays the previously created environments only. To add, rename, or delete an environment, go to the Organization settings section. For more information, see the Organization and Subscription Guide

The administrator and the owner can manage the environments from the settings page of the organization.

To work with a desired environment, click it.

To configure: rename, allocate slots, buy additional resources, go to the Organization settings section. For more information, see the Organization and Subscription Guide

How to work with Deployments?

How to deploy a project, view, and manage deployments, see the Deployments section guide.

Only the owner or administrator can manage deployments.

How to work with Internal databases?

How to view information on the available internal database, see the Database section guide.

Only the owner or administrator can manage the database.

How to work with Request logs?

Only the owner or administrator can view request logs.

How to work with Deploy logs?

Only the owner or administrator can view internal deploy logs.

How to work with Application logs?

Only the owner or administrator can view internal errors and warnings.

You can view according to the selected environment. For more information, see the Request logs guide.

You can view according to the selected environment. For more information, see the Deploy logs guide.

You can view according to the selected environment. For more information, see the Application logs guide.

Request logs
Deploy logs
Application logs