Oracle FS1 GUI Simulator V1.2a Readme

1

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Internal and OPN Partner Use Only

Oracle FS Simulator

Read Me and Tutorial for Pre-Sales Use

Objective of this document

To provide the reader and user with

.

A basic understanding of the simulator and how to use it for pre-sales demonstrations

An understanding of what the FS simulator can and what it can’t do

A guide to download and install the FS simulator

A guide to Download and install the FS System Manager GUI

A tutorial on how to start the simulator with runtime parameters

A understanding of the 4 canned configurations and how to select them

How to start the System manger and log into the simulator

How to properly logout and exit from the FS System Manager

How to properly quit from the simulator

It is our intention that this document should be used in conjunction with the demonstration video

session provided. It is highly advised to view the demonstration video before proceeding.

Overview

The FS simulator provides a behavioral model for the FS Management GUIs to interact with. It is

intended to provide visual references for configuration and setup of the FS1 product. When used

as a pre-sales tool, the simulator is used to show potential customers the FS1 look and feel, how

to configure an FS and how to modify and update an FS from either Oracle FS System Manager

or the Oracle MAXman multisystem manager. Four canned system configurations are provided

with the simulator. These canned configurations are tested and verified.

The FS simulator does not simulate the function of the storage controller or DE hardware. It

cannot simulate data traffic or provide statistical reporting of data traffic.

The Simulator must be used with the provided FS System Manager. They are packaged together

and released to avoid compatibilities issues that can arise if different versions are used.

2


Lastly, The Simulator is designed for more than just pre-sales demonstrations. It is a tool used by

the FS development and test teams. Therefore, it has more function than is needed to

demonstrate the management of an FS1. You may find some of these features fascinating or

even wonder what they do. We will not be covering some of these functions and fields

parameters as part of the pre-sales use of the simulator. Manipulation beyond what is discussed

here can result in a dysfunctional simulator installation that cenn only be resolved by completely

erasing all simulator files and reloading it.

Installation and Startup The simulator will be installed via a Windows installer. This is the preferred method and avoids

potential JAVA compatibility problems. The necessary installation files are automatically installed

with no conflicts or dependencies on existing java applications or jvms. When updates are

released, the windows installer will handle removing the old files and installing the new files.

A zip/tar package is also included and will support a number of platforms. If you install manually

from the compressed package, you must know and understand your system. No support is

provided.

Download the FS simulator and FS System Manager Packages and extract it into a suitable

location. Your directory should look approximately like this:

Chose the appropriate installer version for your machine - use the x64 for 64 bit machines or the

x86 version for 32 bit machines. First, install the Oracle Simulator by clicking on that file and

allowing the installer to complete. Second, install the Oracle FS System Manager by clicking on

that file and allowing it to complete. You should chose a suitable install location on your machine

3


that is easily identifiable in the directory structure; something like C:\FS Simulator will work. You

may choose to install the simulator and the system manager in different directories. This can be

helpful if you need to erase the simulator and reload it from scratch. The System manager

installation will be unaffected.

One installed, you should have the simulator and system manager icons on your desktops

unless you choose not to install them.

Simulator Startup

To start the simulator, click on the simulator icon. I f you do not have a desktop icon, you must

select the simulator executable from the directory it was installed in. Starting from a desktop icon

is preferred.

If this is the first time you have run the simulator, you should see the start up screen that looks

like :

Before proceeding, we want to discuss the four canned configurations and how to set them up.

4


When the Simulator is first started the general console will appear. The first time running the

simulator, the fields will be blank as the above screen shot shows. You can run with the default

configuration or choose one of the canned configurations. Do not select skip and run with the

default. If you do, you will cause the simulator to create an invalid FS1 configuration and you will

not be able to recover it easily.

There are now four "canned" configuration classes in addition to the default configuration class.

The default configuration class is:

com.pillardata.consim.cache.DefaultRegressionConfiguration

The new "canned" configuration classes are:

com.pillardata.consim.cache.CannedConfig4DE2SSD2HDD

com.pillardata.consim.cache.CannedConfig8DESSD

com.pillardata.consim.cache.CannedConfig12DEMix

com.pillardata.consim.cache.CannedConfig12DEMix

In the Set simulator.Simuilator dialog when the simulator is started you can tell the simulator

which configuration class to use by adding a consim.config.load.class "Runtime Parameter" with

one of the configuration class names as its value such as any one of the following:

consim.config.load.class = com.pillardata.consim.cache.CannedConfig4DE2SSD2HDD

consim.config.load.class = com.pillardata.consim.cache.CannedConfig8DESSD

consim.config.load.class = com.pillardata.consim.cache.CannedConfig12DEMix

consim.config.load.class = com.pillardata.consim.cache.CannedConfig30DEMix

I recommend creating a different Runtime Parameters Set for each of the four canned

configurations.

When you start the simulator, click “new” in the runtime parameter sets area. The screen should

look like this:

To illustrate how to create the runtime environment, I will use the configuration as the name for

this configuration. As an example, I will choose “CannedConfig30DEMix”.and click

5


Here's a screen shot of the Set simulator.Simulator dialog with a Runtime Parameters Set named

CannedConfig30DEMix with the Runtime Parameter "consim.config.load.class =

com.pillardata.consim.cache.CannedConfig30DEMix" and click OK in the below dialogue box.

The console will return and look like the below:

Now, we will add the parameter fields. Click on Add in the above screen. The below dialogue box

will appear:

Click on the down arrow in the “Parameter Name:” box and select “consim.config.load.class

6


Next, enter the canned configuration into the Parameter value field . For our example, we will use

“com.pillardata.consim.cache.CannedConfig30DEMix “ as illustrated below. Click Add.

You should return to the console and it should look like the nelow:

In the runtime parameter window, you can use the horizontal scroll bar to see the entire

parameter.

It should be: consim.config.load.class = com.pillardata.consim.cache.CannedConfig30DEMix

7


You can set up one or more of the canned configurations and click run with these runtime

parameters or just select skip to continue.

The simulator console window will start to run.

Next, it is time to start the FS System Manager. Like the simulator, the GUI can be started by

clicking on the desktop icon or from the folder location where the GUI executable is contained to

run from the command line.

The GUI is the real FS System Manager program used to manage real hardware as well as the

simulator. When it first starts, the start-up panel is displayed.

From the FS System Manager GUI start-up panel, the default login for the simulator would be:

Axiom Name: 127.0.0.1 or localhost

Login Name: administrator

Password: pillar

The GUI should start and looks like this:

You are now running the simulator and System manager with a canned configuration!

Next, let’s go through the exit or shutdown of the GUI and Simulator

It is best to shutdown from the simulator the same way you would shutdown and /or logoff from a

real FS1. It is just good form and a good habit to avoid losing work.

8


First, on the action menu, select Oracle FS and click shutdown like the screen below.

You will see a dialogue box pop up asking you to confirm that you want to shutdown. Click Ok to

continue. Next, you will see another dialogue box that titled “Confirm Default name Forced

Shutdown”. Click on the force Shutdown button.

The System Status Screen should now look like the below – notice the lower left corner of the

screen and the yellow Diamond and CU icon:

9


The FS1 simulator is now in shutdown state. The simulator is still running. States are not the

same as actually ending the simulator program on your laptop or desktop. We will do that in an

upcoming step.

Next, go back to the Oracle FS action button and go down the dropdown window to the “Log off

localhost” field and click on it.

Next, you will see a pop-up that asks you to confirm the log off of localhost. Click OK. You will be

returned to the Log on panel of the FS System Manager. You can now simply close that dialogue

panel and the FS System Manager will close.

10


The FS Simulator is still running and needs to be closed if you aren’t going to continue to use.

Go back to the Simulator console windows. You will see a screen that looks like this:

Click on “Quit” in the lower right hand corner. The window and the Simulator program will close.

The simulator has the ability to save configurations and information modified. In the current

version, there is a bug on Windows based systems that causes configuration damage. This bug

will be fixed in the next version. And this document will be updated with the procedure to use.

The other runtime parameters are used for this purpose. They will be explained once functioning

properly.

Documents

Oracle FS1 GUI Simulator V1.2a Readme