Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: CEP in 2011 and Beyond....
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News CEP in 2011 and Beyond.... Post 302479381 by Linux Bot on Friday 10th of December 2010 01:00:01 PM
Old 12-10-2010
CEP in 2011 and Beyond....
John Bates
12-10-2010 01:52 PM
As we approach the end of 2010 and we begin to see a tiny crack of light at the end of the financial crisis tunnel, there are many theories as to which technologies will lead us into the next phase of advancement in financial markets. Stubborn issues with latency, high frequency trading, real-time risk management, and market gaming/fraud continue to dog the industry and provide fertile ground in which new and existing technologies can innovate. In fact, technology consultancy Ovum said in its 2011 Trends to Watch report for financial markets (http://tinyurl.com/2vv42sh) noted thatComplex Event Processing is one technology to watch. 

CEP will be the lifeblood for financial services as regulation increases, markets further fragment, and algorithmic trading becomes engrained in all asset classes. A recent Progress Software survey across industries showed that only eight per cent of enterprises globally are able to report business information in real-time. Without instant visibility into business activity organisations cannot possibly determine what is or is not working and then set the right course of action.

In financial markets, in particular, a lack of visibility between exchanges, ECNs, dark pools, brokers, banks, buyside and trading firms is causing breakdowns in the system. When you see increasingly frequent events setting markets on their ear such as the May 6th flash crash, insider trading activity, fat fingered errors and rogue algorithms, it becomes crystal clear that something needs to be done. 

Progress, with its Apama products, is committed to financial markets along with other, newer markets such as aviation and telecommunications that are opening up to CEP. If you would like further information about the future of CEP and would like to speak to one of the two founders of Progress Apama- yours truly or my colleague Dr. Giles Nelson-then please contact us. 

 



Source...
 

LEARN ABOUT OSF1

iptunnel

iptunnel(8)						      System Manager's Manual						       iptunnel(8)

NAME

       iptunnel - Creates, deletes, and displays configured tunnels

SYNOPSIS

       /usr/sbin/iptunnel  [operation] [args]

DESCRIPTION

       The  iptunnel  command creates configured tunnels for sending and receiving IPV6 or IPV4 packets that are encapsulated as the payload of an
       IPV4 datagram.

       The iptunnel command can perform one of the following operations: Creates a tunnel interface, which  you  must  subsequently  configure	by
       using the ifconfig command. The syntax of the create operation is as follows:

	      iptunnel create [-I int-name] [v4-dest] [v4-src]

	      Specifies  the  interface unit of the tunnel to be created. This is an optional parameter.  The int-name parameter has the following
	      form: iptx, where x is the interface unit number. By default, the interface name selected for the tunnel is iptx+1, or the value	of
	      the  interface  unit  number  of the last tunnel created plus 1.	Specifies the remote end-point to which a tunnel is to be created.
	      Sets the IPV4 source address in the encapsulating header.  The tunnel is enabled (packets are sent/received on the tunnel)  only	if
	      v4-src  is  a valid address on the system.  This is an optional parameter.  Deletes a tunnel interface.  You must disable the tunnel
	      before you can delete it by executing the following command: # ifconfig tunnel name down	delete abort Shows the	tunnel	attributes
	      (name, tunnel end points, next hop for tunneled packets).

EXAMPLES

       To create a tunnel from hobbes to calvin, enter: # iptunnel create -I ipt5 calvin  ipt5  iftype 208 src 16.140.16.86 dst 16.140.16.91

       To display the tunnel attributes, enter: # iptunnel show ipt5 interface ipt5 src 16.140.16.86 dst 16.140.16.91 gate 16.140.16.86 To config-
       uring the tunnel to encapsulate IPv6 packets, enter: # ifconfig ipt5 ipv6 up

	      IPv6 packets will be sent as payloads of IPv4 datagrams from 16.140.16.86 to 16.140.16.91.

	      The tunnel may also be used to send IPV4 packets encapsulated within IPV4 headers as follows: # ifconfig	ipt5  10.10.80.60  netmask
	      255.255.255.0

	      To verify the previous command, enter: # ifconfig ipt5 ipt5: flags=4c1<UP,RUNNING,NOARP,MULTICAST>
		   16.140.16.86 --> 16.140.16.91
		   rxmt 1000, reach time 30000, dad tries 1, mtu 1280, hops 64, token len 64
		   inet 10.10.80.60 netmask ffffff00  ipmtu 1280
		   inet6  fe80::108c:1056  To  deleting the tunnel, enter: # ifconfig ipt5 down delete abort ipt5: delete inet address 10.10.80.60
	      10.10.80.60: aborting 0 tcp connection(s)

	      Then, enter: # iptunnel delete ipt5 interface ipt5 deleted

SEE ALSO

       Commands: ifconfig(8).

       RFC 2003, IP Encapsulation within IP, Perkins, C., October 1996

																       iptunnel(8)
All times are GMT -4. The time now is 07:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy