Information Technology Blog

Posts Tagged ‘Level’

Cloud computing is

education level

The winner is not surprising that personal education in the clouds is a necessary tool for many businesses and even schools. With this type of calculation, not with others, such as grid computing, utility computing or autonomic computing can be confused. Even if you are not absolutely familiar with cloud computing you are in any case, they use regularly, such as personal applications such as Skype. The interesting part about cloud computing is that entire systems can be implemented on a rental basis. The project infrastructure and access tools and applications can be used in place of the most frequently rented from these companies and projects are executed.

The economy

“Cloud Computing” With the economy spiraling downward already cut their IT budgets, education can cloud computing is the answer to many problems, financial problems, particular computer. Many critics are wondering if this type of computing system really work in the long run, losing momentum as it promises a swift solution to a weak economy or if it as any other calculations. Regardless of the hype that was assumed in creating this new system, it is true that Cloud is another form of calculation, what most people like the social networking sites like Facebook and MySpace, e-mail systems like Hotmail, E Business-mail filtering and monitoring of security itself is used. These are all forms of cloud computing.

What are the benefits of cloud computing to education?

It is not surprising that students are in a binding. Not only do they have on student loans and the purchase of books concerned, but they spend hundreds of dollars on software to prevent their duties fully and that their personal do not present them. In this sense, cloud computing grants personal users to form the desired applications without having to purchase the software, use the frustration of the military installation or the host personal memory with software. With platforms for different clouds, such as Software as a Service Infrastructure as a Service and Platform as a Service, Cloud Computing is possible.

Considering the money saved by these cloud applications speculate further that the biggest advantage that cloud computing to the upbringing of their economic factor. Instead of buying software and infrastructure, rents, how often and how many services are intended to be used. All software and files on a remote host personal to free up disk space, while, at any time on the World wide web grants users stored. Given the amount of resources, the supply of cloud computing, users can easily find any type of infrastructure, services or software they need. This helps reduce costs for schools or any organization or company that cloud computing applications, these organizations no longer have to be cut to purchase costly software for a single mortal or a limited number of small staff and students.

Many experts in the IT industry believe in education cloud computing and the benefits they can offer to millions of personal users on a regular basis. However, only time will tell if this calculation is the system will be a success in the world of computing.

I have been working in FIX prescript for nearly 5 years when I started working on FIX prescript I looked upon world wide web for some good tutorial which could supplement or complement lengthy FIX prescript specification there was nothing at that time so when I started my blog I thought to write about my own experience in FIX prescript as short, clear and concise tutorial format. Since I like question answer type of knowledge sharing too I have written some blog post on FIX prescript Interview questions you might find it interesting.

In today’s FIX tutorial we are going to have a look on FIX prescript session level messages. As you guys might know all FIX messages can be broadly classified in two categories Admin messages also called session level messages and Application messages which include Trade, pre trade and post trades messages.  Understanding of how FIX session works is very important because until you know the fundamental of FIX Sequence number, how does FIX session gets connected , what are the sequence of messages that flows between Sender Fix Engine and receiver FIX engine you won’t be healthy to swiftly refer any problem related to FIX protocol.  FIX specification is very clear about what should FIX engine do on various FIX session connection / disconnection scenario.

Just to revise as per FIX prescript first Sender FIX Engine and receiver FIX engine connects to apiece other on TCP/IP prescript on specified IP and Port via leased line , Radianz link , Virtual Private network(VPN) or via internet. Once TCP Socket level connectivity established Sender application sends Logon (fix attach 35=A MsgType=A) with concurred SenderCompID (fix attach 49) and TargetCompID (fix attach 50). Receiver FIX engine receives this message and authenticate Sender FIX Engine client based upon SenderCompID (fix attach 49) and TargetCompID (fix attach 50) ,if client is genuine successfully then receiver fix engine replies with same sends Logon (fix attach 35=A) message and connection is successfully established and then both FIX engine will send Heartbeat messages (fix attach 35=0) at specified  heartbeat interval to keep connection alive. In case receiver FIX engine is not healthy to authenticate client it will send a Logout message (fix attach 35=5) and connection will be terminated though socket connection will still be there. Receiver FIX engine can also send Logout message (fix attach 35=5) if it receives fix message with sequence number lower than it is expecting.

Now let’s see apiece of session level or Admin messages in tiny detail. You can always refer FIX prescript specification document and that is suggested also to get complete description of apiece of these messages.
Some important Session level or Administrative messages specified in FIX specification are following:

Heartbeat:
Heartbeat messages are denoted by MsgType=0 in financial information exchange (FIX) Protocol. Both FIX Session Initiator and FIX Session Acceptor sends apiece other Heartbeat messages to keep FIX session alive on a interval defined by Heartbeat Interval which is usually 30 or 60 seconds. If you see Heartbeat message (FIX attach 35=0) in your FIX Engine log file means your FIX session is up and connected.

Logon:
Logon message is denoted by FIX attach 35=A and it is used to send login message from FIX initiator. As per FIX Protocol once TCP connection between FIX Initiator and FIX Acceptor got established, FIX initiator sends Logon message (tag 35=A) with pre concurred SenderCompID (tag 49) and TargetCompID (tag 50) and with Sequence No (FIX attach 34) anticipating by FIX Acceptor. When FIX Acceptor receives Logon request (MsgType=A) it authenticate FIX session based on CompID specified in FIX Message and Sequence No and reply back with either Logout (tag 35=5) message or Logon(tag 35=A)  message based upon result of authentication.

 

Resend Request
Resend Request (FIX attach 35=2 or MsgType=2) is used for asking of retransmission or replay of lost messages during transmission or due to incorrect sequence number. It’s normally sent by the FIX Engine which is receiving message to initiate the retransmission of messages. FIX Engine uses Resend Request (tag 35=2) if a sequence number gap is detected or if FIX Engine of receiving application lost a message or as a part of initialization process to make sequence number in sync.

Resend Request (FIX attach 35=2 or MsgType=2) can be used to request a single FIX message, a range of FIX messages or all FIX messages subsequent to a particular FIX message.

Its worth noting that sending FIX Engine might like to think about the message type when resending messages; e.g. if a new order is in the resend series and a significant time period has been passed since it was originally sent, the sender FIX Engine might not wish to retransmit the order since market dynamics an price etc might have been changed also this might result in stale order reject which is done by Order Management Systems (OMS). (The Sequence Reset (FIX attach 35=4 or MsgType=4) Also called as Gap Fill is used to skip FIX messages that a sender FIX Engine does not want to resend.)

 

It is mandatory that the receiving FIX Engine process messages in sequential order, e.g. if FIX message number 11 is missed and 12-13 received, the application should ignore 12 and 13 and ask for a resend of 11-13, or 11 -0 (0 denotes infinity). Second approach is strongly suggested to recover from out of sequence conditions as it grants for faster recovery in the presence of certain race conditions when both sides of FIX Engines are simultaneously attempting to recover a sequence number gap.

Test Request
In financial information exchange also called FIX Protocol Test Request is denoted by FIX attach 35=1 or MsgType=1. Test Request FIX Message is used by FIX Engine to forces a heartbeat from the opposing FIX Engine. The Test Request (FIX attach 35=1) message checks sequence numbers or verifies communication line status. The opposite FIX Engine responds to the Test Request Test Request (FIX attach 35=1) with a Heartbeat (FIX attach 35=0) containing the TestReqID (FIX attach 112).

The TestReqID FIX attach 112) verifies that the counterparty FIX Engine is generating the Heartbeat (FIX attach 35=0) as the result of Test Request (FIX attach 35=1) and not a normal timeout. The opposite FIX Engine includes the TestReqID (FIX attach 112) in the resulting Heartbeat (FIX attach 35=0). Any string can be used as the Heartbeat (FIX attach 35=0) (Some fix engine generally uses a timestamp string).

 

Session Level Reject
In financial information exchange (FIX) prescript Session level Reject or  Reject  message is denoted by FIX attach 35=3 or MsgType=3.  Session level Reject is used by FIX engine when a fix message is received but can't be properly processed due to a session-level rule violation as specified in FIX Protocol specification document. As an example FIX Engine will use Session level Reject or a reject it receives a FIX message with invalid basic data (e.g. MsgType 35 =$ ) which successfully passes de-encryption, Checksum (FIX attach 10) and BodyLength (FIX attach 9) checks. As a rule FIX messages should be forwarded to the trading application for business level rejections whenever possible.

Rejected messages should be logged into log file and the incoming sequence number must be incremented by FIX Engine.

 

Its worth noting that receiving FIX Engine  should disregard any FIX message which  is incorrect , can't be parsed or fails a data integrity check. Processing of the next valid FIX message will cause detection of a sequence number mismatch and a Resend Request (FIX attach 35=2 or MsgType=2) will be generated and passed to counterparty FIX Engine.

Generation and receipt of a Reject (FIX attach 3) message indicates a serious error that might be the result of faulty logic in either the sending or receiving FIX Engine.

If the sending FIX Engine chooses to retransmit the rejected message, it should be assigned a new sequence number (FIX attach 34) and sent with PossResend (FIX attach 97) =Y.

Its recommended  to describe the cause of reject in the fix tag  Text (FIX Tag 58)  which then can be used by receiving FIX engine or developer to refer actual cause of Session level reject  (e.g. Price attach is missing in Limit Order).

 

Below are some scenarios where session-level Reject (FIX Tag 3 or MsgType=3) can be used.

CompID problem: Either FIX Initiator or FIX Acceptor is sending incorrect SenderCompID (tag 49) and TargetCompID (tag 50).

Invalid MsgType: Either FIX initiator or FIX Acceptor is sending MsgType other than specified in FIX Specification for that particular FIX Version e.g. FIX4.2

Incorrect data format for value: If a FIX attach has a data type Timestamp and FIX engine is sending some other data type

Required attach missing: Either FIX Initiator or FIX Acceptor is not sending mandatory FIX attach in a particular FIX message e.g. Price (FIX attach 44) missing in a NewOrderSingle (MsgType=D) message with OrdType =2 i.e. Limit Order.

Invalid attach number: Either FIX initiator or FIX Acceptor is sending any attach other than specified in FIX Specification for that particular FIX Version e.g. FIX4.2

Tag not defined for this message type: Either FIX initiator or FIX Acceptor is sending any attach other than specified in FIX Specification for that particular message type e.g. Sending TestReqID in logout message.

Undefined Tag: In case any of sender FIX engine is sending custom attach and that is not configured or supported by Revenging fix engine.

Tag specified without a value: e.g. 35= and there is no value for that particular fix tag. Its not a valid fix message and so receiving fix engine will reject it.

 

Sequence Reset
Sequence Reset also called as Gap fill messages is denoted by FIX attach 35=4 or FIX MsgType 35=4. It is used in response to Resend Request (FIX attach 35=2 or MsgType=2) by sending FIX engine to reset the incoming sequence number on the opposing side FIX engine. Sequence Reset message (fix attach 35=4) operates in two different modes one in which GapFillFlag (FIX attach 123) is ‘Y’ also called Sequence Reset – Gap Fill and second mode on which GapFillFlag (FIX attach 123) is ‘N’ or not present also called Sequence Reset – Reset mode. As per FIX prescript specification the “Sequence Reset (fix attach 35=4)-Reset” mode should ONLY be used to recover from a disaster situation which can't be otherwise recovered by “Gap Fill” mode.

 

The Sequence Reset or GapFill message (fix attach 35=4) can be useful in the following circumstances:

1. While processing Resend Request (FIX attach 35=2 or MsgType=2) sending FIX Engine might select not to send a message (e.g. a stale order). The Sequence Reset (fix attach 35=4) – Gap Fill can be used to fill the place of that message.

2. While processing Resend Request (FIX attach 35=2 or MsgType=2) sending FIX Engine might select not to send a message if all the messages are only administrative or session level messages, because there is no point on resending them in that case also Sequence Reset (fix attach 35=4) – Gap Fill is used to fill the message or sequence gap.

Logout
Logout message is denoted by FIX attach 35=5 or MsgType=5 in FIX prescript specification and it is used to terminate or close any FIX session. In case receiver FIX engine is not healthy to authenticate client it will send a Logout message (fix attach 35=5) and connection will be terminated though socket connection will still be there. Receiver FIX engine can also send Logout message (fix attach 35=5) if it receives fix message with sequence number lower than it is expecting. The Logout message (fix attach 35=5) is used to terminate a FIX session. Termination or disconnection without the exchange of Logout message (fix attach 35=5) messages is treated an abnormal condition.

Exchange of Logout message (fix attach 35=5) before actually terminating or closing the session grants the initiator FIX engine to perform any kind of Sequence Reset (fix attach 35=4) or Gap fill operations that might be required or necessary. Logout initiator should also move for the opposite FIX engine to respond with a confirming Logout message (fix attach 35=5) it can terminate the session in case the remote FIX Engine does not respond within a specified time period.

 

To read more about FINANCIAL INFORMATION EXCHANGE (FIX) protocol, see my FIX Protocol tutorial series.

Find more Data Admin related articles from search form.

One of President Obama’s major initiatives will be to bring the US health care system into the 21st century.     Our lagging health care infrastructure has lead to big medical inefficiency, high premiums to the average citizen and an overall ‘leaky faucet’ effect that is contributing to the pool of problems our economy faces.   The Obama administration has proposed a five year, near $100 billion dollar, initiative to fix our health care system through innovative new technology that includes creating electronic versions of all health records.

Although creating electronic health records is a large step in ‘leveling up’ our health care system to meet modern day information technology standards, there is also the less celebrity concept of implementing high-tech network technology towards health care.     It will be one thing for physicians and patients to have access to medical data, and another for them to communicate that data.

From the Cisco System’s blog:

“Web 2. 0 technologies are beginning to change the practice of medicine,” states Lynne A. Dunbrack, program director for Health Industry Insights a market research and advisory firm in Framingham, MA. “We now have a significant number of physicians who grew up with the Internet, and they want to use online collaboration technology to keep up with the relentless demands for ever-greater speed and efficiency. “

Medical communication technology still needs to catch up to the rest of the Web 2. 0 technology , whether it be the capability for patients to easily browse a number of potential physicians or primary care facilities, or the functionality to grant a physician to instantly access and update a patient’s records via their iphone.   Even though medical technology has advanced in leaps and bounds as far as its primary purpose- diagnosing and repairing patients, it still needs to embrace a new wave of communication and network technology.

This might be a difficult task.   One barrier to the health care stimulus’ task of digitzing records is simply physicians and medical specialists are used to the old way of doing things.   It can be extremely difficult to fully transition from the paper to digital world because it is a 180 degree change in the every-day routine and process of the work.   The same goes for embracing new health care networking and communication technologies.

However, the advantages to utilizing these new technologies will far outweigh the hurdles of changing old ways.   Cutting-edge video conferencing can grant multiple specialists to collaborate and diagnose on a level never before possible.      ‘Medical-networking’ platforms can grant for patients to easily communicate with their doctor’s and nurses on a individualized level, but prevent over-inundation of the acquirable medical resources.

The first step to leveling up our health care system is for the medical community to change their mindset, and realize that any significant change for the good requires crossing a number of hurdles.   The second step is rewiring and revamping the hardware and network infrastructure of medical facilities crossways the country.   The barrier to entry here is the enormous cost and risk for both public institutions and private practices to make the digital leap of faith.   There are ways to soften this blow as well.

Large network providers, like Cisco Systems and Juniper networks, can aid public medical institutions by providing the necessary network hardware infrastructure in bulk.    Private practices are scared of technological change because it seems like a risk (and investment) that could set them back some years, or worse, sink their business.    However, some of the costs that private medical institutions and practices will incur can be lowered by purchasing used network hardware and personal equipment, such as a used router or refurbished server.

Although costly, if US medical institutions change their mindset and network infrastructure, it will place us well on our way to 21st century health care.