Repository structure
The repository structure must be considered before creating new repositories and codes. You can change the repository structure accordingly as you become more familiar with Subversion. Here are some of the multinational project cases that you may encounter:
-
With the M3 and M3 Adaptation Kit integration, there are possible name clashes that you have to manage.
-
Development is done locally against a local M3 Business Engine (BE) instance, but the source is shared in the same repository.
-
Developing against M3 environments running on multiple servers, at the same time sharing a single repository.
For example
A root folder must contain the repository and must provide a structure that enables you to identify certain elements.
For example, C:\repository\M3_folder_v1.
where:
C:\repository\ is the top level folder on
the server C:\ drive, and
M3_folder_v1\ is the root folder
for the M3 on runtime server.
The example structure allows you to create repositories for
other M3 instances on the same runtime server, for example C:\repository\M3_folder_v1.2.
This example shows how to create the root folder structure and not the actual repository. The concept and structure is basically the same for both Windows and iSeries. If you choose to use a different structure, you must consider the same issues, and remember that the same environment names can exist in multiple M3 instances.