Auto-build

Refer to the OI Core Communications Driver Help for information about the Auto-Build process. Key points to remember include:

• Specify a new Galaxy as the target Galaxy until you are familiar with how Auto-Build works. This will help to avoid accidentally overwriting objects.

• Always specify a prefix. This will also help you avoid overwriting objects and lets you differentiate between similarly-named controllers.

• Use pre-check validation to catch illegal object names, such as names that exceed the maximum number of characters and that contain illegal characters. Note that Auto-Build skips names with errors.

• You can only run one Auto-Build process at a time.

• The user who launches the OCMC must be part of the oiAdministrators Windows Local Users and Groups to access the Auto-Build functionality

• Auto-Build add two levels of derivation to accommodate different layers of standardization, for example, corporate standards (global) and local standards.

Auto-Build creates a DI Object for you. The DI Object is derived from the $DDESuiteLinkClient template, and will include the two character prefix that you specify (first character must be alphabetic, the second character can be a letter or number (alphanumeric). The DI Object must include at least one scan group (topic).

The Auto-Build process adds the prefix that you specified to all objects it captures. After Auto-Build completes, you can view, test, and adjust object assignments as needed, using the different IDE views.

• Use the Deployment view to modify object assignments.

• Use the IO Devices view to modify scan group assignments.

• Use the IO Device Mappings view to verify and test IO references.