After an administrator has created the required users and configured them correctly, you can begin the installation of Developer.
You can also create the required users when you are installing developer.
To install Developer, perform the following:
Double-click CDBrowser.exe.
The Unisys Installation Interface appears. This interface controls the installation process.
Click Development Environment.
The InstallShield Wizard appears.
Note: When this wizard appears, the installation program performs the prerequisite checks. If any of the prerequisite checks fail, then a message appears and the installation is terminated. If the checks are successful, you can continue with the installation.
On the InstallShield Wizard, click Next.
Select I accept the terms in the license agreement option, after you read and accept the terms in the license agreement, and then click Next.
Select the target drive and directory for the installation, if you do not want to accept the default installation location, and then click Next.
Note: You cannot install different versions of AB Suite Developer, such as 5.0, 6.1, or 7.0 on the same machine.
Select either of the following setup type:
Complete
Select this option to install the essential components of Developer and Target Builders. The Developer components consist of System Modeler, Debugger, Version Control Tools, Documentation, Builder, Automated Test Tool, Client Framework components, and Target Builders for Windows and MCP.
Notes:
Documentation
If Microsoft Help Viewer is installed, Documentation feature is installed when System Modeler is installed on a workstation. When documentation is installed on your workstation you can view the AB Suite online help in help viewer.
Automated Test Tool
The ATT package is installed when System Modeler is installed on a workstation. ATT supports recording of test cases for AB Suite applications and AB Suite Client Framework applications. If you want to record test cases with Component Enabler Client you need to install Component Enabler.
Client Framework
Although all Client Framework components are installed when System Modeler is installed on a workstation, you might need to install additional development tools, such as Microsoft Blend, in your environment depending on the technologies you choose for developing your client applications.
Custom
Select this option to customize the components that you want to install and click Next.
The following options appear:
System Modeler
Builders
Documentation
System Modeler
This is a mandatory feature. It installs the Developer software, which includes all the functionally required in Developer.
Builders
Select this option to install the Builder software, which allows you to build and deploy an application in both Windows and MCP runtime environment.
The Builder software should be installed if you want to run the Debugger.
Documentation
Select the Documentation feature to install the AB Suite Documentation. When you install Documentation you can view the AB Suite Developer online help through the help viewer. However, Microsoft Help Viewer must be installed.
Note: You can also view the AB Suite online help through the browser even if you do not install the Documentation feature.
Click Next and select any of the following options to create a new Application User or to select an existing Application User:
Select an Application User from existing user accounts
Create a new Application User account.
Allow Installation to automatically create the Application User.
Select an Application User from existing user accounts
You can select this option when you have an Application User created prior to the installation.
To select an Application User from existing user account, perform the following:
After you select, Select an Application User from existing user accounts option, click Next.
Enter the following credentials for the Application User:
Domain Name — Enter the Domain name of which this user is a member. If the Application User is a local user, you can simply accept the period character for the domain name or enter the name of the local machine. However, if the user has been created as a member of a network domain, the name of that domain should be entered here. This could occur if the database that Developer connects to is on a machine other than the local machine.
User Name — You can either type the Application User Name or click Browse and select the Application User name from the Select a User Name dialog box.
Password — Enter the password for the user name on the chosen domain.
Create a New Application User Account
You can choose this option to create a new Application User.
To create an Application User, perform the following:
After you select, Create a New Application User Account option, click Next.
Enter the following credentials for the new Application User:
Domain — Displays the domain name of the computer. You can either retain the domain name or type “.”.
User Name — Enter the new Application User name.
Password — Enter a password for the new Application User.
Confirm Password — Re-enter the password.
Click Create.
A message box appears confirming the creation of the application user.
Click OK on the message box.
Note: The local security policy user is automatically set by the installation. Refer to Configuring the User Accounts for more information.
Allow Installation to Automatically Create the Application User
You can choose this option to allow the installation to create a default Application User.
To automatically create an Application User, perform the following:
After you select, Allow Installation to Automatically Create the Application User option, click Next.
Enter the following credentials for the new Application User:
Display Name — Displays the domain name of your system.
User Name — Displays ABSuite70AppUser, which is the default user name created for AB Suite application user.
Note: You cannot edit the domain name and user name.
Password — Enter a password for the new Application User.
Confirm Password — Re-enter the password.
Click Create.
A message box appears confirming the creation of the application user.
Note: The new Application User is created by using this option only when it is used for the first time. If the user already exists in the system and you use this option, you will be prompted with a message –“The default user already exists. Please enter the password.”
Click OK on the message box.
Note: The local security policy for the user is automatically set by the installation. Refer to Configuring the User Accounts for more information.
Click Next and select any of the following options to create a new Application Administrative User or to select an existing Application Administrative User:
Select an Application Administrative User from existing user accounts
Create a new Application Administrative User account.
Allow Installation to automatically create the Application Administrative User.
Select an Application Administrative User from Existing User Accounts
You can select this option when you have an Application Administrative User created prior to the installation.
To select an Application Administrative User from existing user account, perform the following:
After you select, Select an Application Administrative User from existing user accounts option, click Next.
Enter the following credentials for the Application Administrative User:
Domain Name — Enter the Domain name of which this user is a member. If the Application Administrative User is a local user, you can simply accept the period character for the domain name or enter the name of the local machine. However, if the user has been created as a member of a network domain, the name of that domain should be entered here. This could occur if the database that Developer connects to is on a machine other than the local machine.
User Name — You can either type the Application Administrative User Name or click Browse and select the Application Administrative User name from the Select a User Name dialog box.
Password — Enter the password for the user name on the chosen domain.
Create a New Application Administrative User Account
You can select this option to create a new Application Administrative User.
To create an Application Administrative User, perform the following:
After you select, Create a New Application Administrative User Account option, click Next.
Enter the following credentials for the new Application Administrative User:
Domain — Displays the domain name of your system. You can either retain the domain name or type “.”.
User Name — Enter the new Application Administrative User name.
Password — Enter a password for the new Application Administrative User.
Confirm Password — Re-enter the password.
Click Create.
A message box appears confirming the creation of the application administrative user.
Click OK on the message box.
Note: The local security policy user is automatically set by the installation. Refer to Configuring the User Accounts for more information.
Allow Installation to Automatically Create the Application Administrative User
You can choose this option to allow the installation to create a default Application Administrative User.
To automatically create an Application Administrative User, perform the following:
After you select, Allow Installation to Automatically Create the Application Administrative User option, click Next.
Enter the following credentials for the new Application Administrative User:
Display Name — Displays the domain name of your system.
User Name — Displays ABSuite70AppAdmin, which is the default user name created for AB Suite application user.
Note: You cannot edit the domain name and user name.
Password — Enter a password for the new Application Administrative User.
Confirm Password — Re-enter the password.
Click Create.
A message box appears confirming the creation of the application administrative user.
Click OK on the message box.
Note: The new Application Administrative User is created by using this option only when it is used for the first time. If the user already exists in the system and you use this option, you will be prompted with a message –“The default user already exists. Please enter the password.”
Click Next.
In the Data folder screen that appears, you can either install the data files to the default location, C:\AB Suite 7.0\Data\, or click Change to install the data files to a different location.
This is the location of the Runtime Data directory that stores various data files, such as log files and configuration files.
Click Next.
In the Builder Cache Folder that appears, select the path for the Builder Cache.
The compressed copies of files generated by Builder are stored in this location. This location can be changed after the installation is complete from the Tools, Options dialog box.
When systems are generated to any target platform and multiple workstations are used for this purpose, all workstations must use a shared directory. This ensures that all the shared workstations create, modify, and read the same files in the BuilderCache directory.
To do this, perform the following:
Browse to the location of the BuilderCache directory.
Right-click the BuilderCache directory, and select Properties. The BuilderCache Properties dialog box appears.
Select the Sharing tab and choose Share this folder option.
Click Permissions and add the remote user.
In the Permissions for the BuilderCache, select the FullControl check box for the remote user.
On the remote machine, add the shared BuilderCache directory as a mapped network drive.
Set the network drive as the path for the BuilderCache directory during the Agile Business Suite installation on the remote machine.
In a multi user environment, it is recommended that all users select a shared location for the Builder Cache. This prevents unnecessary re-generates of already generated and unchanged files.
Setting the Builder Cache and Builder Output Path
You can set the builder cache path and the builder output path as follows:
Builder Cache Path
When you install AB Suite Developer, you can either set the builder cache path for All Users or for Current User only.
If you want to set the builder cache path for all users, clear the Set the Builder Cache Path for this user only check box. This check box is not selected by default.
If you want to set the builder cache path for the current user, select the Set the Builder Cache Path for this user only check box.
If there are any installation restrictions on using the C drive, you can change the builder cache path at this stage, during the installation, by clicking the Change button in the InstallShield Wizard.
Builder Output Path
The builder output path, however, can be changed from Visual Studio only. This change affects the Current User and not All Users.
To change the builder output path, perform the following steps:
Start Visual Studio after the installation of AB Suite is complete.
From the Tools menu, select Options.
The Options dialog box appears.
In the left pane, expand System Modeler, expand Builder, and then select General.
In the right pane, enter or browse to the location of your choice in the Location of Build Output box.
Note: You can also enter or browse to a location of your choice in the Location of Cache for generated files box.
If there are any restrictions on using the C drive, you can change the builder output path to an alternative drive of your choice.
Click Next.
In the Ready to Install the Program screen, click Install to begin the Installation.
If you want to change any of the installation settings you can click Back and change the settings. The Installing Agile Business Suite 7.0 Developer screen displays the progress bar.
At the completion of the installation, the Installation Complete Screen appears.
This screen displays the following options:
Show the readme file — displays the readme file when you select the check box and click Finish. You can clear the check box if you do not want to view the readme file. This check box is not selected by default.
Show the Windows Installer log — display the AB Suite <version> Runtime.log file when you select the check box and click Finish. You can clear the check box if you do not want to view the log file. This check box is not selected by default.
Click Finish to complete the installation.