>>Almost, tears are coming out of my eyes.
Believe me, though you made some minor mistakes unknowingly, which I'll describe later, but still you weren't that bad. I REALLY MEAN IT. I understand the situation in which you are in, but you have to know that such issues happen and are pretty common in this industry. Speak to any of your friends or colleagues and check if they had only good professional experiences. I'm sure most of them would comeup with the tough times they had gone through at some point or the other.
By facing such experiences , you keep on learning and that makes you a better person day by day. May be after a year, if you recollect this situation you feel good about the way you might have handled it or how you would have handled in a better manner.
Don't forget the fact that you are atleast good, though may not be the best. If the onsite people were so capable of doing things by themselves then you wouldn't have got an onsite opportunity ;-) This by itself is a clear indicator that you were needed at the client's place.
From understanding, there seem to be mistakes at both the ends (i.e. client and you). The client did not clearly communicate to you. They should have told you that you were the ONLY person responsible for the deployment.
Now coming to your end, there are a few here as well
>> I understood as much as I can and took all the documents from her and then she left the company.
1. That implies you didn't try things on a
test or a dummy environment and you just relied on documentation. Generally, that never helps. Understanding the documentation is the primary part but that never completes the knowledge transfer (and that too in client's place).
>> Deployment is messy and I haven't involved in production deployments before, so this happend since I am very new here.
2. You know that you are new but the client would never be ready to accept this reason and they would say the knowledge transfer was meant for that.
>> I didn't realized that guy with 3+ years of experience working in Singapore needs assistance in fixing HTML issue provided a solution.
3. You could have put it in a better way i.e. explaining what really happend. (One of my team member (he is also new employee) coming to me again and again asking me to give some work to him so that he can also learn. I shared some of my HTML stuff with him.)
>> One month time is very short to fully understand the project and for doing production deployments.
4. For certain they would ask you why you didn't say this during or atleast after the knowledge transfer. Probably you over committed yourself.
Again let me repeat, if you don't make mistakes you have no way to learn and know "Even homer sometimes nods"
At any point of time don't over commit yourself. Saying "No" or "It cannot be done in the given timeframe" is not a bad idea - This is one of the fantastics suggestions that I got from one of my managers.
At any point of time, if you are not clear or you don't fully understand things then escalate or speakup (which I'm working hard to learn).
Hope these indicators help you.
Work is work and family is family. Once you leaver office don't think about work unless you receive a phone call (from office) and have fun with your family during the week-end. That would help you in giving your best on Monday :-)
That is all what I have to share and have a nice week-end.
) used to build the system. Its an expensive portal framework where developers have to write JSPs and some of these JSPs needs to be uploaded to portal. 
