![\"Application](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Application-Lifecycle.png\" "\\"Application")
<\/a><\/p>\nManaging the lifecycle of applications gets simpler when we automate regular tasks like setting up environments, project building, deploying, and managing domains. A recommended approach involves aligning your test environment closely with the production setup, regularly updating the test database with production data, ensuring both environments share a single database. Additionally, we’ll explain how to utilize distinct build environments using the integrated Maven tool for all your projects.<\/p>\n
To realize the schema above, we\u2019ll go through the next steps:<\/p>\n 1. Log in<\/a> to the platform’s dashboard.<\/p>\n 2. Set up a New environment<\/strong>.<\/p>\n 3. Choose the application server you prefer (like GlassFish), specify the cloudlets limit, and give a name to your initial environment, such as prodenv. After that, simply hit the Create<\/strong> button.<\/p>\n Give it a moment, and your setup will be ready in no time.<\/p>\n Instead of the traditional method of developing projects on your own computer and then uploading them as WAR archives, you have the option to build applications directly on the platform. Notable benefits of this method include its speed, reduced time and bandwidth requirements, and ability to take use of cloud computing’s efficiency. Plus, it enables you to continue using your computer without additional strain. Moreover, the platform seamlessly integrates with your version control repositories, allowing you to pull application source code directly from them via protocols like Git or SVN.<\/p>\n Creating an atmosphere that is appropriate for constructing the structure is our next duty.<\/p>\n 1. First, set up a New environment. Choose Maven as your go-to building tool, and make sure to specify the cloudlets limit and name your environment, like ‘buildenv<\/strong>‘ for instance. Plus, you have the flexibility to create an environment sans a compute node. No more juggling multiple building tools for different environments needed!<\/p>\n 2. Your setup will be ready in just a few minutes.<\/p>\n We’re ready to create our first project and put it into action for everyone to use!<\/p>\n 1. Add your project to Maven.<\/p>\n 2. In the below dialogue box, head over to the Git tab (or SVN) if you’re opting for Git as your go-to revision control system. Then, fill in details like your project’s name, its path, the branch you’re working on, and your repository’s login credentials<\/strong>. Also, don’t forget to mention the name of your Environment and the Context where you’ll be deploying your project. Finally, hit the Add button to confirm.<\/p>\n 3. Simply tap on the “Build and deploy<\/strong>” button to get your project up and running.<\/p>\n Let’s build an additional environment that has a database but no computing node. You may store all of the data for your apps there.<\/p>\n 1. To get started, just hit the ‘Create environment<\/strong>‘ button and choose the database you prefer, like MySQL.<\/p>\n 2. Once your environment is up and running smoothly, simply hit the “Open in Browser<\/strong>” button for MySQL<\/strong>. You should also find an email from the platform containing your database credentials. You can utilize these login details to set up your account and access the necessary database for your application.<\/p>\n 1. Please press the Config<\/strong> button located next to the application server in your production environment.<\/p>\n 2. When you’ve got the tab open, go ahead and make a new file called mydb.cfg<\/strong> in the \/opt\/glassfish3\/temp<\/strong> directory. Then, add the below configurations:<\/p>\n 3. Upload MySQL connector in the \/opt\/glassfish3\/glassfish\/domains\/domain1\/lib<\/strong> directory within GlassFish.<\/p>\n 4. Give GlassFish a Restart<\/strong> and then pull up your app in a web browser.<\/p>\n 5. When you use the platform, you can personalize your website’s URL by choosing your domain name instead of sticking with the default one provided by your hosting service. So, it’s a good idea to purchase a domain name<\/a> specifically for your live website.<\/p>\n Once you have your domain, we suggest configuring it by adding a CNAME record to point to your platform. To do this, navigate to the Settings<\/strong> section (look for the wrench icon) for your website’s environment and connect your custom domain<\/strong>. As an example, let’s say your chosen URL is production.com.<\/p>\n Let\u2019s set up our test environment. You can do this by cloning your production environment. This way, you can have different versions of the environment and customize them as necessary. The duplicated environment will be just like the original, with all the data in its databases, along with the deployed \u201c.WAR\u201d and \u201c.JAR packages.\u201d<\/p>\n 1. Clone your production setup to create an identical copy, allowing you to integrate new features and conduct thorough testing.<\/p>\n For instance, if you have to change something in your application:<\/p>\n 1. Include your latest project in Maven.<\/p>\n 2. Simply hit the ‘Build and deploy<\/strong>‘ button to kickstart your new project. Once done, your project should pop up exactly where you’ve set it to be.<\/p>\n 3. Click on the Settings<\/strong> button to your environment, then bind the domain you purchased earlier (i.e. test.com).<\/p>\n 4. To view the modifications, let’s launch our newly created application in a web browser.<\/p>\n Once you’ve run your tests on the latest features, you can switch the domains. This useful feature ensures that your users won’t have any issues when you upgrade your programme. Simply stage your new version in a test environment, then swap the URLs with the production environment in just a few clicks.<\/p>\n 5. Go ahead and open up the settings for one of your environments. Once you’re in there, navigate to the \u201cCustom domains<\/strong>\u201d section. From there, select the other environment that you want to swap with and hit the Swap button.<\/p>\n<\/a><\/p>\n\n
Create the Production Environment<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nCreate the Build Environment<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\nBuild and Deploy the Project<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nCreate Database Environment<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nConfigure Database Connection<\/h2>\n
<\/a><\/p>\n\r\nhost=jdbc:mysql:\/\/mysql{node_id}-{your_env_name}.{hoster_domain}\/{db_name}\r\nusername={get in the email}\r\npassword={get in the email}\r\ndriver=com.mysql.jdbc.Driver<\/code><\/pre>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nCreate the Test Environment<\/h2>\n
<\/a><\/p>\nUpgrade Application<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n