Carey, Regarding the API and user logins, I am glad to hear that. In my testing when I login with a non-Administrator account with a Fixed license I receive errors when attempting to perform almost any operation.
Since I have always received errors when using non-Administrator accounts I had the impression that this was by design. Now that I know this works I need to find out the cause of the errors. Stephen -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Monday, July 17, 2006 9:54 AM To: [email protected] Subject: Re: Mid-Tier Performance Stephen, > As I understand it, only Remedy user accounts with Administrator access can use the API (correct?). No. That is absolutely wrong. The API is what all Remedy supplied clients run on. So every time the User Tool talk to the ARS server it is acting on behalf of a user. (Admin or not) If you want to write your own "Mid-tier" then you can, just make sure that the users are using their own accounts and you should be fine. (BTW: You could even write your own Admin Tool, Import tool, etc.. if you wanted to.) " > I know that I could use a separate Administrator level account to perform ... " What is technically possible is not the issue here. What is LEGAL really is the issue. Taking this approach would be (to the best of my understanding) a violation of the license agreement for ARS. RE: Mid-tier v7... I have not yet tested it against a v6.3 ARS server. But this is what I do know about it. There are some new features. (User saved searches, It should remember other preferences like column orders for results list and maybe even table fields,) I do think I detect some performance improvements, but they appear to be fairly marginal in my testing. The built-in Help text on forms and fields are still "ugly as sin". -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. Never ascribe to malice, that which can be explained by incompetence. On 7/17/06, Heider, Stephen <[EMAIL PROTECTED]> wrote: > 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 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
