An Application Server is a server that has an ability to run web applications. That is to say applications to handle incoming web request, and generate an appropriate response. An application server has a role distinct from that of a web server. These are two essential components and both Tomcat can do.
A Tomcat Java application server can generate HTML response to a request after making a number of operations (connection to a database, an LDAP directory …). For the client (usually a web browser), there is no difference between a static web page: it still receives the HTML language ET to only understand how the response made to server-side exchange.
Requests for the client do not differ either if it wants to access a static resource or a web application, it still uses a URL in the same format (standard HTTP).
- The customer sends a request (ie calling a URL) to a resource request to the server. Example:
- http://bodhost.com/. He Does not know the answer here if will be received IS static (simple HTML page) or dynamic (generated by a web application). In our case, that this is an application meets at welcome on the server bodhost.com.
- On the server side, the web server (eg Apache) that processes incoming HTTP requests. Therefor it deals with all applications, They require a static or dynamic resource. Only one HTTP server does not know answer to requests for static resources. It Can Only return HTML pages, images, etc … existing ones.
- Thus, if the HTTP server finds that the received request is for the application server, it sends it to HTML. Both are connected by a channel named connector.
- The application server (eg Tomcat) receives the request in turn. Tomcat itself is able to execute piece of the application (the servlet ) which is for the query, based on the URL. This is done from the server side Configuration.
- Tomcat Java application server is an operation: representing a query, the other representing the response. The servlet can now work, and generate the response to the request. This May involve the consultation of data sources such as databases.
- Once the response is generated, the application server sends it back through the connector web server. And if ET recovers itself for a static resource, it simply delegates the recovery of the response to generate it properly.
- Now the simple task remains to understand HTML code by a browser as it is. And the HTTP server can return the response to the client to read it accurately.
Web server / application server
Remember the web server and application server are two separate things. These two components are needed on the actual server side, because they depend on each other. How? The application server can not handle HTTP request and the web server does not know how to run applications. These two components are essential and they should not be separated. Therefore to handle both simple HTTP requests (static resources) and web applications it needs to be operated independently. The idea is to change the connector, including one to use HTTP request instead of queries sorted from the server.
Note: Choose a hosting plan that offer dedicated resources for Tomcat such as VPS, Cloud Server Hosting, Hyper-V VPS, Dedicated Server Hosting, etc … )
Q. How do I order the dedicated server hosting package?
Ans. Just choose the package you want to order. Next you will see the product specification. If you want to add some additional product/service, then check the configurable options. At the end we will adjust your account for the specified product/service.
Q. Do you offer any discount?
Ans. Yes, we do offer some special discounts such as 5% discount on annual payment and 10% discount on biannually payment.
Q. What about promotional code, if I have any?
Ans. Once you click on Add Cart button you will see the next page where you can Edit or remove the configuration options. At the bottom, there is an option for Promotional Code. If you have any code, then enter in to required box and click on validate code button. At the end, to complete order process you will have to submit your details.
Q. What payment option do you offer?
Ans. We offer, PayPal, Bank Transfer, and 2CheckOut payment option. In addition you can choose billing cycle among monthly, quarterly, semi-annually, Annually, and biennially.
Q. Do you allow IRC, and ShoutCast?
Ans. We do not allow IRC, however, we do allow to host shoutcast.
Q. What type of Support do you offer?
Ans. We offer complete management that includes round the clock technical support for all hosting packages. We provide 24x7x365 days customer support with an average response in 15 minutes. We also provide toll free phone support, and live chat.
If you have any questions about any of our plans or you are not sure about something you see on our website, then you can submit a request quote form on our website or use our live chat help desk option.
PHPMotion script is a good resource for video sharing application and our lot of customers using it adequately. The most important thing about this script is that it is updated with time to time and it’s free to use as well. Hence, it is helpful for improving performance and fixing any security loop holes.
You can say this media sharing content management system (in short – Video CMS), which is also free to use and it supports other types of media as well (mp3 audio sharing). This software allows you to create and run your own video sharing website such as music, and picture sharing website. To run PHPMotion based website is very simply and if you have a adequate knowledge the can produce fine results with it. In addition, it’s very easy to run your own video website like YouTube, Daily Motion, etc….
In terms of web hosing solution, dedicated server is highly recommended with essential modules, because video files requires high amount of web server resources. Thus, you need to have enough resources allotted to your web hosting account so processing of the all video request of your website will run smoothly. However, if your website is not heavily loaded with video files, then you can use VPS or Cloud hosting solution.
Key Features that are included with PHPMotion
Uploading, Managing, and deletion of audio and video files.
Embedding of flash videos from YouTube
Creation of Photo Galleries
Inbuilt Blogging Tools
Creation and management of groups and members profile
Internal Email Messaging
According to PHPMotion’s official website following requirements are recommended.
- Linux/Unix based web server
- PHP 4.3 and above (including support of CLI)
- MySQL database server
- LAME MP3 Encoder
- Libogg + Libvorbis
- Mencoder and also Mplayer
- FFMpeg-PHP
- GD Library 2 or higher
- CGI-BIN
- Be able to run background processes
PHP Settings
- open_basedir = (no value)
- upload_max_filesize = 100M
- post_max_size = 100M
- max_execution_time = 1500
- session.gc_maxlifetime = 14000
- safe_mode = off
- Thread saftery = disabled
- enable_dl = On
If you are pretty new to Linux and don’t know anything about security tweaks then you should consider below list, where I’ve mentioned several Linux Security Tweaks, which will you have to notice to make your Linux Web Server Hosing secure.
- PhpSysinfo
- rootkit Detection and Installation and Configuration
- ZenOptimizer installation
- Installation of IPtables and Firewall Configuration
- Installation of Mod_security
- Installation of Brute Force Detection Software
- Extensive Binary Hardening
- Scan and hardening /tmp /var/tmp Directories
- Limitations of PAM Resource
- MySQL Tweaks
- PHP Hardening
- configuration and Installation Logrotater
- Host.conf and Sysctl Harden
- Installation and configuration of Logwatch
- Secure Name Configuration
- Remove unsecured and unnecessary Software
- Set up of RBL linked with spam Databases
- Mailman and Send-mail Monitor
- Installation and Configuration of MRTG
- ClamAV - Anti-virue toolkit
- Installation of phpSysinfo
- Installation of Libsafe
- Apache / MySQL / PHP Optimization
- Installation and Configure mod_evasive
- Installation of Nobody Check
- Install and Configuration of Iftop
- Installation of Eaccelerator
- Installation and Configuration of AIDE
- Installation of Munin
- Installation and Configuration of Snort
- Installation of MyTop
- Installation of Nessus Scanner
- PRM - Process resource monitor Installation
- Installation of SIM – Sys Integrity Monitor
- Installation of LES – Linux Environment Security
- Installation of SPRI – Sys Priority Config
- Installation of LSM – Linux Socket Monitor
Windows Network Load Balancing Dedicated Servers
Network Load Balancer or Clusters that were included in Windows Server OS enabled TCP/IP-based services such as follows:
- Web Services
- Terminal Services
- Virtual Private Networking
- Streaming Media
It basically didn’t require any Hardware Support and distributed IP traffic across cluster hosts which ensures detecting host failures and re-distributes traffic to hosts. It provides control and upgrade from Windows NT 4.0 OS. It delivered high performance and fail-over protection in comparison with other load-balancers.
Financial Transactions, Database access, corporate connections and other functions required more reliability which was offered in Windows NLB. Cluster enabled different servers to manage and operate as a single server increasing availability and management.
Windows 2000 Advanced Server and Data Center Server OS includes cluster technology which also provides fail-over for applications and databases. In terms with NLB, traffic is distributed among multi-node clusters.
Advantages of Network Load balancing servers:
> Network Load Balancer Servers are Scalable based upon the activity it hosts. It always adds more no. of servers when we speak of traffic increase.
> Network Load Balancer Server improves reliability of servers. It detects failure of servers and distributes traffic among servers without interrupting any service.
> It distributes traffic based upon the client’s / Users request.
> In comparison, it’s much better than Round Robin Solutions
> 100% Network Uptime
> Centralized access to all cluster servers
> Cost effective when compared to hardware load-balancing techniques
Installation and Management of Network Load-balancing Dedicated Web Servers:
Network Load Balancer is automatically installed and enabled on the Windows Server 2003 and 2008 Operating System. It’s compatible with Ethernet and network adapters, it doesn’t require any hardware. In a NLB, customer is assigned a IP address which is seen as Virtual IP address which all cluster host respond to. Network Load Balancer load-balances only incoming traffic from all IPs. While configuration of NLB, it’s important that there should be a dedicated IP address, primary IPs and Virtual IP’s in order to enable host TCP/IP to respond to IP addresses. Dedicated IP address is entered first and then virtual IP addresses. Services such as PPTP Server does not allow outgoing connections from a different IP address and cannot be used by dedicated IP.
In a cluster, each host is assigned in range of 1 to 32 where lower no. refers to priority. The default host handles all client traffic for virtual IP addresses. Normally, in this case, if the default host fails, the next priority takes place. Network Load Balancer also customized port rules for range of server ports. It can select either Multiple-host or second hosting load balancing policies. With Multiple-host load balancing, incoming request are distributed among all cluster hosts and load percentage can be specified. In this case, it directs all traffic to most priority server. Rules specified at Ports can block different network access. WHen we speak of port rule multiple-host NLB, one of them is selected in affinity mode and Network Load Balancer client’s traffic from on IP addresses on multiple-cluster hosts. It reduces the load on the servers and increases the response time.
In order to manage client sessions, single-client affinity mode balances network traffic from client’s IP on a single cluster host. Network Load Balancer is configured with single port rule covers all port with multiple-host balancing and single client affinity. It is used for applications.
Network Load Balancer also has remote control program which allows administrators to check status of clusters from cluster host. Network Load Balancer for port rules can be enabled or disabled. New traffic can be blocked on host while TCP connections to complete removing host from cluster. Cluster host can disable remote control.
Applications do not need to be modified for load balancing. It does not directly monitor applications. Network Load Balancer provides application mechanism to monitor cluster. Servers can be removed from the clusters for maintenance without interference with other cluster servers. It also allows custom hardware of software upgrades.
Network Load Balancer scales the performance of server based program. It distributes request among different servers in a cluster. With NLB, each IP packet is received by each host. Cluster host responds to different client requests even multiple request from a single client. Load percentage can be handled with each cluster server and can be set as required depending upon the activity. In case one cluster host fails, the traffic and is re-distributed among other cluster host.
Network Load Balancer uses are fully distributed software architecture. A copy of Network Load Balancer driver runs on each cluster host. Drivers check for all incoming network traffic for cluster IP address. On each cluster host, they act as filter between network adapter drive and TCP/IP stack allowing portion of incoming network traffic. Incoming client request are partitioned and load-balanced among cluster host. Network Load Balancer runs as network driver which is below higher-level application protocol such as HTTP and FTP.
Network Load Balancer can also run as drive between TCP/IP protocol and network adapter drivers within Windows protocol. It maximizes throughput by broadcasting subnet to deliver incoming network traffic to cluster host and removers requirement to route incoming packers to individual cluster host. Filtering packets that are not required can be easily be removed than routed packages, it delivers higher Network Load Balancer throughput than any other solution. As network and speed improve, it improves accordingly and reduces dependencies on hardware. It’s availability in fail-over is another advantage.
Network Load Balancer takes advantage of subnet / switch hub to deliver network traffic to cluster host. It increases the load on switches by accessing additional port bandwidth. However, this is not the concern in many applications. Client-side network switch connections are faster than server-side connection. During packet receiving, Network Load Balancer implements delivery of incoming packages to TCP/IP and receiving other packets by Network adapter driver. It means it will speed up all the processes and reduces latency. In many cases, it removes packet data in memory.
Network Load Balancer uses layer-two broadcast or multi-cast to distribute incoming traffic to cluster host. Network Load Balancer re-assigns MAC address of network adapter for which it is enabled. And cluster host assigned the same MAC address. Incoming traffic received by cluster host and Network Load Balancer driver for filtering. MAC address is taken from cluster IP address in the Network Load Balancer properties.
Cluster host that is attached to switch, it might create MAC address conflict due to layer-two switches to see unique MAC address on all switch ports. In order to avoid these problems, Network Load Balancer modifies MAC address for outgoing packages. This prevents switch from learning the cluster’s MAC address and incoming packets for cluster are delivered to all switch ports. Cluster host connected to hub, Network Load Balancer masking for MAC address in Unicast disables to avoid flooding upstream switches. This is done by setting Network Load Balancer registry parameters MaskSourceMAC to 0.
Network Load Balancer unicast mode has a disadvantage of communication disabling between cluster hosts through cluster adapters. Outgoing packets for cluster host are sent to sender’s MAC address, packages are looped within sender by network stack and they do not reach the wire.
Communication between cluster hosts and host outside the cluster is never affected by NLB’s unicast mode. Traffic for all static IP address are received by cluster host due to the same MAC address. Network Load Balancer doesn’t load balance traffic for the IP address, Network Load Balancer deliver the traffic to TCP/IP on host.
With other cluster host, Load balancing Servers checks it’s traffic as load balanced traffic and deliver to TCP/IP. Network Load Balancing also has another mode by distributing incoming traffic to cluster hosts which is called multi-cast mode. Network Load Balancer – Unicast also increases switch flooding by delivering incoming network traffic to cluster hosts, however this is not the case with multi-cast mode. Network Load balancing have Address Resolution Protocol which is required for the cluster’s main IP and virtual IP address resolving to cluster multi-cast MAC address. Network Load Balancing does not include management of incoming IP traffic other than TCP traffic, UDP traffic, Generic routing encapsulation traffic for each port.
Exchange Servers started in 1993 and outgrown since then. It was built in XENIX which is a version of Linux Operating System licensed by Microsoft from AT&T in the 70′s. to exchange server in April 1993.
The users were around 500 in Exchange server in Jan 1995 which then increased to 32000 in 1996. It was then migrated to beta version and the next version was brought in the market.
The Exchange Server 4.0 was released in 1996 and officially sold to public and was to upgrae Microsoft Mail 3.5. It was utilized by 400 client server mails with one database and 500 directories. Following release version was 5.0 which was released in 1997 introduces Administrator console integrated to SMTP-based networks. It also had an add-on feature known as Intenet Mail connecter which could directly communicate with server.
Exchange Server 5.5 was then released in 1997 which came in two versions, Standard and Enterprise. There were many differences in storage limit, mail transport connectors and had the ability of cluster servers.
Exchange Server 2000 edition was released in 2000 which many improvements and it’s limitations were reduced compared to Exchange Server 5.5. It supported more than one cluster and increased it’s supported database. Instant messaging support was also includes and the version includes Microsoft Acive directory which was unavailable in the previous version. The era was then supported by Exchange Server 2007 which was released in 2003. It was supported on Windows 2000 Server and Windows Server 2003. This allowed easy upgration from one operating sytem to another. This was mainly used by major organizations which could not afford downtime caused due to dedicated server migrations.
It main feature includes disaster recovery which allowed administrators to bring servers online faster by sending / receiving emails and recovering them from backups. It also provided anti-virus and anti-spam.
This was introduced in two versions such as standard and enterprise. The standard version allowed 75GB of database storage whereas Enterprise edition allowed 16TB and 4 storage group with 5 databases per group. However, it was only compatible with 32 bit version and not install on 64-bit windows server 2003.
The lastest version is Exchange Server 2007 which was in the beta version in 2006. It can run on 32-bit or 64-bit version of Windows Dedicated Servers. The performance has been improved with this version when compared to Exchange Server 2003.
Exchange server 2007 also introduces features such as voice-mail, filter options, web service support, Outlook Web Access new interface.
BODHost.com supports Exchange Dedicated Server Setup
At the time of request to the DNS Server in order to resolve domain names, it provides different cnames in one order. It redirects the request to servers which are in groups. The BIND feature of DNS resolveing the domain to the server, the request are sent to the same server.
In case of Multiple CNames, when there are four dedicated web servers clusters configured with a IP address, adding them to the DNS with A names. The srv can be set as per our selectionand should meet up the next option.
srv1 IN A xx.xx.xx.1
srv2 IN A xx.xx.xx.2
srv3 IN A xx.xx.xx.3
srv4 IN A xx.xx.xx.4
Add cnames to resolve www.domain.com to one of servers such as
IN CNAME srv2.domain.com.
IN CNAME srv3.domain.com.
IN CNAME srv4.domain.com.
DNS Dedicated Server will then resolve to www.domain.com. The request is sent over group of servers.
Also, the request that is sent to the domain without www should be forwarded to www.domain.com. In order to avoid cname error, we need to do the following :
options {
multiple-cnames yes;
};
In case of Multiple A records for one domain is thus not appropriate DNS server for BIND 9. We use the following :
www.domain.com. 60 IN A xx.xx.xx.1
www.domain.com. 60 IN A xx.xx.xx.2
www.domain.com. 60 IN A xx.xx.xx.3
www.domain.com. 60 IN A xx.xx.xx.4
In this case, if any DNS load balancing dedicated dedicated server, it will have no idea if the server is down. It does not check the port of the dedicated server. IP can be cached by nameserver, the request cannot be sent to load balancing DNS server.
Round Robin DNS load balancing does have many drawbacks but can removed by using Perl scripts.
By using the below steps you can easily install Apache on a Dedicated server :-
http://httpd.apache.org/download.cgi
#cd /usr/local/src
#wget http://mirrors.24-7-solutions.net/pub/apache/httpd/httpd-2.2.8.tar.gz
#tar -xzvf httpd-2.2.8.tar.gz
#cd httpd-2.2.8.tar.gz
#./configure –prefix=/usr/local/apache
# make /compile
# make install /install
#cp /usr/local/apache/bin/apachectl /etc/initr.d/
#service httpd stop
#service httpd start
#httpd –v
These are the points you should remember before transferring a data from one dedicated server to another:-
1)First thing you should remember to give notice to your visitors and users that your website will be down during a specified period of time for planned migration. Ideally, this time should be in the middle of the night (to most of your visitors), to minimize the inconvenience to clients.
2)Prepare DNS for the move:You should make sure that all your DNS records are set to something like an hour. This should be done 48 hours before your move. By doing this will ensure that when you move the website and switch the IP address in the DNS records, people will get to the new location quickly. If you want to double-check the website before it comes back up, add in a new “A” record that already points to the new server’s IP address.
3)Take inventory:You should make a list of all things which you wants to move.Does your web server have a special setup for your website? Do you have any cron jobs running that you will need to set up on the new server? If someone else developed your website and you are not sure about this step, ask them.
4)Put your website on “hold”: Create a small page that just has your website logo and something to the effect of “Sorry. We are moving to a new server. We will be back in couple of hour or so on.” Put this page in place of your web directory and make sure NO pages on your website can be accessed. Keeping people out of any page will result in no loss of data.
5)Set up Email, cron :If your email goes through an account on your server or you have any cron jobs or additional setup to do on the new server, do it now.
7)Once everything is set up bring your website back. To do this, simply swap the IP address in the DNS to the new server’s IP and you should see your website come up pretty quickly.
8)After a day or so, change the TTL in your DNS records back to what it was before . If you forget to do this and leave the TTL at 1 hour, it can create an unnecessary burden on your DNS server.
If everything goes well, you should be able to move a data-driven website or blog with very minimal downtime and with no major problems.
Dedicated Server Migration is one of the most important process and should be done carefully.
> It containes packages for ditribution by SPRMS. It is not invludes in Red Hat. It is the part of core distribution.
> CentOS contains apt RPMS. However, it has issues with distros that utilize multiple libraries.
> centOSplus is also included which are contribution from centOS developers and Users.
> contrib are contribution from users.
> docs which includes manuals and releases of notes
> Added Functionality to the Core distribution
> ISO’s for download from centOS mirror websites
> Updates that released through centOS
centOS is a very user-friendly and interactive Operating System and known to fease very easily. centOS dedicated servers are known to integrate with many control panel such as cPanel.