Installing Rational Statemate : Installing Rational Statemate on Windows : Completing a custom installation

Completing a custom installation

To complete a custom installation:

Note: These steps might vary slightly, depending on what features are selected.
1.
Select Custom as the installation type. Click Next.The Select Features screen opens.
2.

Statemate (Classic) - Traditional Rational Statemate. This version does not contain Micro C components.

Statemate 4.6 - Rational Statemate plus Micro C components.

OS Definition Tool - Optional. Custom operating system configuration.
Statemate MicroC OSI’s - if using the Automotive Open System Architecture (AUTOSAR) or more OS implementations, select this option.

Help Files - These are the Rational Statemate documentation and Help files.

Stmlockman - Required to run the stmlockman daemon on the current system. This Windows service serializes access to the file pm.dat and prevents conflicting write requests from corrupting the file.

Encrypted Files - Optional. These are additional source files and libraries, some of which are encrypted and require an encryption key from Customer Support to extract them.

Nutcracker Service - Required. This provides the porting environment from UNIX-based software to the Microsoft Windows operating system.

Support Info

Note:
The amount of disk space required and available is displayed on this screen. A Rational Statemate Setup message opens if there is not enough disk space on the selected disk.
3.
Click Next. The Help directory screen opens.
4.
Select a location for the Rational Statemate Help files. To change the default location, click Browse. Click Next. The Select Program Folder screen opens.
5.
Choose a name for the Rational Statemate program folder. Select a folder from the Existing Folders list or to change the default, enter the name. Click Next. The Tool Settings File (run_stmm.bat) screen opens.
6.
Select whether to use the pre-configured run_stmm.bat file or to configure it.

The run_stmm.bat file contains several environment variables and is used to start Rational Statemate.

To configure the run_stmm.bat file manually, select Configure the run_stmm.bat file now and click Next. The Set Tools Flag screen opens. Continue to Step 7.

To use a pre-configured run_stmm.bat file:

Select Use Pre-configured run_stmm.bat File. Click Next. The Tool Settings File (run_stmm.bat) screen opens.
Select the location where the run_stmm.bat file is located. If necessary to locate the file, click Browse. Click Next.

If you choose to add Rational Statemate plus Micro C components, the OSEK Path Setting screen opens.
Select Define OSEK path or Use default OSEK path. Click Next.

If you select Define OSEK path, the Set OSEK Path (OSEK Application Only) screen opens. Select the OSEK path to be used when building an OSEK application. Click Next. The Start Copying screen opens. Continue to step Step 26.

If you select Use default OSEK path, the Start Copying screen opens. Continue to Step 26.
7.
Note:
8.
Click Next. The Preferences Directory locations screen opens.
9.
Specify a location for your preferences files. To change the default location, click Browse. Click Next. The Project Management folder location screen opens.
10.
Specify a location for your project management files. To change the default location, click Browse. Click Next. The Configure C Code Generator Reserved Words file to use screen opens.
11.
Note:
12.
Click Next. The Configure Rational DOORS Settings screen opens.

To configure the Rational DOORS interface later, select Configure Later, then click Next. The Select the type of license you want to configure screen opens. Continue to Step 20.

To configure the Rational DOORS interface, select the Configure Now and click Next. The Configure Rational DOORS Settings screen opens.

13.

SET DXLPORTNO=5093 - sets the port number for communication between the Rational DOORS server and Rational Statemate.

SET DXLIPHOST=%COMPUTERNAME% - must be set on the local machine and the path cannot contain any spaces in the settings. (Use the 8.3 syntax; for example, “progra~1” instead of “program files”)

SET DOORSS_BATCH_FILE=doorss.bat - sets the path to the batch file used by Rational Statemate to run Rational DOORS. By default, Rational Statemate creates the file DOORS.bat.

14.
Click Next. The second Configure DOORS Settings screen opens.
15.

@REM SET RT_NO_OLE=ON (When commented out, exports objects as OLE objects. By default, this line is commented out.)

SET PATH=%PATH%;%DOORSHOME%\bin (specifies the path to the Rational DOORS application)

16.
Click Next. The DOORS Invocation File (run_doors.bat) screen opens.
17.
Specify a location for the file run_doors.bat. To change the default location, click Browse. Click Next. The DOORS Home Path Setting screen opens.
18.
Specify the home path for Rational DOORS. To change the default location, click Browse. Click Next. The DOORS License File Path screen opens.
19.
Specify the full path to your Rational DOORS license file. Click Next. The Select the type of license you want to configure screen opens.
20.

Local/Server License use this option to run your license server on the system of the current installation. Complete the following steps:

Click Next. The License Management file location screen opens.
Specify the default location for your license file. To change the default location, click Browse. Click Next. The Enter Stmlockman Hostname screen opens.

Client License use this option when the license server runs on a remote license system. Complete the following steps:

Click Next. The Enter License Details screen opens.
Enter the name of the license server for the current client. To specify a port number, use the format port@servername; otherwise use the server name. Click Next.

Configure Later use this option to configure your license after running the Rational Statemate installation. Click Next. The Enter Stmlockman Hostname screen opens. Continue to Step 21.

21.
Enter the host name of the Stmlockman server. Click Next. The OSEK Path Setting screen opens.
22.

Define OSEK Path - Complete the following steps:

Select Define OSEK Path. Click Next. The Set OSEK Path (OSEK Applications Only) screen opens.
Specify the OSEK path. To change the default location, click Browse. Click Next. The Set Users-List Browse Information screen opens.

Use Default OSEK Path - Select Default OSEK Path. Click Next. The Set Users-List Browse Information screen opens.

23.

None - No external user list extraction. The list of users is built from the defined users in the pm.dat file. Click Next. The Start Copying Files Screen opens.

Windows domain users - This is the standard Windows environment users management. The users list is built by using the domain users and the defined users in the pm.dat file. Click Next. The Windows Domain Controller Setting screen opens. Continue to Step 24.

From file - The users list is built from the content of a text file, named UsersList.txt, in which each non-empty line is considered to be a username, and the defined users in the pm.dat file. Complete the following steps:

Click Next. The User-List File Name screen opens.
Specify the location of the text file listing the possible users. Click Next. The Start Copying Files screen opens. Continue to Step Step 26.
24.
Add the primary and secondary domain controller names beginning with double backslashes (\\). Click Next. The Group Type Information screen opens.
25.

All - Select All to include all group types in the User-List browse information. Click Next. The Start Copying Files screen opens. Continue to Step 26.

Local Group

Select Local Group. Click Next. The Local Group Information screen opens.
Enter the name of the Local Group. Click Next. The Start Copying Files screen opens.

Network Group

Select Networks Groups. Click Next. The Network Group Information screen opens.
Enter the name of the Network Group. Click Next. The Start Copying Files screen opens.
26.
The Start Copying screen opens with the settings you specified. Click Next to confirm your selections. The installation wizard adds Rational Statemate and the External Software (third-party) that you selected.
27.
If you chose to add the NuTCRACKER service, the Choose Destination Location screen opens so that you can select the directory for the NuTCRACKER installation. Either accept the default location or click Browse to select an different directory. Click Next.

The Setup Status screen opens and shows the files being copied to the selected directory.
28.
29.
30.
Click Yes. If you must run the XServer installation manually, click No and see the instructions in the Manually installing the MKS XServer section.
31.