jrun or not jrun....

Hey guys.... so i have been a lame cfadmin for quite a while, and now i am trying to get back on horse...

here is a story, we moved to coldfusion8, which continue to run our completely disorganized application. my goal is to finally stop it and move toward good way with proper deployments and etc.... however every time i come back to get deep in coldfusion, i hit the same stones, which seem make sense to me after lot's of readings, yet - a week later i get all confused again..

so may be some one can point me in the good documentation, that explain all this in the plain english.

my frustrations are...

coldfusion or jrun!? to my knowledge, using jrun you can run bunch of coldfusion instances.

however then there are 2 places to administer them... one via jrun another via coldfusion admin interface, which are seem to have similar things but yet totally differnet

then application level... one way just to add mapping and point to your folder that has a cfm code, another way is to create a real/proper cfm application and then deploy it.

neither way, is clearly documented,  or has a straght forward way of doing general things of delaing with diferences betwen jrun or coldufsion. it is all seem very very flexible and overlapping that make me go nuts

seriously.... is this documented anywhere in a plain english version ? just like let's say apache - there is pretty much ONE way to do stuff is there similar approach to  coldfusion/jrun ?

thanks to all, and please forgive for this lame post.

kiryl