iApp suitable for a new deployment...

Brent

Thank you for the in-depth response...

Will try and run through each of your q's in turn...

Currently, each URL is using it's own VIP, which is using a unique IP.

A config extract looks like:

ltm virtual Common/cms.wokingham.card.co.uk {
    description "Application A BackOffice"
    destination Common/172.16.26.2:https
    ip-protocol tcp
    mask 255.255.255.255
    persist {
        Common/cookie {
            default yes
        }
    }
    pool Common/applicationapool
    profiles {
        Common/HTTP_Rewrite { }
        Common/analytics { }
        Common/application_a_ssl {
            context clientside
        }
        Common/tcp { }
    }
    rules {
        Common/Catch_Errors
        Common/AccessLogging
        Common/Header_Stripping
    }
    snat automap
    vlans-disabled
}
ltm pool Common/applicationapool {
    members {
        Common/applicationanode:webcache {
            address 10.0.0.68
            session monitor-enabled
            state up
        }
    }
    monitor Common/tcp
}
ltm node Common/applicaitonanode{
    address 10.0.0.68
    session monitor-enabled
    state up
}

A) This iApp would be purely for our usage... no requirement for customer access.

B) I would foresee several templates, one for each app... Is it possible for app's to share resources? As potentially we could have one node which serves multiple app's, and I wouldn't like to duplicate where don't have to...

I'd agree that a more modular approach would be suitable, however would query how we apply an update to multiple applications in one hit... e.g. enabling caching, or adding an iRule...

Overall, it's looking like iApp's might be the right approach...

And thanks again for your pointers...

Regards

Gavin