uuu1

777777
Deployment
Objectives
Upon successful completion of this module, you will be able to:
• Perform tasks related to the deployment process as defined in the Integrate Unit Tested Compoentns and Integrate System elements of the Application Solution Development module of the System RVP work stream.
• Deploy customization from a development computer to another computer.
Deployment
Often solutions will be modeled on development computers and need to be moved and merged onto systems for testing or production.
Systems used to bring together multiple custom code for test purposes are referred to as “integration” or “integration test” servers.
Build Implementation Framework (BIF)
BIF is a PTC tool owned by Services Engineering to help deploy customization stored in a PTC SVN source code control server.
BIF should be used when the customization is already stored outside of the Windchill load point.
Storing Customization Outside the Windchill Load Point
1. The system generation tool has several properties which control where generated artifacts are stored.
2. Alternatively, the artifacts can be moved outside a development computer’s Windchill directory after generation.
Generated Artifacts
1. Modeled files in WT_HOME/src.
2. Generated Java files, already edited, from WT_HOME/src.
3. Compiled Java files.
• These are not needed.
• They should be built on the production server to ensure there are no missing classes or incorrect class paths, as well as no Java version issues.
4. Generated SQL files in WT_HOME/db/sql..
5. Registry properties.
• These are not needed; multiple property files from multiple developers would be overwriting each other.
• They should be generated on the production server.
6. Custom resource bundles in WT_HOME/src.
7. Edits to OOTB resource bundles in WT_HOME/wtCustom.
The artifacts should be placed in a separate directory, where edits are made.
Deploying Code
After completing development:
1. Move artifacts to the production server.
2. Run WT_HOME/bin/modelInstall.
• Do not generate SQL; the SQL is already generated from the development environment.
• This edits registry properties.
3. Compile the source.
4. Build the resource bundles.
5. Restart Tomcat and the Method Server.
When the mData files are already present, Rational Rose does not need to be started to generate artifacts or deploy customization:
• WT_HOME/bin/modelInstall can be run from the command line to insert registry settings for customization.
– Conversely, WT_HOME/bin/modelUninstall cleans up registry settings.
• WT_HOME/bin/JavaGen can be run from the command line to generate artifacts.
Exercise 7-1: Group Discussion
Objectives
● Deploy customization from a development computer to another computer.
Scenario
During this discussion, the details of deployment will be reviewed. Please ask any questions you may have.
Step 1. Are Java programs compiled on the development server be deployed?
Step 2. In which directory are the edits to OOTB resource bundles?
Step 3. Does WT_HOME/bin/modelInstall update registry properties?
Completion Criteria
r No. Compile on the production server to ensure the appropriate runtime class path.
r WT_HOME/wtCustom
r Yes, WT_HOME/bin/modelInstall updates registry properties.
Review
Take a few minutes to answer the following questions and then review them with your
instructor.
1. Question: What is the purpose of modelInstall?
2. Question: What file can be used to regenerate artifacts?
a. WTdesigner.mdl
b. cat
c. mData
d. All of the *registry.properties files
e. None of the above
3. Question: Should files in the Windchill directory ever be edited directly?
Summary
After completing this module, you should be able to:
• Perform tasks related to the deployment process as defined in the Integrate Unit Tested Compoentns and Integrate System elements of the Application Solution Development module of the System RVP work stream.
• Deploy customization from a development computer to another computer.