Overview
Key Concepts
General
- Index
- Favorites
- User Getting Started
- General
- User Key Concepts
- Search
- User Testing and Debugging
- User Interface
Account
- Index
- Add a Group to an Organization
- Add a New Azure Cloud
- Add a New Cloud
- Add a User To a Group
- Add a User
- Add a User to a Team
- Azure Setup
- Azure
- Catalogs
- Clouds
- Cost Management
- Create a Team in an Organization
- Delete a Platform
- Deploy an Organization
- Deployment Approval Process
- Enable Access to an Assembly for a User on a Team
- Environment Profiles
- How Cost Tracking and Reporting Works
- Import and Export Catalog
- Account
- Manage OneOps User Accounts
- Notifications
- OneOps Policy Management
- Organization Summary
- Provide Only Necessary Privileges to Accounts
- Reports Summary
- Restrict Access with Teams
- Secrets Proxy
- Security Groups
- Shutdown a Cloud
- View a Reports Summary
- View, Add, or Edit Environment Profiles
- View an Organization Summary
- View Assembly and Organization Consumption with Reports
Design
- Index
- Add a Platform to a Design
- Add a Variable
- Add ELK Stack to an Application
- Add or Delete a Security Group to Open or Close an Additional Port
- Add a Team to an Assembly
- Apache HTTP Server Component
- Apache HTTP Server Pack
- Apache Tomcat Pack
- Artifact Component
- Attachments
- Variables Override Prevention
- Certificate Component
- Chocolatey Package Component
- Components
- Compute Component
- Create Assemblies to Design Applications
- Create Environment Dependency with Environment Profiles
- Daemon Component
- Design Best Practices
- Download Component
- Edit a Platform
- Enable https for a Service (LB Certs)
- File Component
- Filebeat Component
- Firewall Component
- Fully Qualified Domain Name FQDN
- Hostname Component
- Design
- Java Component
- Job Component
- Keystore Component
- Load Balancer Component
- Library Component
- Load/Extract
- Logstash Component
- Manage Assemblies
- DotNet Framework Component
- Microsoft IIS Pack
- IIS Website Component
- Microsoft SQL Server Pack
- Naming Conventions
- NuGet Package Component
- Objectstore Component
- Operating System Component
- Packs
- Platform Links
- Platforms
- Ports by Platform
- Propagation
- Security Group Component
- Secrets Client Component
- Sensuclient Component
- Set Up Multiple Ports/Protocols in Load Balancer
- Share Component
- SSH Keys Component
- Storage Component
- Telegraf Component
- Upgrade an Application Version in an Environment
- User Component
- Variables
- View Design Releases
- Volume Component
- Watching an Assembly
- Website Component
Transition
- Index
- Add CNAME in Azure DNS
- Add CNAME
- Add or Edit Primary and Secondary Clouds
- Add or Reduce Capacity
- Availability Modes
- Configure ECV Check URL on OneOps
- Create an Environment
- Delete an Environment
- Deploy Application after Design Changes
- Deploy an Application for the First Time
- Deploy Application With Database
- Deploy an Environment
- Deploy Multiple Clouds in Parallel
- Deploy and Provision an Application and Environment for the First Time
- Edit an Environment
- Email Notification Relay
- Environment Releases
- Environment
- Transition
- Remove an Unused Cloud from an Environment
- Rollback Code
- Set Variable Cloud Scaling Percentage
- Transition Best Practices
- Transition
- View Deployment Status
Operation
- Index
- Assess the Health of Applications, Platforms and Clouds
- Auto Repair
- Auto Replace
- Auto Scale
- Computes in Operation
- Control Environment
- Enable Platform to Auto Replace Unhealthy Components
- Ensure that Alerts for Production Environment are Sent to NOC
- Find a Platform VIP Name
- Grep or Search Text in Files on Computes
- Operation
- Navigation to Monitors
- Monitors
- Operations
- Operations Summary
- Set Up a Custom Action
- Take a Node out of Traffic (ECV Disable)
- Update or Upgrade New OneOps Code
Home > user > transition > Deploy Application With Database
Deploy Application With Database
Purpose
The purpose of this document is to briefly explain how to configure and deploy a simple web application with a MySql database.
Highlevel Overview
-
Setup MySQL database on OneOps.
-
Create a schema on MySQL.
-
Configure the web application.
-
Deploy the web application on the server.
Step by Step
-
Select the organization where the web application needs to be deployed.
-
Create a new assembly.
-
Go to design tab and add a new platform for the database from list of available packs e.g. use the MySQL pack.
-
Configure the database schema either using ‘Additional DB statements’ or the ‘Attachment’ option.
-
Once all the required components under the database platform are configured, you have to commit the changes.
-
Go to the transition tab and create a new environment. The newly created environment will pull all the design changes.
-
Once the design pull is completed, click on the commit and deploy button. It shows the deployment plan. If no changes are required, click on the “Deploy” button. This action acquires a new VM, installs MySQL, configures the database and starts MySQL.
-
Once deployment is completed successfully, perform a simple test for database connection.
-
Now, go back to design tab and another platform for the server where the web application will be deployed. In this article we will be using a Tomcat pack.
-
Configure the web app to be deployed either using the artifact component or attachment option.
-
Commit the changes. Go to the transition tab and pull the new design changes into the environment.
-
Commit and Deploy generates the deployment plan for the new server.
-
After successful deployment go to the Tomcat server fqdn component and find the DNS details to access the application.
Best Practices
-
Add users SSH keys under the user component for each platform in design.
-
Add the tomcat-daemon component as part of tomcat platform design.
-
For the attachment option, always use a public URL for remote file which do not require authentication.
-
For all environment specific configuration like database add new VM arguments for Tomcat to load them accordingly.
