1.

Oracle Express Installation Guild

Hardware requirement

Requirement Minimum Value: - Physical memory (RAM) 1 GB minimum - Virtual memory Double the amount of RAM - Disk space Total: 4.76 GB - Video adapter 256 colors - Processor 550 MHz minimum (On Windows Vista, 800 MHz minimum)

1. Oracle Express Installation Guild

Hardware requirement

Hard Disk Space Requirements on NTFS:

Installation Type TEMP Space C:\Program Files\Oracle 3.1 MB Oracle Home Datafiles * Total

Basic Installation

200 MB

2.96 GB

1.60 GB

4.76 GB

1. Oracle Express Installation Guild

Software requirement

Software Requirement:
Requirement Value

System Architecture

Processor: Intel (x86), AMD64, and Intel EM64T Note: Oracle provides 32-bit (x86), 64-bit (Itanium), and 64-bit (x64) versions of Oracle Database for Windows. The 32-bit database version, which this installation guide describes, runs on the 32-bit version of Windows on either x86 or x64 hardware. Oracle provides limited certification for 32-bit Oracle Database on 64-bit Windows (x64).

1. Oracle Express Installation Guild

Requirement
Software Operating System

Value

requirement

Software Requirement:

Oracle Database for 32-bit Windows is supported on the following operating systems: Windows 2000 with Service Pack 1 or later. All editions, including Terminal Services and Microsoft Windows 2000 MultiLanguage Edition (MLE), are supported. Windows Server 2003 - all editions Windows Server 2003 R2 - all editions Windows XP Professional Windows Vista - Business, Enterprise, and Ultimate editions Windows NT is not supported. Windows Multilingual User Interface Pack is supported on Windows Server 2003, Windows Server 2003 R2, Windows XP Professional, and Windows Vista.

1. Oracle Express Installation Guild

Step 1

1. Oracle Express Installation Guild

Step 2

1. Oracle Express Installation Guild

Step 3

1. Oracle Express Installation Guild

Step 4

Default Username:

SYSTEM or SYS
Password: someFOLK

1. Oracle Express Installation Guild

Step 5

port numbers are the default values:

a. 1521: Oracle database listener b. 2030: Oracle Services for Microsoft Transaction Server c. 8080: HTTP port for the Oracle Database XE graphical user interface

1. Oracle Express Installation Guild

Step 6

1. Oracle Express Installation Guild

Step 7 - When complete installation press finish.

1. Oracle Express Installation Guild

Check Oracle Service

To check Oracle service weather is running. 1) Goto Control Panel, select Administrative Tools ---> Services.

The following services must in started status :

OracleServiceXE OracleXETNSListener

If the services is not started, please start it.

1. Oracle Express Installation Guild

Check Environment Variables

To set the environment variable for oracle application:1) Goto Control Panel, select System. In the System Properties window, select Advanced tab.

2) In the Advanced tab, click on Environment Variables button.

Please set the following parameter in User Variable column:Variable

Path

Value
D:\oraclexe\app\oracle\product\10.2.0\server\BIN

Please set the following parameter in System Variable column:Variable Path ORACLE_HOME Value D:\oraclexe\app\oracle\product\10.2.0\server\BIN D:\oraclexe\app\oracle\product\10.2.0\server

1. Oracle Express Installation Guild

Check Oracle XE connection

Click the Start button > Run. In the column, type cmd. This will open a command line window similar to Window Command Prompt.
In the Window Command Prompt environment, type sqlplus. Follow by enter the user-name sys as sysdba and password someFOLK.

When a message Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 Production SQL> is shown, which mean it successfully connected to Oracle XE database.

1. Oracle Express Installation Guild

2. Install Schema Object

Install schema object for hts application

List of sql script that install schema object for hts application 01ora_user_schema.sql

- create user hts_dba with password someFOLK, and grant privileges

02ora_util.sql - create utilities function called by procedures, triggers

03ora_table_view.sql
04ora_index.sql 05ora_context.sql

- create context that can store session information

06ora_procedure.sql 07ora_trigger.sql

2. Install Schema Object

Execute SQL script

- Login as sys user (database super user) and execute 01ora_user_schema.sql to create hts_dba user.

- If the sql script is store under d:\sql_script\01ora_user_schema.sql, then execute the command as SQL> @d:\sql_script\01ora_user_schema.sql,

2. Install Schema Object

Execute SQL script

- Follow by connect to hts_dba user (hts application user) just created and execute rest of the sql script ( from 02ora_util.sql to 07ora_trigger.sql )

SQL> connect hts_dbs/someFOLK@XE Connected. SQL>@02ora_util.sql

2. Install Schema Object

Examine the hts database

- To examine the hts database is created, please execute the following command:-

SQL> select table_name from user_table order by table_name;

The result will be same as following figure.

2. Install Schema Object

TABLES list for HTS database

ACCUMULATORDAILY ACCUMULATORHOURLY ACCUMULATORMONTHLY ANALOGDAILY ANALOGHOURLY ANALOGMONTHLY ANALOG_TEMP CARDREADERINFO CARDUSERINFO DIGITALDAILY DIGITALHOURLY DIGITALMONTHLY DRIBBLE HISTALMEVT HISTANALOGSCENARIO HISTCARDACCESSLOG HISTCHOICEINFO HISTCURR HISTDIGITALSCENARIO HISTMCHOICEINFO HISTORY HISTORYINFO HISTSEVERITYINFO HISTUSERINFO HOURANALOG HOURDIGITAL SUMMARYEVENT

2. Install Schema Object

3. History Storage Configuration

Specify data to be stored into History Database

This section of configuration determine : 1) How much online data ( history data and summary data ) is keeped in history database by configuring purging duration of each set datas ( History Data Changes, Analog Hourly Summary data ...) 2) Whether the online data is generated of each set data To configure : Select the menu item shown in Figure 3-1, which is Config Manager, the popup shown in Figure 3-2 will appear.

3. History Storage Configuration

Figure 3-1

3. History Storage Configuration

Figure 3-2

3. History Storage Configuration

Attribute Name AnalogHourly

Description Indicates whether hourly analog summary data needs to be generated.

RDBMS Table AnalogHourly

Default Yes

AnalogDaily

Indicates whether daily analog summary data needs to be generated.

Indicates whether monthly analog summary data needs to be generated. Indicates whether hourly digital summary data needs to be generated. Indicates whether daily digital summary data needs to be generated. Indicates whether monthly digital summary data needs to be generated.

AnalogDaily

Yes

AnalogMonthly

AnalogMonthly

Yes

DigitalHourly

DigitalHourly

Yes

DigitalDaily

DigitalDaily

Yes

DigitalMonthly

DigitalMonthly

Yes

3. History Storage Configuration

Attribute Name AccumulatorHourly

Description Indicates whether hourly accumulator summary data needs to be generated.

RDBMS Table AccumulatorHourly

Default Yes

AccumulatorDaily

Indicates whether daily accumulator summary data needs to be generated. Indicates whether monthly accumulator summary data needs to be generated. Indicates whether the alarm and event messages need to be stored in relational database.

AccumulatorDaily

Yes

AccumulatorMonthly

AccumulatorMonthly

Yes

AlarmEvent

HistAlmEvt

Yes

3. History Storage Configuration

Attribute Name

Description

RDBMS Table

Default

SettingTable

Indicates whether some of the configuration settings such as ChoiceInfo and SeverityTable, need to be stored in relational database.

HistSeverityInfo HistAnalogScenario HistDigitalScenario HistChoiceInfo HistMChoiceInfo HistUserInfo

Yes

PurgeHistDuration

Determines the duration in days for history transaction to be kept in relational database. Determines the duration in days for the hourly summary data to be kept in relational database. Determines the duration in days for the daily summary data to be kept in relational database.

History or t%08X_%08X

60

PurgeHourlyDuration

AnalogHourly DigitalHourly AccumulatorHourly

60

PurgeDailyDuration

AnalogDaily DigitalDaily AccumulatorDaily

60

3. History Storage Configuration

Attribute Name PurgeMonthlyDuration

Description Determines the duration in days for the monthly summary data to be kept in relational database. Determines the duration in days for the alarm and event data to be kept in relational database. Determines the time offset in minutes for hourly summary data to be generated.

RDBMS Table AnalogMonthly DigitalMonthly AccumulatorMonthly

Default 730

PurgeAlmEvtDuration

HistAlmEvt

60

HourlyOffsetTime

N/A

DailyOffsetTime

Determines the time offset in minutes for daily summary data to be generated.
Determines the cut off time in minutes for daily summary data to be generated.

N/A

15

DailyCutOffTime

N/A

3. History Storage Configuration

4. SCADA IO Points History Storage Settings ( History Mode )

Every SCADA IO point can be configured whether they will be updated to relational database individually. The configuration can be done via AnalogBase/ DigitalBase/ MiscBase Dialog of the point respectively. In Figure 4-1, the History section illustrates the history setting for DigitalBase point. Table 4-2 explains the meaning of each setting.

4. SCADA IO Points History Storage Settings ( History Mode )

Figure 4-1

4. SCADA IO Points History Storage Settings ( History Mode )

Table 4-2 Attribute Name HistoryMode Description Specifies either to store every transaction from RTDB or only selective transaction. Always archive - Update every change No archive - Do not update Interval archive - Update according to HistoryInterval configuration Value archive - Update only if value change Default No archive

HistoryInterval

Specifies the scan interval, only used when History Mode is Interval Archive Not used

NumHistCount

4. SCADA IO Points History Storage Settings ( History Mode )

5. Accessing RDBMS as History Database

Connect to Sybase Adaptive Server Enterprise (ASE12.5.4)

To connect to Sybase with hts, specify the command arguments -l as 0, and -S as username, -P as password, -S as sybase sql server name and -D databasename(default databasename is hts).
( Example , -Uusername -Ppassword -Ssqlservername -Dhts -l0 )

Connect to Oracle (10g2 Standard/Express Edition)

To connect to Oracle with hts, specify the command arguments -l as 2, and -S as username, -P as password, -S as oracle connect identify and -D database alias name(default user name is hts_dba, default database alias name is hts). ( Example, -Uhts_dba -Ppassword -Sconnectidentidy -Dhts -l2 )

5. Accessing RDBMS as History Database

6. Supervising hts executing under WillowLynx

To supervising hts , the WillowLynx startup script will need to edited. Example line that need to put in startup script is : For using Sybase Adaptive Server as History Database SYSTEM RUN 50 NONE -Uusername -Ppassword -Ssqlservername Dhts -l0 or

( Hts -Usa -PsomeFOLK -SLOCALHOST -Dhts -l0 -m1 -g0 -b1 -d1 )

For using Oracle as History Database

SYSTEM RUN 50 NONE -Uhts_dba -Ppassword -Sconnectidentidy Dhts -l2

or ( hts -Uhts_dba -PsomeFOLK -SXE -DXE -l2 -m1 -g0 -b1 -d1 )

6. Supervising hts executing under WillowLynx

7. HTS command line option

No
1 2 3

Opt ion
-U -P -S

Description History RDBMS login user name History RDBMS login password Sybase Sql Server Name ( For Library mode 0 ) or Oracle Connect Identidy (For Library mode 1 ) or ODBC Database Source Name (For Library mode 2 ) Default hts

-D

Database name ( For Library mode 0, 1 ) or Database Alias name ( For Library mode 2 ) Default hts
Determine library used to connecting History RDBMS, 0 CT-Lib (For Connecting Sybase Only), 1 ODBC lib, (For connecting any ODBC 3.5 supported RDBMS ) 2 Pro*C Lib ( For Connecting Oracle Only ) Default 0 History RDBMS , 0 - sybase, 2 - mysql , 1 - oracle, not used RTDB Hostname, Default localhost Gateway mode, not used

-l

6
7 8

-R
-h -g

7. HTS command line option

9 10

-n -s

Gateway register name, not used 0 Do not connect to supervisor 1 - Connect to supervisor until successed 2 - connect to Supervisor if supervisor is running Default 2 History data changes storage option, 0 Store all changes in single table, 1 Store all changes separately for each point. Default 0 Bulk Copy Mode, 0 dont use bulk copy, 1 use bulk copy. Default 0 Point Information Mapping HistCurr table update interval. 0 Update every changes, > 0 Update lastest changes periodic which interval is number of miniutes specified. Default 0

11

-m

12 13

-b -a

14

-r

PointType code. PointType of AnalogBase Point will treated as Accumulator Type point. Default 200

15 16

-w -f

Dribble folder path Default $SCADA_PROJECT/rtdb/runtime RTDB dribble filename ( without specify parent directory ) in the Dribble folder to start reading from. Default In the $SCADA_PROJECT/rtdb/Index, between the label runtime, and project, the string as drb_vXX_XXX will be used as default value

17

-d

Debug mode, 0 - Debug off, 1 - Debug on, > 1 Debug on with more messages Default 0

7. HTS command line option

8. WillowLynx retrieve HTS database data

Retrieve Hts database data by Alarm Search

1) In the SysDisplay, select Operations > Search Alarm(s).

2) In the Search Alarm(s) popup window, do the selection as below:Search Criteria: String

Current View: Historical Alarm

Alarm Type: Alarm, Event

If database search successfully, then the result will show as figure 8.1;
If WillowLynx failed connect to Oracle hts database, then the result will show as figure 8.2

8. WillowLynx retrieve HTS database data

Figure 8-1

8. WillowLynx retrieve HTS database data

Figure 8-2

8. WillowLynx retrieve HTS database data

Retrieve Hts database data by Trend

1) In the Schematic page, double click on gadget to display its runtime popup which show in figure 8.3.
2) In the runtime popup window, then click on Trend button, then Trend Display popup window is display which show in figure 8.4.

3) If the WillowLynx successfully connect to Oracle HTS database, then the trend pen will plot in continuous line. Else, it will display the trend pen line plot as dotted-line.

8. WillowLynx retrieve HTS database data

Figure 8-3

8. WillowLynx retrieve HTS database data

Figure 8-4

Toolbar Area

Current DateTime Indicator

Status Indicator

Plot Area

Sliding & Scaling Area

Trend Marker

Legend Table

8. WillowLynx retrieve HTS database data