In Oracle, the schema is owned by a user. In a single instance you can create multiple users and use those users with multiple instances of Windchill. We have one instance shared with 2 WC10.2 and 1 WC11 Windchill dev environments.
All you need to do is create user manually and in PSI select the option to use existing database user
Hi Ben, Binesh,
Thanks for your quick response.
As I installed oracle on a remote machine, I run PSI on the oracle server and crated new database, Windchill user using PSI and completed the first Windchill Installation.
Do I need to run the PSI to create the Database Instance or User again on the oracle server else should I simply run the create_user.sql?
Will there any problem if the tablespace are shared across the oracle users(schma) or Instance (SID)?
And can we use the same port number (1521 default) for the new user too?
Thanks in advance for your response again.
BR,John
Deepali Bharade wrote:
How to change WTDocument to use a different lifecycle that starts with a state that people don’t have permission to use OOTB. In that case it would just be a new OIR for the WTDocument. The affect we want is to remove “Document” from the dropdown of documents user can create.
To prevent a particular type from being created and remove it from the dropdown menu you can simply use the Type and Attribute Manager and set "Instantiable" to no.
If you want to create a new db instance, the run PSI and give a different set of data files. If you want to create another user and schema, then run create_user.sql.
I assume you are not running two prod. installs. In any case, creating another database instance using PSI gives you the ability to manage/dedicate resources for each of the instances.
We haven't come across any issue with Windchill sharing same instances, but again these are development server with a very less usage.
WtPart and CAD Document build failed in Windchill along with this we are seeing there is a difference in wtpart version and corresponding CAD version ?
CAD Part version is keep etting changed but its wtPart remained at initial one.
Please help
So we currently use Change Management in Windchill to manage our engineering changes, and have noticed that there appears to be a date field in the change activity that never gets filled out. I am curious as to what this date field is for and how to get it to populate with data? (See attached screenshot for details.)
-marc
I am in the middle of creating some access control rules and have the following questions for everyone:
My first inclination is to create them as high up the structure as it makes sense. In this particular case I want a set of rules for a custom role called ENG Admin. Think of a Library Manager or Product Manager permissions but only for WTParts and CAD / EPM Docs. Since it would seemingly apply to every Product and a lot of Libraries, my thought was to create it at the ORG level.
I look forward to seeing what the group comes up with.
-marc
CAD / PLM Systems Manager
TriMark Corporation, New Hampton, Iowa
At Mike Lockwood's recommendation we have moved almost everything out of the context (and their related templates) and up to the ORG. This makes it much easier to make system wide changes without having to make them inside every single product and library.
Tom,
That was first thought too, but then I sabotaged my thinking by looking at the messed up way PTC did it...
Mike is on the right track most of the time when it comes to Windchill, so I think I will follow his advice as well.
-marc
I truly don't believe that anyone at PTC responsible for this stuff actually tries to administer a real system. If they did, each would come to the conclusion within a day that all ACL's which are common to a group of Products and Libraries should be deleted from the them and brought to Org level. Super laborious to make an agreed change one by one across 85 Products and 13 Libraries.
Note: Using "Private" for some contexts is also critical to make this work well (meaning avoid use of DENY like the plague).
- Examine all the ACL's resulting from creating a Product/Lib from the OTB templates.
- Decide which are common to many Products/Lib's; create these at Org, PDM and delete from Product/Lib; save result as new Product/Lib templates.
- By exception and with careful documentation, add some to individual Product/Lib
- For some contexts (esp. Lib's), make Private, which removes inheritance from Org/PDM and makes that context only use the ACL's in it.
- Try to start with 'no user can do anything and add each as needed (avoids DENY)
- Look carefully at the effect (many OTB) of the pseudo-role TeamMembers, which can wreak havoc unless you really understand what it's doing
- Have to think in 5 dimensions: to what (object type), when (at what state), who (principals), what can be done (permissions)
- Even with all this done superbly, you'll get completely messed up unless you null out the many "implies": properties that automatically select additional permissions when you select any (see my other rants on this one)
- Confirm all using Manage Security
- Best for Manage Security is to create objects (i.e. CAD Doc), one at each state in each representative Product/Lib and leave permanently, and then create some test users than can be used to confirm.
- Big decision to be made for every single ACL is to use a Group or a Role (context team role exposed at Org level). Over time, I've moved almost all to the Role instead of directly to Groups. This also facilitates use of Shared Teams where possible.
Don't mean to sound negative here - I actually truly love the puzzle of figuring out the most elegant and robust way to approach user permissions, with related groups, roles, etc.
What are the primary differences between the Team and Enterprise versions of Relex?
Marc,
That is the Due Date or Deadline of each particular workflow task, when you enable deadlines on your tasks. You can have some tasks with deadlines, and some tasks without deadlines.
A few cautions ... Windchill's functionality is a little weak in this area. It doesn't take into account working hours. So if the deadline is 3 hours, and the user receives a workflow task at 4:00 PM, it will be overdue at 7:00 PM.
I could find the query for single level but, I need to retrieve the BOM with all levels and quantity as well.
Thanks for the proposes solution! We will try this at short notice. I will inform you about our findings.
What is the message when build fails?
I presume you are updating part structure from CAD, not the other way around?
If you are updating WTPart structure from CAD, the WTPart has to iterate (not the CAD Doc) to complete the the build process. Build changes the part structure (ie changes the part uses table). Those change have to be stored in a new part version. The difference in version to CAD is not a problem, when the part iterates it carries forward the CAD association from the previous WTPart version.
Your screen shot shows the build status of the parts as "Excluded". Is this deliberate? This means exclude from build operation. If you need them to be driven by cad, set for build on each one and select "build" option. This will update the build state to "to be built". The presence in structure and quantity will then be driven by CAD following the next build operation.
If you looking to update CAD to reflect manually created WTPart structure you need the WTParts on left side of compare table. In this case CAD iterates and you need a work space for that to happen in.
Hi All,
Import from Spreadsheet action is not available. Can anyone please let me know like how to enable that action and import that data from spreadsheet to Windchill.
Thanks and Regards,
Aditya Achanta
Found the action in Product details.
Navigate to Product --> Details --> Actions --> Import from Spreadsheet
Basically we want to disable it for parent I.e. document only.. keeping soft types intact.. but the issue is when you make document unistantiable it's applied on all its children.. then the only way you have is turn it on for each sub type manually.. we have more than 80 subtypes.. so this is quite a tedious job..
When you create a new Subtype, just remove the the inheritance of the parent type. So you won't need to do it the next time.
A simple solution is to change one subtype. Export the type wt.doc.WTDocument (all subtypes are exported too), compare the exported types (search for the example you've changed) and then import it again.
look for something like this:
<csvPropertyValue handler="com.ptc.core.lwc.server.TypeDefinitionLoader.processTypePropertyValue">
<csvname>instantiable</csvname>
<csvisDefault>false</csvisDefault>
<csvvalue>true</csvvalue>
</csvPropertyValue>
https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS30168
I get windows.dll load error everytime I run PSI with CPS03. I have installed JRE for both 32 and 64 bit. Any inputs would help !