Headstart WindchillNo Comments

default thumbnail

I know most of these commands are in your memory but wanted to make an effort to add all the commands used in the windchill PLM system here.

Please feel free to add more, in the comments section.

  • To run Tomcat in development mode:

    • Start a Windchill Shell and change the folder to the Tomcat installation directory
    • Execute the following command: ant -f config.xml configureJspEngine -Dmode=dev
    • Restart Tomcat (release 9.1 or earlier) or the Method Server (release 10.0 or newer)
  • To revert back to production mode:

    • Start a Windchill Shell and change the folder to the Tomcat installation directory
      Execute following command: ant -f config.xml configureJspEngine -Dmode=prod
      Restart Tomcat (release 9.1 or earlier) or the Method Server (release 10.0 or newer)
  • Resource Build:

    • ResourceBuild compiles rbInfo files from the /src directory instead of the /wtCustom directory , which is not a recommended practice. ant -f codebase/MakeJar.xml is needed after its execution.
    • Ex. ResourceBuild com.ptc.ext.*
  • Tools.xml:

    • ant -f bin/tools.xml bundle -Dbundle.input= [-Dbundle.source= -Dbundle.output=]
      • This command compiles rbInfo files from the /src directory.
      • Ex. ant -f bin/tools.xml bundle -Dbundle.input=com.acme.*
      • This command ant -f bin/tools.xml bundle -Dbundle.input= -Dbundle.source=, will compile rbInfo files from the directory defined by -Dbundle.source:
      • Ex. ant -f bin\tools.xml bundle -Dbundle.input=example.MySize.* -Dbundle.source=c:\temp
    • ant -f bin/tools.xml bundle_custom -Dbundle.input=
      • This command compiles rbInfo files from the /wtCustom directory. ant -f codebase/MakeJar.xml is needed after its execution.
      • Ex. ant -f bin/tools.xml bundle_custom -Dbundle.input=com.ptc.ext.<your-rbinfo-files>
      • or run: ant -f bin/tools.xml bundle_custom -Dbundle.forceCompile=true -Dbundle.input=registry
      • After this, do not forget to run: ant -f codebase/MakeJar.xml custUpdate
      • Note: For Enumeration type, there is another way to do this: use the EnumCustomize utility. After its execution, a corresponding folder structure will be created under /wtCustom.
    • ant -f bin/tools.xml class -Dclass.includes= [-Dclass.force=true/false -Dclass.source= -Dclass.output=]
      • This command is used to compile Java classes from the directory /src.
      • Ex. ant -f bin/tools.xml class -Dclass.includes=com/ptc/serviceAcademy/training/*
      • This command ant -f bin/tools.xml class -Dclass.includes= -Dclass.source= is used to compile Java classes from the directory defined by -Dclass.source:
      • Ex. ant -f bin/tools.xml class -Dclass.includes=com/ptc/serviceAcademy/training/* -Dclass.source=c:\ext
    • ant -f bin/tools.xml sql_script -Dgen.input=
      • This command is used to generate the SQL script in the <WC HOME>/db directory.
      • Ex. ant -f bin/tools.xml sql_script -Dgen.input=com.ptc.serviceAcademy.training.*
      • Note: You have to check the directory to see if the classes are generated. Sometimes even if it shows “Successful” in the shell window, but in fact, the classes are not truly generated.

Be the first to post a comment.

Add a comment