DSXchange

If any of you have worked with Datastage using Terminal Server connectivity, could you please share your thoughts?

If you have any document on this, pls send it across.

We are looking at something which gives pros and cons if we access Datastage using Terminal Server like Client side installations?, Number of max concurrent users?, Performance, Scalability

Connecting from a remote client on the network versus Connecting via Terminal Server or Remote Desktop to the server work the same as far as the number of concurrent users are concerned. This is managed by the DataStage Server and because your jobs are actually being run on the Server side there is no client connectivity related performance issue.

Also if you are connecting via Terminal Server then you do not need a client installed on the remote computer however this means that you will have the client installed on the Server.

Hope this little bit helps.

mahveen wrote:If any of you have worked with Datastage using Terminal Server connectivity, could you please share your thoughts?

If you have any document on this, pls send it across.

We are looking at something which gives pros and cons if we access Datastage using Terminal Server like Client side installations?, Number of max concurrent users?, Performance, Scalability

I've seen a lot of success with metaframe, the product effectively manages profiles and registry settings and gives very good performance. I haven't seen it attempted via terminal services. Does it handle multiple users on the one remote machine at the same time?