-
.Net
-
Backup
-
Data Storage Containers
-
Docker Containers
-
Environment Management
- Swap-Domains
- Clone Environment
- Create Environment
- Environment Aliases
- Environment Aliases
- Environment Migration between Regions
- Environment Regions
- Environment Transferring
- Environment Variable
- Environment Variables
- Environment Variables(Apache meaven, Memcached)
- Environment Variables(Go)
- Environment Variables(JAVA)
- Environment Variables(Load Balancer)
- Environment Variables(Node.js)
- Environment Variables(PHP)
- Environment Variables(Ruby)
- How to Migrate a WordPress Site to BitssCloud PaaS
- How to migrate my environments from another Jelastic provider?
- HTTP Headers
- Java VCS Deployment with Maven
- Setting Up Environment
- Share Environment
- Why is my environment in sleeping mode?
- Show all articles (9) Collapse Articles
-
Java
- Environment Variables - Java custom Environment Variables
- Java App server Configuration
- Java Options and Arguments
- Multiple Domains on Tomcat server
- Secure Java Encryption and Decryption
- Spring Boot Standalone and Clustered Java Applications with BitssCloud
- Timezone Data for Java/PHP App Server
- Tomcat HTTP to HTTPS redirect
- WildFly server
-
LiteSpeed Web Server
-
OOM Killer
-
Python
-
Reseller SetUp
-
Secure Socket Layer (SSL)
-
Troubleshooting
-
Account Management
-
CDN
-
Databases
- Database Configuration
- Database Connection Strings
- Database Hosting in BitssCloud
- Environment Variables(Database)
- Galera Cluster not working
- How to export/Import Database via Command line
- How to install MSSQL server on Linux (2017)
- MariaDB/MySQL Auto-Сlustering
- MongoDB Database Backups
- PostgreSQL Database Backups
- PostgreSQL Database Replication
- PostgreSQL Master-Slave Cluster
- Remote Access to PostgreSQL
- Schedule Backups for MySQL and MariaDB Databases
- Scheduling Databases Backups
-
Domain Name Management
- Container Redeploy
- Custom Domain Name
- DNS Hostnames for Direct Connection to Containers
- How to Bind Custom Domain via A Record
- How to Bind Custom Domain via CNAME
- Multiple Custom Domains on an Nginx Web Server
- Multiple Domains with Public IP
- Multiple Public IP Addresses for a Single Container
- Setup WordPress Multisite Network with Domain Mapping and CDN
-
Jenkins
-
Load Balancing
-
PHP
- Creating Environment for PHP
- Deploy PHP Project Via GIT SVN
- How to Check Change PHP Version in BitssCloud
- How to create environment for AngularJs/ReactJs
- How to Enable PHP Extensions
- How to Install Custom PHP Application
- Ion cube Loader
- MariaDB PHP connection
- MySQL PHP Connection
- NGINX PHP
- PHP App Server Configuration
- PHP Connection to MongoDB
- PHP security settings
- PHP Session Clustering
- PostgreSQL PHP Connection
- Running Multiple Domain Names on Apache Server
- Security configuration for Apache
- Zero Downtime (ZDT) Deployment for PHP
- Show all articles (3) Collapse Articles
-
Release Notes
-
Ruby
-
SSH
-
Wordpress
-
Application Management
-
Cluster
-
Deploying Projects
-
Elastic VPS
- CentOS VPS
- Elastic VPS configuratation
- Elastic VPS with full root access
- Installation of cPanel in BitssCloud
- Java Console Application with CentOS VPS
- Linux VPS Access via Public IP
- Linux VPS Access via SSH Gate
- Setting Mail Server Inside CentOS VPS
- Setting Mail Server Inside CentOS VPS
- SSH Access to VPS Gate
- Ubuntu VPS
- Ubuntu with CSF Firewall
-
High Availability
-
Jitsi
-
Node.js
-
Pricing System
-
Request Handling
-
Scaling
- Application Server with horizontal scaling
- Automatic Horizontal Scaling
- Automatic Horizontal Scaling: Multi Nodes
- Automatic Vertical Scaling
- Database Horizontal Scaling
- Docker Containers Horizontal Scaling
- Horizontal Scaling
- Load Balancer with horizontal scaling
- Memcached horizontal scaling
- Storage Container
- VPS Horizontal Scaling
-
Traffic Distributor
-
General
- Apache & NGINX Modules
- BitssCloud Dashboard Guide
- Build and Deploy Hooks
- Cron Job scheduler
- FFMPEG Setup
- File Synchronization
- FTP Overview
- FTP/FTPS Support in BitssCloud
- How to Deploy Magento into BitssCloud PHP Cloud
- How to Enable Expert Mode in JCA
- How to open a support ticket to BitssCloud
- Installation of FTP
- Kubernetes Cluster
- MarketPlace
- Reduce Cloud Waste with Automatically Scheduled Hibernation
- Run Configuration
- SFTP Protocols for Accessing BitssCloud Containers.
- Supported OS Distributions for Docker Containers
- Timezone Addon
- Two-Factor Authentication
- Types of Accounts
- Varnish
- Websockets Support
- What is Cloudlet
- What is PaaS & CaaS
- WordPress AddOn
- Zero Code Change Deploy with No Vendor Lock-In for Smooth Migration across Cloud Platforms
- Show all articles (12) Collapse Articles
-
Go lang
-
Wordpress category
-
Data Storage Container
-
Memcached
-
Account & Pricing
WildFly server
WildFly is a modern, flexible, lightweight, and managed application runtime, which is written in Java and implements the latest standards and technology of the Java Platform Enterprise Edition (Java EE) specification. WildFly is entirely free and open-source, available to be run on multiple platforms. Among the main features of this application server:
- customizable runtime based on the pluggable subsystems, which can be integrated or removed on demand
- Java EE8 support to implement the latest enterprise Java standards in easy to consume framework
- modular approach with an ability to start each service in isolation
- fast, lightweight, and optimized for ultimate performance
To create a WildFly application server for Java project hosting within BitssCloud PaaS, follow the simple steps below. Creating WildFly Server 1. Log in to your BitssCloud account and click the New Environment button in the upper left corner of the dashboard.
2. In the opened environment topology wizard, navigate to the Java tab and select WildFly (the 10-16 versions are supported) from the list of available application servers. Then, specify the allocated resources limit using cloudlet sliders, choose a region (if several ones are available) and edit the name of your environment.
Notes:
- WildFly is not compatible with Java 6 and 7; therefore these versions are not available
- due to the minimal WildFly resources requirements, it is strongly recommended to allocate more than 1 cloudlet for this node. Otherwise, you can experience low server performance and even its failure
- WildFly can be launched in the Standalone mode using the configuration file defined in the STANDALONE_MODE_CONFIG environment variable
- BitssCloud provides out-of-box support of the WildFly servers Auto-Clustering in the Managed Domain mode via the appropriate switcher in the topology wizard
Click the Create button when ready.3. Wait for a couple of minutes for your environment to be created and click the Open in Browser button next to it.
4. The WildFly default welcome page lists some useful links to help you get started.
In order to access the WildFly Administration Console, click the appropriate link (circled in the image above) or get the URL from the email (received after server creation) alongside other access credentials. Also, you can establish an SSH connection to your WildFly server and use the WildFly CLI inbuilt utility for managing.
Standalone Mode
The WildFly application server is run in the “standalone” mode by default so that each instance is an independent process based on the configuration file defined via the STANDALONE_MODE_CONFIG environment variable.
There are four certified profiles for standalone mode:
- standalone.xml (default) – configurations for Java Enterprise Edition 8 Web with the required technologies
- standalone-full.xml – configurations for Java Enterprise Edition 8 Full with all the EE 8 technologies
- standalone-ha.xml – configurations for Java Enterprise Edition 8 Web with high availability
- standalone-full-ha.xml – configurations for Java Enterprise Edition 8 Full with high availability
In case of using the HA configs (the last two options), the jgroups protocol is used for messaging between nodes. It is configured to use the authorization with the MD5 token and asymmetrical encryption by default. Such an implementation prevents non-authorized nodes from being able to join a cluster and non-members from communicating with cluster members. Note: It is highly recommended to change the default auth_value parameter within your standalone HA configuration file on the production environments. This concludes our tutorial on the WildFly server installation! Now, you can configure it in the way you need and proceed to the application deployment.