Frank,
Contacted PTC for difference between the two settings and this was their response: "The only difference between the two is that setting upload after native save is used only for 3rd party CAD software. Creo does not recognize this setting."
You should set the dm_upload_objects to automatic in your config.pro.
Dear All,
I am using PTC Creo 2.0 with windchill integration. But every time opening big assembly it pop up below dialog box. Many times my team members pressed OK & all assemblies are revised and checked out & creates a lots of trouble for me. I want to disable Revise and Check out now option. Please do needful
"Add" does work with consistency if you set the preference that Daniel Nordin has described above, answering my question.
Thank you for your reply.
I copied Apache folders from Windchill server to Proxy Server then edited httpd.conf file. I think that was why I was getting the error. It is better to install a new apache instead of copying one to another location.
I understand copying apache is not enough for a stable solution. When copied there are lots of config that should be considered. Then I seek for Apache installation file on web and found Apache Version 2.2.25 download link from apache.org domain.
Reverse Proxy on Windchill is working stable now after installing the one I downloaded. Of course I did all the configs written in the solution I referred.
Thanks
I don’t believe you can disable the menu action in CAD, we tried hard to do that because we want all revisions be controlled by the Change Process. However I am pretty sure you can prevent the action from being successful using access control rules. That is what we did, but it has been a while and it will take some research for me to remember how we accomplished that. Let me know if you need that and I will get you some answers.
Thanks Lewis for your feedback.
You can give your suggestion and we will see how we can implement the same.
Thanks,
jitu
Hi,
Scenario:
1. Create WTPart with attachment and new modeled object called lineitems.
Result: Successfully saved WTPart,attachment and line items.
2. Checkout and Edit WTPart and edit attributes, add more attachment and add more line items.
Result: Successfully saved WTPart , attributes and line items.
Issue: Attachment is not getting saved.
here is my code:
@Override
public FormResult doOperation(NmCommandBean paramNmCommandBean, List<ObjectBean> paramList)
throws WTException
{
FormResult localFormResult1 = new FormResult(FormProcessingStatus.SUCCESS);
for (ObjectBean localObjectBean : paramList)
{
Object beanObject = localObjectBean.getObject();
if(beanObject instanceof WTPart)
{
logger.debug("Is Persistable:"+beanObject);
beanObject = PersistenceHelper.manager.save((Persistable)beanObject);
if ((beanObject instanceof RevisionControlled))
{
Mastered localMastered = ((RevisionControlled)beanObject).getMaster();
localMastered = (Mastered)PersistenceHelper.manager.save(localMastered);
break;
} } }
return localFormResult1;
}
Could you please help me to save attachment when we do checkout and edit.
Thanks,
Sithik
Hi,
I do not see why it is complicated to prevent users to be perform a Revise and Check Out thanks to the Access Control.
I agree you can't change the menu, you can set the default value though.
For Access Permissions, simply do not allow Revise for EPMDoc for the Release state for that role/usergroup.
When user try to Revise they will get an error message.
This make me think that of a new idea. Link Creo Menu to ACL, so if user is not allowed to Revise, then the option is not provided in the menu...
Hello Ben Perry, adding footnotes to longer, more complex articles to easily identify what changed since the last revision is a really interesting idea and I can see the potential benefits. I have made note of your suggestion so that we can consider it when we are next planning changes and enhancements to our articles.
Windchill method servers have historically run in GMT (though I believe that's changing in a near-term future release...) as it made use of some of the older JDBC APIs that use the JVM's default TimeZone as the time zone when reading/writing Timestamps to the database (where databases normally store timestamps without time zone information, requiring you to specify the time zone when reading or writing).
Timestamps in Windchill's own logs should be written with respect to the actual server time zone, not GMT (barring bugs, of course).
The way to get the actual server time zone rather than GMT is WTContext.getContext().getTimeZone(). One could, at least in newer releases, use WTContext.getDefaultTimeZone() -- except that it is not denoted as being a supported API, though I can see no reason whatsoever for this.
So Jess,
Instead of this:
try(java.io.PrintWriter output = new java.io.PrintWriter(new java.io.BufferedWriter(new java.io.FileWriter("/home/ptc/QuickLinks.log", true)))) { output.println(new java.sql.Timestamp(System.currentTimeMillis()) + "\t" + currentUser.getName()); } catch (java.io.IOException e2) { e2.printStackTrace(); }
What do you suggest to write the timestamp to my file "/home/ptc/QuickLinks.log" in the timezone of the server, instead of GMT?
Sorry if it is simple question - I'm still somewhat novice at java coding.
Sithik,
Are you interested in editing your post and formatting your java code as such? When editing, choose the Use advanced editor button. After entering that mode, you can highlight your code and click the buttons in the screenshot below to format your code for easier visibility.
Thanks!
I would like to know how to build a query report to search for WTParts that do not have association with EPMDocument. I see that only one link goes to EPMDocument from WTPart i.e EPMBuildHistory, are there any other links, using which i can query?
Thanks,
Shashi
First off, for logging, I'd suggest just using log4j and either writing into the normal method server log file or adjusting log4jMethodServer.properties to route your loggers' output to a separate log file.
More broadly, I was answering how to get the "real" server time zone (rather than GMT) from within the method server. There are lots of usages for this information. [By the way, by WTContext I was referring to wt.util.WTContext.]
If, however, you just need to render a time to the current time zone, you could use wt.jmx.core.MBeanUtilities.renderAsTimestampPlusTimeZone(java.util.Date). If you don't like that format, then use your own, e.g.:
dateFormat = new SimpleDateFormat( "yyyy-MM-dd HH:mm:ss.SSS" )
dateFormat.setTimeZone(WTContext.getContext().getTimeZone());
dateFormat.format(date);
The intention here is that there are some events that I want logged to some separate file, and not in the MS or BMS. But the current drawback is that it is not using the same timezone as the MS and BMS.
I have replaced
new java.sql.Timestamp(System.currentTimeMillis())
with this:
wt.jmx.core.MBeanUtilities.renderAsTimestampPlusTimeZone(new java.util.Date())
So my full code to print the timestamp (with server time zone applied) and username to the separate log file is this:
try(java.io.PrintWriter output = new java.io.PrintWriter(new java.io.BufferedWriter(new java.io.FileWriter("/home/ptc/QuickLinks.log", true)))) { output.println(wt.jmx.core.MBeanUtilities.renderAsTimestampPlusTimeZone(new java.util.Date()) + "\t" + currentUser.getName()); } catch (java.io.IOException e2) { e2.printStackTrace(); }
The resultant timestamp is
2015-08-27 20:53:44.601 -0500
as opposed to
2015-08-27 20:53:44,601 (the formatting printed in the MS/BMS log)
But at least it is in the same timezone as the messages in the MS and BMS logs.
Thanks Daniel,
I think this could be my temporarily solution till I get permanent disable for Revise and checked out option.
Jitu
Shashi,
take a look at this document Resource for reporting
There are lots of report already done to use and some other helpful news about reporting.
If you don't want the time zone in your output then use:
java.text.SimpleDateFormat dateFormat = new java.text.SimpleDateFormat( "yyyy-MM-dd HH:mm:ss.SSS" )
dateFormat.setTimeZone(wt.util.WTContext.getContext().getTimeZone());
String formattedDate = dateFormat.format(date);
renderAsTimestampPlusTimeZone() includes the time zone so that there is no question or confusion about which time zone is being referenced.
But again if your purpose is logging, then just use log4j and let it do the timestamping of the log lines, allow you to control log verbosity on the fly, etc. Then you only have to worry about formatting dates if you want to log additional timestamps to the log line beyond the time for log line/event itself. While there still is println() based logging in Windchill, there has been an ongoing effort to eradicate it and replace it all with log4j calls. There are loads of advantages to this over directly doing your own file or console output when it comes to logging.
Hi
We have an issue when we start Creo2.
Almost every morning we have to start twice because we get a "fatal error..." popup at first start up.
it is as follows> start Creo2>logon password>click on Work space then the error occurs.......
if Creo2 is closed during the day and we start again, we can have several "Fatal error...." pop ups before getting thru to server
Creo2 M150 Intralink 10.2 m30
Frank,
When we first went to Windchill our tried and true process was to remove modifed objects from the workspace as it was the most reliable method! But, after 6 years we have learned how to efficiently interact with WC. Here is my proposal and recommendation:
1) Update - Use Update once per day before the user starts working to find and update objects that other users have changed to ensure they are working with the latest content. Do not use update when Objects are in Creo Session...if a large assembly, then WC wants to download required dependents of the assembly. In our case, large assembly = 100,000+ objects.
2) Add - In Windchill Environment, the goal is to avoid the Add function as much as possible. We have our collector settings at None for Dependent cad documents on add to workspace. I have done lots of time testing and found out that it takes less total time when letting Creo open and download the necessary components. (File -> Open in Creo and type in the assemlby/drawing name without any objects in the workspace VS. Add required dependents and then open in Creo.)
3) Check-Out - Train the users to interact with the conflict pop-up in Creo. Example - Use continue for the family tables that get marked as modified unintentionally, then check-out when an intentional change is planned for.
4) Check-In - Train the users to check-in from Creo. We have the collector settings at Required for dependent cad documents. Only the checked out items in the check-in table will be checked in and if necessary you can check-out lower level dependents in the table on the fly if needed...it ignores all the modifed items in the list. With this logic, you can reduce the time the user goes to the workspace to refresh table, add or remove items. Tthere is obviously a risk to this process....thus due dilligence is required to check-out the items that are intentionally modified.
5) Remove - The primary reason to use remove is to reduce the objects in cache to get performance back in our environment. We have found out that deleting a workspace and creating a new one ensures good performance over the long run.
We are still in WC10.1 and anxious to test the autoupload functionality to the server side workspace when going to WC10.2. We were not able to utilize it in WC10.1.