![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
You may also wish to change which entities are excluded from the backing store using CDD settings (see Excluding Entities from the Backing Store for more information. This change does not require project redeployment. It requires that the updated CDD file is copied to all runtime machines.Examine the alter script before you run it. The section What the Schema Update Utility Can and Cannot Handle Automatically provides more information.
− If you modified aliases when you created the schema, locate the yourname.aliases file you used. It will help you to modify those aliases in the newly generated file, so they match.
2. Open the be-jdbcdeploy.tra file for editing and set the following properties:be.jdbc.schemamigration.url=DbURL
be.jdbc.schemamigration.user=username
be.jdbc.schemamigration.pswd=password
−
−
3.
4. Run the be-jdbcdeploy utility as explained in Task H, Generate the Project-Schema-Specific SQL Scripts (with Wizard), using the updated EAR file.
5. If any of the new or changed definitions result in entries in the yourname.aliases file, and you want to change the provided aliases, follow instructions in Task I, Check the Aliases File and Modify Aliases as Desired. If you modify aliases, remember to generate the scripts again so the modified aliases are used.
6. Examine the generated yourname_alter.sql script and modify as needed so you only run statements for changes you want to make. See What the Schema Update Utility Can and Cannot Handle Automatically for details.
7. The utility handles changes to attributes (entity properties) as DROP and ADD operations. However, DROP operations are commented in the script to avoid data loss.If a column is empty, or you do not want to keep the data they contain, you can enable the DROP operation and let the utility handle the change.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |