Eng-Tips is the largest engineering community on the Internet
Intelligent Work Forums for Engineering Professionals
-
Congratulations waross on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MULTIPLE WINDOWS 1
- Thread starter GPowers2
- Start date
-
1
- #3
JohnRBaker
Mechanical
Actually if you launch a second (or even a third) session from the same desktop, you will only be checking out a single license. Now there is one thing to be aware of, unlike when you're running a single session, it will now be possible to check-out TWO or more applications at the same time, however, like Gateway, opening a SECOND copy of the SAME application will NOT require an additional license.
For example, if I had three sessions open on a single desktop and I was running Modeling in two of them and Drafting in the third, the licenses checked-out would be:
Gateway = 1
Modeling = 1
Drafting = 1
And before anyone asks, this would still be the case even if you were running on a workstation with dual or even a quad processor. We don't go by 'cores', but by the fact that only one user is actually logged in, even if he decides to run two or more sessions, he's still only a SINGLE user and that is what we have licensed, a USER using a copy of the software.
John R. Baker, P.E.
Product 'Evangelist'
UGS NX Product Line
SIEMENS PLM Software
Cypress, CA
For example, if I had three sessions open on a single desktop and I was running Modeling in two of them and Drafting in the third, the licenses checked-out would be:
Gateway = 1
Modeling = 1
Drafting = 1
And before anyone asks, this would still be the case even if you were running on a workstation with dual or even a quad processor. We don't go by 'cores', but by the fact that only one user is actually logged in, even if he decides to run two or more sessions, he's still only a SINGLE user and that is what we have licensed, a USER using a copy of the software.
John R. Baker, P.E.
Product 'Evangelist'
UGS NX Product Line
SIEMENS PLM Software
Cypress, CA
BOPdesigner
Mechanical
So John, by the license being per user. If the same user is logged into two desktops, and has a session of the same application open on each of them, are they using 2 licenses or just one?
JohnRBaker
Mechanical
By 'user', we mean per user/per station. The licensing does not actually KNOW who the users are, just THE SAME USER on such-and-such a station decided to start 2 or 3 sessions on THAT SAME STATION. If you log onto a different station, the licensing see you as some OTHER USER on some other such-and-such a station.
In other words, it will take 2 licenses, one per each of your Windows LOGINS.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
In other words, it will take 2 licenses, one per each of your Windows LOGINS.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
The licensing of per user/per workstation is a lot better than that of their competitor from MA. They checkout a license for every session of the application launched on a single workstation. Of course with a Windchill Data Management solution, you have to do loops to use multiple sessions because of the way they cache the user workspaces.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
If you are opening the MAster in one session and the specification in another you have to be aware that the master will also be open in the session with the specification. You could get some strange results because you coould be saving the master in two sessions.
BOPdesigner
Mechanical
Yes I was thinking that same thing yesterday. I had an assembly open in one session and one of its components open on the other. The changes to the component were not taking effect in the assembly. I suppose you could close the component and reopen it from the assembly tree but that doesn't seem productive. So what senerios other than working on independent sets of data on each session would this be useful?
JohnRBaker
Mechanical
Actually you don't have to explicitly Close and then Reopen the modified component(s). You see there are two often overlooked items found on the File -> Close list of options, and those are the 'Reopen Selected Parts...' and 'Reopen All Modified Parts' options.
In the case of the 'Reopen Selected Parts...' you will get a list of all of the currently out-of-date parts, based on the fact that the file opened is older than the version currently saved on the disk, open in your session,. In that case all you have to do is select the component that you wish to update and hit OK.
And in the case of the 'Reopen All Modified Parts' option, it's even simplier as all you have to do is select the option and acknowledge that you actually wish to replace ALL of the modified components and it's done, period.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
In the case of the 'Reopen Selected Parts...' you will get a list of all of the currently out-of-date parts, based on the fact that the file opened is older than the version currently saved on the disk, open in your session,. In that case all you have to do is select the component that you wish to update and hit OK.
And in the case of the 'Reopen All Modified Parts' option, it's even simplier as all you have to do is select the option and acknowledge that you actually wish to replace ALL of the modified components and it's done, period.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
JohnRBaker
Mechanical
Yes, I should have caveated my reply that the suggestions I had made were for Naive Mode users only. TeamCenter users may have different and additional options avialble to them.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
JohnRBaker (Mechanical)
15 Feb 08 12:31
Yes, I should have caveated my reply that the suggestions I had made were for Naive Mode users only. TeamCenter users may have different and additional options avialble to them.
John,
Please tell me that you dropped a letter and meant to say "Native Mode"! <GRIN>
Chris Cooper
Senior CAD Specialist
Cleveland Golf / Never Compromise
15 Feb 08 12:31
Yes, I should have caveated my reply that the suggestions I had made were for Naive Mode users only. TeamCenter users may have different and additional options avialble to them.
John,
Please tell me that you dropped a letter and meant to say "Native Mode"! <GRIN>
Chris Cooper
Senior CAD Specialist
Cleveland Golf / Never Compromise
JohnRBaker
Mechanical
Chris,
That's what the TeamCenter crowd sometimes call it ;-)
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
That's what the TeamCenter crowd sometimes call it ;-)
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
John,
As you say you can have as many sessions of NX running as you like on a single workstation including different versions, and it only checks out one license. I have needed to do this in the past to have a model open in two sessions in order to pick apart how it was built so I can rebuild a better version after deleting a root feature. By opening the native part from disk and modifying it in a session without necessarily saving anything I can then open a second copy based on the original disk image and use it to interrogate the original feature tree.
In teamcenter however you can have two teamcenter logins running on the one tube, but they seem to be locked to only one NX session. In addition the owner of that session is the first login only. All this is quite logical, but I can't for the life of me manage to do the same trick in teamcenter as I do in native when picking apart a model in two NX sessions.
No matter what your system is whether in teamcenter or native you can't have open two copies of the same file, or any two files called the same thing, (from different directories for example), in the one NX session. It just wouldn't make sense to do that. As I said you can have two sessions open in native and work in alternate parallel sessions as it were. Teamcenter does not seem to be able to to the same.
What I have to do in teamcenter is export the model to native and open it in a second session from there. It seems to be either that or save it under a different name, which I don't favor because every extra item you add in teamcenter has to be managed and incurs some cost to do so.
Now I don't have much of a question, just noticed that the teamcenter guys are calling native "Naive" and kind of wanted to know if there was any way to match the level of sophistication that I'm able to manage in native.
In case anyone is wondering, we really do need to do this from time to time. Sometimes we find that the best way forward is to rebuild part of the model. Some of those times things already got tooled up, and worse we pay the toolmaker for additional changes, so we need to keep the majority exactly the same. To keep it the same the only way to do that is by re-applying variable radius blends with setback and multiple edge sets, using exactly the same parameters. These blends got deleted because we trashed the root feature to fix a problem that probably shouldn't have been there in the first place. Hence it's real handy to flick back and forth between session so I can fix what radii were applied where in these variable blends I'm trying to rebuild.
Best Regards
Hudson
As you say you can have as many sessions of NX running as you like on a single workstation including different versions, and it only checks out one license. I have needed to do this in the past to have a model open in two sessions in order to pick apart how it was built so I can rebuild a better version after deleting a root feature. By opening the native part from disk and modifying it in a session without necessarily saving anything I can then open a second copy based on the original disk image and use it to interrogate the original feature tree.
In teamcenter however you can have two teamcenter logins running on the one tube, but they seem to be locked to only one NX session. In addition the owner of that session is the first login only. All this is quite logical, but I can't for the life of me manage to do the same trick in teamcenter as I do in native when picking apart a model in two NX sessions.
No matter what your system is whether in teamcenter or native you can't have open two copies of the same file, or any two files called the same thing, (from different directories for example), in the one NX session. It just wouldn't make sense to do that. As I said you can have two sessions open in native and work in alternate parallel sessions as it were. Teamcenter does not seem to be able to to the same.
What I have to do in teamcenter is export the model to native and open it in a second session from there. It seems to be either that or save it under a different name, which I don't favor because every extra item you add in teamcenter has to be managed and incurs some cost to do so.
Now I don't have much of a question, just noticed that the teamcenter guys are calling native "Naive" and kind of wanted to know if there was any way to match the level of sophistication that I'm able to manage in native.
In case anyone is wondering, we really do need to do this from time to time. Sometimes we find that the best way forward is to rebuild part of the model. Some of those times things already got tooled up, and worse we pay the toolmaker for additional changes, so we need to keep the majority exactly the same. To keep it the same the only way to do that is by re-applying variable radius blends with setback and multiple edge sets, using exactly the same parameters. These blends got deleted because we trashed the root feature to fix a problem that probably shouldn't have been there in the first place. Hence it's real handy to flick back and forth between session so I can fix what radii were applied where in these variable blends I'm trying to rebuild.
Best Regards
Hudson
JohnRBaker
Mechanical
Hudson,
I'm not a TeamCenter person and I don't actually run NX under TeamCenter, primarily because I have so many different versions of UG/NX installed at any one time and since I'm always installing the latest phases during Beta testing and before a release is finalized, again to test and verify changes and updates, it has never been efficient to run in anything but 'naive' mode.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
I'm not a TeamCenter person and I don't actually run NX under TeamCenter, primarily because I have so many different versions of UG/NX installed at any one time and since I'm always installing the latest phases during Beta testing and before a release is finalized, again to test and verify changes and updates, it has never been efficient to run in anything but 'naive' mode.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
- Status
Similar threads
- Locked
- Question