Web Enterprise Development: Music Store Maintenance Using Java APIs

This document details the development of a web-based music store project, musicStoreProjectMaint, designed for managing music details, albums, artists, and music collections. Built with an administrative interface, the project focuses on minimizing manual work involved in handling album, artist, and customer data. Core functionalities include adding, updating, and deleting information about artists and their music. The system incorporates custom tags for artist data and features a user-friendly GUI. The project transitions from a local text file input to a database architecture for enhanced robustness. The report covers the project's architecture, database framework, application implementation, and GUI, along with test scenarios and used technologies, including the use of Java Persistence API (JPA) and SSL for security. Desklib provides access to past papers and solved assignments for students.

Running head: WEB ENTERPRISE DEVELOPMENT
Web Enterprise Development
Name
Institution

WEB ENTERPRISE DEVELOPMENT 2
TABLE OF CONTENTS
Introduction.................................................................................................................................................3
Related Research.........................................................................................................................................4
Design of Functionality................................................................................................................................6
PART 1 PRODUCT MAINTENANCE...........................................................................................................7
PART 2 Product Maintenance with custom tag validation.....................................................................14
PART 3 Product Maintenance with a database using JDBC....................................................................15
PART 4 MAINTENACE OF PRODUCT WITH A JAVA PERSISTENCE API (JPA) BASED DATABASE...............15
PART 5 MAINTENANCE OF PRODUCT USING SSL AND HALMARK..........................................................19
References.................................................................................................................................................21

WEB ENTERPRISE DEVELOPMENT 3
Introduction
As will be depicted by screenshot demonstrations in this report, the main aim of the
developed musicStoreProjectMaint is a web-based music portal. Looking to handle several
features including music details, record album, artist and distinct music collections, it portrays all
necessary information. Therefore it is entirely built from an adminstrative terminate, thence, only
guarantees their access. The determination of the project lies on building up an app aimed to
minimize hefty work involved in handling album, artist, and customer. By tracking wholly
contigents of the artist, music and type of album. Having a centralized association music storage
application, it is established on a context involving core routines to insert, update as well as
remove registers based on the various entities. Through the database adminstrator, customers’
needs for music products can be amply accomplished.
The project’s core functions include adding, deletion as well as updating information
about the performer, their songs as described in form of an album. Similarly, inserting fresh as
well as changing the artists’ product is possible. The custom tag exists so as to hold the artists’
data on product. As a fundamental facet of the system, it showcases a user favorable Graphic
User Interface (GUI). Despite implementing a local text file input, an advanced architecture is
enforced through a database which ensures a found architecture. As such, the application is
modular thus, open to be added with other features. First, attempt to provide an overview
platform for the various entities including products, customer and the product. Secondly, it is
mandated that an error assuring fucntion to be appended in case users input inappropirate data on
the application. Thridly, enhancing the adminstrator’s role in managing the store was sought to
be handled by sorting products’ information. Lastly, a customer’s ability to select certain
products as favorites is handy.

WEB ENTERPRISE DEVELOPMENT 4
Therefore, this report delves in to describing how the project was developed hence:
architecture carrying out the database’s framework, move towards implementing the major
sections of database, application as well as the GUI. A blueprint of how the system functions will
be depicted through the applications framework. The GUI will comprise of concrete scenarios of
explaining various test scenes and used technologies.
Related Research
This section of the paper will discuss a portion of the work that was displayed amid this
course. Additionally, it makes a little investigation about a few subjects that identifies with the
task being referred to. The primary motivation behind this part is to demonstrate the connection
between this venture and the subjects that are being explored in the field. It's an extension of the
task being referred to where it means to relate them in a more prominent whole. As said over our
task was to make a basic application with the end goal for clients to arrange CD's and DVD's. As
you may have seen we made the interface utilizing java. This was a basic and straight forward
methodology.
In consideration to the way that the sort of association is managed, it can be thought of
like a "virtual" kind of association. One can expand the possibility of this single association to be
identified with other association in the field too. These can be associations that convey the
distinctive items to this association. In this particular case we demonstrated just a single part of
this association which manages the requesting of compact disc's and dvd's by clients. If we
somehow happened to view this application as a sub-some portion of other application in this
association, than we could apply a portion of the viewpoints that are exhibited in Afsarmanesh,
et al. (2015). The fundamental intention is the interrelation and data trade between the diverse

WEB ENTERPRISE DEVELOPMENT 5
frameworks. In Afsarmanesh, et al.(2015) they present the WaterNET framework were the
principle reason for the framework was to enhance data offering to alternate (sub)system(s)
inside the organization. The case went up against here is where all the sub-frameworks work
freely and the vast majority of them are heterogeneous ordinarily. They present us with an
answer for interrelating these frameworks with one another so that the music store database
project and sharing of data is executed amongst them.
On the off chance that we consider to the arrangement Afsarmanesh, et al. (2015)
presents us, we can envision how the interrelation between the diverse associations that conveys
items to our association can be interrelated to one another. For if the Music Store application was
to be considered as being a piece of more noteworthy totality, the need of data sharing between
the distinctive frameworks may rise. Other than this answer for interrelate the distinctive
frameworks with one another it additionally displays different viewpoints about data access and
perceivability levels for virtual endeavors in (Frenkel 2017). Frenkel presents us a viewpoint that
would be worth considering when managing virtual associations that are identified with different
organizations.
Design of Functionality
The outline as portrayed in the specialized plan is for the most part to serve to give a
'high level' diagram of the application structure. In this manner few out of every odd single class
or trait might be available in the chart. Classes and different things that don't particularly clear up
or show anything "strange" have been overlooked for additional clearness.

WEB ENTERPRISE DEVELOPMENT 6
Figure Technical Design of Music Store website.
JDBC
Connection*ResultSet* Customer, Order, Product, Artist, Music track
JSP WEB PAGE
COLLECTION LOCAL CLASSES
DB
APP

WEB ENTERPRISE DEVELOPMENT 7
PART 1 PRODUCT MAINTENANCE
As implemented by the project’s team, various funcationalies are as described in the figures
below.
Figure 1: Importing project from local computer in Zip format.
Development began by importing the project file into NetBeans IDE so as to undergo further
construction.

WEB ENTERPRISE DEVELOPMENT 8
Figure 2 Renaming project file to “MusicStoreProductMaint”
As depicted above, the second step involved renaming the project file into the appropriate name
and ready to view all files.
Figure 3: Adding Library files

WEB ENTERPRISE DEVELOPMENT 9
Figure 4: Locating the product.txt file

WEB ENTERPRISE DEVELOPMENT 10
Figure 5: Created index.jsp file
Figure 6: Viewing music store catalog

WEB ENTERPRISE DEVELOPMENT 11
Figure 7: Updating catalog with a music project.

WEB ENTERPRISE DEVELOPMENT 12
Figure 8: Deleting a music project from catalog
Figure 9: Editing an already existing entry on the music catalog.