Fix Problem Installing Lotus Sametime 8.5.2 On unsupported Linux Distribution

Fix Problem Installing Lotus Sametime 8.5.2 On unsupported Linux Distribution

By   18:37   No comments:

Well, if you are trying to install Lotus Sametime 8.x.x on an unsupported Linux Distro, just like how I did, you will come across this error, "This operating system is not supported."

Thankfully getting around the system checks Lotus Sametime performs well and made things easy.

Here is what you need to do, just type the following command on your terminal before running the installer:

# export STSkipAllChecks=true

Still having problem installing Lotus Stand Time, Just follow the below official troubleshooting methods.

Before deploying Lotus Sametime 8.0 server, IBM strongly recommends that the appropriate fix be applied to the server:

• Linux: ICAE-79BKS5

• AIX: ICAE-79CNL2

• Solaris: ICAE-79CNMJ

• Win32: ICAE-79CNNA

For more information regarding the hotfixes above, refer to the technote titled "Fixes to known stability issues with Sametime 8.0 server" (#1289862).

Before deploying the Lotus Sametime 8.0 connect client, IBM strongly recommends that you install a required fix. For more information, refer to the technote titled "Sametime 8.0 Connect client fix required prior to deployment: Update install.xml" (#1291831).

Additional fixes for Sametime 8.0.x can be found as they become available on Fix Central.

Product Documentation:

The IBM Sametime documentation pages list product documentation, white papers, Redbooks, Redpapers, Redpieces, and additional documentation for supported releases of IBM Sametime Standard, IBM Sametime Entry, IBM Sametime Advanced, and IBM Sametime Unifed Telephony.

http://www.ibm.com/developerworks/lotus/documentation/sametime/

Read More

Difference Between The Suite And Server Versions Of Acronis Disk Director

Difference Between The Suite And Server Versions Of Acronis Disk Director

By   12:20   No comments:

Please be aware that Acronis Disk Director Suite 9.0 support Windows 2003 Server but Acronis Disk Director 10.0 does not. Acronis did not have different versions for home users and servers until the 10.0 version of Acronis Disk Director was released.

The main difference between Acronis Disk Director Server 10.0 and Acronis Diask Director Suite 10.0 is that the first product is oriented for servers and supports server operating systems and that Acronis OS Selector is included into Suite version only.

Acronis True Image 9.1 Workstation does not support Windows 2003 Server, you can use Acronis True Image 9.1 Server for Windows.

I recommend you to download and install the free trial version of Acronis True Image 9.1 Server to see how the software works on your computer.

http://www.acronis.com/enterprise/download/

Read More

Web Server Traffic Reporting With Webalizer In Linux | Running A WebServer In Linux Machine

Web Server Traffic Reporting With Webalizer In Linux | Running A WebServer In Linux Machine

By   18:57   No comments:

If you're running a Website, you're likely to be interested in the amount of traffic it receives, where it's coming from, and where it's going. The analysis of Web traffic enables developers to assess whether or not the Websites hosted on your server are being used as expected. It allows those developers to make the changes required to deal with unexpected loads, or to direct visitors towards particular Web pages of which they may not be aware.

Traffic reporting for Web pages is a two-stage process. First, there needs to be a log of each request made for each Web page; fortunately, that's exactly what Apache's /var/log/httpd/access_log log file contains. Second, the raw data in that log file needs to be turned into a useful report. This is where Webalizer, an open source Web server log analysis program, comes in handy. Webalizer periodically goes through Apache's access logs and produces an HTML report, complete with charts, so that we can quickly and easily identify any trends in site traffic.

If Webalizer is not installed, install it from the Package Management tool by selecting the Webalizer package from the Web Server package group, or by entering yum install webalizer at the command prompt.

Fedora's Webalizer package is already configured to read /var/log/httpd/access_log once daily to regenerate its reports, so there's no need to configure Webalizer. The default configuration writes its reports to the directory /var/www/usage, which can be accessed via the browser at http://localhost/usage/, as shown in Figure below.

Note that if Webalizer's cron job has not been run, nothing will be available at this address: you'll see an error message. To force Webalizer to generate reports, run webalizer from the command line as root.

The reports are very detailed, showing not only tables that indicate the "number of hits" the site has received, but graphs of changing hit counts over time, traffic statistics broken up by month, week, day, and hour, and details of which "user agents" (Web browsers) were used to access the sites.

There are many, many Web traffic analysis tools like Webalizer. You may already have experience with another and, if so, you may prefer to use that. I'd recommend Webalizer because it provides comprehensive statistics in a clearly understandable format, and requires no configuration to set up and get working.

Figure: A Webalizer report.

While Web traffic analysis reports are useful to Web application developers, they can also be useful to you, the system administrator. A traffic report can give you an idea of when site traffic typically spikes to higher levels, and which parts of your Website attract the greatest numbers of users, which will help you make decisions about network bandwidth .

For example, if you find that your server is serving a lot of images, and that, consequently, those requests are slowing down the other processes on the machine, you might think about setting up a second LAMP server purely to serve the images, thereby reducing the load on your first server. You might also decide to use traffic shaping tools to alter your network bandwidth to route more (or less) traffic to particular servers or services. This can be particularly handy if you're seeing bandwidth spikes to particular services, or at particular times.

Read More

Configuring Linux Web Server With MySQL And PHP

Configuring Linux Web Server With MySQL And PHP

By   10:35   No comments:

Today , dynamic Websites are more the rule than the exception. Most sites require some type of database back-end and use one scripting language or another. A bare-bones Apache configuration is perfectly suited to serving up static Web pages without any further configuration, but if you're looking to build a more dynamic site, a little more work is in order.

Installing MySQL and PHP

First , you'll need to make sure all of the appropriate packages for MySQL and PHP are installed. Here we're going for a pretty basic installation of MySQL and PHP.

Figure: Displaying the packages in the Web Server group.

You can install the necessary PHP and MySQL packages using the Package Management tool  In Linux Server. Launch the tool, scroll down to Web Server, and click the Details button to display the packages in the Web Server group, as shown in Figure above; most of these will probably already be installed.

Ensure that the php and php-mysql packages are ticked (tick them if they're not) and click the Close button.

Next, ensure that the MySQL Database package group is checked. As we're building a server to use MySQL exclusively, we can uncheck the PostgreSQL Database package group, too. Click the Details button for MySQL Database and make sure that php-mysql and mysql-server are checked.

Once you're done, click Update in the main window to install or remove any packages.

Tip: If you'd rather make use of PostgreSQL than MySQL, there's no problem with that. In the Web Server package group, check php-pgsql to give PHP the ability to communicate with PostgreSQL databases. You can uncheck php-mysql to keep your server lean and mean, or leave it in, for added flexibility.

To complete your installation, restart the Apache service using your preferred method.


Testing your Installation of PHP
To test the installation of PHP, let's create a file named phpinfo.php in the /var/www/html directory; you'll need to switch to root to do this. The file should contain only the following three lines of code:

This page will call the built-in PHP function phpinfo() to display all the available information about your PHP installation. Run this page by opening http://localhost/phpinfo.php in your Web browser (Applications > Internet > Firefox Web Browser).

Figure: Displaying phpinfo.php in Firefox.

Firefox should display details about your server, as shown in Figure above. If it does, congratulations: PHP is working! If not, check that the Apache service is up and running, then check Apache's error log (/etc/httpd/logs/error_log). Searching the Web for any error messages displayed in the error log will usually lead to a solution; alternatively, try your luck at some friendly web server forums.

Tip: Once you've checked the installation, it's a good idea to delete phpinfo.php , lest someone should stumble across the critical details of your PHP installation.

Read More