| Standard software environment procedure detailsThis section describes the standard software environment
procedure details. Step 1. Create new package VRCsIn this example, you will create a special package VRC for
the customization department: tcB60O_a_cus. The new package VRC must be derived
from the tcB60U_a_stnd update package VRC, which contains the patches/updates
for the standard software of the LN Common package. - Start the Package VRCs (ttadv1511m000) session.
- On the toolbar, click New. The Package VRCs (ttadv1111s000) details session
starts.
- Enter the respective segment of the identifier for the new
package VRC in the Package, Version, Release, and Customer fields.
In this example you want to create the tcB60O_a_cus
VRC. Therefore you must enter the following: - Package: tc
- Version: B60O
- Release: a
- Version: cus
- Enter or select the package VRC from which you want to
derive the new package VRC in the fields in the Derived from area.
In this example the new VRC must be derived from the
B60U_a_stnd VRC. Therefore you must enter the following: - Version: B60U
- Release: a
- Version: stnd
- Click Save, and click Close to return to the Package VRCs (ttadv1511m000) overview session.
- Quit the overview session.
Note: Infor recommends that you create own VRCs for all
packages, except Tools (tt), Tools Add-on (tl), Data Director (da), OpenWorld
Middleware-enabling (tm), and New Technology (nt). Step 2. Create new directories for the software components of the
new package VRCsYou must create the run-time directories in which the
software components of the new VRCs can be stored. For each package VRC you
must define the path to the directories for, for example, forms, menus, and so
on. In this example, the run-time directories must be stored in the
${BSE}/application directory. In this example, you will create the run-time directories
for the software components for the new customization VRC tcB60O_a_cus.The
run-time directories be stored in the ${BSE}/application directory. At a later stage, you can copy the software components from
the standard package VRC tcB60_a, and the update VRC tcB60U_a_stnd, in the
run-time directories of the new customization VRC. - Start the Directories of Software Components (ttadv1115m000) session.
- On the toolbar, click New Group and enter
the new customization package VRC tcB60O_a_cus in the group fields above the
grid.
- On the toolbar, click New to create the
new directories for the software components.
- Type or select the software component for which you want to
create a directory in the Softw. Component. field. It is recommended to specify
a directory for each type of software component. In the Path on System field, you can enter the path to the
directory on the system. This system can be local, or remote in a client/server
environment. Refer to the session help for details.
- Save the new data and close the session.
Note: You must create directories for each new package
VRC. Step 3. Create a new package combinationYou must create a package combination to which you can link
the new package VRC. In this example, you will create the package combination
b60oacus. You must define the name and description of the package combination
and the location of table and domain definitions. In this example, you will create the package combination
to which you can link the customization package VRCs. - Start the Package Combinations (ttaad1520m000) session.
- On the toolbar, click New to create the
new package combination. The Package Combinations (ttaad1120s000) session starts.
- Enter the package combination, e.g. b60oacus, in the Package Combination field, and enter the directory
where the table definitions of the package combination must be stored in the Table Definition Path field. If the directory does
not exist, you will be prompted to verify the creation of the directory.
- Click Yes to confirm the creation of the
table definition directory. The Package Combinations (ttaad1120s000) session restarts.
- Click Save in the Package Combinations (ttaad1120s000) details session, and click Close to return to the Package Combinations (ttaad1520m000) session.
- Quit the overview session.
Step 4. Link package VRCs to the new package combinationYou must link the new package VRCs to the new package
combination. In this example, you will link the customization package
VRC, tcB60O_a_cus, to the customization package combination,
b60oacus. - Start the Packages by Package Combination (ttaad1121m000) session.
- On the toolbar, click New Group and enter
the customization package combination b60oacus in the group field above the
grid.
- On the toolbar, click New to link package
VRCs to the package combination.
- Type or enter the package VRC code in the Package Version,
Release, and Customer fields. In this example, this code is tcB60O_a_cus. You
must repeat this step for all package VRCs that must be included in the package
combination. Infor recommends that you include VRCs for all packages, except
Tools (tt) and Tools Add-on (tl).
- Click Rebuild DD on the appropriate menu to rebuild
the runtime data dictionary of domains, table definitions, sessions and file
redirections. If necessary, the tables of the companies that are linked to the
package combination will be reconfigured to the new data definitions. Before
the process actually starts, the Select Device (ttstpsplopen ) session starts, which you can use to print an error
report of the errors that occur during the procedure. When the process is
completed, a message appears that shows the number of events that have
occurred.
- Click OK to return to the Packages by Package Combination (ttaad1121m000) session.
- Quit the session when the process is completed.
Step 5. Link companies to the new package combinationYou must link the package combination to one or more
companies, which contain the appropriate data for LN. In this example, you will link the new package combination
b60oacus to only one (existing) company, but you can also link the package
combination to a range of companies. - Start the Change Package Combination by Company (ttaad1101m000) session.
- Enter the old and new package combination.
- Enter the company that you want to link to the new package
combination in the Selection Range group box.
- Click Change to start the process.
- Click Close when the process is completed
to quit the session.
Step 6. Link users to new package combinationYou must link the package combination to the users who will
customize the LN software. If a user is linked to the new package combination, the user’s
default company number must also be linked to this package
combination. In this example, you will link the new package combination
b60oacus to a large range of users, but you can also link the package
combination to individual users. - Start the Change Package Combinations for Users (ttaad2200m000) session.
- Enter the old and new package combination.
- In the Selection Range group box, enter the users who you
want to link to the new package combination.
- Click Change to start the process.
- Click Close when the process is completed
to quit the session.
Step 7. Change the authorizations for the developersFor users with developer authorization to be able to create
or customize software components, you must change the developer authorization
template that is linked to their user profile, so that they are authorized for
the package VRCs in the new package combination. The template is defined in LN ’s Authorization
Management System (AMS). For more information on the developer authorizations,
refer to “User management.” In this example, the package VRC in the developer
authorization template has been changed to tcB60O_a_cus. - Start the Developer Authorization Template (ttams1151m000) session. This session is password
protected.
- Enter the required password. The session now
starts.
- On the toolbar, click New Group and enter
the developer authorization template to which the new VRCs must be
added.
- Click New. The Developer Authorization Template (ttams1151m000) session starts.
- Enter the new package VRC.
- In the Authorization for group box, enter the modules and
language for which the developers must be authorized.
- On the toolbar, click Save and Close, to
return to the Developer Authorization Template (ttams1551m000) overview session.
- On the appropriate menu, click Convert Changes To Runtime DD to convert the
template data to the run-time data dictionary.
- Quit the session when the process is completed.
Step 8. Initialize Test tool for Business Data Entities
(BDEs)You only have to perform this step if you want to
create/customize and test business objects (Business Data Entities). The BOL Test Tool - Public Layer (tlbct3250m000) session offers the possibility
to store test data in test history tables, so that you can reuse the test
later. To be able to use this test tool, you must first specify
the companies where the test data must be stored. - Start the Initialize Tools (tlcom0200m000) session. This session will create tables needed for the public test tool and to
store data from Tools Add-ons (tl) regression tests.
- You can setup a different company number for public test
tool and regression tests. In the Public Test Tool Data and Regression Test Data fields, specify the company
numbers in which the corresponding data must be stored. For example, enter 300
and 101 respectively.
- Click Next to continue. An overview of
the actions to be executed is displayed.
- Click Finish to create the tables in the
specified companies.
When, for example, you start the public test tool from now
on, the data will be read from company 300. Data generated or read within
regression tests will be stored in/ read from company 101. Step 9. Authorize normal users for a new or other
environmentTo make sure that normal users without developer
authorizations can use the new environment, you must change their user data. In this example you will change the package combination of
a normal user to b60oacus. - Start the User Data (ttaad2500m000) session.
- Double-click a user in the grid. The User Data (ttams1100s000) details session starts.
- In the Package Combination field, enter the package
combination of the new environment. In the Company field, enter a company that is linked to this
package combination. Click Save and Close to return to the User Data (ttaad2500m000) overview session.
- In the User Data (ttaad2500m000) session, select the user, and on the appropriate menu, click Convert Changes To Runtime DD. The Convert Changes to Runtime DD (ttams2200m000) session starts.
- Based on your specific requirements, select the appropriate
check boxes and then click Convert to change the user’s package combination in
the runtime data dictionary.
- Click Close to quit the
session.
The new software environment is ready to use. To activate the
new user settings, the users must log off and log on again. Note You can also create a software environment with a One-step software environment procedure. This procedure is
simple and delivers the same result as the standard software environment
procedure. However, you must use the sessions mentioned in the standard
software environment procedure to maintain the created software environment. | |