Generation

The overall sequence of events to generate the completed application model is as follows:

The generation process is initiated from Developer when you select the Build command or the Rebuild command. Refer to Build Options for more information on Build Options.
Builder first checks for any model structure validation error. If there are no errors, build proceeds to the next logic validation phase. In logic validation phase, Builder ensures that all the methods are validated. If any method is not validated, Builder performs the validation now. If the logic contains any errors, the generate process is cancelled. If model structure validation errors exists;
- in any system component such as Ispecs or events, generation process is aborted.
- in reports, builder excludes those reports and proceeds to the next logic validation process.
Builder determines what files/code needs to be generated by reference to the previous deployment (if any) of the application using the selected configuration to the targeted server If change analysis detects that the element has changed since it was last built, Builder generates the source files for the element.

In Windows platform, builder performs the following additional steps during generation:

When all the elements have been validated and all the source files have been generated, the compilation phase begins. The generated C# source code files are input to the compiler to be compiled and linked to produce the deployable executable components. Compilation creates dynamic link libraries (DLLs), executable files, a configuration XML file for AB Suite models, a configuration RTXML file for AB Suite Client Framework models, and other files.
A deployment package is constructed containing all of the deployable elements. This file is placed in a temporary location, specified in the Package Intermediate Directory configuration property. If this property is empty, by default, the Builder Output directory is used.
The deployment service is remotely invoked and retrieves the deployment package from the package intermediate directory and deploys the application, making any necessary database changes.

Notes:

When the user selects the Rebuild option instead of the Build option, Builder performs a complete rebuild of the selected model--no change analysis is performed.
Refer to Build Options.
If you are not able to build an AB Suite application, check whether the smbca.exe process is running in the task manager. You should stop the smbca.exe process manually to continue with the build process.

Reports might be generated and deployed separately to the Segment generation and deployment or in conjunction with it.

No matter whether reports are generated and deployed separately or with the segment, you might choose to generate and deploy:

A single report
A group of reports
All reports

Each report is generated and deployed as a separate component. However, if multiple reports are being generated and deployed at the same time they are batched up and deployed in a group.

The following table mentions the Build details for various platforms, which is applicable for an AB Suite application and AB Suite Client Framework application:

Field	Description
Start Deployment With	Set this field to Generate from the drop-down list. The build starts from the build phase specified. *Note:* This is applicable for Windows platform only.
Stop Deployment After	Set this field to Install from the drop-down list. The build ends after the build phase specified. *Note:* This is applicable for Windows platform only.
Retain Existing Database	Unchecking causes a new database to be created. *Note:* This is applicable for Windows, and MCP platforms.
Host	Name of the deployment server. *Note:* This is applicable for Windows, and MCP platforms.
User Name	Name of the user. *Note:* This is applicable for Windows platform only.
Domain Name	By default, the domain name is set to dot (.). *Note:* This is applicable for Windows platform only.
Password	The password set for the user name or user code. *Note:* This is applicable for Windows, and MCP platforms.
MultiThreaded Compilation	Checking this option enables the build process in large applications to identify the compilation streams that can be executed in parallel to speed up the overall build time on multi-CPU build machines. By default, this option is enabled and can be disabled in cases where an application must be compiled serially. In most small test applications, only a single compilation stream might be available. In these cases, the multithread compilation option does not effect compilation times. *Notes:* This is applicable for Windows platform only. Multi-thread builds might result in a build operation failure with structured exception errors. This occurs in a few models for particular environment. If you experience such structured exception errors during multi-thread builds, you can work around the problem by running the build with a single-thread. For this, go to Visual Studio and set Tools > Options > System Modeler > Builder > Number of Build Threads to 1.
Check for Inconsistencies between Online and Reports	You can select this option to check for inconsistencies in any methods, classes, and attributes defined in a segment, which are used by a report. You can select this option only if you want to introduce this additional verification. If the elements defined in a segment are used by a report and these elements have been modified after the last online system build, a warning message appears in the build log. The warning message warns you that the elements in the segment that are referenced by the report have been modified, so building the report might fail or result in report runtime errors. If any inconsistencies are detected then the build stops after completing this verification. You can deselect this option, if you want to continue with the build despite the warning, then you can submit this build again. Alternatively, you can build and deploy the online system to resolve these inconsistencies. *Note:* This is applicable for Windows platform only.
Folder is	This is the deployable Element of the model. *Note:* This is applicable for the MCP platform only.
User Code	Name of the user code. This is the same as the User Name. *Note:* This is applicable for the MCP platform only.
Access Code	The access code set for the target host installation. *Note:* This is applicable for the MCP platform only.
Access Password	The password set for the Access Code. *Note:* This is applicable for the MCP platform only.
Charge Code	The charge code for the systems user code. *Note:* This is applicable for the MCP platform only.
Use host Details for FTP	Checking the box takes the default User Code name and password as mentioned in the User Code and password fields. *Note:* This is applicable for the MCP platform only.
FTP User Code	Name of the User code. This is the same as the user name. *Note:* This is applicable for the MCP platform only.
FTP Password	The password set for the FTP User Code. *Note:* This is applicable for the MCP platform only.
FTP Charge Code	The charge code for the FTP user code. *Note:* This is applicable for the MCP platform only.
Delay Compile and Deploy	Checking this box allows you to set the date and time when you want the system to generate. *Note:* This is applicable for the MCP platform only.
Deploy Date	The date on which you want the generate to commence. *Note:* This is applicable for the MCP platform only.
Deploy Time	The time at which you want the generate to commence. *Note:* This is applicable for the MCP platform only.