We have recently, well, months ago, attempted to put in Digital Signage at our facility. The idea was to have one greet customers and vendors as they came onsite for meetings or to drop things off. These presentations might include a warm greeting for expected visitors and also have videos or pictures that captured some of the work we’ve performed. The other unit was to be used more informally to let employees know what is happening around the company, important things as well as fun things, like when the next Chili cook off is happening. Oh…. Better sign up for that soon

As with any technology there are many options available that attempt to do the same thing. Some offer their solutions and such as just hook up a PC to your TV and run straight Power Point, put your TV on the local network and push down images from your local webserver, others suggest you need a client/server setting and some offer a nice compact appliance that can mount on the back of the TV. Sounds pretty slick and easy to do, that is the intention.

However; as with anything, the intention may be good, but doesn’t necessarily get it down. The work may actually become frustrating and time consuming without a resolution in sight. We encountered this with our solution. On and off over the period of a few months, time was spent troubleshooting why were able to use the appliances if we ran off a local SDCard rather than utilize our existing network and push the images via the webserver. The vendor graciously worked with us to keep on task and finally after pushing and throwing up our hands, came onsite to finish this project. The vendor was not able to save the day and a new option had to be explored. In troubleshooting, it was noted that though several tests worked with the webserver and the local network, the appliances were not happy. We could not determine if it was one particular thing or many, or even down to the way the Wireless router was functioning. All systems checked out individually, though it was noted the firmware could use to be updated on the Wireless Router, but deemed that for another day.

So, with that, the solution. It was discovered through this time that there was a service provided by the appliance maker to put your presentations and devices on their servers and essentially store and run in the cloud but use the client software on-site and push content back from the web to the appliances on-site. This is what we determined to do. The setup was quiet simple and is working quite well. Through all the back and forth, discovered that the point of contact vendor does most installations this way and very few the original method we attempted. The lesson here is to ask the questions of the vendors to explore all options and in doing so, find out what most of their client base uses. We asked the options, but didn’t ask how many clients used which method, that would have saved a lot of time, patience and money in the long run.

Technorati Tags: Technology,Case,Digital,Signage,speedway,items,customers,vendors,meetings,presentations,visitors,unit,employees,Chili,Better,options,Some,solutions,Power,Point,client,server,appliance,Sounds,intention,solution,appliances,SDCard,vendor,task,option,systems,Router,maker,servers,setup,Through,installations,method,lesson,clients,patience,money,months,onsite,webserver
Windows Live Tags: Technology,Case,Digital,Signage,speedway,items,customers,vendors,meetings,presentations,visitors,unit,employees,Chili,Better,options,Some,solutions,Power,Point,client,server,appliance,Sounds,intention,solution,appliances,SDCard,vendor,task,option,systems,Router,maker,servers,setup,Through,installations,method,lesson,clients,patience,money,months,onsite,webserver

WordPress Tags: Technology,Case,Digital,Signage,speedway,items,customers,vendors,meetings,presentations,visitors,unit,employees,Chili,Better,options,Some,solutions,Power,Point,client,server,appliance,Sounds,intention,solution,appliances,SDCard,vendor,task,option,systems,Router,maker,servers,setup,Through,installations,method,lesson,clients,patience,money,months,onsite,webserver

By default apache tomcat runs on port 8080.

Instead of running tomcat on port 8080, we can also run it on port 80.

Run following command as root user in machine you want make tomcat to work on port 80.

$ iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination :8080

Above command is using Port Forwarding technique, where all requests coming to port 80 on eth0 are forwarded to port 8080.

Advantage of port forwarding technique is security. Since port numbers 0 to 1023 are privileged ports its not suggested to give direct access to no root users.

Now test tomcat on your machine with ip address or localhost

Example:

http://127.0.0.1

http://locahlost

Either of the above command will get the response from  tomcat ROOT webapp.

-Sany

MooresCloud founder Mark Pesce’s Xzibit reference is still a very apt description of the Light, his company’s Linux-based LED lamp. The Australian team’s box-shaped illumination runs the open OS (including a LAMP web server stack) on an integrated mini PC with an accelerometer and WiFi. The relative power and networking provide obvious advantages for home automation that we’ve seen elsewhere, but it’s the sheer flexibility of a generalized, web-oriented platform that makes the difference: the Light can change colors based on photos or movement, sync light pulses to music and exploit a myriad of other tricks that should result from a future, web-based app store. When and how the Light launches will depend on a Kickstarter campaign to raise $700,000 AUD ($717,621 US) starting on October 16th, although the $99 AUD ($101 US) cost is just low enough that we could see ourselves open-sourcing a little more of the living room.

[Adam Bercu] and [Dan Landers] from Artisan’s Asylum in Somerville, MA brought a very, very cool toy to Maker Faire this year. It’s a two hundred pound WiFi repeater deploying robot able to amble across unforgiving terrain and my foot.

The robot is controlled through a web interface with the help of a front-mounted web cam with pan and tilt controls. All the signals are sent through a WiFi connection to a node.js web server; not the best way to communicate with a robot over long distances, but [Adam] and [Dan] have a few tricks up their sleeve.

On the back of the robot are two Pelican cases loaded up with a battery and a Linksys WRT54G wireless router. When the robot reaches the limits of its range, it activates a solenoid, dropping a WiFi repeater. This repeater has enough battery juice to stay powered for about a day and a half, meaning the robot can make multiple trips to deploy a wireless network through some very hostile terrain. Perfect for disaster and search and rescue operations.

There are two videos after the break: the first is [Dan] going over the capabilities of his tank bot and the second is a short demo of the bot tearing up the grass at Maker Faire.

What?

A few days ago we published how to install a gnulinux web server box into a VirtualBox machine.

Now we want to disable the GUI, since we will access the box through SSH and removing the GUI will improve the machine’s performance.

How?

We need to edit the grub config: /etc/default/grub

Change this line:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to

GRUB_CMDLINE_LINUX_DEFAULT="text"

…and comment this one:

GRUB_HIDDEN_TIMEOUT=0

Now update grub config:

sudo update-grub

Restart your box and voilà, that’s it… you have a nice text screen now…

Despite this you always can start the GUI from command line with this command:

startx &

What?

We want to install a web server into a VirtualBox Machine.

We will use:

• OS: this guide is valid for any Debian/Ubuntu derivative (using right now Linux Mint 12/13)

• web server: Apache

• DB: MySQL

• DB admin: phpMyAdmin

• Other: PHP

• Mail Server: sendmail

How?

Easy! Following these steps!

1. Install the OS in the VM as usual. (be sure you can reach the network from your guest OS)

2. First than all install SSH Server, so the rest of this guide can be done through a SSH conection:

   1. sudo apt-get install openssh-server

3. Install CSF firewall

   1. Install libwww-perl

      1. sudo apt-get install libwww-perl

   2. Get the code

      1. wget http://www.configserver.com/free/csf.tgz

   3. Untar it

      1. tar -xzf csf.tgz

   4. Run installation script (first cd csf)
      

      1. sudo sh install.sh

   5. Now let’s test that the required iptables modules are working for 100% in our system, type this command:

      1. sudo perl /etc/csf/csftest.pl

      2. You’ll get a small report and if everything looks fine, continue to the next step.

   6. Open the csf config file sudo nano /etc/csf/csf.conf, check the default port numbers and eventually other settings. Each setting is well documented, if you’re ready then change also this row TESTING = “1″ to enable the firewall (use ctrl+x to save the file).

   7. Now we need to restart the csf service using sudo csf -r, open a second terminal and login using SSH. You need this extra step to be sure that your firewall doesn’t have blocked ssh access for yourself

4. Install Apache & PHP & MySQL

   1. APACHE

      1. sudo apt-get install apache2

      2. We want to use the MPM prefork module instead of the MPM worker module for the best performance:
         

         1. sudo apt-get install apache2-mpm-prefork

   2. PHP

      1. sudo apt-get install php5-cgi php5-cli

      2. We install suPHP for more security, suPHP makes it possible that PHP scripts are executed by the user who has created the script. (keep in mind that suPHP needs all scripts run under certain directory, i.e. /var/www, because of this I will create a soft link from the user home dir to a user dir into /var/www) Enter into the terminal:

         1. sudo apt-get install libapache2-mod-suphp

   3. MySQL

      1. sudo apt-get install mysql-server libapache2-mod-auth-mysql php5-mysql

         1. Provide a strong password for the MySQL root user!

5. phpMyAdmin – The first virtual hosting account
   

   1. If you don’t have yet a user created, create one (usually with Mint 12/13 you create one at the installation, if you do not want to use it, create a new one)

   2. Create a dir for the user into /var/www:

      1. sudo mkdir /var/www/newuser

   3. And give the ownership to the user

      1. sudo chown newuser:newuser /var/www/newuser

   4. Move to your user’s home directory and create a new soft link

      1. ln -s /var/www/newuser public_html

   5. Now we create a host file for Apache:

      1. sudo nano /etc/apache2/sites-available/myphpmyadmin.conf

   6. Inside this new file we will add the following code:

<VirtualHost *:80>
ServerName myhostname.com
ServerAdmin webmaster@localhost
DocumentRoot /var/www/newuser/phpmyadmin
ErrorLog /var/log/apache2/phpmyadmin-error.log
LogLevel warn
CustomLog /var/log/apache2/phpmyadmin-access.log combined
</VirtualHost>

1. Save the file with ctrl+x (you will create the phpmyadmin dir soon)

   1. Enable the site configuration with

      1. sudo a2ensite myphpmyadmin.conf
         

   2. and reload Apache with

      1. sudo /etc/init.d/apache2 reload

      2. (Apache will say that your dir does not exist… and he’s right… so…)

   3. Return to your user’s home directory and download phpMyAdmin using

      1. wget http://downloads.sourceforge.net/project/phpmyadmin/phpMyAdmin/3.4.3.1/phpMyAdmin-3.4.3.1-english.tar.gz

   4. Untar the gz archive with

      1. tar xvfz phpMyAdmin-3.4.3.1-english.tar.gz

   5. and move the extracted directory to your host directory with

      1. mv /home/newuser/phpMyAdmin-3.4.3.1-english /home/newuser/phpmyadmin

   6. Restart apache with sudo /etc/init.d/apache2 reload and then open your client’s web browser, enter the server name in the address bar and you should see the phpMyAdmin login page. (you can login
      with the MySQL root password)

      1. http://<hostname>/

      2. You will need to edit your /etc/hosts so you can reach the hosted OS’ IP through the hostname you used in the Apache’s configuration file. The best is to set manualy an IP in the hosted OS and the in your client set the hosts. For example if your manualy set IP is 192.168.0.100 and the hostname you set is mynewhostedos, then you will need in your /etc/hosts a line like this one:

   192.168.0.100 mynewhostedos

   Then you can type http://mynewhostedos in the address bar of your browser.

2. Aditional tasks

   1. PHP packages

      1. sudo apt-get install php5-curl php5-gd php5-mcrypt

         1. You need to fix the #; comment bug inside the mcrypt.ini file or you get depreciated warnings. (The file misses the # before the comment, it has only the semi colon, edit it and add the #, it
            is in /etc/php5/conf.d) Restart Apache after your installed these PHP functions

   2. MySQL super user

      1. Create a kind of super user for your database using phpMyAdmin, it’s much safer to use a
         different user than the “root” user for normal database operations.

         1. CREATE USER ‘usr’@'localhost’ IDENTIFIED BY ‘pass.’;

         2. GRANT ALL PRIVILEGES ON *.* TO ‘usr’@'%’ WITH GRANT OPTION;

   3. phpMyAdmin access (if your server will become public you need to restrict the access to your DB)

   4. Your phpMyAdmin host is accessible for everyone, you should protect your database tool against bots using

<Directory /home/newuser/phpmyadmin>
                     Options Indexes FollowSymLinks MultiViews
                     AllowOverride None
                    Order allow,deny
                    # add here your IP addresses
                    allow from 100.100.100.100
</Directory>

1. You need to enter these rules into your host configuration file.

And you are done, you have a web server working.

Now you’ll need to add virtual hosts so you can host different sites with differents URLs, but this is stuff for another post.

Remember 1: to put CSF’s tesing = 0 if you will go to a productive environment.

Remember 2: it’s a good practice to run a package database update frenquently. So, let’s update it now, after installing all the packages above: sudo apt-get update; sudo apt-get upgrade

Optional:
SMTP Server

1. install postfix (https://help.ubuntu.com/community/Postfix)
   

2. If needed configure it to use a ISP’s SMTP (http://www.howtoforge.com/how-to-relay-email-on-a-postfix-server)
   

3. Test it:

   1. echo “hello world” | /usr/sbin/sendmail -v your@email.com

4. To test it fully try with mutt (http://www.hypexr.org/linux_mail_server.php)
   

Customer had hired a Consultant to originally setup their Exchange 2007 environment and now their Certificate had expired. Was originally setup to use their 2008 Enterprise CA so customer not only did not know how to generate the request from within Exchange but also did not know how to submit it to their own CA (I know).

Now with a 2003 CA I would just generate the certificate request from within Exchange Management Shell then Browse to http://CA-Name/CertSRV> Click Request a Certificate>Advanced Certificate Request>Submit a Certificate Request by Using a Base-64…..>Then select “Web Server” from the Certificate Template drop-down (Figure 1).

However, on a 2008 CA you do not have the option for Web Server (Figure 2)

This obviously makes it difficult to use the old familiar web-based interface to request your certificate. I believe these additional templates were removed from /CertSRV by default due to security reasons but I have yet to confirm.

Resolution:

So in this case I just needed to generate the certificate request on 2007, copy the .req file to my CA, and use the certreq.exe utility on the CA to process the request. The commands for the request are as follows:

Certreq.exe –submit –attrib “CertificateTemplate:webserver” C:\RequestFile.req NewCertName.cer

Depending on the settings of your CA this request may be auto approved (in which case the .cer file will be located in your current working directory in Command-Prompt; or just specify a path in the command) or you may need to approve it. You can do this either by launching the Certificate Authority MMC snap-in and going to “Pending Requests” or using the following command:

Certreq.exe –accept NewCertName.cer

Once you get the cert file just import it using Exchange Management Shell (if 2007; I usually recommend the GUI Wizard in 2010).

References:

Exchange 2007 Certificate Request Command

Exchange 2007 Certificate Import Command

Exchange Enable Certificate for Services

Exchange 2010 Certificate Request/Import/Assignment Process

If you choose to use the command line method on a 2003 CA then you may have to go through the following article

In searching to see if anyone else had published these steps I ran across the blog of Jeff Schertz. I’ve been to his blog before and always find great content. Here’s the referenced post but check out some of his other great articles; specifically for Lync.

Edit: Check this post if you receive a “Certificate Not Issued (Incomplete)” message via command prompt.

]]> http://techworldrocks.wordpress.com/2012/08/29/em-console-fails-to-load-when-weblogic-is-configured-as-windows-service/ Wed, 29 Aug 2012 22:36:15 +0000 vaishalipavashe http://techworldrocks.wordpress.com/2012/08/29/em-console-fails-to-load-when-weblogic-is-configured-as-windows-service/ Its been found that EM console fails to load when weblogic is configured as windows service. When we install weblogic as service only commEnv.cmd file is called which is not sufficient to set EM environment so to make EM console work, follow below work-around:

1. Edit installSvc.cmd file to add setDomainEnv.cmd instaed of commEnv.cmd:
Replace:
call “%WL_HOME%\common\bin\commEnv.cmd”

with
call “%DOMAIN_HOME%\bin\setDomainEnv.cmd”

2. The setDomainEnv.cmd script will correctly setup up the classpath, so comment out or remove the following line:

set CLASSPATH=%WEBLOGIC_CLASSPATH%;%CLASSPATH%

3. Now re-install weblogic service and start it

4. Access EM console on admin IP:Port and it will load properly

• nodejs.org

#yum update

Install all development tools

#yum groupinstall “Development Tools”

Install MySQL

#yum install mysql mysql-server
#chkconfig –levels 235 mysqld on
#/etc/init.d/mysqld start
#mysqladmin -u root password yourrootsqlpassword

To install Php

yum install php-mysql php-gd php-imap php-ldap php-odbc php-pear php-xml php-xmlrpc

Install some dependency applications for nginx

#yum install zlib-devel wget openssl-devel pcre pcre-devel sudo gcc make autoconf automake

Download ngnix for installation

#wget http://nginx.org/download/nginx-1.2.0.tar.gz

#tar -zxf nginx-1.2.0.tar.gz

#wget http://downloads.sourceforge.net/pcre/pcre-8.10.tar.bz2

#tar -jxf pcre-8.10.tar.bz2

#cd pcre-8.10

#./configure

#make

#make install

#cd nginx-1.2.0

#./configure –prefix=/opt/nginx –user=nginx –group=nginx –with-http_ssl_module

When the configuration process completes successfully, you will see the following output:

nginx path prefix: “/opt/nginx”

nginx binary file: “/opt/nginx/sbin/nginx”

nginx configuration prefix: “/opt/nginx/conf”

nginx configuration file: “/opt/nginx/conf/nginx.conf”

nginx pid file: “/opt/nginx/logs/nginx.pid”

nginx error log file: “/opt/nginx/logs/error.log”

nginx http access log file: “/opt/nginx/logs/access.log”

nginx http client request body temporary files: “client_body_temp”

nginx http proxy temporary files: “proxy_temp”

nginx http fastcgi temporary files: “fastcgi_temp”

Issue more two commands to complete nginx setup.

#make

#make install

Create an user named “ngnix”

useradd -M -r –shell /sbin/nologin –home-dir /opt/nginx nginx

Create a init script for nginx

Vi /etc/rc.d/init.d/nginx

#!/bin/sh

#

# nginx â this script starts and stops the nginx daemon

#

# chkconfig: – 85 15

# description: Nginx is an HTTP(S) server, HTTP(S) reverse \

# proxy and IMAP/POP3 proxy server

# processname: nginx

# config: /opt/nginx/conf/nginx.conf

# pidfile: /opt/nginx/logs/nginx.pid

# Source function library.

. /etc/rc.d/init.d/functions

# Source networking configuration.

. /etc/sysconfig/network

# Check that networking is up.

[ "$NETWORKING" = "no" ] && exit 0

nginx=”/opt/nginx/sbin/nginx”

prog=$(basename $nginx)

NGINX_CONF_FILE=”/opt/nginx/conf/nginx.conf”

lockfile=/var/lock/subsys/nginx

start() {

[ -x $nginx ] || exit 5

[ -f $NGINX_CONF_FILE ] || exit 6

echo -n $”Starting $prog: “

daemon $nginx -c $NGINX_CONF_FILE

retval=$?

echo

[ $retval -eq 0 ] && touch $lockfile

return $retval

}

stop() {

echo -n $”Stopping $prog: “

killproc $prog -QUIT

retval=$?

echo

[ $retval -eq 0 ] && rm -f $lockfile

return $retval

}

restart() {

configtest || return $?

stop

start

}

reload() {

configtest || return $?

echo -n $âeloading $prog: â

RETVAL=$?

echo

}

force_reload() {

restart

}

configtest() {

$nginx -t -c $NGINX_CONF_FILE

}

rh_status() {

status $prog

}

rh_status_q() {

rh_status >/dev/null 2>&1

}

case “$1″ in

start)

rh_status_q && exit 0

$1

;;

stop)

rh_status_q || exit 0

$1

;;

restart|configtest)

$1

;;

reload)

rh_status_q || exit 7

$1

;;

force-reload)

force_reload

;;

status)

rh_status

;;

condrestart|try-restart)

rh_status_q || exit 0

;;

*)

echo $”Usage: $0 {start|stop|status|restart|condrestart|try-restart|reload|force-reload|configtest}”

exit 2

esac

Give accurate permission to the init script and add it for automatic startup:

chmod +x /etc/rc.d/init.d/nginx

chkconfig –add nginx

chkconfig –level 2345 nginx on

/etc/init.d/nginx start

Install PHP-FPM :

yum install php-fpm

chkconfig –levels 235 php-fpm on

/etc/init.d/php-fpm start

vi /etc/php-fpm.d/www.conf

[...]

;listen = 127.0.0.1:9000

listen = /tmp/php5-fpm.sock

[...]

/etc/init.d/php-fpm restart

Then edit nginx.conf to run a CakePhp application:

vi /opt/ngnix/configure/ngnix.conf

server {

listen 80;

server_name 107.22.178.21;

access_log /var/log/nginx/example.com.access.log;

error_log /var/log/nginx/example.com.error.log;

rewrite_log on;

root /var/www/html/example.com/app/webroot;

index index.php index.html index.htm;

# Not found this on disk?

# Feed to CakePHP for further processing!

if (!-e $request_filename) {

rewrite ^/(.+)$ /index.php?url=$1 last;

break;

}

# Pass the PHP scripts to FastCGI server

location ~ \.php$ {

fastcgi_pass unix:/tmp/php5-fpm.sock;

fastcgi_index index.php;

fastcgi_intercept_errors on; # to support 404s for PHP files not found

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

include /opt/nginx/conf/fastcgi_params;

}

location ~* \favicon.ico$ {

access_log off;

expires 1d;

add_header Cache-Control public;

}

location ~ ^/(img|js|css)/ {

access_log off;

expires 7d;

add_header Cache-Control public;

}

# Deny access to .htaccess files,

# git & svn repositories, etc

location ~ /(\.ht|\.git|\.svn) {

deny all;

}

}

yum -y upgrade
yum install httpd

Afterwards, open /etc/httpd/conf/httpd.conf and make sure that the dav and dav_fs modules are enabled in the LoadModule section (they should be enabled by default):

vi /etc/httpd/conf/httpd.conf

LoadModule dav_module modules/mod_dav.so
LoadModule dav_fs_module modules/mod_dav_fs.so

Then create the system startup links for Apache and start it:

chkconfig –levels 235 httpd on
/etc/init.d/httpd start

Virtual Host Configuration:
—————————

Now create virtualhost configuration for the foloder you want to share by WebDAV. In my case I am using /var/www/html/test. Also I am using the httpd global configuration for my vhost. If you have separate vhost configuraiton file for the folder then you can use that one.

First, we have to create the directory /var/www/html/test and make the Apache user and group (apache) the owner of that directory:

mkdir -p /var/www/html/test
chown apache:apache /var/www/html/test

Then add the new vhost at the end of /etc/httpd/conf/httpd.conf:

vi /etc/httpd/conf/httpd.conf

NameVirtualHost *:80
<VirtualHost *:80>
ServerAdmin webmaster@localhost

DocumentRoot /var/www/html/test
<Directory /var/www/html/test>
Options Indexes MultiViews
AllowOverride None
Order allow,deny
allow from all
</Directory>

</VirtualHost>

/etc/init.d/httpd reload

Configure The Virtual Host For WebDAV
————————————-

Now we create the WebDAV password file /etc/httpd/conf.d/passwd.dav with the user Admin (the -c switch creates the file if it does not exist):

htpasswd -c /etc/httpd/conf.d/passwd.dav Admin

You will be asked to type in a password for the user Admin.

(Please don’t use the -c switch if /etc/httpd/conf.d/passwd.dav is already existing because this will recreate the file from scratch, meaning you lose all users in that file!)

Now we change the permissions of the /etc/httpd/conf.d/passwd.dav file so that only root and the members of the apache group can access it:

chown root:apache /etc/httpd/conf.d/passwd.dav
chmod 640 /etc/httpd/conf.d/passwd.dav

Now we modify our vhost at the end of /etc/httpd/conf/httpd.conf and add the following lines to it:

vi /etc/httpd/conf/httpd.conf

The Alias directive makes (together with <Location>) that when you call /webdav, WebDAV is invoked, but you can still access the whole document root of the vhost. All other URLs of that vhost are still “normal” HTTP.

NameVirtualHost *:80
<VirtualHost *:80>
ServerAdmin tapas.mishra@wordpress.com

DocumentRoot /var/www/html/test/
<Directory /var/www/html/test/>
Options Indexes MultiViews
AllowOverride None
Order allow,deny
allow from all
</Directory>

Alias /webdav /var/www/html/test

<Location /webdav>
DAV On
AuthType Basic
AuthName “webdav”
AuthUserFile /etc/httpd/conf.d/passwd.dav
Require valid-user
</Location>

</VirtualHost>

Reload Apache afterwards:

/etc/init.d/httpd reload

Testing WebDAV
—————

We will now install cadaver, a command-line WebDAV client:

yum install cadaver

To test if WebDAV works, type:

cadaver http://localhost/webdav/

You should be prompted for a user name. Type in Admin and then the password for the user Admin. If all goes well, you should be granted access which means WebDAV is working ok. Type quit to leave the WebDAV shell:

[root@server ~]# cadaver http://localhost/webdav/
Authentication required for webdav on server `localhost’:
Username: Admin
Password:
dav:/webdav/> quit
Connection to `localhost’ closed.
[root@server ~]#

1. Create a weblogic server domain and start Admin server

2. Copy below jars in $DOMAIN_HOME/lib folder:

a. wllog4j.jar (Available in $WL_HOME/lib
b. log4j-x.x.x.jar (Download latest log4j.jar from link: http://www.findjar.com/index.x?query=log4j )

3. Login to Admin console, click on Admin server name and navigate to Logging -> Advanced

4. Select Log Implementation from default JDK to log4j logging. Save this and activate changes. Before we restart server complete below step

5. Navigate to $DOMAIN_HOME on physical box and cretae a file called log4j.xml in domain home. Copy below content in it:

<?xml version=”1.0″ encoding=”UTF-8″ ?><!DOCTYPE log4j:configuration SYSTEM “log4j.dtd”>
<log4j:configuration>
<appender name=”CONSOLE”>
<layout>
<param name=”ConversionPattern”
value=”%d [%t] %-5p %c – %m%n”/>
</layout>
</appender>
<appender name=”FILE”>
<param name=”File” value=”/<Log4j Logging location>/Log4j.log”/>
<param name=”Append” value=”true”/>
<layout>
<param name=”ConversionPattern” value=”%d{ISO8601} %-5p {%t}[%c] – %m%n”/>
</layout>
</appender>
<logger name=”org.apache”>
<level value=”WARN”/>
</logger>
<logger name=”org.springframework”>
<level value=”WARN”/>
</logger>
<root>
<level value=”DEBUG”/>
<appender-ref ref=”FILE”/>
<appender-ref ref=”CONSOLE”/>
</root>
</log4j:configuration>

6. Before saving, change location of Log4j.log as per your environment

7. Now navigate to $DOMAIN_HOME/bin folder and edit setDomainEnv.sh/cmd file:

Locate below 2 lines in script:

if NOT “%LOG4J_CONFIG_FILE%”==”" (
set JAVA_PROPERTIES=%JAVA_PROPERTIES% -Dlog4j.configuration=file:%LOG4J_CONFIG_FILE%

Above them add below line:

set LOG4J_CONFIG_FILE=”$DOMAIN_HOME\log4j.xml”

8. Save this file and restart server. Check at command prompt you will be able to see log4 logging

9. Also you can check log4j log cretaed in mentioned location in log4j.xml. Content of the log would be something link below:

2012-08-14 20:16:39,220 DEBUG {[ACTIVE] ExecuteThread: ’0′ for queue: ‘weblogic.kernel.Default (self-tuning)’}[com.bea.console.utils.ResourceBundleCache] – findBundle bundle baseName[global] locale language[en]
2012-08-14 20:16:44,993 DEBUG {[ACTIVE] ExecuteThread: ’0′ for queue: ‘weblogic.kernel.Default (self-tuning)’}[com.bea.console.utils.MBeanUtils] – Getting connection with, Host = localhost @ port = 8001

This logging format is based on the configuration we have mentioned in log4j.xml:

<param name=”ConversionPattern” value=”%d{ISO8601} %-5p {%t}[%c] – %m%n”/>

10. If you want to change this logging format you can refer below link and confiure accordingly:

http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html

Note: You can configure log4j using log4j.xml or log4j.properties configuration files.

The outcome of this tutorial will be a webpage that looks like this:

After a bit of googling around I found out that there are plenty of light-weight html frameworks working from python, javascript, and various technologies.

I chose a framework called pico.

https://github.com/fergalwalsh/pico/wiki

Execute these steps on the BeagleBone:

git clone http://github.com/fergalwalsh/pico.git
opkg install python-distutils
opkg install python-compile
cd pico 
python setup.py install

This should install pico on your BeagleBone. Now you can cd into an example directory and try it out!

cd examples/helloworld
python -m pico.server

Now you can play a bit with the example and then I’ll continue.

…

Finished already? Let’s continue with putting something actually working behind the web interface.

****

If you don’t have any idea what to do for a start use this led blinker script below. I’ll create a script to send commands to my Arduino.

wget http://gigamega-micro.googlecode.com/files/gpiotester.py

Since I have an Arduino behind the BeagleBone for now I’ll have to communicate with that through serial port.

Let’s get and install pySerial.

wget http://pypi.python.org/packages/source/p/pyserial/pyserial-2.6.tar.gz
tar -xf pyserial-2.6.tar.gz
cd pyserial-2.6
python setup.py install

Easy isn’t it?

So now that we have a Serial class we can communicate with the Arduino from the BeagleBone using Python.

I wrote the script below to control the robot. Yeah, it’s not too elegant but will do for now.

http://buggers.svn.sourceforge.net/viewvc/buggers/robots/scarabeus/beaglebone/webcontrol/beagle2arduino.py?view=markup&pathrev=336

Note that I’m using string commands so I’m sending strings directly to my Arduino.

Now that we have something to call from a webpage, let’s create the page itself!

You should check out the codes in the example folder to get the hang of the framework, it shouldn’t take too long.

This is what I came up with in the end:

http://buggers.svn.sourceforge.net/viewvc/buggers/robots/scarabeus/beaglebone/webcontrol/index.html?revision=325&view=markup

Note: if you are experiencing some kind of lag or blocked messages, you can help it by running the following on the BeagleBone. This “wakes up” the serial port. The above python code of mine will require a bit more massage to get this effect.

screen /dev/ttyUSB0

And finally here’s a video of controlling my rover using the above web page:

Like if you like my whistling and of course comments are always welcome!

References

http://pypi.python.org/pypi/pyserial

http://www.mediacollege.com/internet/javascript/form/add-text.html

https://github.com/fergalwalsh/pico/blob/master/examples/helloworld/index.html

http://www.w3schools.com/

I got all warm and fuzzy knowing I was on the right track. The next step was to check that PHP was running properly. I opened Notepad and inserted the following code:

<?php
phpinfo();
?>

I made sure to select All Files when saving to ensure that I saved the file as info.php and not info.php.txt

I even opened a new windows explorer to ensure it. The file type was listed as PHP. I felt confident and FTP’d my file over to my server. No go. It didn’t work.

I reopened the file and saved it as UTF-8 encoding. Still no go.

Then I stumbled onto something very useful. I could just create the file from the command line on the remote server. I logged into Putty and logged in to my server.

First thing as always….

#sudo su

I hate the headache of running along and my momentum is interrupted because I am not logged in as root.

#vi /var/www/info.php

This not only edits an existing file but will create a new one. A typical vi editor opens a blank file. I typed my code directly in the screen and saved the file and voila! It works like a champ. When I type webservername/info.php

into my browser I now get the info I wanted.

I know that there are great programmer editors out there, and I will download one eventually, but sometimes when learning something new it is good to start with the bare bones so that you can truly understand how it works.

 $java -version

kalau sudah terinstall akan keluar output text versi java yang terinstal :

java version "1.7.0_03"
 Java(TM) SE Runtime Environment (build 1.7.0_03-b04)
 Java HotSpot(TM) Client VM (build 22.1-b02, mixed mode, sharing)

kalau belum, download dulu deh trus instal sesuai paket file nya. biasa nya .sh kalau .sh cara install nya sh ./java…..sh klo paket nya rpm cukup ketikan rpm -ivH namajava.rpm, simpelkan? ok anggap saja ini sudah terinstall.

Sekarang download dulu tomcatnya di http://tomcat.apache.org/download-70.cgi, sudah di dwonload? ok kita lanjut ke langkah berikutnya.

1. Ekstrak file tomcat dan copy ke direktori /usr/share/

#tar xvfz apache-tomcat-7.0.27.tar.gz -C /usr/share/

2. Aktif kode akses untuk file servis tomcat

#cd /usr/share/apache-tomcat-7.0.27/bin/
 #chmod 755 *.sh

3. Membuat services untuk tomcat

#touch /etc/init.d/tomcat
 #cd /etc/init.d/
 #nano tomcat

Lalu copy paste source code dibawah ini :

#!/bin/bash
 # deskripsi : Tomcat Start Stop Restart
 # nama proses wajatmaka: tomcat
 # chkconfig: 234 20 80
 #perhatikan versi java yang anda punya
 JAVA_HOME=/usr/java/jdk1.7.0_03
 export JAVA_HOME
 PATH=$JAVA_HOME/bin:$PATH
 export PATH
 CATALINA_HOME=/usr/share/apache-tomcat-7.0.27/

case $1 in
 start)
 sh $CATALINA_HOME/bin/startup.sh
 ;;
 stop)
 sh $CATALINA_HOME/bin/shutdown.sh
 ;;
 restart)
 sh $CATALINA_HOME/bin/shutdown.sh
 sh $CATALINA_HOME/bin/startup.sh
 ;;
 esac
 exit 0
 

Ok sekarang bagaimana cara menghidupkan, mematikan, dan hidupkan ulang service tomcat :

#service tomcat start //menghidupkan servis tomcat
 #service tomcat restart //hidupkan ulang servis tomcat
 #service tomcat stop //matikan servis tomcat

Ok, setelah anda hidupkan servis tomcat, buka Browser anda lalu ketikan :

]http://localhost:8080/

Instalasi dan Konfigurasi tomcat SELESAI

To get around this, I port forwarded to the host machine, and had the host port forward (again) to the virtual machine’s ports. I’m not sure if there is a better way of exposing a virtual machine (oraclebox/vagrant) to the outside world, and I’ll keep digging but I’m just glad that progress has been made. Sometimes the obvious answers stare at us in the face and it takes a little poking around to find them properly.

EDIT: A suggestion by mlb- has been to check my virtual network interface – it might be a NAT issue, and I should check if it’s bridged properly. Let’s hope for better results!

The idea being that changes can be made to the database externally without doing the following:

(1) Compromising SQL server.

(2) Secure the internal network from outside access/hacking.

(3) Overloading the SQL server causing it to fall over.

I would also like the DMZ Webserver to be mirrored for further testing.

This is the plan, no doubt this will evolve and change with time – but I am going to enjoy the ride.

1. Set up an account on AWS. To get started, you will need an Amazon acount. You can find how to create your account here. You will need to enter a credit card, but it won’t be charged as we will only be using a server that is on the free usage tier.
2. Once you log in to the AWS Console (It’s a link under the dropdown in the top right), go to the EC2 tab and launch a new Instance. An instance is a cloud computer, which is a virtual machin. Clicking this option starts the process for choosing options of your cloud computer.
3. Create an Instance. Select your instance Type. You can select Windows and Linux instance types. I’m going to use Ubuntu. Alos, you can use Community AMIs.
   
   
4. Ensure number of instances is set to 1 and type is set to Micro (so it’s free) . The availability zone doesn’t really matter here so select no preference on that dropdown and hit continue. On the next page, all of the defaults are fine, so we just hit continue again.
5. Generate and download a key pair. This step is essential to securely access your cloud computer. In this step, you generate a special file, which is a .pem file, that you’ll use to authenticate and log into your machine. Make sure your browser allows for file downloads before you proceed through this step. You’ll need to keep this file handy to connect to your cloud computer.
6. Configure the Firewall for your cloud computer. In this step, you’ll specify the ports that will be open on your server. For a LAMP server, the default firewall configuration is to open ports for SSH, HTTP, and MySQL, which opens ports 22, 80, and 3306.

   Upon completing these steps, simply click Launch. When you do so, Amazon will build your cloud computer and turn it on. It took just over a minute for Amazon to generate my virtual machine and boot my server.

7. Next you will get a screen showing everything you’ve just selected – as long as nothing looks particularly odd you can click “Launch” and your new server will be up and running within a minute or so! The EC2 Dashboard shows my running instance below.

   

8. Now it is time to connect to the machine. You can download the private SSH key from your Amazon account. If you want to connect to the machine from Windows using the popular tool Putty, you will need to convert your private key to the .PPK format.

   On Linux, you can open a Terminal and run the following command:
   ssh -i /path/to/your/private/key.pem root@ec2-50-19-73-179.compute-1.amazonaws.com

   Now its time to install the LAMP stack Apache, MySQL and PHP. Here is the link to install LAMP in Ubuntu.

That’s all. Let me know if anybody has any concerns or issues.