TM1 Forum

I've got Archtect installed on our server and on my laptop. It works fine if I remote desktop into the server and use it there, but it is noticably sluggish when running from my laptop. Does architect normally have this problem, or is it perhaps something with our set up?

ps do most people run Architect on the server? I find this quite an odd practice, but we've had several IBM/Cognos consultants tell us to install other traditionally 'client' software on servers and run it via remote desktops! (And then other consulants tell us we don't need to do this.....)



--EDIT-- Just re-read the FAQ. TM1 clients really don't seem to like WAN's. Although I am using a LAN I suspect it might still be better to use architect on the server.

Yes, Network itself can be a bottleneck.

You can either install the client on the user machines or you can allow your users to Remote Desktop to the server. Personally, I think you should go with the first option. Allowing all the users to Remote Desktop to the server will have its own issues e.g. security, number of Telnet etc.

End Users should using either Perspectives/Architect installed on their local machines or they can use TM1Web.

BTW, since when Paris Hilton started using TM1? This news should be on IBM's website - Celebrities using IBM Cognos TM1 to Forecast their Budgets

ParisHilton wrote:I've got Archtect installed on our server and on my laptop. It works fine if I remote desktop into the server and use it there, but it is noticably sluggish when running from my laptop. Does architect normally have this problem, or is it perhaps something with our set up?

ps do most people run Architect on the server? I find this quite an odd practice, but we've had several IBM/Cognos consultants tell us to install other traditionally 'client' software on servers and run it via remote desktops! (And then other consulants tell us we don't need to do this.....)

--EDIT-- Just re-read the FAQ. TM1 clients really don't seem to like WAN's. Although I am using a LAN I suspect it might still be better to use architect on the server.

We use a local client for people who are on the same network as the server itself. For people who are interstate where network speed is a problem, we've always had a dedicated server (previously running Terminal Services, currently running Citrix) which runs the client software. The reason for this is that instead of sending the whole data set up and down the pipe, you're only sending commands and screen displays. Using remote desktop to the server itself is an option but probably not a common one; the advantage with a Citrix or similar setup is that you don't have to bother setting up printers, network shares and the like.

Thanks for the replies.

I've been needing real help with my budget ever since 'that' video got out on to the internet

Our users are on the LAN and tbh the performance is fine. It's just surprising that architect feels slower when not using a remote desktop.

ParisHilton wrote:Thanks for the replies.

I've been needing real help with my budget ever since 'that' video got out on to the internet

Our users are on the LAN and tbh the performance is fine. It's just surprising that architect feels slower when not using a remote desktop.

turn the properties window on, if you need it, not all the time

can be the difference between "omg" and "uh, works a bit better"

but in the end.. the tm1client sends thousands of small, senseless, small, packets through the network
maybe another reason to buy tm1, if your switches doesn't blink enough to make a small party.