learn unix and linux commands

Mastering SOA: Exposing Services Through Rich User Interfaces


 
Thread Tools Search this Thread
# 1  
Old 09-11-2008
Mastering SOA: Exposing Services Through Rich User Interfaces

In this new installment to the "Mastering SOA" series, learn best practices for rich interface development in an SOA, based on the experiences of Collect America.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script to Start services based on dependent services on other AIX machine

Hi, I just started working on a script. After my research, i found a command which can help me: AIM: To build a script which starts the services (Services 1) on server 1 automatically whenever its down. And it has a dependency on other service (Service 2) on Server 2. So my script has to... (4 Replies)
Discussion started by: draghun9
4 Replies

2. Solaris

Interfaces and Virtual-interfaces queries

Hi Al, In course of understanding networking in Solaris, I have these doubts on Interfaces. Please clarify me. I have done fair research in this site and others but could not be clarified. 1. In the "ifconfig -a" command, I see many interfaces and their configurations. But I see many... (1 Reply)
Discussion started by: satish51392111
1 Replies

3. Solaris

Boot on single user mode with net services

Hi everybody, I'm running soalris 10, and I would like to know if it posible to boot on single user mode(init s), and then set up (may be manually or not) all the networks services, did someone try this before?? Tks (4 Replies)
Discussion started by: jespada
4 Replies

4. Shell Programming and Scripting

shange user's pass for all services on a remote host

here is the picture: a website on server1 & a "username" logged in that site. The same username has a shell(nologin)/ftp/samba/mail(qmail) acount on server2. i have s form on server1 that can pass the username & its NEW password to a sript that should change all passwords on server2. the... (5 Replies)
Discussion started by: veskonedev
5 Replies
Login or Register to Ask a Question
Net::Nslookup(3pm)					User Contributed Perl Documentation					Net::Nslookup(3pm)

NAME
Net::Nslookup - Provide nslookup(1)-like capabilities SYNOPSIS
use Net::Nslookup; my @addrs = nslookup $host; my @mx = nslookup(type => "MX", domain => "perl.org"); DESCRIPTION
"Net::Nslookup" provides the capabilities of the standard UNIX command line tool nslookup(1). "Net::DNS" is a wonderful and full featured module, but quite often, all you need is `nslookup $host`. This module provides that functionality. "Net::Nslookup" exports a single function, called "nslookup". "nslookup" can be used to retrieve A, PTR, CNAME, MX, NS, SOA, and TXT records. my $a = nslookup(host => "use.perl.org", type => "A"); my @mx = nslookup(domain => "perl.org", type => "MX"); my @ns = nslookup(domain => "perl.org", type => "NS"); my $name = nslookup(host => "206.33.105.41", type => "PTR"); "nslookup" takes a hash of options, one of which should be term, and performs a DNS lookup on that term. The type of lookup is determined by the type argument. If server is specified (it should be an IP address, or a reference to an array of IP addresses), that server(s) will be used for lookups. If only a single argument is passed in, the type defaults to A, that is, a normal A record lookup. If "nslookup" is called in a list context, and there is more than one address, an array is returned. If "nslookup" is called in a scalar context, and there is more than one address, "nslookup" returns the first address. If there is only one address returned, then, naturally, it will be the only one returned, regardless of the calling context. domain and host are synonyms for term, and can be used to make client code more readable. For example, use domain when getting NS records, and use host for A records; both do the same thing. server should be a single IP address or a reference to an array of IP addresses: my @a = nslookup(host => 'example.com', server => '4.2.2.1'); my @a = nslookup(host => 'example.com', server => [ '4.2.2.1', '128.103.1.1' ]) By default, when doing CNAME, MX, and NS lookups, "nslookup" returns names, not addresses. This is a change from versions prior to 2.0, which always tried to resolve names to addresses. Pass the recurse => 1 flag to "nslookup" to have it follow CNAME, MX, and NS lookups. Note that this usage of "recurse" is not consistent with the official DNS meaning of recurse. # returns soemthing like ("mail.example.com") my @mx = nslookup(domain => 'example.com', type => 'MX'); # returns soemthing like ("127.0.0.1") my @mx = nslookup(domain => 'example.com', type => 'MX', recurse => 1); SOA lookups return the SOA record in the same format as the `host` tool: print nslookup(domain => 'example.com', type => 'SOA'); dns1.icann.org. hostmaster.icann.org. 2011061433 7200 3600 1209600 3600 TIMEOUTS
Lookups timeout after 15 seconds by default, but this can be configured by passing timeout => X to "nslookup". DEBUGGING
Pass debug => 1 to "nslookup" to emit debugging messages to STDERR. AUTHOR
darren chamberlain <darren@cpan.org> perl v5.12.4 2011-08-15 Net::Nslookup(3pm)