Here are the concepts and terminology you need to know to follow the tutorials.
Applications
You can deploy WSO2 ESB apps, WSO2 Data Services, Microservices, Jaggery apps, Java Web apps, and multiple other types of applications and services in WSO2 Integration Cloud.
For information about how to develop each application type and prepare them to be deployed in the Cloud, see App Development.
Runtimes
WSO2 Integration Cloud allows you to deploy multiple services in several different runtimes . If the runtime that you need is currently not available, you can request it from the WSO2 Cloud team. Go to the Integration Cloud and click the Support link at the top.
Cloud users
Users who register to WSO2 Cloud are automatically assigned to the tenant admin role of the organization that s/he creates. Tenant admins can invite other users to the Integration CloudUsers role or the admin role in the Cloud. Both the IntegrationCloudUsers and the admin roles have privileges to access all functions of the Cloud.
Architecture
The WSO2 Integration Cloud is developed according to a container-based architecture.
Environment variables
You can use environment variables to change an application's internal configuration without changing its source code. It is recommended to use environment variables to set the values of dynamic properties such as database connections details (e.g., database URL, username, and password), Log4j properties, system properties etc.
For more infromation on environment variables, see Use environment variables.
Transports
WSO2 Integration Cloud has backend support for most of the common WSO2 ESB transports, including the Virtual File System (VFS) transport and MailTo transport.
File InBound endpoints
An Inbound endpoint is a message entry point (source). Its behavior can be either polling or listening. It improves multi-tenancy and dynamic message source creation. The Integration Cloud has support for HTTP/S, and file Inbound endpoint types. For JMS, RabbitMQ, MQTT, Kafka, and custom Inbound endpoints, we recommend that you use custom Docker Images.
For more information, see Working with Inbound Endpoints.
Tags
You can add tags to an application as a key/value pair. Using tags, you can define metadata about the application such as the application creator, creation date, version etc.
Application privacy
By default, an application you create in WSO2 Integration Cloud is public and accessible via the Internet. In order to secure and limit access to your application, you can mark it private by opening the application and clicking its Settings menu.
For more information, see Change the application's privacy.
Container specifications
This defines the hardware specifications of the server in which you want your application to be deployed. The Integration Cloud provides pre-defined specifications with increasing amount of memory and CPU power.
When you select a specification for your runtime, it is recommended to select one that is above the requirements of your application to ensure that your application runs smoothly. You can also set runtime specifications for your application using the JAVA_OPTS environment variable, but that cannot override the container specification.