I've asked BMC for some references, white papers, etc about the following scenario - and have not received much of a response as of yet, so I'll ask the people that know :)
I have a customer that has created a 'web content' (read presentation layer / portal) that allows them to create, query and update incidents. This portal simply consumes the Web Services for doing this. While this is quite functional - they do have some performance concerns - while the times they are experiencing are 'acceptable' - they feel they can be improved, and thus have reached out to see what we can find out. So, does anyone else have created their own portal, and have utilized Web Services, or native Java API, etc..?? What are your experiences, etc?? Are there any pros/cons of web-services over java api? Next - does anyone have any performance statistics they can share with regards to Incident Create, Incident Query and Incident Modify web-services? To be fare with my fellow friends here - below are some of the numbers the customer is currently experiencing... The system(s) are well tuned and architected, load balanced and separated traffic across segments, it is ARS7.5 and Oracle for your reference... Search Incident - 4.7 Sec (see results list) View Incident - 10.9 Sec Update Incident without attachment - 11.5 Sec Submit Incident without attachment - 20.4 Sec Submit Incident with 3MB attachment - 25.4 Sec So honestly - these numbers do not appear all that bad - but they are asking for comparisons - so I figured I'd ask :) Thanks - and hope everyone is have a great time at RUG (wish I could have attended this year to ask this question in person) Robert Molenda [email protected] _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
