This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.
Originally for a company, people are using a paper basis to record all the details needed in a company such as staffs information,leave application,staff salary statement,clients information and so on. Paper previously used because it is effective and efficient, and easy-to-stored but face difficulties if the paper is removed, lost or there is some fault write. As time goes by people prefer to use the computer to record all the details and information in computer. It will reduces some of the organisation cost such as man power to write the staff's information,paper cost,fault write and so on. The paper basis still being done till today but the process been reduce. Most of the organisation are using computer to computerized all the work flow that regarding to the company. The process also being implement in a systematics and less process. The enterprise system is being implemented in an organization or company in way to support the business logic of the company. One of the system that usually being used is Content Management.Content Management that we understand is the process of managing any type of digital information such as text,images,graphics,video,sound,documents,records, data and etc. There several type of digital content. Some companies save the digital contect in their computer and if needed send to clients or other organization using the email application. Using email application is easy as everyone able to create it by free and use it anywhere but the is one problem that always occurred that is when the digital content that need to be send is in large size and can't be uploaded using the email. Zeta Intergrated Solution Sdn. Bhd also known as Zeta or Zetasb was incorporated in July, year 2004. This company developed by youth who have a lot of experience in the field of Information and Communication Technology (ICT) for more than 20 years. One of the system that has been develop and implement in the company are AchieveIT(ECMS). ArchieveIT is a system where all types of digital content can be uploaded without using the email and there are no limitations of the file size.
The problem with ArchieveIT (ECMS) now is that the system has been applied on every client's computer and once the data has been stored one day in a week, the data will be restored back in the vendor server. The file that can be view is in .tif format which been problem as now day the document is save in other format also such as .doc, .docx, .txt, .gif, .jpeg and others documentation format. The library of the system displays the data quite slow. ECMS also didn't have their own repository storage to save the entire document. It was a waste of time as the process should be in one flow only instead of two flows.
ECMS should designed based on typical three-tier architecture. Three-tier is a client-server architecture in which the user interface, functional process logic ("business rules"), computer data storage and data access are developed and maintained as independent modules, most often on separate platforms.The three-tier model is considered to be software architecture and a software design pattern. Apart from the usual advantages of modular software with well defined interfaces, the three-tier architecture is intended to allow any of the three tiers to be upgraded or replaced independently as requirements or technology change. For example, a change of database from MySQL to PostgreSQL would only affect the data tier.
Example of three-tier architecture
This is the top most level of the application. The presentation tier displays information related to such services as browsing, downloading, and searching documents. It communicates with other tiers by outputting results to the browser/desktop client tier and all other tiers in the network using web-service transport.
Application Tier (Business Logic/Logic Tier)
The logic tier is pulled out from the presentation tier and, as its own layer; it controls an application's functionality by performing detailed processing. This tier also enforces security policy for data access.
Here information is stored and retrieved. This tier keeps data neutral and independent from application servers or business logic. Giving data its own tier also improves scalability and performance. This tier consists of SQL Database Servers for storing document hierarchy structure, LDAP for user account, WebDAV for document data and cluster filesystem for data indexing.
A 'Web service' is defined by the W3C as "a software system designed to support interoperable Machine to Machine interaction over a network." Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services. The W3C Web service definition encompasses many different systems, but in common usage the term refers to clients and servers that communicate using XML messages that follow the SOAP standard. In such systems, there is often machine-readable description of the operations offered by the service written in the Web Services Description Language (WSDL).For ECMS, web service act as transport middleware in client-server operation. All request reply for each operations defined in WSDL is done using SOAP over HTTP.
Web-service Enabled System
Tightly coupled system, programmers need to understand many underlying details on each systems.
Loosely coupled system, programmers don't need to know the details of underlying system for each vendor.
Any changes in one system may cause other system breakdown.
As long as the provided API (WSDL) is stable (unchanged), no modification need to be done for other party.
Multiple point of vulnerability, a bugs in one system can cause other system vulnerable as well.
Single point of vulnerability, a bugs in one vendor doesn't propagate to other vendors' system.
Comparison between web-service enabled application with traditional system
Search engine should be designed to run on top of Apache Lucene library. Apache Lucene for a high performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform. All documents attribute will be analyzed for every successful save/update operation. For certain file format, the content of the document itself is also analyzed and indexed for easier searching later.
Currently, the following file format is supported for content extraction:
Supported File Format for Content Based Search Index
In order to optimize search engine matches, many words need to be in base or root form. This process is called stemming. The stem need not be identical to the morphological root of the word; it is usually sufficient that related words map to the same stem, even if this stem is not in itself a valid root. A stemmer for English, for example, should identify the string "cats" (and possibly "catlike", "catty" etc.) as based on the root "cat", and "stemmer", "stemming", "stemmed" as based on "stem". A stemming algorithm reduces the words "fishing", "fished"," fish", and "fisher" to the root word, "fish". For ECMS, Porter algorithm is used to stem
The English word. Every word for each document is analyzed and then stored as file. This file is called 'indexes'. Indexes will be used for every search operation and will help improve performance since word analyzer only happen during document upload and update. Document searching will simply read the already processed result, resulting faster operation. For cluster deployment, it is required for 'indexes file' to be stored in cluster-aware file system.
All file transfer is using Message Transmission Optimization Mechanism (MTOM) protocol. MTOM is the W3C Message Transmission Optimization Mechanism, a method of efficiently sending binary data to and from web services. It uses XOP (XML-binary Optimized Packaging) to transmit binary data and is intended to replace both MIME and DIME attachments. It also allows large data to be transferred using minimal memory footprint at the server and client side.
Document Classification and Indexing (Document Attribute).
In order to not to be confused with search indexes, term 'document attribute' is used to replace 'document indexes' or 'indexing'. Document attribute consists of 'summary', 'document details' and 'bookmark'. This entire attribute is searchable by ECMS search engine. While 'summary attribute' simply describe short description of files, 'document details' will store information in tabular form. In this tabular form, only 'description' field is searchable. 'Title' fields are stored as-is and not searchable. 'Bookmark' or 'marker' on the other hand is useful for marking multipage document or geotagging a map.
Understanding Document and Node
In ECMS, document is managed by hierarchy of node. Each node can have multiple child and only single parent. All nodes must have parent except 'Top Level Node'. Top Level Node is used to store organization or user's home location. Each node must have associated type for proper hierarchy tree. The following is the list of node type and their description:
Deploying and Managing ECMS:
SQL Database Server
Supported database is Oracle, DB2, Sybase, MS SQL Server, PostgreSQL, MySQL,HypersonicSQL, Mckoi SQL, SAP DB, Interbase, Pointbase, Progress, FrontBase,Ingres, Informix and Firebird. Database server must have a database named "ECMS" and granted with privilege read, write, modify. All the tables required will be automatically created when the ECMS application finish deployed.
For most ECMS operation, LDAP only require read-only access. Write access only required when user perform password changing operation.All user that exists within predefined Distinguished Name (DN) automatically granted as a valid ECMS user. To define base Distinguished Name for user lookup, see Glassfish Application Server section.All user account policy such as account expiration, lock account, minimum password length are defined in LDAP server.
LDAP structure for ECMS:
LDAP structure for valid organization entry
LDAP structure for valid group entry
LDAP structure for valid user entry
The enterprise system is a need in an organisation as time goes by, people will want to write less than they write today and also less paper will be used. It's a must to have enterprise system in an organization to support the business logic or process flow of an organisation and from time to time the system should evolve as time goes by the technology we used today will change from time to time for a better performance in life.