| Copy software components procedure detailsThis section describes the copy software components
details. Step 1. Copy components in a software environmentThe procedure begins by copying the software components of
the source package VRC (e.g. tcB60_a) into the into
the new package VRC (e.g. tcB60O_a_cus1). - Start the Copy Software Components to New Package VRC (ttadv6265m000) session.
- In the Selection Range group box, define the range of
packages and languages for which you want to copy the software
components.
- In the VRC group box, define the target VRC and the source
VRC that contains the software components. For example, the target VRC is the
VRC code of the LN Common (tc) package in the new customization environment B60oacus.
- Under Options, select the appropriate check boxes. For
example, you can make sure that the link between a form, report, or menu in the
source VRC is also copied to the target VRC.
- On the Components tab, select the components that you want to
copy to the target VRC.
- Click Copy to start the process.
Step 2. Create the run-time data dictionary for labelsLN stores language-dependent software components, as labels, per
package VRC. The labels must be compiled for use at run time. To compile your
new environment’s labels: - Start the Compile Labels (ttadv1243m000) session.
- In the From and To fields
for Language, define a range of languages whose labels
you want to compile.
- Use the From and To fields for, Package, Version, Release, and Customer, to define the range of package VRCs whose
labels you want to compile.
- Tip: Always compile the labels for an entire package.
-
If your bshell is running on a different machine than
the data dictionary, you can either select the: - Install files on remote machine option, to install the label dump, and index files on the same machine as the
data dictionary.
- Install files on local machine option,
to install the label dump, and index files on your local machine. The label
dump and index files are only available to users that use your local machine.
- Click Compile. The compiled labels are stored in the
${BSE}/lib/labels directory. The label files (and label index files) will be
used to display labels on forms, menus and reports at run time, for users of
the language for which you compiled the labels.
Step 3. Create the run-time data dictionary of the components in a
package combinationYou must create a run-time data dictionary for the new
software environment that contains the new package combination’s software
components. For example, you create the runtime data dictionary of the
customization environment’s package combination b60oacus. - Create Runtime Data Dictionary (ttadv5210m000)
- In the Options group box, select the appropriate check boxes
for your new environment’s package combination.
- In the Selection Range group box, enter the package
combination for which you want to create the run-time data dictionary. You must
also define a range of sessions. For example, the run-time data dictionary is
created for the new package combination b60oacus.
- Click Create Runtime to start the process.
Note: If you have selected the Print Errors check box, you can view the errors in
the log file in the ${BSE}/log/log.reconfig directory. The Select Device (ttstpsplopen ) session starts, in which you can select a printer to
print the log file. Step 4. Compile the program scripts and library scripts of the
copied componentsThe next step in the procedure is to compile the program
scripts and DLLs of the copied software components into the new package, e.g.
VRC tcB60O_a_cus. - Start the Compile Program Scripts / Libraries (ttadv2230m000) session.
- In the VRC fields, enter the package VRC
to which you have copied the software components.
- In the Prog.Script/Library field, define the range of
program scripts and libraries that must be compiled.
- In the Program Script Type field, select the program script’s type.
- Based on your specific requirements, select the appropriate
check boxes under Options. For example, you can select in the Compile field to compile all scripts or only the new
scripts or functions in the new package VRC.
- In the (Syntax) error messages to file field, enter the path name where the errors and
events that occurred during the compiling process is stored.
- Click Compile to start the process.
Step 5. Compile the reports of the copied componentsThe following step compiles the report scripts of the
software components that are copied into the new package VRC. - Start the Compile Reports (ttadv3240m000) session.
- In the Package and VRC fields, enter the
package VRC to which you have copied the software components.
- In the Language fields, define for what languages the
reports of the copied software components must be compiled.
- In the Report fields, define the range of reports that you
want compile.
- In the Compile field, select a compilation option.
- In the (Syntax) error messages to file field, you must enter
the path name where the errors and events that occurred during the compiling
process is stored.
- Click Compile to start the process.
Step 6. Create the run-time data dictionary of the forms and
menusYou must also compile the forms and menus for the new
environment’s data dictionary. - Start the Create Runtime Data Dictionary (Forms and Menus) (ttadv5214m000) session.
- In the Selection Range group box, you must define the package
VRC language for which the run-time data dictionary of the forms and menus must
be created.
- Select the Forms and/or Menus check box(es) and then define the appropriate
range of forms and/or menus.
- In the Dump field, you can select a selection method for the
forms and menus for which the run-time data dictionary is created. For example,
you can create the data dictionary only for the forms and menus in the selected
VRC.
- Click Create Runtime to start the process.
If you have selected the Print Errors check box, you can view the errors in
the log file in the ${BSE}/log/log.reconfig directory. The Select Device (ttstpsplopen ) session starts, which you can use to select a printer
to print the log file. Step 7. Install Web Help for the components in the target
environmentTo make online Help available for your software, you must
install Web Help on a Web server in your domain. | |