Mi Jeong Yoo,
Were you able to get your migration issue resolved?
Mi Jeong Yoo,
Were you able to get your migration issue resolved?
Hi Bhagirath,
Were you able to get this working using Jess's suggested helps?
I run it successfully in Linux environment, but my local test environment is WINDOWS7.
Below is the error info.
Exception in thread "main" wt.util.WTRemoteException: Unable to invoke remote method; nested exception is:
wt.util.WTRemoteException: Unable to locate method server; nested exception is:
wt.util.WTRemoteException: Unable to locate method server; nested exception is:
wt.util.WTRemoteException: Unable to get server; nested exception is:
wt.util.WTRemoteException: Unable to locate server manager; nested exception is:
wt.util.WTRemoteException: Unable to locate server manager's registry; nested exception is:
java.io.FileNotFoundException: http://whichen-ws01.cisco.com/wt.properties
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at wt.util.WTContext.getResourceAsStream(WTContext.java:3568)
at wt.util.WTProperties.getServerProperties(WTProperties.java:965)
at wt.manager.RemoteServerManager.getRegistry(RemoteServerManager.java:723)
at wt.manager.RemoteServerManager.acquireServerManager(RemoteServerManager.java:587)
at wt.manager.RemoteServerManager.getServerManager(RemoteServerManager.java:566)
at wt.manager.RemoteServerManager.remoteInvoke(RemoteServerManager.java:502)
at wt.manager.RemoteServerManager.getServer(RemoteServerManager.java:283)
at wt.manager.RemoteServerManager.getServer(RemoteServerManager.java:267)
at wt.method.RemoteMethodServer.getMethodServer(RemoteMethodServer.java:1022)
at wt.method.RemoteMethodServer.invoke(RemoteMethodServer.java:620)
at com.cisco.whichen.Test.main(Test.java:43)
The attachments is two method for remote method I got from the community, but both of them can't work in my test environment, please help me.
Thanks
I agree with James. It is much neasier to read the PDFs off-line and searching PDFs also gives better results.
then you can simply set the number of allowed errors to a high value - like this one can check-in in failed models.
We found that this is of great use because this gets us valid data on modelling problems and one can easily spot them at promotion requests.
Those errors are then transparent and can be solved so there are no more problems popping up at release dealine...
greetings
I am trying to figure out if there is a way of taking our production settings/code and rehost it on our training server while retaining the current users and rights on the server. Already know how to copy over the code and change all the settings to reflect the new server name and database server. Also we usually take the database and export it/import it into the other database server. Also taking the LDAP and export, rename server name and import it back in to WindchillDS.. The hard part is retaining the users and settings contained in the training server. Anyone ever do that? Thanks!
Mitch,
As you are well aware from this post, you are correct that when you rehost production system to a training server, it wipes out all the data that was on the training server and makes a mirror image of it. If you're looking to retain information on the test server, the high-level answer is to find out what you can do to backup that information, and then restore it AFTER the rehost.
The backup/restore strategy differs depending on what exactly you are trying to backup and restore, but to address your question regarding "users and settings" I'll address users here: one option is the LoadFromFile framework.
Information on LoadFromFile (and LoadFileSet, which is a bulk way to handle many LoadFromFile files) can be found in PTC documentation (look for "data load" guides), but essentially the idea here is that you prepare an XML file in a specific way to define all the user information upfront, then run a simple Windchill shell command to load it in programmatically - and users is one of these things (among many) that can be loaded. You can bulk load objects at rates of thousands per second or so, MUCH faster than manually. You can also load demo data in this manner as well - in fact, it's the same framework the Windchill installer uses to load its base and demo data upon initial installation.
If you're interested I'd be happy to discuss this in further detail to address the other settings you mention. Feel free to reach me at robert.sindelar@eccellent.com.
With MODIFY IDENTITY, you can only change the number and the organization.
You need the MODIFY right to change the name.
The name doesn't make the object unique in the DB.
With the MODIFY right, you can change everything (content, number, any attribute, ...).
My point of view is that we should be able to change the name with the MODIFY IDENTITY ACL.
I need to have people change the name of parts that have previously be released.
I can't give them the right to modify released parts otherwise they could do anything on them.
Any advice or opinion ?
Thanks.
François
Good answer Bob. Todd also mentioned that to me. What about going into each library or project in details and export the users and that out and then import it back in on the re-hosted/refreshed server? Would that accomplish the same for me? Thanks, Mitch
We have both our production and test servers set up with Office 365.
We use a relay, and from the IT side you have to add the IP address of the server to the relay. Now a note for the below info, IT just told me that since the IP is "allowed" you don't actually have to pass it credentials. So whole mail.properties lines may not be required.
But otherwise it was pretty simple.
In the Windchill folder next to site.xconf we have a mail.properties file.
contents: (replace bold text)
wt.mail.smtp.username=Username
wt.mail.smtp.password=Password
and within wt.properties we have these lines (again replace bold text)
wt.mail.from=email@email.net
wt.mail.mailhost=relay.company.local
wt.mail.mime.charset=UTF-8
wt.mail.properties=$(wt.home)$(dir.sep)mail.properties
wt.mail.verbose=false
wt.mail.verboseTransport=false
Hopefully that helps.
Steve
*edit: I should mention add the info to wt.properties through the the shell/xconfmanager commands.
Tom Uminn wrote:
I'll be combining this with some web statistics to determine the number of views of these PDF's but would prefer to ad 'colour' to these stats from customer feedback... the more the better.
I'm not sure what other people do, but I try to only download each document once. Each time I download one of these PDFs I save it locally (to a special docs folder) so I won't have to re-search for and re-download it again.
I do the same thing. Download once locally to a particular docs directory and then view from there.
One download of each version/build document I need stored to a network folder so I can access them from either my desk computer or a server.
We suspected this might be the case too and will factor this in when we get the stats.
However, unless I get some responses from Admins indicating that they prefer the Help Center to the PDF, I think I already have a consensus.
Each cad worker requires a functioning copy of the cad software being published. The Creo View Adapters simply start up that cad software and tell it what to do. They still depend on the native cad software to do the actual work. You will need to configure your cad worker to sit and wait to publish until the license file is available (basically you're doing using it for the day.) The only other option is to purchase an additional seat of the cad software.
What error message is printed in the logs when Windchill attempts to connect to the smtp server? That message should give us a better idea of why Windchill is failing to connect.
It's failing because of the below line:
java.io.FileNotFoundException: http://whichen-ws01.cisco.com/wt.properties
This error is saying that it can't find the wt.properties file for the server. But, the above URL isn't the right location for wt.properties. It should be looking for http://whichen-ws01.cisco.com/Windchill/wt.properties instead. The fact that it is using the wrong location makes me think there is some misconfiguration in your properties. What is the current value of wt.server.codebase in your wt.properties file?
When will PTC produce an Android version of their Windchill Mobile app?
Everyone I know has an android tablet. iPads are still quite expensive.