List, ARS 6.3 p17 (Windows Server 2003, SQL Server 2000, 4GB RAM, SCSI RAID-5, 2 Xeon 3GHz CPUs)
Mid Tier 6.3 p17 (Windows Server 2003, IIS 6, New Atlanta ServletExec 5, 4GB RAM, SCSI RAID-5, 2 Xeon 3GHz CPUs) Both servers are plugged into the same switch - 1Gb Full Duplex. All workstations run Windows XP Pro SP2 with all patches. One of the best features (IMHO) of the ARS platform is the ability to design forms and workflow once and have them work in both Windows and a browser. It provides companies with the flexibility to either go with performance (Remedy User Tool) or portability (browser). The trade off seems to be the performance of mid tier applications. I am trying to find a solution that will speed up Mid Tier performance. Depending upon an office's bandwidth to our data center even small apps are very sluggish. We have offices in 4 time zones and some of the small offices do not have or need high bandwidth. We have 2 main Remedy applications. One is used by technicians and managers; the other is used by all other employees. We have a number of internal non-Remedy ASP.NET applications that run great over the same WAN connections. I created a separate app for employees (instead of a separate VUI) for performance. The app is relatively small and has only enough workflow and objects that is needed. The app is accessed exclusively from Internet Explorer. Installing and maintaining the Remedy User Tool on 4000 computers is not an option at this time. Here are a couple options: Option 1: Create an ASP.NET (most likely 2.0) application instead of using mid tier. The app would use the ARS .Net API to interface with the Remedy system. The benefit would be a significant performance boost. The downside is the additional development time to recreate the functionality of the Remedy application. With this approach, what is the better or preferred way of making sure Remedy properly tracks the user name that is submitting tickets? As I understand it, only Remedy user accounts with Administrator access can use the API (correct?). I know that I could use a separate Administrator level account to perform the submits but Remedy would record that user name as the submitter instead of the actual employee submitting the ticket. I also know that I could use SQL to change the Submitter, Created By and Modified By fields. Is there a better way? I would rather have Remedy/API handle this instead of using SQL outside of Remedy. Option 2: Upgrade to Mid Tier 7.0 p1 Has anyone done this with an ARS 6.3 server? Any compatibility issues with keeping ARS at 6.3 with mid tier 7.0? Would there be a bigger increase in performance upgrading ARS to 7.0? BMC continually tries to improve the mid tier performance with each release. Are there significant performance gains? Thanks for any insight. Stephen _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
