TE-42_M-AARS-ISM.pdf

CODE IDENT

16331

NUMBER

JLCCTC-0007-14

REV

C

UNCLASSIFIED

AFTER ACTION REVIEW SYSTEM (AARS) & INDEPENDENT

SIMULATION MODULE (ISM)

VERSION M-AARS-ISM v6.2.2

OPERATOR & MAINTENANCE MANUAL (O&M)

Contract Number: W900KK-13-D-002

CDRL: H001

INSTALLATION/CONFIGURATION/RUNTIME SIMULATION

MANAGEMENT PROCEDURES

Document Number: JLCCTC-0007-14

July 25, 2014

Prepared For:

U.S. Army Program Executive Office Simulation, Training, and Instrumentation (PEO STRI) 12350 Research Parkway

Orlando, Florida 32826-3276

Prepared By:

Lockheed Martin, Corporation, Mission Systems and Training (MST)

100 Global Innovation Circle Orlando, Florida 32825-5003

Copyright 2011

Lockheed Martin Corporation Rights to the U.S. Government are apportioned pursuant to DFARS 252.227-7013 and 252.227-7014

DISTRIBUTION STATEMENT C:

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS. OTHER REQUESTS FOR

THIS DOCUMENT SHALL BE REFERRED TO PEO STRI.

NUMBER

JLCCTC-0007-14

PAGE INTENTIONALLY LEFT BLANK

NUMBER

JLCCTC-0007-14

iii

CHANGE HISTORY

DATE REV MOD PAGES DESCRIPTION

22 NOV 13 - All Reformatted to same look and feel as the rest of the jlcctc documents.

10 MAR 14 A All Incorparated customer comments from draft delivery

04 APR 14 1 All Updates for IE6. Made changes to account for replacement of Scalix email server with iRedMail. Updated Section 5.2 including Table 6, Section 5.3, Section 5.4.3, Section 6.2 and replaced Appendix A.

7 JUL 14 B All Updated with changes from customer review 25 JUL 14 C All Updated with changes from customer review.

NUMBER

JLCCTC-0007-14

iv

PAGE INTENTIONALLY LEFT BLANK

NUMBER

JLCCTC-0007-14

v

Table of Contents CHANGE HISTORY........................................................................................................................ III

TABLE OF CONTENTS ................................................................................................................... V

LIST OF FIGURES .........................................................................................................................VII

LIST OF TABLES ...........................................................................................................................VII

1 CHECKLISTS FOR BUILDING EACH NODE

1.1 AARS/ISM Road Map

1.2 AARS Checklist

1.3 Mapserver Checklist

1.4 ISM Checklist

1.5 AARS 2D Client Checklist

2 INTRODUCTION

2.1 Cautions and Notes

2.2 List of Abbreviations and Acronyms

2.3 jlcctc Help Desk Contact Information

3 MRF AARS / ISM ARCHITECTURE

4 SCENARIO GENERATION

5 INSTALLATION

5.1 Operating System and Hardware Requirements

5.2 Software License Requirements

5.3 jlcctc Lockdown Installation

5.3.1 jlcctc REDHAT Linux Enterprise Lockdown Installation

5.3.2 jlcctc Windows 7 (and Apps Disk) Lockdown Installation (2 DVDs)

5.4 Linux Apps Installation

5.4.1 AARS Installation

5.4.2 Mapserver Installation

5.4.3 ISM Installation

5.5 Windows App Installation

5.5.1 AARS 2D Client Installation

6 CONFIGURATION

6.1 AARS Server Configuration

6.1.1 Copy configuration files

6.1.2 High Level Architecture Overview

6.1.3 RTI Configuration

6.1.4 HOG Configuration

6.1.5 LAARC Configuration

6.2 ISM Server Configuration

6.2.1 Copy configuration files

NUMBER

JLCCTC-0007-14

vi

6.2.2 pSM Configuration

6.2.3 oSM Configuration

6.2.4 IP Address Configuration

6.2.5 E-mail Server Configuration

6.3 AARS 2D Client Configuration

6.3.1 AARS 2D Client Configuration

6.3.2 AARS 2D Client Terrain Installation

6.4 Mapserver Configuration

7 TECH CONTROL OPERATION

7.1 AARS Server Operation

7.1.1 HOG Operation

7.1.2 LAARC

7.1.2.1 Startup/Operation

7.1.2.2 Start Up AARS 2D Clients

7.1.2.3 2D Client Late Join

7.1.2.4 AARS Checkpoint Restore/Pause Resume

7.1.2.5 AARS Shutdown

7.2 ISM Server Operation

7.2.1 oSM Operation

7.2.2 Event Generator Operation

7.2.3 ISM Checkpoint Restore

7.2.4 ISM Shutdown

7.2.5 MISC operation

7.2.5.1 When Scenario.dat file is updated

7.2.5.2 When JNEM resigns from the federation and rejoins

8 INSTALLATION VERIFICATION TEST

9 TROUBLESHOOTING

9.1 AARS

9.2 ISM

9.3 Map Server

9.4 All Linux Applications (AARS-ISM-Mapserver)

Appendix A Configuring the ISM EMAIL System

1 ISM MAIL SERVER

2 WEBMAIL CLIENT

3 MAIL GROUPS MANAGEMENT

NUMBER

JLCCTC-0007-14

vii

List of Figures Figure 3-1. AARS-ISM MRF Network Architecture Figure 6-1. pSM Configuration Figure 6-2. pSM Info Flow Figure 9-1. Event Manager Error Figure 9-2. startOSM script - default Figure 9-3. startOSM script - fixed Figure 9-4. Event Generator Workstation Map Problem Figure 9-5. Event Generator Workstation Map Problem

List of Tables Table 1-1 AARS/ISM Road Map Table 1-2 AARS Checklist Table 1-3 Mapserver Checklist Table 1-4 AARS Checklist Table 1-5 AARS 2D Client Checklist Table 5-1 Software Licenses Required

NUMBER

JLCCTC-0007-14

1 CHECKLISTS FOR BUILDING EACH NODE

This Section contains several checklists to be used when building each Node within the AARS and ISM Systems.

CAUTION

To ensure a successful system installation, it is imperative that each step in each of the following series of checklists is completed in sequence. If this is overlooked, the potential for failure in the follow-on phases is high.

1.1 AARS/ISM Road Map

Table 1-1 AARS/ISM Road Map AARS/ISM Road Map

X Print/Review Document Found on Disk jlcctc_RHEL5_64BIT_Install_Config_Guide_XXXXXXX.d oc and any jlcctc_RHEL5_Revision. The documents in the directory jlcctc_Lockdown_Files jlcctc RHEL SLD Release disk provided from the CTS release. *

Installation Guide for AGM X.X.X Microsoft Windows 7 SPx

AGM Windows 7 Release disk provided from the jlcctc or CTS release. * jlcctc Windows 2008 Lockdown Procedures jlcctc Windows 2008 Lockdown Disk provided from the jlcctc or CTS release. * **

AGM X.X.X Windows 7 (64-bit) Secured Operating Configuration Procedures jlcctc Windows 7 Lockdown Disk provided from the jlcctc or CTS release. *

*Note: The site MRF Lead should have the disks mentioned above.

X AARS/ISM Road Map Build Order Complete jlcctc LINUX Lockdown Installation for AARS (if necessary) from section 5.3.1

Complete jlcctc LINUX Lockdown Installation for Mapserver (if necessary) from section 5.3.1

Complete jlcctc LINUX Lockdown Installation for ISM (if necessary) from section 5.3.1

Complete jlcctc Windows 7 Lockdown Installation for AARS 2D Client (if necessary) from section 5.3.2

Complete AARS Installation from section 5.4.1

Complete Mapserver Installation from section 5.4.2

Complete ISM Installation from section 5.4.3

Complete AARS 2D Client WS Installation from section 5.5.1

Complete AARS Configuration from section 6.1

Complete ISM Configuration from section 6.2

Complete Installation Verification Test from section 8

NUMBER

JLCCTC-0007-14

1.2 AARS Checklist

Table 1-2 AARS Checklist X Pre-Installation Checklist Verify correct version of jlcctc Lockdown is applied to the target machine Obtain AARS/ISM DEVSWMRFW v.6.2.2 Linux Apps installation media Review Hardware Specs Obtain AARS IP Address Obtain ISM IP Address Obtain Mapserver IP Address Obtain WARSIM Database (oranfs1) IP Address

X Pre-Configuration Checklist Obtain WARSIM UOE files Obtain JNEM Senario.dat file Obtain RTI License Server (dcnfs1) IP Address Obtain RTI.rid file Obtain Correction version of .fed file Ensure User rtmuser is a member of the wheel group.

NUMBER

JLCCTC-0007-14

1.3 Mapserver Checklist

Table 1-3 Mapserver Checklist X Pre-Installation Checklist Verify correct version of jlcctc Lockdown is applied to the target machine Obtain AARS/ISM DEVSWMRFW v.6.2.2 Linux Apps installation media Review Hardware Specs Obtain AARS IP Address Obtain ISM IP Address Obtain Mapserver IP Address Obtain WARSIM Database (oranfs1) IP Address Make sure you have the Terrain Drive (Hard Drive)

None

NUMBER

JLCCTC-0007-14

1.4 ISM Checklist

Table 1-4 AARS Checklist X Pre-Installation Checklist Verify correct version of jlcctc Lockdown is applied to the target machine Obtain AARS/ISM DEVSWMRFW v.6.2.2 Linux Apps installation media Review Hardware Specs Obtain AARS IP Address Obtain ISM IP Address Obtain Mapserver IP Address Obtain WARSIM Database (oranfs1) IP Address Obtain ISM Tactical Net IP Address

X Pre-Configuration Checklist Obtain WARSIM UOE files Obtain JNEM Senario.dat file Ensure User rtmuser is a member of the wheel group.

Obtain Inject Points information (Email Addresses and Unit names)

NUMBER

JLCCTC-0007-14

1.5 AARS 2D Client Checklist

Table 1-5 AARS 2D Client Checklist X Pre-Installation Checklist Verify correct version of jlcctc Lockdown is applied to the target machine Obtain AARS/ISM DEVSWMRFW v.6.2.2 Linux Apps installation media Review Hardware Specs Obtain AARS IP Address Obtain Mapserver IP Address

Find out terrain required for exercise

NUMBER

JLCCTC-0007-14

2 INTRODUCTION

This document describes the use of the After Action Review System (AARS) and Independent Simulation Module (ISM) server software. AARS and ISM in the MRF federation provide near real time reporting on activity within the simulation via the AARS-2D Client and the AARS Reporting Tool (ART), as well as the interface to the Joint Non-Kinetic Effects Model (JNEM) via the Event Generator Workstation (EG). The technical installation and operations of the AARS and ISM machines is described within this document.

It is assumed that the user of this document has received initial training on AARS and ISM operations, and understands basic LINUX operating system, networking, database and client server concepts and procedures. Every attempt has been made by the AARS and ISM Graphical User Interfaces (GUIs) to simplify the complex task of managing simulation information flow and federation and client connectivity while maintaining flexibility and compatibility with the ever-changing world of simulations and tactical messaging.

This document is organized similarily to WARSIM Tech Control document. However, since the content for this document is a lot smaller, the volumes are organanized as corresponding chapters.

The following describes each of the Chapters dedicated to AARS/ISM Tech Control:

• Chapter 3 - Architecture Overview

• Chapter 4 – Senario Generation

• Chapter 5 – Installation

• Chapter 6 – Configuration

• Chapter 7 – Tech Control Operation

• Chapter 8 – Installation Verification

• Chapter 9 – Troubleshooting

2.1 Cautions and Notes

Cautions and notes are used to emphasize important and critical instructions for the following conditions:

CAUTION

An operating procedure, practice, etc., if not correctly followed, could result in damage to or destruction of the system software.

NUMBER

JLCCTC-0007-14

NOTE

Information or operating procedure that is essential to highlight.

2.2 List of Abbreviations and Acronyms

Throughout this manual, abbreviations and acronyms are used. The objective is to spell out these abbreviations and acronyms the first time they are attempted. Thereafter, the abbreviation and/or acronym are used except in paragraph titles and formal lists.

CAUTION

Each phase and corresponding procedures are specifically arranged in the order they are to be performed. DO NOT diverge from this sequence.

CAUTION

All graphics are for examples only. The information shown in some fields may be incorrect. Use the information in the procedure text to determine correct values to use.

2.3 jlcctc Help Desk Contact Information

Please contact the jlcctc Help Desk for any help needed with installation or use of the AARS, ISM, Mapserver or AARS 2D Client systems.

Phone: (407) 306-7583 (M-F 0900-1700 Eastern) E-Mail: jlcctc.helpdesk@lmco.com

NUMBER

JLCCTC-0007-14

3 MRF AARS / ISM ARCHITECTURE

Figure 3-1. AARS-ISM MRF Network Architecture represents the three separate machines and the connections made to the federation and clients using the simulation network and the tactical network. While there is no “one size fits all” in the world of military simulations, the AARS- ISM Suite is no different. Due to dependencies within the client-server nature of AARS, ISM, and Mapserver, the following rule applies: if the exercise will include JNEM or the EG, both machines (AARS and ISM) need to be installed, as the AARS machine provides the HLA interface to the simulation. If only AARS is used, then the technician does not need to install and configure an ISM machine. The basic requirement remains: connect to the simulation and to the AARS Clients and tactical computers where required.

Figure 3-1. AARS-ISM MRF Network Architecture

The AAR machine hosts the High Level Architecture (HLA) interface to the MRF Run Time Infrastructure (RTI) on the simulation network, as well as the Live After Action Review Collector (LAARC) that provides the data feed to AARS-2D Clients. The ISM machine receives the HLA simulation information from the AARS machine, and provides both the EG web server as well as the C2 messaging interface. The tactical network connects the ISM to the live Command and Control (C2) systems – normally the All Source Analysis System – Light (-L) or Distributed Common Ground System (DCGS-A) for intelligence messages. The MapServer provides detailed map images for simulation use. It is important to remember that an AARS-ISM technical operator has to understand the connectivity requirements for the ISM suite prior to configuration. While many changes can be made during operations, AARS-ISM-Mapserver remains reliant upon others to provide a properly configured network in order to ensure success.

Since most installations of AARS-ISM will be static in a Mission Command Training Center (MCTC) or Simulation Center, the network configurations may remain unchanged from exercise

MRF

NUMBER

JLCCTC-0007-14

to exercise, with only the tactical network requiring an update. The requirement of the ISM machine is to have a presence on the tactical network. This must be understood by the network administrators.

NOTE

Due to the increased use of remote/distributed simulation exercises, the above diagram is only a guide. In order to properly configure the various network interfaces within the suite, a thorough understanding of the applications and data flow is required.

NUMBER

JLCCTC-0007-14

4 SCENARIO GENERATION

This section is not applicable to AARS, ISM, Mapserver and 2D Client.

NUMBER

JLCCTC-0007-14

5 INSTALLATION

5.1 Operating System and Hardware Requirements

These installs have been tested and verified to run on the Common Hardware Platform (CHP HP 8400) computers. The process of loading machines has been automated to the fullest extent possible, and works on all standard fielded CHP computers, including HP 8400’s and HP z800’s.

Each of the separate components is loaded in the same manner – with the operator choosing which type of machine to build from a menu pick-list.

The AARS-ISM MRF Suite uses a customized set of CDs which include:

• jlcctc RedHat Linux Enterprise Lockdown (version 03MAR2014)

• jlcctc Windows 7 Lockdown Disk (version 03MAR2014)

• jlcctc Windows 7 Apps Disk (version 03MAR2014)

5.2 Software License Requirements

Software licenses are provided based on the Hardware configuration installed at the time of fielding. Based on the make-up of any particular exercise and the hardware used, additional licenses may be required. The table below lists the Software Licenses required by machine type.

Table 5-1 Software Licenses Required Node Name Operating

System COTS Software

L i n u x

W n d o w s

A G M

P o s t g r e s

A p a c h

T o m c a t

R e d M a l

R T I N G

P r o

M S

O f f i c

AARS 1 1 1 1

ISM 1 1 1 1 1

Mapserver 1 1 1 2D Client 1 1

* Microsoft Office is licensed through the Windows AGM Software ** License is provided through License Server (dcnfs machine)

5.3 jlcctc Lockdown Installation

Complete this Section if the operating system is not installed. If the operating system is installed go to Section 5.4.

NUMBER

JLCCTC-0007-14

5.3.1 jlcctc REDHAT Linux Enterprise Lockdown Installation

STEP ACTION RESULT

1. Power on system. Computer starts booting sequence.

2. Insert jlcctc RHEL5 Lockdown DVD.

3. Press appropriate System Key to select boot device. (Optical Drive)

4. Select boot from Optical Drive and press Enter.

Linux Kickstart Screen appears

5. At the Linux Kickstart Screen, type server and then press Enter.

6. The machine will automatically install the Operating System.

When finished the following Reboot prompt will appear.

7. Press Enter to reboot.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

8. While machine is rebooting, eject the disc BEFORE the machine begins to boot up or it will boot up to the kickstart screen again!

Localhost login prompt appears.

9. Login with:

• Username: root

• Password: (Ask system administrator)

Logged in as root and command prompt is ready.

10. Type system-config-display

System-config-display appears.

11. • Select Hardware tab o Select Configure button for

Monitor Type o Expand Generic LCD Display o Select LCD Panel 1280x1024 o Select OK

12. • Select Settings tab o Select the Resolution drop down o Select 1280x1024 o Select OK o It will tell you that the settings were changed.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

13. Select OK

You will then be returned to a command prompt Disregard warnings about lost connection to display

14. Once back at the command prompt, enter startx

This starts up the Gnome Desktop environment.

15. • Right-click on desktop and select terminal.

• Type cd /tmp/jlcctc_Lockdown_Files

• Type ./jlcctc_Lockdown_Script_1.

script

It starts the jlcctc Lockdown Script 1.

It prompts to enter the Security Level.

16. Select the proper classification available from the prompted menu

The script continues and prompts to press <Enter>

17. During the remaining processing of the lockdown script, the user will be prompted several times for hit <Enter> to continue.

Accept all default values and the final <Enter> request will reboot the system.

Do not press <Enter> until prompted.

Script continues to advance and reboots the machine when complete. After the machine reboots, you will be prompted with a graphical login.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

18. Login

• Username: admin

• Password: (Ask system administrator)

Security Agreement appears

19. Accept the Security Agreement by clicking on ACCEPT button

20. Right-click on desktop and open a terminal

21. Type su – Enter password : (Ask system

22. cd to /tmp/jlcctc_Lockdown_Files Type ./jlcctc_Lockdown_Script_2.script and press enter.

jlcctc_Lockdown_Script_2.script starts

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

23. 1) Select n when asked about

NFS

2) Select n when asked if this machine is the log collector.

3) During the execution the user will be prompted to set the grub password.

Enter the desired grub password twice.

4) Copy and paste the encrypted string that gets displayed. Highlight the string and paste it (middle-click) where the cursor is blinking and press <Enter>.

5) Select “n” when asked if you are updating a Warsim system?

6) Accept all remaining defaults and hit <Enter> when prompted

7) Finally you will be prompted to hit <Enter> to reboot. Do so and let the machine reboot.

24. The jlcctc RHEL5 Lockdown OS installation is now complete.

You can now install any of the Linux Apps (AARS, ISM, or Mapserver) See section 5.4.

5.3.2 jlcctc Windows 7 (and Apps Disk) Lockdown Installation (2 DVDs)

1. Insert the jlcctc Windows 7 Lockdown disc into the computer and reboot the machine.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

2. Press appropriate System Key to select boot device. (Optical Drive)

3. Select boot from Optical Drive and press Enter.

You will get a blue background with US Gold Master title.

4. 1) Enter the Computer Name (e.g.

AARS2DClient001)

2) Enter the time zone (i.e.

(UTC-0500) Estern Time (US & Canada))

3) Enter the Administrator Password: (Ask system

The system starts the installation and reboots several times When done, the Windows 7 automatically starts and logs you in.

5. 1) A window pops up with the following message: Operating System Deployment Completed Successfully.

2) Select Next

A dialog pops up asking you to insert Windows 7 Application (Disk 2) and run app_setup.exe

6. Insert Windows 7 Application (Disk 2)

7. 1) Select Windows Start Computer and navigate to D:

drive or DVD ROM drive.

2) Execute app_setup.exe

Installer GUI appears

8. Keep default applications and select Run Installer

This installs the selected applications and the windows indicates the progress of the installation in the lower right corner showing # of applications being installed out of total selected applications.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

9. 1) Wait until all installation is completed. It will indicate a reboot is required.

2) Select OK

Computer reboots and Windows 7 Login window appears

10. CTRL+ALT+DELETE to log on as Administrator - Password: (Ask system administrator)

11. The AARS 2D Client software requires use of the “Windows Classic” theme to display properly. To change the theme, perform the following steps:

1) Right-click on the desktop and select Personalize

2) Select the Windows Classic theme

12. The jlcctc Windows 7 Lockdown OS installation is now complete.

You can now install AARS 2D Client (AARS, ISM, or Mapserver) See section 5.5.

5.4 Linux Apps Installation

The following installation procedures describe AARS, ISM, and Mapserver installation steps.

These applications install on the jlcctc REDHAT Linux Enterprise Lockdown OS.

Prior to the installations, you need the following IP Addresses:

• AARS Server (machine name – aars1)

• ISM Server (machine name – ism1)

• Map Server (machine name – mapserver)

• RTI License Server (aka dcnfs)

• WARSIM DB (aka oranfs)

You also need the following information:

• admin password

• root password

• rtmuser password

NUMBER

JLCCTC-0007-14

5.4.1 AARS Installation

STEP ACTION RESULT

1. Login to jlcctc RedHat Linux Enterprise Lockdown machine as admin.

Security Agreement window appears.

2. Accept the Security Agreement by

3. Insert the AARS/ISM Linux Application Install DVD media into the CDROM

4. Open a terminal window (Right click on the desktop Open Terminal)

A Terminal window appears.

5. In the terminal window, type su – and enter the <<root password>>

Logged in as root.

6. In the terminal window, type mount /media/dvd Note: May need to use cdrom instead of dvd e.g. mount /media/cdrom for this and the following steps which refer to dvd

This mounts the installation media in the /media/dvd directory

7. In the terminal window, type cd /media/dvd

This changes the directory to the location of the install script - /media/dvd.

8. In the terminal window, type bash rtminstall

This starts the installation script The environment portion will begin to unpack and this may take a couple of minutes to complete.

Once the environment portion unpacks, the user will get prompted for server.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

9. Type aars1 The user will then get prompted to set up the machine’s networking. Network Configuration window pops up.

10. 1) Click on eth0 and click the “Edit” button

2) Select “Statically set IP addresses” and then type in the machine’s IP address, subnet mask and gateway address of this machine

3) Make sure that the box is checked for “Activate device when computer starts”

4) Select OK

1) Ethernet device window pops up

4) Ethernet device window closes

11. 1) Select the DNS tab

2) Set the Hostname to aars1

12. 1) Select Hosts tab

2) Select each machine Edit

3) Enter correct IP Address (Edit only the IP address unless you are using different domain name, then you need to update the domain names as well)

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

13. 1) Select Devices tab

2) Select eth0

3) Select Deactivate

4) Select Activate Note this step is different if accessing through remote desktop or Exceed. Instead of activating and deactiviating the interface the following command should be run as root – Type service network restart and press enter.

If this alternate step is not taken the installation will fail.

This restarts the network interface eth0

14. 1) File Save

2) File Quit

This exits out of the network configuration tool

15. The install script will automatically complete the rest of the setup and install for this machine type.

Upon completion, the machine automatically reboots.

16. When the machine reboots, login as rtmuser and use <<rtmuser default password>> Accept the Security Agreement by clicking on ACCEPT button

You should see LAARC and HOG icons on the desktop.

Continue installing the rest of the AARS/ISM components. When all installation and configuration is complete, see chapter 8 for the installation verification steps.

5.4.2 Mapserver Installation

1. Login to jlcctc RedHat Linux Enterprise Lockdown machine as admin.

Security Agreement window appears.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

4. Open a terminal window (Right click on the desktop Open Terminal)

A Terminal window appears.

5. In the terminal window, type su – and enter the <<root password>>

Logged in as root.

6. In the terminal window, type mount /media/dvd Note: May need to use cdrom instead of dvd e.g. mount /media/cdrom for this and the following steps which refer to dvd

This mounts the installation media in the /media/dvd directory

7. In the terminal window, type cd /media/dvd

This changes the directory to the location of the install script - /media/dvd.

script.

The environment portion will begin to unpack and this may take a couple of minutes to complete.

Once the environment portion

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

9. Type mapserver The user will then get prompted to set up the machine’s networking.

Network Configuration window pops up.

2) Select “Statically set IP addresses” and then type in the machine’s IP address, subnet mask and gateway address of this machine

3) Make sure that the box is checked for “Activate device

2) Ethernet device window pops up

5) Ethernet device window closes

2) Set the Hostname to mapserver

3) Enter correct IP Address (Edit only the IP address unless you are using different domain

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

13. 1) Select Devices tab

2) Select eth0

3) Select Deactivate

4) Select Activate Note this step is different if accessing through remote desktop or Exceed. Instead of activating and deactiviating the interface the following command should be run as root – Type service network restart and press enter.

If this alternate step is not taken the installation will fail.

This restarts the network interface eth0

14. 1) File Save

2) File Quit

This exits out of the network configuration tool

15. The install script will automatically complete the rest of the setup and install for this machine type.

Machine will restart at the end of the installation.

Upon completion, the machine automatically reboots.

16. Power down the machine.

Insert terrain drive into the machine.

Boot up the machine.

17. When the machine reboots, login as rtmuser and use <<rtmuser default password>> Accept the Security Agreement by

18. 1) Open a terminal window

2) Type df –h to see if the terrain drive is mounted.

(/usr/local/mapdata/terrain)

3) Open up Firefox and open http://mapserver:8086.

You should be able to see the maps and click to view the interactive map page.

Continue installing the rest of the AARS/ISM components. When all installation and configuration is

NUMBER

JLCCTC-0007-14

5.4.3 ISM Installation

STEP ACTION RESULT

1. Login to jlcctc RedHat Linux Enterprise Lockdown machine as admin.

Security Agreement window appears.

4. Open a terminal window (Right click on the desktop Open Terminal)

A Terminal window appears.

5. In the terminal window, type su – and enter the <<root password>>

Logged in as root.

6. In the terminal window, type mount /media/dvd Note: May need to use cdrom instead of dvd e.g. mount /media/cdrom for this and the following steps which refer to dvd

This mounts the installation media in the /media/dvd directory

7. In the terminal window, type cd /media/dvd

This changes the directory to the location of the install script - /media/dvd.

script.

The environment portion will begin to unpack and this may take a couple of minutes to complete.

Once the environment portion

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

9. Type ism1 The user will then get prompted to set up the machine’s networking.

Network Configuration window pops up.

2) Select “Statically set IP addresses” and then type in the machine’s IP address, subnet mask and gateway address of this machine

3) Make sure that the box is checked for “Activate device

Ethernet device window pops up

Ethernet device window closes

2) Set the Hostname to ism1

3) Enter correct IP Address (Edit only the IP address unless you are using different domain

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

13. File Save Saves Changes

14. 1) Select Devices tab

2) Select eth0

3) Select Deactivate

4) Select Activate Note this step is different if accessing through remote desktop or Exceed. Instead of activating and deactiviating the interface the following command should be run as root – Type service network restart and press enter.

If this alternate step is not taken the installation will fail.

This restarts the network interface eth0

15. 1) File Quit This exits out of the network configuration tool and the installation continues.

After a few minutes the user will be prompted to enter the domain administrator (postmaster) password.

16. Type the postmaster password and select < Next >

The install script will automatically complete the rest of the ISM setup and install for this machine type. At the end it recommends a reboot. Reboot is actually mandatory.

17. Reboot the machine Machine reboots.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

18. When the machine reboots, login as rtmuser and use <<rtmuser default password>> Accept the Security Agreement by clicking on ACCEPT button

You should see pSM, OSM, and EG Console icons on the desktop.

Continue installing the rest of the AARS/ISM components. When all installation and configuration is

5.5 Windows App Installation

The following installation procedures describe AARS 2D Client installation steps. The application installs on the jlcctc Windows 7 Lockdown OS.

Prior to the installations, you need the following IP Addresses:

• AARS Server

• Map Server

You also need the following information:

• xadministrator password (Ask system administrator)

• Which terrain database to use

5.5.1 Windows Firewall –Disable and Stop

STEP ACTION RESULT

1. Login to jlcctc AARS 2D Client Windows machine as xadministrator with <<xadministrator password>>

Logs into the Windows as xadministrator.

2. Select OK to any security information/warnings.

Desktop for xadministrator appears.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

3. Click on Start (Windows, ) in lower left hand corner on the toolbar.

Start menu appears.

4. Enter services in the “Search programs & files” search box.

Search Results appear.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

5. At the top of the search results under Programs click on Services.

This may take several minutes.

Windows Services window pops up.

Note: If User Account Control Settings are on then an Account Control Window will pop up. Type in the admin username and password.

Sometimes the User Account Window comes up minimized. If it comes up minimized you will see a flashing gold shield on the taskbar. Click the shield to bring up the Accunt Control Window.

6. Scroll down the Services list until Windows Firewall appears and double click on the name.

Windows Firewall Properties window pops up.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

7. First change Startup type to Disabled and then select stop.

Startup type shows disabled and Service status shows Stopped.

8. Select OK. Windows Firewall Properties window closes.

9. Close the Services window by clicking the ‘X’ in the upper right hand corner.

Services window disappears.

5.5.2 AARS 2D Client Installation

STEP ACTION RESULT

1. If necessary Login to jlcctc AARS 2D Client Windows machine as xadministrator with password. If already logged in go to step 3.

Logs into the Windows as xadministrator.

2. Select OK to any security information/warnings.

Xadministrator desktop appears.

3. Insert the AARS 2D Client Application Installation DVD into the computer.

DVD tray closes.

4. Open Windows Explorer and Navigate to the DVD drive

Content of DVD appears.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

5. Execute setup.exe by double-clicking it.

Note: If hide file extensions for known file types property is turned on in the Windows Explorer settings the “.exe” porition may not show up. The file type is “Application” for this file. The associated icon is blue with a sailboat in white.

Install shield wizard appears.

6. Select install from the popup installation window.

AARS_MRF Installation window

7. Select Next on AARS_MRF V6.2 popup window.

AARS Setup window appears.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

8. 1) Enter IP Address of the AARS1 Server

2) Leave Printer to No Printer.

3) Select Next.

AARS File destination setup window appears.

9. Keep the default for the AARS File destinations set up and select Next

AARS Setup window appears.

10. Select Typical and select Next Select Features window appears.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

11. Keep the default and select Next The dialog provides a summary of the components which will be installed.

12. Select Next The installation process launches the installation of the TechSmith Screen Capture Codec.

13. Select Install TSCC Installation Complete Message appears.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

14. Select OK C++ 2008 SPI Installation window

15. Select Next Licnese Agreement window appears

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

16. 1) Read the agreement

2) select the checkbox if you agree

3) select Install

MS Visual C++ Setup Complete message appears

17. Select Finish The final dialog indicates that the installation of the AARS 2D Client application is complete.

18. Select Finish

19. You have completed the installation of an AARS 2D Client.

You should see AARS Login icons on the desktop.

20. See Section 6.3 AARS 2D Cleint Configuration for additional steps needed before using.

NUMBER

JLCCTC-0007-14

6 CONFIGURATION

6.1 AARS Server Configuration

AARS Server includes 2 Graphical User Interfaces (GUI) components: High Level Architecture Operations GUI (HOG) and Live After Action Review Collector (LAARC). These two components must be configured for the exercise prior to the operation for the training.

6.1.1 Copy configuration files

The following files are necessary to configure AARS Server Configuration.

• Download correct RTI.rid and FOM.fed (e.g. MRF_v6_3_FOM.fed) file to /home/rtmuser/HLA directory. These files can be found from the federation webpage setup (e.g. http://fmtr:8080/jlcctc; machine name may vary) by the federation manager.

• Copy WARSIM Universe of Entities (UOE) file into /home/rtmuser/import/mrfw directory. This file can be found in warsimdb machine (a.k.a. WARSIM oranfs1 server) /common/scenarios/<scenario_name>/xxxxxCOMMON0/ directory. Suggest logging into the oranfs1 machine as the techctrl user. If the user rtmuser is not part of the wheel group then the file may need to be copied as a different user. Make sure to ask WARSIM Tech Controller for the correct version of the file. Scenario name can be found from Virtual Controller Console window on the vcws1 machine by looking at the Object Model Explorer sub-window in the upper left. The scenario name is the first bullet under “My Commands”. Upon copying the file, unzip or untar it in the same directory overwriting the original files.

• Copy JNEM scenario.dat file into /home/rtmuser/import/jnem directory. The file can be another name with .dat extention. This file is typically found in JNEM server /home/jnem/jnem/dat directory. Make sure to ask JNEM Tech Controller for the correct version of the file. If the user rtmuser is not part of the wheel group then the file may need to be copied as a different user.

6.1.2 High Level Architecture Overview

In the MRF federation, AARS/ISM Suite includes a High Level Architecture (HLA) Operations GUI (HOG) interface which provides interactions with federate models, including the Joint Non- Kinetic Effects Model (JNEM). The HOG application and associated control GUI is automatically installed on the aars1 machine. HOG is the interface between the AARS and the Run Time Infrastructure - RTI. This interface extracts objects and interactions, publishes objects or interaction for other MRF federates to use. In addition, this interface allows for interoperability between the Event Generator and the Joint Non-Kinetic Effects Module (JNEM).

In MRF, this process connects to the ism1 machine via the simrtm process.

NUMBER

JLCCTC-0007-14

6.1.3 RTI Configuration

Basic setup prior to starting any executable is as follows:

1. Ensure that your network interface is set-up correctly. Once logged into the desktop as rtmuser, verify that the AARS machine is on the Simulation network, and can ping a gateway or other federate members.

2. Get the latest RTI.rid and FOM.fed file (name changes but always ends with .fed) from the federation manager and install it in the home/rtmuser/HLA directory.

3. Scroll to the RTI.rid file configuration under the networking sections. Change the FederateEndpoint to the IP for the AARS Server e.g. FederateEndpoint 192.168.0.2.

Port is not needed so remove “:port”. If this line is commented out make sure to uncomment before exiting.

All executables reside in home/rtmuser/HLA directory. These steps must be done in order for initial startup. After connectivity is made, stop and restart the hero process.

6.1.4 HOG Configuration

HOG allows the ISM operator to connect to the federation and publish or subscribe to specified objects or interactions via the RTI. HOG provides the GUI component and there are two more components to the HLA interface: The HLA Application Manager (HAM) and HLA Entity Relay Object (HERO) executables. HERO connects to the federation and HAM connects to the ISM Sim Inteface.

STEP ACTION RESULT

1. (HOG) Double click HOG icon on the desktop

The welcome screen will appear

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

2. 1) Select Configuration tab

2) Select HAM tab

3) check the value boxes for

“play jnem” and “use sim”

4) Select Save

3. 1) Select the HERO tab

2) auto join: uncheck this option

3) federate name: ISM_HLA

4) federation name:Confederation_1

5) fom file: MRF.fed – Select the

“Browse” button and navigate to the FED file that was previously loaded in the /home/rtmuser/HLA directory.

6) hla stats sleep: 60

7) rti address: 127.0.01 -

Change this value to the IP address of the RTI License Manager. (Typically WARSIM dcnfs1 IP)

8) rti config path: is of the form /opt/RTI-NG-Pro-vX.X.X/Linux-rehX.X-i386-gcc- X.X.X-opt-mt/config/rtienv.csh

9) rti port: 27000

10) save dir:

/home/rtmuser/HLA

11) Select Save

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

4. 1) Click on the Network tab:

2) sim address: This should be the IP address of the ISM Server (ism1) where the SIMRTM process is running.

3) Select Save

5. This completes the HOG, HAM, and HERO configuration.

NOTE: A tech may need to move “.sav” and “.save” files out of the “HLA” directory and move them over to the “opt” directory should the overall “home” directory allocated memory starts to fill up (df –h to view this). This is if MRF v6.1 Federation Tech Control is sending “save” files to each of the Federates to be saved locally on their box. The other option is to make a soft link on the overall “HLA” directory over to the “opt” directory.

6.1.5 LAARC Configuration

LAARC provides the following major capabilities:

• Connects to the WARSIM AUI database

• Collects the simulation information into the AARS RTM database

• Connects to the AARS 2D Clients to provide simulation data

STEP ACTION RESULT

1. Double-click the LAARC icon on the desktop

This displays the set-up window for the LAARC

2. Select Configuration Tab

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

3. Select Data Collection Tab

4. Set following information correctly:

• AARS Database Password:

(Ask system administrator)

• AARS Database Name: rtm

• AARS Database User:

rtmuser.

May need to scroll down for the following items.

• WARSIM Database Password:

check with WARSIM tech control

• WARSIM Database Name:

check with WARSIM tech control (typically AUI)

• WARSIM Database User:

check with WARSIM tech control (typically rtmuser)

5. Select Save

6. Select LAARC Tab under CONFIGURATION Tab

7. Set following information:

• ASAS Directory:

home/rtmuser/LAARC/ASAS

• DCGS Directory:

home/rtmuser/LAARC/DCGS

• jdlm dir: /home/jdlm

• jnem file:

/home/rtmuser/import/jnem/( file name).dat (Browse and select the scenario file received from JNEM)

• Repository Directory:

home/rtmuser/LAARC/REPOS

• Use Dead Reckoning: Check this Box

• use jdlm: Check this Box

• use jnem file: Check this

Box

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

8. Select Save

9. Select the NETWORK tab Under the CONFIGURATION Tab

10. Set following information:

• AARS Database IP: 127.0.0.1

• WARSIM Database IP:

warsimdb

11. Select Save

12. This Completes the LAARC Configuration.

6.2 ISM Server Configuration

The Plans Scenario Manager (pSM) is a graphical user interface (GUI) application that operates within a workspace on the ISM Linux desktop. It provides the operator the ability to incorporate simulation database information, configure application messaging and communications parameters required for the Event Generator operations. The overall purpose of the pSM is to create the necessary ISM database initialization files prior to simulation operations.

The pSM has one basic interface: It imports the initial data files from the simulation, and prepares them for the scenario management functionality. The pSM prepares ISM data files during both the pre-execution and execution phases of a simulation event.

6.2.1 Copy configuration files

The following files are necessary to configure ISM Server Configuration.

• Copy WARSIM Universe of Entities (UOE) file into /home/rtmuser/import/mrfw directory. This file can be found in warsimdb machine (a.k.a. WARSIM oranfs1 server) /common/scenario/<scenario_name>/xxxxxCOMMON0/ directory. Make sure to ask WARSIM Tech Controller for the correct version of the file. Scenario name can be found from Virtual Controller Console window on the vcws1 machine by looking at the Object Model Explorer sub-window in the upper left. The scenario name is the first

NUMBER

JLCCTC-0007-14

bullet under “My Commands”. Upon copying the file, unzip or untar it in the same directory overwriting the original files.

• Copy JNEM scenario.dat file into /home/rtmuser/import/jnem directory. The file can be another name with .dat extention. This file is typically found in JNEM server /home/jnem/jnem/dat directory. Make sure to ask JNEM Tech Controller for the correct version of the file.

6.2.2 pSM Configuration

For pSM Configuration begins with importing two (2) sets of files: WARSIM UOE files, and JNEM <scenario>.dat files. UOE files include the simulation data from the WARSIM database.

Importing the scenario data allows the ISM operator to import the unit types from the WARSIM database files which will ultimately make them available to the EG Workstation operator. JNEM <scenario>.dat file includes the JNEM scenario information such as neighborhood and various groups defined within JNEM.

The charts below show the data flow and tasks an operator must complete in order to prepare the data files for export and transfer to the ISM. Many of the selections within the pSM are already properly set during a pSM build; however the ISM Operator has the ability to change these settings. It is important to note that an incorrect setting in the pSM may cause the ISM processes to fail. If any specific data settings are not known, leave the default data settings alone. In many cases, the initial data set provided will work.

At a minimum, the following tasks must be completed for each exercise:

1. Configuration:

The pSM allows the user to manipulate many inter-process communication (IPC) settings as well as environmental variables. See Figure 6-1. pSM Configuration.

• Select specific messages of interest

• Establish tactical network for ISM

• Associate Warfighting Functions processes with ISM machine

NUMBER

JLCCTC-0007-14

Figure 6-1. pSM Configuration

2. Info Flow:

Information flow is the heart of the RTM process. As an information manager, the RTM Suite is able to send the right message at the correct time to the right recipient. Many of the settings within the pSM are simply associations: associating units with inject points, associating messages with units, etc. The “Info Flow” menu brings together all of the data that has been configured up to this point. As shown in Figure 6-2. pSM Info Flow, there are two (2) main areas of information flow: message and intelligence.

• Associate BFA with Reporting Structure

• Select reporting headquarters

• Establish inject points

• Associate message flow with inject points

• Verify event criteria (time/event)

• Export Data files

• Check files for accuracy

NUMBER

JLCCTC-0007-14

Figure 6-2. pSM Info Flow

1. IMPORT

2. Double-click the green pSM icon

Database Login dialog appears

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

3. Enter pSM Database password: (Ask pSM window appears

4. Select Import MRF-W Import MRF-W Data window appears

Note: The number of files may vary.

5. Select Import Import status window appears

Once complete a screen will appear showing any files that did not import correctly.

6. After the Import button is selected a terminal window will appear, scrolling thru all of the import data. Once the import process is complete, if the import was not successful, a message will appear in the window indicating bad files. Any bad files detected during import will be located in the /home/rtmuser/ldr directory.

Change directories to /home/rtmuser/ldr to resolve issues with any .bad file listed.

If there are any questions about these files, contact the Senior ISM Operator for assistance.

Once all problems are fixed, or if there are no bad files, a final window will appear as next column.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

7. Select importJNEM There will be a prompt asking to confirm the delete of the existing neighborhoods.

8. Select Yes File selection dialog appears

9. Browse to /home/rtmuser/import/jnem directory and select the correct <scenario>.dat file.

Select OK

Once the Import JNEM process is done, it will display unit information with simulation unit count and the count of neighborhoods filled out.

10. Configure Events

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

11. Select ConfigEvent

1) Select Enter Event Attributes

Tab

2) Select the correct Event

Classification

3) Leave rest of the fields alone. You may enter Event ID and Event Name, but they are not required

4) Select Save

Manage Event Configuration window opens

12. Select System of Interest Tab

1) Select all interested systems

2) If unsure, select all three

3) Select Save

13. Select Message of Interest Tab

• The specific messages that the

RTM will build are found here.

To provide maximum flexibility within the RTM, various formats are available. It is important to work with the Subject Matter Experts (SME)'s at the receiving inject point to ensure the proper type messages are selected.

• If desired to select all messages,

1) Select Select by C4I System

2) Select All

3) Select OK

4) Select Close

• Select Save

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

14. Select Simulations of Interest Tab

1) Check the interest box

15. Select Save Select Close

16. Configure Network

17. Select ConfigNetwork Select Network Configuration Tab

18. Enter the Tactical IP Address of the ISM, and leave the E-mail address, O/R Name, URN, and C4I Name field set to their default values.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

19. • The default E-mail address field value is: rtmuser@ism1

• The default O/R Name field value is (33 characters between the colon): :~~~~RTMSIM~~~USMAIN~OPS~~RTM1~~~~:

• NOTE: The RTM portion of the O/R Name value must always match the

RTM machine name. IE: machine rtm1 is O/R Name of:

:~~~~RTMSIM~~~USMAIN~OPS~~RTM1~~~~: Machine rtm2 is O/R Name of: ~~~~RTMSIM~~~USMAIN~OPS~~RTM2~~~~:

• The default URN value for rtm1 is: 1999151

• The default C4I Name value for rtm1 is: 1 - This value must always match the number attached to the end of the RTM machine name. IE: rtm1 would equal C4I Name; rtm2 would get a C4I Name of 2.

Document the default values for the E-mail address, O/R Name, and URN fields in case a value is accidentally deleted or changed.

Reference this document to re-enter the default values in the necessary fields.

In order to stimulate tactical C4I systems, the RTM is treated as another host on the tactical network, and in some cases, is initialized on more than one network due to exercise architecture considerations. The RTM Operator or Exercise Lead should contact the Communications Officer/G-6 for this information.

Select Save

20. Select IPC Configuration tab

21. Change the HLA IP address to the actual IP address (Control Net IP) of the AARS server that the HLA runs on for ISM to receive simulation HLA data and the ISM EG workstation to receive unit and situational SIM data.

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

22. Configure Message

23. Select ConfigMessage

24. Select WFF Event Configuration Tab.

Ensure 1 is selected for machine name for all.

25. NOTE

The “Message Header Defaults” tab is available for review and verification. This tab should be used with caution (shown below), as the entries made in this window determine how the RTM constructs each specific message type and how it transmits the message to the receiving inject point. Once again, the default data loaded when the pSM is built contains the correct information in most cases.

Select Save

The “JNEM Message Radius” Tab is available for review and verification. The entries made in this window determine the ISM radius in meters for reporting an event or incident to units in the area. Adjust the interval based on unit density in the Area of Operations.

Select Save

The “JNEM Message Interval” tab is available for review and verification. The entries made in this window determine the ISM interval for sending Civilian Activity Report (CAR) to Training Audience Unit Mailboxes. It defaults to every 6 minutes, but can be adjusted to change the optempo of the exercise.

26. Select Save

27. Information Flow

28. Select Info Flow Message

29. Select Select Message Flow Defaults Tab

NUMBER

JLCCTC-0007-14

STEP ACTION RESULT

30. Verify the Primary WFF (BFA) is associated with the proper Reporting Structure in the “Select Message Flow Defaults” tab.

31. Select Select Reporting Headquarters Tab

32. The next step in managing the information flow is to determine the reporting headquarters. By their very nature, military organizations are organized into a hierarchal structure.