To use the Software Configuration Management systemYou can use the Software Configuration Management System (SCM) to copy a software component from an original VRC to a dedicated development VRC. You can then modify the component, for example, to fix a bug. If the component is finished and tested, you can put it back into the run-time environment. This process is called the check-out and check-in process. The component can still have the same VRC code, but it has a different revision number. Older revisions of the component are still retrievable. During the check-out period:
The following figure shows the Software Configuration Management (SCM) concept. ![]() SCM controls only the revisions of components in one VRC. If a component is copied to another VRC, the revision information is no longer available. Note There is a fundamental difference between copying software components in a new run-time environment and copying components into a development VRC with SCM. The components, which are copied into a development VRC with the SCM tool, are positioned at the same level as the original and have the development extension code, for example, tfB61O_a_dev1. This process is known as the check-in and check-out process. The following figure shows the relation between the SCM procedure and the copy procedure. ![]() Note SCM only supports configuration management for the main component types such as Forms, Sessions, Table Definitions, Reports and Functions. The 4GL component types such as Labels, Questions, Messages are not supported. SCM makes use of the RCS software on the LN Server. RCS (Revision Control System) is freeware software. For more information on SCM, refer to the Infor10 ERP Enterprise Development Tools (LN) Development Guide (U8883 US). In earlier versions of Infor Enterprise Server, SCM is only available on UNIX platforms. From version 8.4.2 you can also activate SCM on Windows platforms. For details, refer to solution 230630. SCM Groups In SCM groups, developers can share their checked-out runtime components, so they can test each other's components, but they cannot change them. When you start using SCM, the system automatically generates an SCM group for you. The name of your SCM group is identical to your user name. Normally, you can only access components that belong to your own SCM group. To test a component that belongs to another SCM group (a component that was checked-out by another developer), you must modify your login configuration:
To return to your own SCM group: log off, remove the -- -set BAAN_SCM_GRP = .... setting from your Windows client configuration, and log in again. To set up the SCM environment Take the following steps to activate SCM for a VRC:
Repeat these steps for each VRC for which you want to activate SCM. Sessions The following sessions can be started from the Software Configuration Management (SCM) menu:
| |||