interested monitoring software| Cloud Monitoring: Easily Report on Cloud Applications, Servers and Services

interested monitoring software >>> Cloud Monitoring <<<

Easily Report on Cloud Applications, Servers and Services

1. Are you experimenting with cloud infrastructure and cloud applications? How are you Monitoring them?

2. Need to monitor public clouds (like Amazon EC2, Google, Apps, etc)? up.time makes it easy.

When You Start Experimenting with Cloud, up.time Has You Covered

• Know what to migrate into the cloud first: Quickly identify candidates for the cloud with detailed deep (and relevant) historical performance metrics that profile workloads in physical and virtual environments. Then easily monitor cloud platforms (EC2) and applications from inside the cloud.
• Easily monitor and manage cloud, virtual, and physical with a single tool: Cloud monitoring (Amazon EC2), virtual server monitoring (VMware, etc), physical server monitoring (Windows, Solaris, AIX, HP-UX, Linux, Novell NetWare) from a single console. Multiple datacenters, virtualized applications, and cloud-based applications.
• Too many tools? Eliminate point tool and integration headaches. up.time meets current and future tool needs for physical, virtual and cloud monitoring and management.
• Build automation that makes scaling up and problem solving simple: Management and monitoring tools need to understand how applications change over time and must trigger workflows to deal with changing workloads. up.time can automatically spin up and monitor virtual or cloud instances to meet capacity demands.
• Drive SLAs, regardless of virtual, physical or cloud environment: up.time understands the SLA dependencies between applications across physical, virtual and cloud environments. Quickly identify breakdowns in infrastructure and immediately see how they affect the SLAs.
• Isolate problems quickly: Intelligent alerting eliminates "sea of red," and offers fast root-cause detection and automated actions to stop recurring outages. Customize alerting so only the right person gets the right alert at the right time.
• Affordable licensing: Complete application and server monitoring. No tiers or management packs and free lifetime upgrades with support. Just count your physical servers (even in virtual and cloud environments!). Installs in minutes; deploys in less than 1 day. Over 700 enterprise customers in 32 countries agree.

Free Trial: Download a 30-day Trial of up.time (Virtual Appliance

Also Available)

Cloud Flare ++ It'll supercharge your website.

█ Cloud Flare?

CloudFlare is a FREE system that acts as a proxy between you and our server. By acting as a proxy, CloudFlare caches static content from the site, which lowers the number of requests to the server, but still allows you to access the site. There are several advantages of the CloudFlare system which are answered below. Cloudflare (like explained above) acts as a proxy to speed up and make it less "heavy" on traffic to the VPS, which means acting like a proxy through the DNS, DDoS attacks are easily diverted keeping the site and forum chugging along nicely.

CloudFlare has just announced that they happened to pick up a cool $20 million in investment last November. Almost a 1000% increase on funds raised in 2009, proving that someone thinks they’re on to something. And Qwerty.ie couldn’t agree more, that’s why we already use CloudFlare!

For those that haven’t heard of CloudFlare yet (the emphasis being on the yet), it provides a distributed network that creates a community environment to help protect your website and all other members within the network. Information about unwanted traffic is shared which means if one website is attacked then that attack can quickly be blocked from accessing everyone in CloudFlare! It’s added security for your website. As if that wasn’t enough, CloudFlare will distribute your website across the network, making it practically indestructible (please do not test this on Qwerty.ie!). Your website will be faster and use less bandwidth.

CloudFlare and W3 Total Cache WordPress Integration

CloudFlare protects and accelerates any website online. Once your website is a part of the CloudFlare community, its web traffic is routed through our intelligent global network. We automatically optimize the delivery of your web pages so your visitors get the fastest page load times and best performance. We also block threats and limit abusive bots and crawlers from wasting your bandwidth and server resources. The result: CloudFlare-powered websites see a significant improvement in performance and a decrease in spam and other attacks.

CloudFlare’s system gets faster and smarter as our community of users grows larger. We have designed the system to scale with our goal in mind: helping power and protect the entire Internet.

CloudFlare can be used by anyone with a website and their own domain, regardless of your choice in platform. From start to finish, setup takes most website owners less than 5 minutes. Adding your website requires only a simple change to your domain’s DNS settings. There is no hardware or software to install or maintain and you do not need to change any of your site’s existing code. If you are ever unhappy you can turn CloudFlare off as easily as you turned it on. Our core service is free and we offer enhanced services for websites who need extra features like real time reporting or SSL.

To get straight to the point of using CloudFlare, here are the advantages:

• Your website will loads twice as fast
• Your website will uses 60% less bandwidth
• Your website will have 65% fewer requests
• Your website will be way more secure

And all this is for free!

Presentation: http://cdata.github.com/presentations/what-else-is-cloudflare/

Storage RAID Data Collection(Auto Dump)

Storage RAID Data Collection
The RAID "Auto Dump" Facility is required for most problems that relate to HDS RAID subsystems.

A dump can only be initiated from the subsystem SVP, and thus most commonly it requires action from an HDS engineer.

This function is a procedure that merges the separate DUMP and FDCOPY functions into one operation, and provides a single compressed file available for transfer from the SVP. The default location of this file is:

• C:\DKC200\TMP\hdcp.lzh (for 9900, 9900V)
• C:\DKC200\TMP\hdcp.tgz (for USP, NSC, USP-V, USP-VM)

For instructions on how to perform an Auto Dump on a RAID subsystem, refer to the SVP section --> 2. Function of the SVP of the Maintenance Manual.

Note A common mistake is to collect the file called dump.lzh or dump.tgz. This file is included in hdcp.lzh or hdcp.tgz and cannot be used alone without the logs and config info. Always collect hdcp.lzh or hdcp.tgz

Types of Auto Dump:

1. RAPID
   Gathers logs, SVP operation history, configuration information. NOT collected: Dump data (Processor, ABEND, WCHK1) and monitor data. This type should only be collected when urgent initial analysis is required and/or slow upload connection is available. This type is typically used for Backend (Hard Disk) related errors and for system healthchecks.
2. NORMAL
   Performs and collects dumps (all microprocessors, ABEND, WCHK1), in addition to files gathered by RAPID. Monitor data is not collected. This type should be collected by default when no instruction has been given and the problem types refered to in "3. DETAIL" below do not apply.
3. DETAIL
   Gathers monitor data, in addition to information gathered by RAPID and NORMAL. This type should be collected when there is some suspicion that the problem is related to performance, subsystem workload, sidefile or HUR journal overflow.

Note: If the performance problem is happening when the dump is about to be taken, then if at all possible set the System Option MODE 31=ON, wait 5 minutes, then take the Detailed dump. This could save a lot of time later on. Turn MODE 31 OFF when you have taken the dump.

Other Autodump types are available with USP,NSC,USP-V,USP-VM and should only be collected if instructed by GSC.

IMPORTANT

Before performing dump procedure, check maintenance STATUS and VERSION.

In the case of Mainframe subsystem, also display Main Frame Paths (USP, NSC, USP-V, USP-VM) or Physical Paths (9900, 990V)

Special Instructions when a DETAIL dump is to be collected for Performance Problem troubleshooting:

1. For 9900 and 9900V, be sure to start the SVP Monitor (refer to Monitoring function in SVP MM pages). All items of data are collected internally, regardless of display settings. Choose at least ONE display setting. Choose an interval appropriate to the error condition (ex: "60 sec" interval can collect data for 7 hour period). This step is not required for USP, NSC55, USP-V or USP-VM
2. Turn on System Mode 31 before the testing starts for the problem you are trying to troubleshoot. Mode 31 captures critical trace data related to Host IO performance. Its buffers can wrap after just 60 seconds on a busy port. Thus make sure that the DETAIL dump is taken before the testing is complete - and at a time the problem is being experienced.
3. Open maintenance STATUS and VERSION before starting the dump.
4. If MODE 31 has been turned on, remember to turn it off after the DETAIL DUMP completes. MODE 31 can have a performance impact on some workload types and should not be left on unless specifically requested by GSC.

Sendmail Quick Reference

Tips and Tricks for Sendmail

mailq – Prints the mail queue's contents, same as /usr/lib/sendmail –bp

newaliases – Rebuilds the aliases database file, same as /usr/lib/sendmail –bi

hoststat – Prints persistent host status info, same as /usr/lib/sendmail -bh

purgestat – Purges (zeroes) persistent host status info, same as /usr/lib/sendmail -bH

smtpd – Runs in daemon mode, same as /usr/lib/sendmail –bd –q30

mailq –OmaxQueueRunSize=1 - Quickly print the total number of messages within mail queue

/usr/lib/sendmail –q –Otimeout.queuereturn=99d - Purges the mail queue without timing out any messages. Useful if the mail server has been down longer than the queuereturn value set in the cf.

/usr/lib/sendmail –bv foolist | grep –v deliverable - Prints only undeliverable addresses from in the mail list foolist. Great for use in a shell script to remove badd addresses from a mailing list.

Command Line Switches

-B 7bit - Causes sendmail to clear the high-bit of every incoming byte.

-B 8bitmime – Causes sendmail to preserve the high-bit or every incoming byte.

-ba – Uses ARPAnet/Grey-Book protocols to transfer mail.

-bD – Runs as daemon, like –bd, but does not fork and does not detach from controlling terminal.

-bd – Runs as daemon, forks and detaches.

-bH - Purges (zeroes) persistent host status info.

-bh - Prints persistent host status info.

-bi - Initializes the aliases database.

-bm – Causes sendmail to read and send message (this is the default)

-bp – Prints the contents of the mail queue.

-bs – Runs sendmail on standard I/O.

-bt – Runs sendmail in rule testing mode.

-bv 
 - Verifies address.

-C /tmp/different.cf – Uses different.cf as its configuration file.

-c - Sets HoldExpensive option to true.

-d  - set debug mode.

   * -d0 – Shows general config
   * -d0.1 – Prints version
   * -d.04 – Prints local hostname and any aliases for it.
   * -d0.15 – Prints the list of delivery agents declared
   * -d0.20 – Prints address of each network interface
   * -d8 – Traces most DNS lookups
   * -d8.1 – Prints failure of low level MX searches.
   * -d8.2 – Prints calls to getcanonname
   * -d8.3 - Traces dropped local hostnames
   * -d8.5 – Shows hostnames tried in getcanonname
   * -d8.8 – Shows when MX lookups return the wrong type.
   * -d11 – Traces delivery agent calls
   * -d11.1 – Traces arguments passed to the delivery agent
   * -d11.2 - Prints the user ID that the delivery agent is invoked as
   * -d21 – Traces rewriting of addresses
   * -d21.1- Traces general ruleset rewriting
   * -d21.2 – Traces use of $& macro
   * -d21.3 – Shows $> subroutines called
   * -d21.4 – Displays result of rewrite
   * -d21.15 – Shows $digit replacement
   * -d21.35 – shows token by token LHS matching
   * -d27 – Traces aliasing
   * -d27.1 – Traces general aliasing
   * -d27.2 – Traces :include: files, alias self-references, and errors on home
   * -d27.3 – Traces the ~/.forward path and the alias wait
   * -d27.4 – Prints "not safe" when a file is unsafe to trust
   * -d27.9 – Shows uid/gid changes when reading :include: files
   * -d35 – Traces macros
   * -d35.9 shows macro values as they are defined
   * -d35.14 – Shows macro names being converted to integer id’s
   * -d35.24 – Shows macro expansion
   * -d37 – Traces options and class macros
   * -d37.1 – Traces the setting of options
   * -d37.8 – Traces the adding of words to a class
   * -d41 – Traces the queue
   * -d41.1 – Traces queue ordering
   * -d41.2 – Shows failure to open qf files
   * -d41.49 – Shows skipped queue files
   * -d41.50 – Show every file in queue

-F  - Set senders full name

-f 
 - Set senders address

-h  - Set minimum hop count

-i – Set IgnoreDots option to true

-M - Set macro

-N - Set return DNS notify information

   * never – Never return the info
   * success – Return on successful delivery
   * failure – Return on failure
   * delay – Return on delayed delivery

-n – Supresses aliasing

-O - Set an option (long name)

-o – Set an option (short name)

-pUUCP:test – Sets protocol in $r macro to UUCP and $s macro to test

-q30m – Sets queue processing to every 30 min

-qR@here.com – Processes the queue once delivering only mail to @here.com

-R hdrs – bounces only the headers

-R full – Bounces headers and body

-s – Sets SaveFromLine option to true

-T 5d – Sets Timeout.queuereturn option to 5 days

-t – Gathers a list of recipients from messages headers

-U – make this the initial MUA to MTA submission

-V test123456 – Sets the DSN ENVID string to test123456

-v – Runs sendmail in verbose mode

-X /var/tmp/trace.mail – Logs both sides of smtp transactions to trace.mail file.



Rule Testing Mode (/usr/lib/sendmail –bt)

? – Prints help

.DrUUCP – Defines macro r as UUCP

=S5 – Prints the contents of ruleset 5

=M – Displays list of delivery agents

${name} – Prints the value of macro name.

$=w – prints the contents of the class macro w

/mx here.com – Returns the MX records for here.com in the order they will be utilized

/parse foo – Parses the value of the address foo, returns the value of crackaddr(), and the final parsed address including the delivery agent.

/try local foo – Rewrites the address foo based on the rules for local delivery

/tryflags HS – Sets the flags used by /parse and /try to H for header and S for sender, can also use E for envelope and R for recipient

/canon foo - Transforms the hostname foo into its canonical form

/map aliases foo – Looks up foo in the aliases database

3,0 – me@foo – Runs the address me@foo through rulesets 3 and 0

dim_STAT installation on Solaris 10

DOWNLOAD LINK: http://dimitrik.free.fr

As the root user,
bash-3.00# tar xvf dim_STAT.tar

bash-3.00# cd dim_STAT-INSTALL/
bash-3.00# ls
ExpReport_15.tar.Z LICENSE-GPLv2.txt LICENSE.txt README.sol86 UNINSTALL.txt anySTAT soft
INSTALL.sh LICENSE-freeware.txt README STAT-service UserGuide conf x.install
bash-3.00# ./INSTALL.sh


===========================================
** Starting dim_STAT Server INSTALLATION **
===========================================

HOSTNAME: solten
IP: ::1
DOMAINE:

Is it correct? (y/n): n
** Hostname [solten]: solten
** IP addres [::1]: 192.168.2.222
** Domainname []: admincmd.blogspot.com
**
** ATTENTION!
**
** On your host You have to assign a USER/GROUP pair as owner
** of all dim_STAT modules (default: dim/dim)

User: dim
Group: dim
Is it correct? (y/n): y


**
** WARNING!!!
**
** User dim (group dim) is not created on your host...
** You may do it now by yourself or let me do it during
** installation...
**

May I create this USER/GROUP on your host? (y/n): y


======================================
** dim_STAT Directory Configuration **
======================================

** WebX root directory (5MB):
=> /WebX
=> /opt/WebX
=> /etc/WebX

[/opt/WebX]:


** HOME directory for dim_STAT pkgs [/apps]:
** TEMP directory [/tmp]:

** HTTP Server Port [80]: 999 ** DataBase Server Port [3306]: ** Default STAT-service Port [5000]: 1999
================================================== ** Process... ================================================== => Host : solten => IP address : 192.168.2.222 => Domain : admincmd.blogspot.com => User : dim => Group : dim => WebX root directory : /opt/WebX => HOME directory : /apps => TEMP directory : /tmp => HTTP Server Port : 999 => DataBase Server Port : 3306 => Default STAT-service Port : 1999

Is it correct? (y/n): y


** !!
** !! !!! WARNING !!!
** !! ---------------
** !!
** !! ALL DATA will be DELETED!!! in: /apps/* !!!
** !! as well /WebX, /etc/WebX, /opt/WebX !!!
** !!
Delete all data? (y/n): y




** Cleanup /apps
** Add User...
** WebX Setup...
** dim_STAT Server extract...
** HTTP Server Setup...
** Database Server Setup...
** ADMIN/Tools Setup...
** TEMP directory...
** Permissions...
** Crontab Setup...
Sun Microsystems Inc. SunOS 5.10 Generic January 2005


**
** INSTALLATION is finished!!!
**
May I create now a dim_STAT-Server start/stop script in /etc/rc*.d? (y/n): y
============================================================================
NOTE:
=>
=> Please, set a password to the user dim
=> to enable clean up procedure via cron!..
=>


** =========================================================================
**
** You can start dim_STAT-Server now from /apps/ADMIN:
**
** # cd /apps/ADMIN
** # ./dim_STAT-Server start
**
** and access homepage via Web browser - http://solten:999
**
** To collect stats from any Solaris-SPARC/x86 or Linux-x86 machines
** just install & start on them [STAT-service] package...
**
** Enjoy! ;-)
**
** -Dimitri
** =========================================================================


bash-3.00# cd /apps/ADMIN/ bash-3.00# ./dim_STAT-Server start
================[ dim_STAT-Server: start ]================

*
* MySQL Database Server
*
=> Log output : /apps/mysql/data/mysqld.log.3306
=> Local socket: /apps/mysql/data/mysql.sock.3306
=> Admin Access: root# /apps/mysql/bin/mysql -S /apps/mysql/data/mysql.sock.3306

Starting...
Starting mysqld daemon with databases from /apps/mysql/data
Done.
Starting HTTP server from: /apps/httpd
Done.
================[ dim_STAT-Server: start -- done. ]================



TEST
Config First level security
1) via /apps/httpd/bin/htaccess create /apps/httpd/etc/.htpasswd file and add any pairs of user/password you need
2) create ".htaccess" file with context:

AuthName "Welcome to dim_STAT Host"
AuthType Basic
AuthUserFile /apps/httpd/etc/.htpasswd

require valid-user

3) copy ".htaccess" file into /apps/httpd/home/docs and /apps/httpd/home/cgi-bin
4) try to connect to your web server now and check the access user/password - that's all!

For example:
1) add user/password
bash-3.00# /apps/httpd/bin/htpasswd -c /apps/httpd/etc/.htpasswd dimuser
Adding password for dimuser.
New password:
Re-type new password:

2)create ".htaccess"
bash-3.00# vi .htaccess
Adding....

AuthName "Welcome to dim_STAT Host"
AuthType Basic
AuthUserFile /apps/httpd/etc/.htpasswd

require valid-user

bash-3.00# cat .htaccess

3) copy ".htaccess" to destination
bash-3.00# cp /tmp/.htaccess /apps/httpd/home/cgi-bin
bash-3.00# cp /tmp/.htaccess /apps/httpd/home/docs
bash-3.00# cd /apps/ADMIN
bash-3.00# ./dim_STAT-Server stop
bash-3.00# ./dim_STAT-Server start
4)Login again

Invalid default value for 'logTime'

Process of database restoration using the following SQL query :

CREATE TABLE `smf_log_online` (

SESSION varchar( 32 ) NOT NULL default '',
logTime timestamp default 'CURRENT_TIMESTAMP' ,
ID_MEMBER mediumint( 8 ) unsigned NOT NULL default 0,
ip int( 10 ) unsigned NOT NULL default 0,
url text NOT NULL default '',
PRIMARY KEY ( SESSION ) ,
KEY logTime( logTime ) ,
KEY ID_MEMBER( ID_MEMBER )

) TYPE = MYISAM


There is a massive problem occur, The following message:

" #1067 - Invalid default value for 'logTime' "


For this problem you need to change SQL statement to get it to work following:

remove '' from 'CURRENT_TIMESTAMP' ..

CREATE TABLE `smf_log_online` (

SESSION varchar( 32 ) NOT NULL default '',
logTime timestamp default CURRENT_TIMESTAMP ,
ID_MEMBER mediumint( 8 ) unsigned NOT NULL default 0,
ip int( 10 ) unsigned NOT NULL default 0,
url text NOT NULL default '',
PRIMARY KEY ( SESSION ) ,
KEY logTime( logTime ) ,
KEY ID_MEMBER( ID_MEMBER )

) TYPE = MYISAM

Apache Service error msg: no listening sockets available, shutting down.

if you could not start the apache service and error message in Event v iewer show you that an error occurred.

The Apache service named reported the following error:
>>> no listening sockets available, shutting down .

and

The Apache service named reported the following error:
>>> Unable to open logs

Solutions:
-Web servers accept incoming connections by listening on port 80 by default. Type "netstat -an" from a command prompt. You will see the actual port numbers currently being used by another application.You can change apache port to another port, by editing httpd.conf in the apache folder under conf. and then restart a proccess
for example:

# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
#Listen 80
Listen 888

-Remove comment "#" before "Listen 80" , by editing httpd.conf in the apache folder under conf. and then restart a proccess
for example:

# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 80

The benefits to using VoIP. (PBX)

The benefits to using VoIP.

แน่นอนว่าเทคโนโลยีใหม่ย่อมนำสิ่งที่ดีกว่ามาให้เสมอ สำหรับ VoIP ก็เช่นเดียวกัน ประการสำคัญของประโยชน์ที่ได้รับจาก VoIP คง ต้องเป็นเรื่องการลดค่าใช้จ่ายในการโทรศัพท์ขององค์กรลง ไม่ว่าจะเป็นการโทรในพื้นที่เดียวกันหรือโทรทางไกล แม้กระทั่งการโทรต่างประเทศ ทั้งโทรภายในองค์กรเองหรือโทรติดต่อกับหน่วยงานอื่นๆหรือลูกค้า ล้วนแล้วแต่ได้รับประโยชน์ในเรื่องค่าใช้จ่ายในการโทรศัพท์ทั้งสิ้น ซึ่งประโยชน์ที่ได้รับจากการนำ VoIP มาใช้อาจสรุปประเด็นเป็นข้อๆ ได้เช่น

1. ลดค่าใช้จ่าย (Cost Savings) ใน การติดต่อสื่อสารทางโทรศัพท์ลง เนื่องจากเสียงได้ถูกเปลี่ยนให้อยู่ในรูปแบบเดียวกับข้อมูล จึงทำให้สามารถส่งสัญญาณเสียงไปในเครือข่าย LAN หรือ WAN ได้เลย ไม่ต้องผ่านเครือข่าย PSTN ที่มีค่าใช้จ่ายสูงกว่า

2. เพิ่มความยืดหยุ่นในการติดต่อสื่อสารให้กับองค์กร เช่น ในสาขาหรือ Siteงานชั่วคราว สามารถนำ VPN ร่วมกับ VoIP ประกอบกันเพื่อสร้างระบบการติดต่อสื่อสารเต็มรูปแบบภายในองค์กรได้อย่างง่ายดายและรวดเร็ว

3. จัดการ ระบบเครือข่ายได้ง่ายขึ้น เนื่องจากเครือข่ายการติดต่อสื่อสารทั้งหมด สามารถยุบรวมกันให้เหลือเพียงเครือข่ายเดียวได้ อีกทั้งในกรณีที่มีการโยกย้ายของหน่วยงานหรือพนักงาน การจัดการด้านหมายเลขโทรศัพท์และอื่นๆ สามารถทำได้โดยไม่จำเป็นต้องเดินสายสัญญาณใดๆขึ้นมาใหม่

4. รองรับการขยายตัวของระบบในอนาคต หากในอนาคตองค์กรขยายตัวใหญ่ขึ้น VoIP สามารถรองรับผู้ใช้งานได้เพิ่มมากขึ้นในทันทีโดยการเพิ่ม "Virtual" User เข้าไปในระบบเท่านั้นเอง
5. ลดค่าใช้จ่ายในการดูแลและจัดการระบบ (Reduce Operating Expenses) เนื่องจากใช้ซอฟต์แวร์ในการจัดการ ทำให้ VoIP นั้นง่ายในการจัดการและบำรุงรักษา
6. เพิ่มประสิทธิภาพการทำงาน (Increase Productivity) พนักงานสามารถส่งเอกสารผ่านเครือข่ายควบคู่ไปกับการสนทนา หรืออาจจัดการประชุมออนไลน์(Conference Call) ทั้งภาพและเสียง และแม้กระทั่งส่งเอกสารการประชุมให้กับผู้เข้าร่วมประชุมผ่านทางเครือข่ายได้อีกด้วย
7. ใช้ร่วมกับการสื่อสารไร้สายได้ ทำให้อุปกรณ์สื่อสารไร้สายต่างๆ เช่นโทรศัพท์มือถือหรือPDA สามารถติดต่อผ่าน VoIP เข้ามาในเครือข่ายขององค์กรได้
8. เพิ่มประสิทธิภาพในการติดต่อกับลูกค้า (Improved Level of Services) โดยใช้ความสามารถของแอพพลิเคชั่นต่างๆ ของ VoIP เช่น "Click-to-talk" เพื่อเพิ่มความสะดวกและรวดเร็วในการติดต่อกับลูกค้า

ตัวอย่าง Application การใช้งานเทคโนโลยี VoIP

1. PBX to PBX Connection
• ทั้ง 2 ฝั่งของสำนักงานจะสามารถใช้งานตู้สาขา PBX ของสำนักงานอีกฝั่งเปรียบเสมือนตู้สาขา PBX ของฝั่งตัวเอง
• Users ภายในไม่จำเป็นต้องทำการ Dial-out ออกไปบนระบบโทรศัพท์ PSTN เพื่อทำการเชื่อมต่อเข้ากับตู้สาขา PBX ของสำนักงานอีกฝั่ง

2. Long Line PBX Extension
• เป็นการเชื่อมต่อที่สำนักงานใหญ่ขยายการเชื่อมต่อตู้สาขา PBX ไปที่สำนักงานสาขาที่ไม่มีตู้ PBX ใช้งานอยู่
• ทางสำนักงานสาขาสามารถใช้งานตู้ PBX ผ่านทางสำนักงานใหญ่ได้เสมือนกับเป็นตู้สาขา PBX ของฝั่งตนเอง

3. Teleworker/ Local Access
• เป็นการเชื่อมต่อที่ยินยอมให้ Remote User ฝั่ง สำนักงานใหญ่สามารถใช้งานโทรศัพท์เข้ามาที่สำนักงานใหญ่ แล้วใช้ระบบเครือข่ายของสำนักงานใหญ่เชื่อมต่อไปยังสำนักงานสาขาผ่าน เทคโนโลยี VoIP เพื่อสามารถใช้งานโทรศัพท์ในพื้นที่ของสำนักงานสาขาได้โดยเสียค่าบริการในอัตราของพื้นที่ของสำนักงานสาขานั้นๆ

4. Service Provider CPE
• ผู้ให้บริการต่างๆ เช่น... ISP สามารถที่จะเสนอบริการเสริมต่างๆ ทางด้าน VoIP
บนระบบเครือข่ายความเร็วสูงที่มีการใช้งานอยู่เดิมแล้ว

จากที่ได้กล่าวมาแล้วทั้งหมด... เป็นการแนะนำให้ทราบถึงเทคโนโลยี VoIP และการนำเทคโนโลยี VoIP มาประยุกต์เพื่อใช้งานได้มากยิ่งขึ้น



ที่มา: http://www.vcharkarn.com/include/article/showarticle.php?Aid=17875&page=4

STARTUP/SHUTDOWN GLASSFISH ADMIN SERVER

The ‘asadmin’ utility is used to perform several administrative tasks on the Application Server. The server life cycle commands such as ‘start-domain’ is used to start the domain named domain-1 and ‘stop-domain’ is used to stop the Administration Server of the domain-1.

How to start?

log in as root:

#cd /www/opt/SUNWappserver/bin

#./asadmin start-domain domain1

#./asadmin start-node-agent

Starting Domain domain1, please wait.

Log redirected to ..........\domain1\logs\server.log.

Redirecting output to ..........\domains\domain1\logs\server.log

Domain domain1 started.

Domain [domain1] is running [Sun Java System Application Server 9.1_01 (build b09d-fcs)] with its configuration and logs at: [.......\domains].

Admin Console is available at [http://localhost:4848].

Use the same port [4848] for "asadmin" commands.

User web applications are available at these URLs:

[http://localhost:8080 https://localhost:8181 ].

Following web-contexts are available:

[/web1 /__wstx-services jpa-example ].

Standard JMX Clients (like JConsole) can connect to JMXServiceURL:

[service:jmx:rmi:///jndi/rmi://rajus01-755:8686/jmxrmi] for domain management purposes.

Domain listens on at least following ports for connections:

[8080 8181 4848 3700 3820 3920 8686 ].

Domain supports application server clusters and other standalone instances.

How to stop?

#cd /www/opt/SUNWappserver/bin

#./asadmin stop-node-agent

#./asadmin stop-domain domain1

Domain domain1 stopped.