8/13/2019 OracleXE

1/47

1. Oracle ExpressInstallation Guild

8/13/2019 OracleXE

2/47

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)

8/13/2019 OracleXE

3/47

1. Oracle Express

Installation Guild

Hardware requirement

Hard Disk Space Requirements on NTFS:

InstallationType

TEMPSpace

C:\ProgramFiles\Oracle

OracleHome

Datafiles * Total

BasicInstallation

200 MB 3.1 MB 2.96 GB 1.60 GB 4.76 GB

8/13/2019 OracleXE

4/47

1. Oracle Express

Installation Guild

Software requirement

Software Requirement:

Requirement Value

SystemArchitecture

Processor: Intel (x86), AMD64, and Intel EM64TNote: Oracle provides 32-bit (x86), 64-bit (Itanium),and 64-bit (x64) versions of Oracle Database forWindows. The 32-bit database version, which this

installation guide describes, runs on the 32-bitversion of Windows on either x86 or x64 hardware.Oracle provides limited certification for 32-bit OracleDatabase on 64-bit Windows (x64).

8/13/2019 OracleXE

5/47

1. Oracle Express

Installation Guild

Software requirement

Software Requirement:

Requirement Value

OperatingSystem

Oracle Database for 32-bit Windows is supported onthe followingoperating systems:

Windows 2000 with Service Pack 1 or later. Alleditions,including Terminal Services and Microsoft Windows2000MultiLanguage Edition (MLE), are supported.Windows Server 2003 - all editionsWindows Server 2003 R2 - all editions

Windows XP ProfessionalWindows Vista - Business, Enterprise, andUltimate editionsWindows NT is not supported.Windows Multilingual User Interface Pack issupported on WindowsServer 2003, Windows Server 2003 R2, Windows XP

Professional, andWindows Vista.

8/13/2019 OracleXE

6/47

1. Oracle Express

Installation Guild

Step 1

8/13/2019 OracleXE

7/47

1. Oracle Express

Installation Guild

Step 2

8/13/2019 OracleXE

8/47

1. Oracle Express

Installation Guild

Step 3

8/13/2019 OracleXE

9/47

1. Oracle Express

Installation Guild

Step 4

Default Username:

SYSTEM or SYSPassword: someFOLK

8/13/2019 OracleXE

10/47

1. Oracle Express

Installation Guild

Step 5port numbers are the default values:

a. 1521: Oracle database listener

b. 2030: Oracle Services for MicrosoftTransaction Server

c. 8080: HTTP port for the OracleDatabase XE graphical user interface

8/13/2019 OracleXE

11/47

1. Oracle Express

Installation Guild

Step 6

8/13/2019 OracleXE

12/47

1. Oracle Express

Installation Guild

Step 7 - When complete installation press finish.

8/13/2019 OracleXE

13/47

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

OracleXETNSListenerIf the services is not started, please start it.

8/13/2019 OracleXE

14/47

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 Propertieswindow, select Advanced tab.

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

Please set the following parameter in User Variable column:-

Variable Value

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

Please set the following parameter in System Variable column:-

Variable Value

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

ORACLE_HOME D:\oraclexe\app\oracle\product\10.2.0\server

8/13/2019 OracleXE

15/47

1. Oracle Express

Installation Guild

Check Oracle XE connection

Click the Start button > Run. In the column, type cmd. This willopen a command line window similar to Window Command Prompt.

In the Window Command Prompt environment, type sqlplus. Followby enter the user-name sys as sysdba and password someFOLK.

When a messageConnected to: Oracle

Database 10g ExpressEdition Release 10.2.0.1.0Production SQL> isshown, which mean itsuccessfully connected toOracle XE database.

8/13/2019 OracleXE

16/47

2. Install Schema Object

8/13/2019 OracleXE

17/472. 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

8/13/2019 OracleXE

18/472. Install Schema Object

Execute SQL script

- Login as sys user (database super user) and execute01ora_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,

8/13/2019 OracleXE

19/47

2. Install Schema Object

Execute SQL script

- Follow by connect to hts_dba user (hts application user)just createdand execute rest of the sql script ( from 02ora_util.sql to07ora_trigger.sql )

SQL> connect hts_dbs/someFOLK@XEConnected.SQL>@02ora_util.sql

8/13/2019 OracleXE

20/47

2. Install Schema Object

Examine the hts database

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

SQL> select table_name from user_table order by table_name;

The result will be same as following figure.

8/13/2019 OracleXE

21/47

2. Install Schema Object

TABLES list for HTS database

ACCUMULATORDAILYACCUMULATORHOURLYACCUMULATORMONTHLYANALOGDAILYANALOGHOURLYANALOGMONTHLYANALOG_TEMPCARDREADERINFOCARDUSERINFODIGITALDAILYDIGITALHOURLYDIGITALMONTHLYDRIBBLEHISTALMEVT

HISTANALOGSCENARIOHISTCARDACCESSLOGHISTCHOICEINFOHISTCURRHISTDIGITALSCENARIOHISTMCHOICEINFOHISTORYHISTORYINFOHISTSEVERITYINFOHISTUSERINFO

HOURANALOGHOURDIGITALSUMMARYEVENT

8/13/2019 OracleXE

22/47

3. History Storage Configuration

8/13/2019 OracleXE

23/47

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 inhistory 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 isConfig Manager, the popup shown in Figure 3-2 will appear.

8/13/2019 OracleXE

24/47

3. History Storage Configuration

Figure 3-1

Figure 3-2

8/13/2019 OracleXE

25/47

3. History Storage Configuration

8/13/2019 OracleXE

26/47

3. History Storage Configuration

Attribute Name Description RDBMS Table Default

AnalogHourly Indicates whether hourlyanalog summary data needsto be generated.

AnalogHourly Yes

AnalogDaily Indicates whether dailyanalog summary data needsto be generated.

AnalogDaily Yes

AnalogMonthly Indicates whether monthlyanalog summary data needsto be generated.

AnalogMonthly Yes

DigitalHourly Indicates whether hourlydigital summary data needsto be generated.

DigitalHourly Yes

DigitalDaily Indicates whether dailydigital summary data needsto be generated.

DigitalDaily Yes

DigitalMonthly Indicates whether monthly

digital summary data needsto be generated.

DigitalMonthly Yes

8/13/2019 OracleXE

27/47

3. History Storage Configuration

AccumulatorHourly Indicates whether hourlyaccumulator summary dataneeds to be generated.

AccumulatorHourly Yes

AccumulatorDaily Indicates whether dailyaccumulator summary dataneeds to be generated.

AccumulatorDaily Yes

AccumulatorMonthly Indicates whether monthlyaccumulator summary dataneeds to be generated.

AccumulatorMonthly Yes

AlarmEvent Indicates whether the alarmand event messages needto be stored in relationaldatabase.

HistAlmEvt Yes

Attribute Name Description RDBMS Table Default

8/13/2019 OracleXE

28/47

3. History Storage Configuration

Attribute Name Description RDBMS Table Default

SettingTable Indicates whether some ofthe configuration settingssuch as ChoiceInfo andSeverityTable, need to bestored in relationaldatabase.

HistSeverityInfoHistAnalogScenarioHistDigitalScenarioHistChoiceInfoHistMChoiceInfoHistUserInfo

Yes

PurgeHistDuration Determines the duration indays for history transactionto be kept in relationaldatabase.

History or t%08X_%08X 60

PurgeHourlyDuration Determines the duration indays for the hourly summarydata to be kept in relationaldatabase.

AnalogHourly DigitalHourlyAccumulatorHourly

60

PurgeDailyDuration Determines the duration indays for the daily summarydata to be kept in relational

database.

AnalogDaily DigitalDailyAccumulatorDaily

60

8/13/2019 OracleXE

29/47

3. History Storage Configuration

Attribute Name Description RDBMS Table Default

PurgeMonthlyDuration Determines the duration indays for the monthlysummary data to be kept inrelational database.

AnalogMonthlyDigitalMonthlyAccumulatorMonthly

730

PurgeAlmEvtDuration Determines the duration indays for the alarm andevent data to be kept inrelational database.

HistAlmEvt 60

HourlyOffsetTime Determines the time offsetin minutes for hourlysummary data to be

generated.

N/A 0

DailyOffsetTime Determines the time offsetin minutes for dailysummary data to begenerated.

N/A 15

DailyCutOffTime Determines the cut off timein minutes for dailysummary data to begenerated.

N/A 0

8/13/2019 OracleXE

30/47

4. SCADA IO Points History

Storage Settings ( History Mode )

8/13/2019 OracleXE

31/47

4. SCADA IO Points History

Storage Settings ( History Mode )

Every SCADA IO point can be configured whether they will beupdated to relational database individually. The configuration can bedone via AnalogBase/ DigitalBase/ MiscBase Dialog of the point

respectively. In Figure 4-1, the History section illustrates the historysetting for DigitalBase point. Table 4-2 explains the meaning of eachsetting.

8/13/2019 OracleXE

32/47

4. SCADA IO Points History

Storage Settings ( History Mode )

Figure 4-1

Attribute Name Description Default

Table 4-2

8/13/2019 OracleXE

33/47

4. SCADA IO Points History

Storage Settings ( History Mode )

HistoryMode Specifies either to store everytransaction from RTDB or onlyselective transaction.

Always archive

- Update every change

No archive- Do not update

Interval archive- Update according toHistoryInterval configurationValue archive

- Update only if value change

No archive

HistoryInterval Specifies the scan interval, onlyused when History Mode isInterval Archive

0

NumHistCount Not used 0

Attribute Name Description Default

8/13/2019 OracleXE

34/47

5. Accessing RDBMSas History Database

8/13/2019 OracleXE

35/47

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 -las 0,

and -Sas username, -Pas password, -Sas sybase sql server nameand -Ddatabasename(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 -las 2,

and -Sas username, -Pas password, -Sas oracle connect identifyand -Ddatabase alias name(default user name is hts_dba, defaultdatabase alias name is hts).

( Example, -Uhts_dba -Ppassword -Sconnect ident idy -Dhts -l2 )

8/13/2019 OracleXE

36/47

6. Supervising hts executingunder WillowLynx

To supervising hts the WillowLynx startup script will need to edited

8/13/2019 OracleXE

37/47

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 -Sconnect ident idy -Dhts -l2

or

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

8/13/2019 OracleXE

38/47

N O t D i ti

8/13/2019 OracleXE

39/47

7. HTS command line option

No Option

Description

1 -U History RDBMS login user name

2 -P History RDBMS login password

3 -S Sybase Sql Server Name ( For Library mode 0 ) or Oracle Connect Identidy (For Library mode 1 ) or ODBCDatabase Source Name (For Library mode 2 ) Default hts

4 -D Database name ( For Library mode 0, 1 ) or Database Alias name ( For Library mode 2 ) Default hts

5 -l Determine library used to connecting History RDBMS, 0CT-Lib (For Connecting Sybase Only), 1ODBClib, (For connecting any ODBC 3.5 supported RDBMS ) 2Pro*C Lib ( For Connecting Oracle Only )

Default 0

6 -R History RDBMS , 0 - sybase, 2 - mysql , 1 - oracle, not used

7 -h RTDB Hostname, Default localhost

8 -g Gateway mode, not used

9 -n Gateway register name, not used

8/13/2019 OracleXE

40/47

7. HTS command line option

y g

10 -s 0Do not connect to supervisor 1 - Connect to supervisor until successed 2 - connect to Supervisor ifsupervisor is running Default 2

11 -m History data changes storage option, 0Store all changes in single table, 1Store all changes separatelyfor each point. Default 0

12 -b Bulk Copy Mode, 0dont use bulk copy, 1 use bulk copy. Default 0

13 -a Point Information Mapping HistCurr table update interval. 0Update every changes, > 0Update lastestchanges periodic which interval is number of miniutes specified. Default 0

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

15 -w Dribble folder path Default $SCADA_PROJECT/rtdb/runtime

16 -f RTDB dribble filename ( without specify parent directory ) in the Dribble folder to start reading from. DefaultIn the $SCADA_PROJECT/rtdb/Index, between the label runtime, and project, the string asdrb_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

8/13/2019 OracleXE

41/47

8. WillowLynx retrieveHTS database data

8/13/2019 OracleXE

42/47

Figure 8-1

8/13/2019 OracleXE

43/47

8. WillowLynx retrieve

HTS database data Figure 8-2

8/13/2019 OracleXE

44/47

8. WillowLynx retrieve

HTS database data

8/13/2019 OracleXE

45/47

8. WillowLynx retrieve

HTS database data

Retrieve Hts database data by Trend

1) In the Schematic page, double click on gadget to display its runtimepopup which show in figure 8.3.

2) In the runtime popup window, then click on Trend button, thenTrend 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.

Figure 8-3

8/13/2019 OracleXE

46/47

8. WillowLynx retrieve

HTS database data Figure 8-4

ToolbarArea

CurrentDateTimeIndicator

8/13/2019 OracleXE

47/47

8. WillowLynx retrieve

HTS database data

Plot Area

Sliding &ScalingArea

Legend Table

Indicator

TrendMarker

StatusIndicator