DEPLOYING OPEN SOURCE WEB APPLICATION 1

Deploying Open Source Web Application

Name

Institution Affiliation

Course

Date
DEPLOYING OPEN SOURCE WEB APPLICATION 2

Introduction

Splunk is the leading forum for Operational Intelligence. Splunk program scans, tracks,

analyses, and visualizes machine-generated big data from websites, databases, computers,

networks, sensors and mobile devices. More than 11,000 companies utilize Splunk tools to

deepen the market and consumer awareness, minimize cybersecurity danger, boost service

delivery and - costs. Splunk Enterprise indexes machine data in real-time, allowing various

positions around the company — from device managers to business analysts — to quickly

gain expertise from the vast volumes of machine data provided by the environment. Adopting

a cloud approach allows companies to improve agility, cut prices, decrease time to market

and empower creativity. Splunk Business is suitable for deploying in a cloud setting,

providing enterprise-grade availability and scalability to enable the storage of hundreds of

terabytes of data every day from workloads located on-premises, in the cloud or through

hybrid environments. This paper covers guidance for deploying Splunk Enterprise on

Microsoft Azure, a free and scalable cloud framework with an increasing collection of

integrated cloud resources, including analytics, computation, database, telephone,

networking, storage and web.

Reasons why I opted to use Azure for my enterprise:

1. Service infrastructure (IaaS) and PaaS:

Azure has an enticing IaaS and PaaS blend. In order to offset their need, IaaS helps

businesses to outsource their Azure networks. PaaS helps businesses to develop their

smartphone apps and solutions without acquiring and handling the fundamentals. Top

Microsoft partner consultants in Azure will work with Azure PaaS and IaaS companies to

design Cloud business applications for rapid business growth.

2. Security:
DEPLOYING OPEN SOURCE WEB APPLICATION 3

The Security Development Lifecycle (SDL) is Azure's leading security system. It has

encryption at its heart, and the private data & resources of Azure Cloud stay secure and

reliable. Microsoft Azure delivers over 50 enforcement programs and is the most trusted

cloud network in the US Government. The new international cloud privacy standard, ISO

27018, has now been adopted for the first time. Therefore, Microsoft guarantees maximum

protection over all Azure Cloud activities and documents (Yang-Turner, 2018).

3. Analytical and Intelligence capabilities: Azure embraces SQL and NoSQL data tools,

incorporates support for more in-depth digitalisation and exposes critical enterprise processes

and policy outlook. Azure is the first cloud network with Blockchain's (BaaS) functionality,

deep intelligence, bots and cognitive APIs. For enterprises, it is critical to choose the right

cloud provider. Many businesses see business growth boosting following the use of Azure as

a cloud portal. Read the blog to find out why Azure is considerably bigger than AWS

(Tender, 2021). Fast Learning Curve: familiar frameworks like Visual Studio, ASP.NET and

languages like C++, Visual Basic and C#, are used to build native Cloud applications, making

it possible for consultants to develop cloud-based enterprise applications (Machiraju, 2018).

4. Interoperability: On-site applications such as the Azure cloud database can generate

analog implementations. Interoperability: Azure embraces universal standards, such as XML,

SOAP, REST, HTTP, and Internet protocols. An Eclipse software development kit for Java,

PHP and Ruby is accessible written in these languages and Azure tools.

How to deploy and set up your website

This guide is for those who have not interacted with Azure and want to start a fast road map.

At that time, I will registered for an Azure free trial account, creating a test database, and

creating a cloud-based test SSRS report for a complete Azure SQL database novice.

Step 1: Sign Up for a Free Azure Account

DEPLOYING OPEN SOURCE WEB APPLICATION 4

First, you must register for a free Azure trial. I accessed it at https://azure.microsoft.com/en-

us/ and subscribe to a free trial. Notice that you need to either have a credit card (for proof of

identity) or link the account with an MSDN subscription, also during a free trial. Please note

that you must associate your Windows Live ID with an Azure trial instance.

If you want to see the new Azure rates, which have dropped in recent two years, you can visit

this site and use the Azure pricing calculator: http://www.windowsazure.com/en-

us/price/calculator/ You can do a test without being paid.

Step 2. New Azure Management Portal access and SQL database developmental and

Creating a New Database Azure SQL

You will return and start the Azure Management Portal (Figure 1) by heading to

http://manage.windowsazure.com after building your trial account. While in the portal, a new,

empty SQL Azure database can be created by clicking the NEW connection at the bottom of

the portal. Figures 2-4 of the portal characterize the folder, authentication, snapshot series,

etc.

Figure 1: The new Azure Management Portal dashboard looks like this.
DEPLOYING OPEN SOURCE WEB APPLICATION 5
DEPLOYING OPEN SOURCE WEB APPLICATION 6

Figure 2: Use the New dialogue to create a SQL Database.

DEPLOYING OPEN SOURCE WEB APPLICATION 7
DEPLOYING OPEN SOURCE WEB APPLICATION 8

Figure 3: Use the dialogue to create a new Database (and call it Sample AZURE).

Figure 4: You will need to enter basic authentication for the sample database and make

sure to keep the checkbox checked.

After you go through the basic steps to create a new database, you'll return to the

Management Portal with the database server and empty database name (Figure 5). SQL
DEPLOYING OPEN SOURCE WEB APPLICATION 9

Database auto-generates a unique, ten-character alphanumeric server name[ CITATION Sta19 \l

2057 ]. You cannot change the name of your SQL Database server.

Figure 5: A new empty database and domain name used in the management portal.

SQL Database automatically creates a unique alphanumeric server name of ten characters.

The name of your SQL database server cannot be changed.

Finally, you want to access this data from "outside" – there is a link to access the

communication strings in the critical configuration section of the portal (Figure 6).
DEPLOYING OPEN SOURCE WEB APPLICATION 10

Figure 6: You can see from this dialog which link strings are visible.

Step 3: Remote access to SQL Azure Database

The next significant move is to enter the new SQL Management Studio directory. Either SQL

Server 2012 or SQL Server 2008R1 may be used (Service Pack 1). From there, you can

generate tables and other database objects using the SSMS creator. Figure 7 displays the

SSMS Link Dialog, including the connection strings server name in Figure 6. Please note that
DEPLOYING OPEN SOURCE WEB APPLICATION 11

SQL Authentication must be used (figure 7): Azure does not support authentication of

Windows.

Figure 7: Try to bind from the local Management Studio instance to the Azure database

server.

Sadly, the link doesn't function (see the error message in Figure 8). This is because you

would need to build an IP firewall back in the dashboard of the Azure Management Portal.
DEPLOYING OPEN SOURCE WEB APPLICATION 12

Figure 8: The first attempt to link failed - an IP firewall rule must be established!

You cannot link to a SQL Azure database in your local management studio instance unless

you have defined an IP firewall rule back in the Azure Management dashboard[ CITATION

Mac18 \l 2057 ].

Step 4: IP Firewall Rule Identification

From step 3, you will need to specify an IP firewall rule to connect SQL Azure databases.

Return to the Azure Management Portal; in the Configure Database section, go to the Azure

Database and access the IP Firewall Rules dialogue (Figure 9). Click on the connection "Add

to Allowed IP Addresses" in this dialog.

DEPLOYING OPEN SOURCE WEB APPLICATION 13

Figure 9: You must set the IP firewall rule back in the Management Portal!

Note: Microsoft revamped the Windows Azure portal to include additional features from

early March 2013. Through browsing the SQL Databases/Configure list, you may add a

permitted IP address and then press the Manage Connection at the bottom of the page. You

would then be prompted to include the latest IP address in the firewall rules.

You should then go back to the Management Studio and enter the database and generate any

database items that you need until it is done and then saved (under the screen). The client

artifacts that you develop are placed in the Azure database on the relation string linked server.

Note: It's worth remembering at this stage that you have two choices in the Azure database to

create new tables. You may either use the Management Studio on your nearest customer

machine or use the Azure Portal. The above is basically a web-based Management Studio

subset to create database artifacts. Since I'm still new to this, I don't know the advantages of
DEPLOYING OPEN SOURCE WEB APPLICATION 14

using a portal over a management studio until a management studio is not accessible as an

alternative, of course.

Finally, I have built a rather basic reporting database chart, a simple client table with a few

client identification and name rows. I don't want to fix some market problems—just to

evaluate mechanics. It is worth remembering two things:

First of all, any tables you generate MUST include a clustered index primary key in Azure's

current version (as I wrote at the beginning of March 2013). Tables without clustered indexes

will not be enabled by Azure.

Secondly, it is also worth mentioning that Azure databases do not accept recent SQL Server

2012 constructs, such as Sequence Objects - if you attempt, you will receive an error message

that the features "not supported in this SQL Server edition."

Step 5: Establish a reporting authority

The next phase was to build a basic SSRS project, point to Azure and then transfer the SSRS

project to an instance of SSRS Azure.

Note: The Azure Management Portal had no choice in January 2013 (the original date of this

Article). The following is the necessary workaround. Microsoft introduced features to the

management portal immediately before publication (early March 2013) to build a reporting

case. You may now either use the direct function or use the solution I will mention. Besides

the feature, there are rather similar steps to build a reporting instance.

As it turns out, there is no functionality in the Azure Management Portal in defining a SQL

Azure Reporting case. Fortunately, I find this URL, which explains that the dialog to build a

reporting instance is in the OLD edition of the management portal and not the current one
DEPLOYING OPEN SOURCE WEB APPLICATION 15

(http://blogs.msdn.com/d/pssql / archive/2021/11/15/ack-where-the-he-did-azure-reporting-

and-data-sync-go.aspx).

As it turns out, the current Azure Management Portal does not contain features to identify a

SQL Azure Reporting instance until the beginning of March 2013. In the OLD edition of the

management portal, the dialog to build the reporting instance is not the current one.

To enter the old portal, you can then click at the right upper corner of the new portal (near the

login option) to access the old portal (figure 10).

Figure 10: You must revert to the "Previous portal" to build a SQL Azure reporting

implementation.

This will initiate the old portal edition (Figure 11), where you will build a new SQL Azure

Reporting Services URL subscription and set the name and password of the administrator

(Figures 12-13). As these measures are completed, the old portal (Figure 14) displays the
DEPLOYING OPEN SOURCE WEB APPLICATION 16

current instance Web Service URL.

DEPLOYING OPEN SOURCE WEB APPLICATION 17

Figure 11: The "Previous portal" used in creating to new Reporting instance to the Azure.

Figure 12: Create a new SQL Reporting Server.

DEPLOYING OPEN SOURCE WEB APPLICATION 18

Figure 13: This is a new Web Service URL reporting instance.

Finally, a standard SSRS project with a common data source indicating the SQL Azure

database can be developed (Figures 15-16). Note that Windows Authentication cannot be

included in the data source identifiers - you must use the name that you gave when the Azure

database was first defined[ CITATION Lia19 \l 2057 ]. Then reports can be generated against the

shared data source and deployed back in Figure 14 to the Web site URL (by going to the

SSRS project properties and providing the Web service URL, as shown in
DEPLOYING OPEN SOURCE WEB APPLICATION 19

Figure 17).

Figure 14: This is your new SSRS project, with the Shared Data Source pointing to

Azure DB.
DEPLOYING OPEN SOURCE WEB APPLICATION 20

Figure 15: These are the implementation assets for the project reporting services.

If you deploy the SSRS project, you can use the URL Web Service to view the study. You

may also use the URL in your own individual ASP.NET project.

4.Firewall security

Azure Protection Centre has two key aims: to help you appreciate the existing security

condition to strengthen your security quickly and efficiently

The main function of the Security Centre to accomplish these objectives is a safe

ranking.

The Protection Centre regularly evaluates your security resources, subscriptions and

organization. It then adds all the results into a single score so that you can say the current

condition at a glance: the higher the score, the lower the danger level you found.

The stable ranking is seen as a percentage rating in the Azure portal pages, but the underlying

values are often shown clearly:

DEPLOYING OPEN SOURCE WEB APPLICATION 21

Check the suggestions page of the Protection Centre for outstanding measures required to

improve your score to increase your security. Each piece of advice contains guidelines to help

you solve the problem.

Security monitoring is categorized into recommendations. Each control is a logical set of

safety recommendations that represent your vulnerable attack surfaces. Your score only

changes after all recommendations for a particular resource are remedied. In order to see how

effectively the company secures each threat surface, check the ratings for each protection

control.

Enhance your safe ranking

Remove protection recommendations from your list of recommendations to increase your

safe ranking. You may manually remedy each suggestion on each resource or use the Fix

option (if available) to easily solve a problem on several resources. See Remediate guidelines

for more detail.

Another way to increase your score and ensure that your users do not build tools that affect

your score negatively is to customize the Enforce and Deny choices for the advice you are

using.

Prevent misconfigurations with advice from Enforce/Deny

DEPLOYING OPEN SOURCE WEB APPLICATION 22

Failure to configure protection is a big cause of accidents. Security Centre is also able to

discourage modern resources from being misconfigured in terms of precise

recommendations.

This will help protect your workload and stabilize your secure ratings.

A stable configuration is provided in two modes depending on a basic recommendation:

With the Azure policy negative impact, you may avoid creating unsafe tools. You can take

advantage of the DeployIfNotExist impact of Azure policy and automatically remediate

incompliant resources when you create it with the Enforce option. You will find this on the

top of the selected safety guidelines resource information list.

Prevent the existence of resources. Open the suggestion that you must meet your current

capital and click the Deny button at the top of the list[ CITATION DeT21 \l 2057 ].
DEPLOYING OPEN SOURCE WEB APPLICATION 23

The settings panellists the scope choices.

Set the reach of the subscription or management category to be selected.

Procedures

You may use the three dots at the end of the row to modify a specific subscription or use

Change to Deny from the checkboxes to choose different subscribers or classes.

DEPLOYING OPEN SOURCE WEB APPLICATION 24

Enforce a secure configuration

Open the recommendation that you'll deploy a template deployment for if new resources don't

satisfy it, and select the Enforce button at the top of the page.

The configuration pane opens with all of the policy configuration options [ CITATION Cha17 \l

2057 ].
DEPLOYING OPEN SOURCE WEB APPLICATION 25
DEPLOYING OPEN SOURCE WEB APPLICATION 26

Set the range, name of the task, and other choices.

Choose Check + Build.

Recommendations on choice denial

With the deny choice, these guidelines may be used:

DEPLOYING OPEN SOURCE WEB APPLICATION 27

• Access to firewall and virtual network storage accounts should be blocked

• Automation account variable should be encrypted

• Azure redis cache must be in a virtual network.

•For these guidelines, the compliance option should be used:

• Auditing the SQL Server is allowed

• Azure Backup should be supported on virtual machines

Conclusion

The final steps are over, and you have now launched your web successfully. It can now start

and run on the VM. If you want to check this, you can remotely access the VM and browse to

the IIS site directory. The freshly deployed files for your website can be viewed here. Posting

the code once would store all the configurations in a publishing profile so that you can use

this profile and deploy it with only one click sometime in the future.
DEPLOYING OPEN SOURCE WEB APPLICATION 28

References

Chandrasekara, C. (2017). ASP. Net Web Application Deployment to Azure and IIS.

In Beginning Build and Release Management with TFS 2017 and VSTS (pp. 83-151).

Apress, Berkeley, CA.

De Tender, P. (2021). Lab 4: Deploying an Azure Web App and Migrating from WebVM.

In Migrating a Two-Tier Application to Azure (pp. 109-130). Apress, Berkeley, CA.

DEPLOYING OPEN SOURCE WEB APPLICATION 29

Liang, J., Liu, F., Li, S., & Cai, Z. (2019, July). A Comparative Research on Open Source

Edge Computing Systems. In International Conference on Artificial Intelligence and

Security (pp. 157-170). Springer, Cham.

Machiraju, S., & Gaurav, S. (2018). Partner Solutions for BizTalk Azure Applications (pp.

227-298). De| G Press.

Stackowiak, R. (2019). Analyzing and Visualizing Data in Azure. In Azure Internet of Things

Revealed (pp. 87-118). Apress, Berkeley, CA.

Yang-Turner, F., Gripper, L., Swann, J., Do, T., Foster, D., Volk, D., ... & Crook, D. (2018,

July). An Open-Source Azure Solution for Scalable Genomics Workflows. In 2018

IEEE World Congress on Services (SERVICES) (pp. 39-40). IEEE.