NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 1 of 29
NHHDA Software Release Notes
Release 11.0.0
Version Number 1.0
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 2 of 29
NHHDA Software Release Notes
Release 11.0.0
Status : Final
Version : 1.0
Date : 27 June 2013
Prepared by : Cognizant
Approved by (Cognizant) : Project Manager
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 3 of 29
Table Of Contents
1 Introduction .................................................................................................. 4 1.1 Purpose ...................................................................................................... 4 1.2 Scope ......................................................................................................... 4 1.3 Structure of Document .............................................................................. 4 1.4 Amendment History .................................................................................. 5
1.5 Summary of Changes ................................................................................ 5 1.6 Changes Forecast ...................................................................................... 5 1.7 References ................................................................................................. 5 1.8 Abbreviations ............................................................................................ 5 1.9 Intellectual Property Rights and Copyright ............................................... 5
2 Environment ................................................................................................. 7 2.1 Build Environment .................................................................................... 7 2.2 Database Customisation ............................................................................ 7
3 Installation Procedure ................................................................................. 9 3.1 Pre-requisites ............................................................................................. 9 3.2 Database Server ......................................................................................... 9 3.3 Application Server .................................................................................. 11
4 Post-Installation Procedures ..................................................................... 27 4.1 Database Checks ..................................................................................... 27
4.2 Quick Installation Check ......................................................................... 27
5 NHHDA Amendments in this release ....................................................... 28
6 Known defects not in this release ............................................................. 29
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 4 of 29
1 Introduction
1.1 Purpose
This document refers to Release 11.0.0 of the NHHDA software and this
number should always be used when referring to the NHHDA software or
related documents. There is an additional reference number associated with
this release, C11.0.0S, which relates to the Cognizant build of the software.
1.2 Scope
This is a full release that will install all of the NHHDA server and client
files. The release has been built using the new version of the following
software components:
Software Version
Oracle Database 11.2.0.3
Oracle Pro*C pre-compiler 11.2.0.3.0
Sun Studio compiler 12 C
Oracle Fusion Middleware (used for Forms &
Reports)
11.1.1.6
Oracle WebLogic server 10.3.6
Java RTE 1.6.0.31
For detailed list of other supporting components and versions, please refer
to [OUPGAPP].
This release should only be installed onto a Sun SPARC server running the
Solaris 5.10 operating system and Oracle Database Server Release
11.2.0.3.0.
It should be noted:
that this version has not been tested on any previous version of Sun
Solaris or Oracle Database Server;
that this version was built and tested using Sun Solaris 5.10, patched
to 118833-36.
1.3 Structure of Document
Section 2 deals with the environment used to build the software and issues
regarding user customisation of the database.
Section 3 addresses any installation issues for this version of the application.
Full installation details are provided in the NHHDA Installation Guide
[NINGDE].
Section 4 identifies any post installation actions that need to be undertaken.
Section 5 lists the changes in this release and any subsequent patches since
the last full release of the application.
Section 6 highlights any known defects that are not fixed in this release.
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 5 of 29
1.4 Amendment History
Version Date Details
1.0 27/06/2013 CP1383 - Updated for Tech Upgrade (Oracle
DB upgrade from 10.2.0.3 to 11.2.0.3 and OAS
upgrade from 10.1.2.2 to 11.1.1.6)
1.5 Summary of Changes
Changes as indicated in the amendment history.
1.6 Changes Forecast
None.
1.7 References
Mnemonic Information Details
[NINGDE] Title:
Version No:
Author:
Date:
NHHDA Installation Guide
17.0
Cognizant
27 June 2013
[NOPSGDE] Title:
Version No:
Author:
Date:
NHHDA Operations Guide.
17.0
Cognizant
27 June 2013
[NSMGDE] Title:
Version No:
Author:
Date:
NHHDA System Management Guide.
18.0
Cognizant
27 June 2013
[OUPGAPP] Title:
Version No:
Author:
Date:
Oracle Upgrade approach document
1.1
Cognizant
27 June 2013
1.8 Abbreviations
AA Annualised Advance
EAC Estimation of Annual Consumption
NHHDA Non Half Hourly Data Aggregation
OR Observation Report
1.9 Intellectual Property Rights and Copyright
The copyright and other intellectual property rights in this document are
vested in ELEXON. These materials are made available to participants in
the GB electricity industry to review and copy for the sole purpose of their
participation in the electricity industry. All other commercial use is
prohibited including downloading, copying, distributing, modifying,
transmitting, publishing, selling or creating derivative works (in whatever
format) from this document or in other cases use for personal academic or
other non-commercial purposes. All copyright and other proprietary notices
contained in the document must be retained on any copy you make.
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 6 of 29
All other rights of the copyright owner not expressly dealt with above are
reserved.
No representation, warranty or guarantee is made that the information in this
document is accurate or complete. While care is taken in the collection and
provision of this information, ELEXON Limited shall not be liable for any
errors, omissions, misstatements or mistakes in any information or damages
resulting from the use of this information or action taken in reliance on it.
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 7 of 29
2 Environment
2.1 Build Environment
The database server software was built on the following environment:
Sun Solaris 5.10 for SPARC chip-set, patched to 118833-36
Oracle 11g Server Release 11.2.0.3.0
Pro*C/C++: Release 11.2.0.3.0
Sun Studio 12 C Compiler, patched to 124867-01
The Windows application server software was built on the following
environment:
Microsoft Windows 2003 with Service Pack 2
Oracle Application Server 11g (11.1.1.6.0) - Forms & Reports
Services Standalone edition, plus the patches listed in [NINGDE]
Appendix G.
The Sun Solaris application server software was built on the following
environment:
Sun Solaris 5.10 for SPARC chip-set
Oracle Application Server 11g (11.1.1.6.0) - Forms & Reports
Services Standalone edition, plus the patches listed in [NINGDE]
Appendix G.
2.2 Database Customisation
Please note that NHHDA application’s tables, views, database indexes and
constraints are considered to be part of the software and, as such, should not
be customised, or have their location within the database amended. If you
do amend these items, you may be required to satisfy the Certification
Agent that there are no functional implications for the application. If any
customisation has been applied to the NHHDA application’s database
objects, we suggest you reverse the changes prior to installing this new
release. Failure to do this may result in the upgrade failing.
The tables used by this application are all stored under a single schema
within the Oracle database. Read access to these tables is allowed for ad-hoc
user queries and investigations, however all other forms of access are
strictly prohibited. Whilst it is possible to create additional tables and views
for analysis of the data, there is no guarantee that the installation or upgrade
script will be able to successfully cope with these tables. If additional tables
or views are required it is recommended that they are placed in a separate
schema within the database. However even if they are placed in a separate
schema, the users should check that these tables/views are all still valid,
present and correct after the NHHDA installation process has successfully
completed.
The installation/upgrade scripts have been designed to report differences between
the schema used to build and test the application and the schema from the database
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 8 of 29
being installed / upgraded. Where possible the script notes the differences and
allows the installation/upgrade to continue, however it is then up to the user to
ensure that these differences do not affect the running of the application (including
performance).
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 9 of 29
3 Installation Procedure
The release affects the database server software and application server
software. The set of software can be downloaded from ELEXON portal.
The Sun Solaris application server software is delivered in the same bundle
as the database server software; the Windows application server in a
separate bundle. For full details on how to install or upgrade the application
please refer to [NINGDE].
3.1 Pre-requisites
3.1.1 New Instance
If the release is installed as a new instance then it is strongly recommended
that it is installed onto a Sun SPARC server running the Solaris 5.10
operating system and Oracle Server Release 11.2.0.3.0.
3.1.2 Upgrade from an Existing Installation (NHHDA10.0.3)
To upgrade from a previous release:
release 10.0.3 must already have been installed in the database. No
other upgrade path will be supported.
all objects within the database need to be valid before the upgrade
is applied.
it is strongly recommended that it is installed onto a Sun SPARC
server running the Solaris 5.10 operating system and Oracle Server
Release11.2.0.3.0.
NB: new versions of application files are installed. If you have moved or
copied the current application files, then you will have to move/copy the
new files from this release.
3.2 Database Server
3.2.1 New Instance
Refer to the [NINGDE].
3.2.2 Upgrade from an Existing Instance (NHHDA 10.0.3)
In order to upgrade the server release, the following steps should be taken
before installing the software:
Ensure that all users has exited from NHHDA online (Front end)
Connect to UNIX as the NHHDA batch user.
Stop the NHHDA system by typing “nhhda_stop”.
Take a backup of the runtime directory.
Rename the runtime directory. For example, if the current runtime
directory is NHHDA_10_0_0, then rename it as NHHDA_11_0_0.
Here after, the renamed directory (NHHDA_11_0_0) will be
referred as runtime directory.
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 10 of
29
Copy nhhda_setup_solaris_11_0_0.gz from ELEXON portal to the
HOME directory of Solaris server. (Use the FTP tool WinSCP3to copy
the software from Windows to Solaris)
Extract the file nhhda_setup_solaris_11_0_0.gz using gunzip
command.
Change the mode of the executable using the below command.
chmod a+x nhhda_setup_solaris_11_0_0
Run nhhda_setup_solaris_11_0_0.
Reset the runtime directory, Oracle home directory and Oracle instance
as necessary when prompted.
Files have been moved into the directory structure as per a full install. If you
do not use the default locations for application files, move or copy the
installed files to their runtime locations.
If any obsolete files, which were delivered in previous releases but are not
included in the current release, are found, such files are deleted.
3.2.3 Pre-Upgrade Database Clean Up
Before running the upgrade, it is necessary to purge the “DBA Recycle
Bin”, which consists of copies of database objects which have been
dropped. (Oracle retains these copies to allow an object drop to be reversed,
but their existence prevents the upgrade from working.)
Log on as the Oracle UNIX user (or another user in the DBA
group);
Ensure that the $ORACLE_SID environment variable refers to the
database being upgraded;
Run sqlplus connected “/ as sysdba”. Run the command:
purge dba_recyclebin;
3.2.4 Pre-Upgrade Database Investigation
Take a backup of data from the below DB table:
cdb_activity_type
cdb_file_directory
cdb_ref_values
ndb_nar_file_location
CDB_EXPORT_CONFIGURATION
NDB_NAR_FILES
cdb_system_parameter
3.2.5 Database Update
Once the new version of NHHDA software is deployed, below updates on
DB should be done to update the correct runtime directory.
Log on as the NHHDA Owner UNIX user.
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 11 of 29
Login to the database using the command sqlplus
<username/password@DBname>. The user should have the DDL
access to the necessary tables.
Execute the below queries. In the below queries, the
<<OLD_RUNTIME_DIRECTORY>> and
<<NEW_RUNTIME_DIRECTORY>> should be replaced by the
correct one.
update cdb_activity_type set image_pathname =
replace(image_pathname,'<<OLD_RUNTIME_DIRECTORY>>','<<NEW_RUNTIME_DIRECTOR
Y>>');
update cdb_file_directory set path =
replace(path,'<<OLD_RUNTIME_DIRECTORY>>','<<NEW_RUNTIME_DIRECTORY>>');
update cdb_ref_values set value_from =
replace(value_from,'<<OLD_RUNTIME_DIRECTORY>>','<<NEW_RUNTIME_DIRECTORY>>'
) where domain_code in ('ARCD','NDPD');
update ndb_nar_file_location set directory =
replace(directory,'<<OLD_RUNTIME_DIRECTORY>>','<<NEW_RUNTIME_DIRECTORY>>');
update CDB_EXPORT_CONFIGURATION set directory =
replace(directory,'<<OLD_RUNTIME_DIRECTORY>>','<<NEW_RUNTIME_DIRECTORY>>');
update NDB_NAR_FILES set directory =
replace(directory,'<<OLD_RUNTIME_DIRECTORY>>','<<NEW_RUNTIME_DIRECTORY>>');
update cdb_system_parameter set VALUE = '11.0.0 (C11.0.0S)' where param_type='SYS' and
param_type2 = 'NDB';
Commit;
Execute the below query to ensure that all database objects are valid.
This query should not return any records.
select * from dba_objects where status <> 'VALID';
3.2.6 Post-Upgrade Actions
None
3.2.7 Restart NHHDA
Restart the NHHDA system by typing “nhhda_start”.
3.3 Application Server
Instructions are provided in this section:
1) Upgrading the NHHDA software on an existing Oracle Application
Server on Microsoft Windows.
2) Upgrading the NHHDA software on an existing Oracle Application
Server on Sun Solaris.
3.3.1 Oracle Application Server on Windows
This section describes how to adapt the instructions given in [NINGDE]
section 2.3.2 for an upgrade (i.e. version 10.0.3 of the NHHDA Oracle
Application Server is installed already).
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 12 of
29
NHHDA Directory:
Instructions for creating the NHHDA directory, and copying all the files
from the directory CD to the NHHDA directory.
Files/Directories Description
NHHDA Create the NHHDA directory in the root directory
of the drive where Oracle Application Server is
installed (or you may choose another directory
name but the instructions assume the directory is
named NHHDA).
For example, if the OAS is installed in D drive, the
NHHDA directory should be created under the D
drive like D:\NHHDA. If multiple environments
are required for different test system, create
multiple directories like NHHDA1, NHHDA2 etc.,
Forms Copy the NHHDA\Forms directory with its
contents from the directory CD to the NHHDA
directory.
Library Copy the NHHDA\Library directory with its
contents from the directory CD to the NHHDA
directory.
Icons Copy the NHHDA\Icons directory with its contents
from the directory CD to the NHHDA directory.
Menu Copy the NHHDA\Menu directory with its
contents from the directory CD to the NHHDA
directory.
Help Copy the NHHDA\Help directory with its contents
from the directory CD to the NHHDA directory.
NHHDA Env Directory:
Instructions for copying the NHHDA ENV directory files from the directory CD
to beneath the <ORACLE_HOME> directory, where <ORACLE_HOME>
represents the Oracle Home directory where Oracle Application Server is
installed.
In the below examples, the directory structure has the below notations.
<MW_HOME> denotes the Middleware Home directory. For
example: D:\oracle\Middleware11gR1
<DOMAIN_NAME> denotes the domain name created during the
OFM configuration. For example: ELXON
<ORACLE_INSTANCE> denotes the Oracle instance directory of
the OAS. For example: D:\oracle\Middleware11gR1\asinst_1
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 13 of 29
Files/Directories Description
nhhda.env Copy the NHHDA ENV\nhhda.env file from the
directory CD to the
<MW_HOME>\user_projects\domains\<DOMAIN_N
AME>\config\fmwconfig\servers\WLS_FORMS\appli
cations\formsapp_11.1.1\config directory on the
application server. If multiple environments are
required for different test systems, create multiple
copies of this file e.g. named nhhda1.env, nhhda2.env
nhhdaRegistry.dat Copy the NHHDA ENV\nhhdaRegistry.dat file from
the directory CD to the
<MW_HOME>\user_projects\domains\<DOMAIN_N
AME>\config\fmwconfig\servers\WLS_FORMS\appli
cations\formsapp_11.1.1\config\forms\registry\oracle\f
orms\registry directory
formsweb.cfg If the formsweb.cfg file does not exist in the
<MW_HOME>\user_projects\domains\<DOMA
IN_NAME>\config\fmwconfig\servers\WLS_F
ORMS\applications\formsapp_11.1.1\config
directory:
Copy the NHHDA ENV\formsweb.cfg file from
the directory CD to the
<MW_HOME>\user_projects\domains\<DOMAI
N_NAME>\config\fmwconfig\servers\WLS_FOR
MS\applications\formsapp_11.1.1\config directory
on the application server.
If the formsweb.cfg file exists in the
<MW_HOME>\user_projects\domains\<DOMA
IN_NAME>\config\fmwconfig\servers\WLS_F
ORMS\applications\formsapp_11.1.1\config
directory, add the lines below to the end of that
file.
[nhhda]
lookandfeel=Generic
colorScheme=Gray
background=nhhda
envFile=nhhda.env
form=nhhda.fmx
width=1000
height=700
separateFrame=TRUE
ImageBase=codeBase
serverApp=nhhdaRegistry
(omit the separateFrame=TRUE line if you do
want the forms application to run on a separate
browser window)
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 14 of
29
Files/Directories Description
If multiple environments are required, create
multiple sections containing these lines, named
e.g. [nhhda1] [nhhda2] etc – one for each .env file.
forms.conf If the forms.conf file does not exist in the
<ORACLE_INSTANCE>\config\OHS\ohs1\modul
econf directory:
Copy the NHHDA ENV\forms.conf file from the
directory CD to the
<ORACLE_INSTANCE>\config\OHS\ohs1\modu
leconf directory on the application server.
If the forms.conf file exists in the
<ORACLE_INSTANCE>\config\OHS\ohs1\modul
econf directory, add the lines below to the end of
that file.
# BEGIN NHHDA CONFIG
RewriteRule ^/forms/nhhda_help/(..*) /nhhda_help/$1 [PT]
AliasMatch ^/nhhda_help/(..*) "D:\nhhda\Help\$1"
WLExcludePathOrMimeType /forms/nhhda_help
RewriteRule ^/forms/nhhda_reports/(..*) /nhhda_reports/$1 [PT]
AliasMatch ^/nhhda_reports/(..*) "D:\nhhda\Reports\$1"
WLExcludePathOrMimeType /forms/nhhda_reports # END NHHDA CONFIG
If multiple environments are configured, these
lines should be updated by suffixing the
environment number as given below.
# BEGIN NHHDA1 CONFIG
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 15 of 29
Files/Directories Description
RewriteRule ^/forms/nhhda1_help/(..*) /nhhda1_help/$1 [PT]
AliasMatch ^/nhhda1_help/(..*) "D:\nhhda1\Help\$1"
WLExcludePathOrMimeType /forms/nhhda1_help
RewriteRule ^/forms/nhhda1_reports/(..*) /nhhda1_reports/$1 [PT]
AliasMatch ^/nhhda1_reports/(..*) "D:\nhhda1\Reports\$1"
WLExcludePathOrMimeType /forms/nhhda1_reports
# END NHHDA1 CONFIG
plan.xml This file can be found under the directory
<DOMAIN_HOME>\deploymentplans\formsap
p\11.1.1
This file maps the relative path given in the files
forms.conf and nhhda.env
Under <variable-definition> add below entry: In the below entry,
ensure that the <value> tag is mapped to the directory where
NHHDA directory is created.
<variable>
<name>vd-d:\</name>
<value>d:\</value>
</variable>
Under <module-descriptor external="false"> add below entry: In the
below entry, ensure that the url-pattern is set to the directory where
the help and reports directories were created.
<variable-assignment>
<name>vd-d:\</name>
<xpath>/weblogic-web-app/virtual-directory-mapping/[url-
pattern="nhhda/reports/*"]/local-path</xpath>
</variable-assignment>
<variable-assignment>
<name>vd-d:\</name>
<xpath>/weblogic-web-app/virtual-directory-mapping/[url-
pattern="nhhda/help/*"]/local-path</xpath>
</variable-assignment>
Note: The above changes are mapping the reports
and help directories correctly. The values given in
the <value> tag and url-pattern should jointly form
the help and reports directories.
svaicons Directory:
Instructions for creating the svaicons directory and copy .gif files.
Files/Directories Description
svaicons
Create the directory svaicons in the <ORACLE_
HOME>\forms\java directory.
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 16 of
29
nhhda.gif Copy the NHHDA\Icons\nhhda.gif file to the
<ORACLE_HOME>\forms\java directory.
Icons Copy all the files (including nhhda.gif) from the
NHHDA\Icons directory to the
<ORACLE_HOME>\forms\java\svaicons
directory.
fmrweb.res File:
Instructions for maintaining the key mappings same as forms 6i.
fmrweb.res Rename the
<ORACLE_INSTANCE>\config\FormsComponent\forms\fmrweb.res file
to
<ORACLE_INSTANCE>\config\FormsComponent\forms\fmrweb_orig.res,
and then copy
<ORACLE_INSTANCE>\config\FormsComponent\forms\fmrpcweb.res to
<ORACLE_INSTANCE>\config\FormsComponent\forms\fmrweb.res.
forms.conf File:
Instructions for customising the contents of file <forms.conf >.
Keyword Description
/forms/html/ Change the default directory
D:\oracle\Middleware11gR1\asinst_1
to reflect the correct oracle home of
OAS.
/forms/nhhda_help Change the default directory D:\
NHHDA\Help to specify the correct
location of NHHDA help files.
/forms/nhhda_reports Change the default directory
D:\nhhda_reports to specify the
location where NHHDA report files are
stored.
WebLogicHost Change the default Web logic Host
CTSINTBMVELX3.cts.com to specify
the host where the web logic server is
hosted.
WebLogicPort Change the default web logic post
number 9007 to the correct web logic
port number which would have been
chosen during the OFM installation.
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 17 of 29
NHHDA Reports Directory:
Instructions for creating the nhhda_reports directory which is used to store
NHHDA report files, generated from the NHHDA application.
Files/Directories Description
reports Create the reports folder as specified in the
/forms/nhhda_reports alias in the forms.conf file to
store the reports generated from the application. If
different folders are required for different
environments, create sub-folders e.g. with the same
names as the environments, nhhda1, nhhda2 etc
formsweb.cfg File:
Instructions for customising the contents of file <formsweb.cfg>.
Keyword Description
Global Change Replace all occurrences of
D:\oracle\Middleware11gR1\Forms11g
with the correct Oracle Home if exists.
nhhda.env File:
Instructions for customising the contents of file <nhhda.env>. If there are
multiple environments, then each of the multiple .env files may be customised
with different values.
Keyword Description
ORACLE_HOME Change the default directory
D:\oracle\Middleware11gR1\Forms11g to reflect
the correct oracle home of OAS.
ORACLE_INSTANCE Change the default directory
D:\oracle\Middleware11gR1\asinst_1 to reflect
the correct oracle instance of OAS.
FORMS_PATH Change the default directory
D:\oracle\Middleware11gR1\Forms11g\ to reflect
the correct oracle home of OAS.
Also if the NHHDA folder was not created on D:
or it was given a different name, then replace all
the occurrences of D:\ NHHDA.
CLASSPATH Change the default directory
D:\oracle\Middleware11gR1\Forms11g to reflect
the correct oracle home of OAS.
PATH Change the default directory
D:\oracle\Middleware11gR1\Forms11g to reflect
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 18 of
29
Keyword Description
the correct oracle home of OAS.
Also if the NHHDA folder was not created on D:
or it was given a different name, then replace all
the occurrences of D:\ NHHDA.
FORMS Change the default directory
D:\oracle\Middleware11gR1\Forms11g to reflect
the correct oracle home of OAS.
FORMS_RESTRICT_
ENTER_QUERY
By default this parameter is set to TRUE. When
it is set to TRUE, Oracle Forms limits the types
of query criteria that can be entered when in
Enter-Query mode. In general, it disallows the
use of:
conjunctions (AND, OR)
keywords which modify parts of the
SELECT statement outside of the
WHERE clause (ORDER BY),
All functions, including SQL functions
(LENGTH, TO_CHAR, LPAD,
SUBSTR).
Also, the Query/Where window is unavailable
when set to TRUE.
If the users need the freedom to enter these
types of criteria, add a line to the nhhda.env file,
setting the parameter to FALSE.
EP98NREPPATH This should not be changed from
/forms/nhhda_reports which is an alias defined in
the forms.conf file. The only valid change is to
define the variable as a sub-folder within this
alias e.g. /forms/nhhda_reports/nhhda1/. if
multiple environments are configured, it should
be updated by suffixing the environment number
(as defined in the forms.conf file) e.g.,
/forms/nhhda1_reports/
EP98NTEMP Change to specify the reports path. It must match
the /forms/nhhda_reports alias match entry in the
forms.conf file, e.g. D:\nhhda\reports. If
EP98NREPPATH is defined for multiple
environment, then the same sub-folder name must
be added to this variable as given in the
forms.conf file, e.g. D:\nhhda1\reports\
EP98NHELP Change to specify the Help files path. It must
match the /forms/nhhda_help alias match entry in
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 19 of 29
Keyword Description
the forms.conf file.
host_address Change the host_address entry to reflect the Host
address of OAS.
EP98NFILEEXT Change the default value .nhh to specify the
extension to be used for displayed NHHDA
Reports. (The advantage of using an extension
such as .nhh which is unique to NHHDA is that
there is complete freedom to configure how this
extension is opened on the clients.)
EP98SPORTPRTEXT Change the default value .por to specify the
extension to be used for NHHDA Reports which
are printed portrait. (The advantage of using an
extension such as .por which is unique to
NHHDA is that there is complete freedom to
configure how this extension is opened on the
clients.)
EP98SLANDPRTEXT Change the default value .lnd to specify the
extension to be used for NHHDA Reports which
are printed landscape. (The advantage of using
an extension such as .lnd which is unique to
NHHDA is that there is complete freedom to
configure how this extension is opened on the
clients.)
EP98PRINTW Do not change the default value of 132 – this is
used to control whether reports are printed
portrait or landscape.
EP98NVERS Do not change this line.
-N.B. Restart Oracle Application Server after modifying all configuration files.
3.3.2 Oracle Application Server on Solaris
This section describes how to adapt the instructions given in [NINGDE]
section 2.3.2 for an upgrade (i.e. version 9.0.0 or 9.0.1 of the NHHDA
Oracle Application Server is installed already).
NHHDA Directory:
The instructions in the table below are for creating the NHHDA directory,
and copying all the files from the unix_web_forms directory within the
NHHDA installation (RUNTIME directory) to a new directory named
NHHDA. Note that it is possible to leave the files in the location where
they are delivered – in which case, omit the instructions in this table and
then the directory referred to as /oradata/sva/NHHDA in subsequent
sections is the unix_web_forms/NHHDA directory. Ensure that the oracle
user has read and execute permissions on the files under this directory.
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 20 of
29
Files/
Directories
Description
NHHDA Create the /oradata/sva/NHHDA directory on the unix server
where Oracle Application Server is installed (or you may
choose another directory name but the instructions assume the
directory is named /oradata/sva/NHHDA).
If multiple environments are required for different test system,
create multiple directories like NHHDA1, NHHDA2 etc.,
forms Copy the NHHDA\forms directory with its contents from
unix_web_forms to /oradata/sva/NHHDA directory.
icons Copy the NHHDA\icons directory with its contents from
unix_web_forms to oradatw/sva/NHHDA directory.
library Copy the NHHDA\library directory with its contents from
unix_web_forms to /oradata/sva/NHHDA directory.
menu Copy the NHHDA\menu directory with its contents from
unix_web_forms to /oradata/sva/NHHDA directory.
help Copy the NHHDA\help directory with its contents from
unix_web_forms to /oradata/sva/NHHDA directory.
Instructions for copying the NHHDA_ENV directory files from the
unix_web_forms directory to beneath the $ORACLE_HOME directory, where
$ORACLE_HOME is the Oracle Home directory where Oracle Application Server
is installed. This section cannot be omitted.
In the below example, the directory structure has the below notations.
<MW_HOME> denotes the Middleware Home directory. For example:
/app/oracle/Middleware11gR1
<DOMAIN_NAME> denotes the domain name created during the OFM
configuration. For example: ELXON
<ORACLE_INSTANCE> denotes the Oracle instance directory of the
OAS. For example: /app/oracle/Middleware11gR1/asinst_1
Files/Directo
ries
Description
nhhda.env Copy the NHHDA_ENV/nhhda.env file from unix_web_forms to the
<MW_HOME>/user_projects/domains/<DOMAIN_NAME>/config/f
mwconfig/servers/WLS_FORMS/applications/formsapp_11.1.1/confi
g directory on the application server. If multiple environments are
required for different test systems, create multiple copies of this file
e.g. named nhhda1.env, nhhda2.env.
nhhdaRegistr
y.dat
Copy the NHHDA_ENV/nhhdaRegistry.dat file from
unix_web_forms to the
<MW_HOME>/user_projects/domains/<DOMAIN_NAME>/config/f
mwconfig/servers/WLS_FORMS/applications/formsapp_11.1.1/confi
g/forms/registry/oracle/forms/registry directory
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 21 of 29
Files/Directo
ries
Description
formsweb.cfg Set the ORACLE_HOME variable to point to the OAS home
directory.
If the formsweb.cfg file does not exists in
<MW_HOME>/user_projects/domains/<DOMAIN_NAME>/con
fig/fmwconfig/servers/WLS_FORMS/applications/formsapp_11.1
.1/config directory:
Copy the NHHDA_ENV/formsweb.cfg file from
unix_web_forms to the
<MW_HOME>/user_projects/domains/<DOMAIN_NAME>/con
fig/fmwconfig/servers/WLS_FORMS/applications/formsapp_11.1
.1/config directory on the application server.
If the formsweb.cfg file exists in the
<MW_HOME>/user_projects/domains/<DOMAIN_NAME>/con
fig/fmwconfig/servers/WLS_FORMS/applications/formsapp_11.1
.1/config directory, add the lines below to the end of that file.
[nhhda]
lookandfeel=Generic
colorScheme=Gray
background= nhhda
envFile= nhhda.env
form= nhhda.fmx
width=1000
height=700
separateFrame=TRUE
ImageBase=codeBase
serverApp= nhhdaRegistry
(omit the separateFrame=TRUE line if you do want the forms
application to run on a separate browser window)
If multiple environments are required, create multiple sections
containing these lines, named e.g. [nhhda1] [nhhda2] etc – one for
each .env file and change the respective .env file name assigned in
the parameter envFile given above.
forms.conf If the forms.conf file does not exist in the
<ORACLE_INSTANCE>/config/OHS/ohs1/moduleconf
directory:
Copy the NHHDA_ENV/forms.conf file from unix_web_forms to
the <ORACLE_INSTANCE>/config/OHS/ohs1/moduleconf
directory on the application server.
If the forms.conf file exists in the
<ORACLE_INSTANCE>/config/OHS/ohs1/moduleconf add the
lines below to the end of that file.
# BEGIN NHHDA CONFIG
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 22 of
29
Files/Directo
ries
Description
RewriteRule ^/forms/nhhda_help/(..*) /nhhda_help/$1 [PT]
AliasMatch ^/nhhda_help/(..*) "/oradata/sva/NHHDA/help/$1"
WLExcludePathOrMimeType /forms/nhhda_help
RewriteRule ^/forms/nhhda_reports/(..*) /nhhda_reports/$1 [PT]
AliasMatch ^/nhhda_reports/(..*) "/oradata/sva/NHHDA/reports/$1"
WLExcludePathOrMimeType /forms/nhhda_reports
# END NHHDA CONFIG
If multiple environments are configured, these lines should be
updated by suffixing the environment number as given below.
# BEGIN NHHDA1 CONFIG
RewriteRule ^/forms/nhhda1_help/(..*) /nhhda1_help/$1 [PT]
AliasMatch ^/nhhda1_help/(..*) "/oradata/sva/NHHDA1/help/$1"
WLExcludePathOrMimeType /forms/nhhda1_help
RewriteRule ^/forms/nhhda1_reports/(..*) /nhhda1_reports/$1 [PT]
AliasMatch ^/nhhda1_reports/(..*) "/oradata/sva/NHHDA1/reports/$1"
WLExcludePathOrMimeType /forms/nhhda1_reports
# END NHHDA1 CONFIG
plan.xml This file can be found under the directory
<DOMAIN_HOME>/deploymentplans/formsapp/11.1.1
This file maps the relative path given in the files forms.conf and
nhhda.env.
Under <variable-definition> add below entry: In the below entry,
ensure that the <value> tag is mapped to the directory where
NHHDA directory is created.
<variable>
<name>vd-/oradata/sva</name>
<value>/oradata/sva</value>
</variable>
Under <module-descriptor external="false"> add below entry: In
the below entry, ensure that the url-pattern is set to the directory
where the help and reports directories were created.
<variable-assignment>
<name>vd-/oradata/sva</name>
<xpath>/weblogic-web-app/virtual-directory-mapping/[url-
pattern="NHHDA/reports/*"]/local-path</xpath>
</variable-assignment>
<variable-assignment>
<name>vd-/oradata/sva</name>
<xpath>/weblogic-web-app/virtual-directory-mapping/[url-
pattern="NHHDA/help/*"]/local-path</xpath>
</variable-assignment>
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 23 of 29
Files/Directo
ries
Description
Note: The above changes are mapping the reports and help
directories correctly. The value given in the <value> tag and url-
pattern should form the help and reports directories.
svaicons Directory:
Instructions for creating the svaicons directory and copy .gif files.
Files/Directories Description
svaicons Create the directory svaicons in the $ORACLE_
HOME/forms/java directory
nhhda.gif Copy the NHHDA\Icons\nhhda.gif file from
unix_web_forms\Icons to the
$ORACLE_HOME/forms/java directory.
Icons Copy all the files (including nhhda.gif) from the
NHHDA/Icons directory to the
$ORACLE_HOME/forms/java/svaicons directory.
fmrweb.res File:
Instructions for maintaining the key mappings same as forms 6i.
Files/Direc
tories
Description
fmrweb.res Rename the <$ORACLE_INSTANCE>/config/FormsComponent/forms/admin/resource/US/fmrweb.res
file to
<$ORACLE_INSTANCE>/config/FormsComponent/forms/admin/resource/US/fmrweb_ori
g.res, and then copy
<$ORACLE_INSTANCE>/config/FormsComponent/forms/admin/resource/US/fmrpcweb.re
s to
<$ORACLE_INSTANCE>/config/FormsComponent/forms/admin/resource/US/fmrweb.res.
forms.conf File:
Instructions for customising the contents of file <forms.conf>.
Keyword Description
/forms/html Change the default ORACLE_HOME
/app/oracle/Middleware/asinst_1/ to the correct
Oracle Home Directory of OAS.
/forms/nhhda_help Change the default directory
“/oradata/sva/NHHDA/help“ to specify the location
of NHHDA help files.
/forms/nhhda_reports Change the default directory
“/oradata/sva/NHHDA/reports” to specify the
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 24 of
29
location of NHHDA report files.
WebLogicHost Change the default Web logic Host
CTSINTBMVELX3.cts.com to specify the host
where the web logic server is hosted.
WebLogicPort Change the default web logic post number 9007 to
the correct web logic port number which would
have been chosen during the OFM installation.
NHHDA Reports Directory :
Instructions for creating the reports directory, which is used to store NHHDA
report files generated from the NHHDA application.
Files/Directories Description
reports Create the reports folder as specified in the
/forms/nhhda_reports alias in the forms.conf file to
store the reports generated from the application.
Ensure that the oracle user can write to this
directory. If different folders are required for
different environments, create the reports folder uner
the respective NHHDA folder created. e.g. Create
the folder reports under NHHDA1, NHHDA2 and
NHHDA3 etc.
formsweb.cfg File :
Instructions for customising the contents of file <formsweb.cfg>
Keyword Description
Global Change Replace all occurrences of
D:\oracle\Middleware11gR1\Forms11g
with the correct Oracle Home if exists
nhhda.env File :
Instructions for customising the contents of file <nhhda.env>. If there are multiple
environments, then each of the multiple .env files may be customised with
different values.
Keyword Description
ORACLE_HOME Change the default directory
/app/oracle/Middleware/Forms11g to reflect the correct
oracle home of OAS.
ORACLE_INSTANCE Change the default directory
/app/oracle/Middleware/asinst_1 to reflect the correct
oracle home of OAS
TNS_ADMIN Change the default directory
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 25 of 29
Keyword Description
/app/oracle/Middleware/asinst_1/config to reflect the
correct TNS admin directory of OAS.
FORMS_PATH Change the default directory
/app/oracle/Middleware/Forms11g to reflect the correct
oracle home of OAS.
Also if the NHHDA folder was not created under
/oradata/sva or not named NHHDA then replace all
occurrences of /oradata/sva/NHHDA.
CLASSPATH Change all the occurrence of the default directory
/app/oracle/Middleware/Forms11g to reflect the correct
oracle home of OAS.
PATH Change all the occurrence of the default directory
/app/oracle/Middleware/Forms11g to reflect the correct
oracle home of OAS.
Also if the NHHDA folder was not created under
/oradata/sva or not named NHHDA then replace all
occurrences of /oradata/sva/NHHDA.
LD_LIBRARY_PATH Change the default directory
/app/oracle/Middleware/Forms11g to reflect the correct
oracle home of OAS.
Change the default directory /tmp/OraInstall2006-12-
05_09-28-55AM/jre/1.4.2/ to reflect the correct jre
home.
Also if the NHHDA folder was not created under
/oradata/sva or not name NHHDA then replace all
occurrences of /oradata/sva/NHHDA.
FORMS_RESTRICT_
ENTER_QUERY
By default this parameter is set to TRUE. When it is set
to TRUE, Oracle Forms limits the types of query criteria
that can be entered when in Enter-Query mode. In
general, it disallows the use of:
conjunctions (AND, OR)
keywords which modify parts of the
SELECT statement outside of the
WHERE clause (ORDER BY),
All functions, including SQL functions
(LENGTH, TO_CHAR, LPAD,
SUBSTR).
Also, the Query/Where window is unavailable when set
to TRUE.
If the users need the freedom to enter these types of
criteria, add a line to the nhhda.env file, setting the
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 26 of
29
Keyword Description
parameter to FALSE.
EP98NREPPATH This should not be changed from /forms/nhhda_reports/
which is an alias defined in the forms.conf file. If
multiple environments are configured, then it should be
updated by suffixing the environment number (as
defined in the forms.conf) e.g., /forms/nhhda1_reports/
EP98NTEMP Change to specify the reports path. It must match the
/forms/nhhda_reports alias match entry in the
forms.conf file e.g.. /oradata/sva/NHHDA/reports If
EP98NREPPATH is defined for multiple environments,
then it should be changed to match with the alias entry
in the forms.conf file. e.g.
/oradata/sva/NHHDA1/reports.
EP98NHELP Change to specify the help files path. It must match the
/forms/nhhda_help alias match entry in the forms.conf
file.
host_address Change the host_address entry to reflect the Host
address of OAS.
EP98NFILEEXT Change the default value .nhh to specify the extension
to be used for NHHDA Reports.
(The advantage of using an extension such as .nhh
which is unique to NHHDA is that there is complete
freedom to configure how this extension is opened on
the clients.)
EP98SPORTPRTEXT Change the default value .por to specify the extension to
be used for NHHDA Reports which are printed portrait.
(The advantage of using an extension such as .por which
is unique to NHHDA is that there is complete freedom
to configure how this extension is opened on the
clients.)
EP98SLANDPRTEXT Change the default value .lnd to specify the extension to
be used for NHHDA Reports which are printed
landscape. (The advantage of using an extension such
as .lnd which is unique to NHHDA is that there is
complete freedom to configure how this extension is
opened on the clients.)
EP98PRINTW Do not change the default value of 132 – this is used to
control whether reports are printed portrait or landscape.
EP98NVERS Do not change this line.
N.B. Restart Oracle Application Server after modifying all configuration
files.
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 27 of 29
4 Post-Installation Procedures
4.1 Database Checks
The user should check for any invalid database objects. If any are found
then they should be investigated and resolved. If the user has any
customised applications or reports on the database they should be checked
to ensure they still function correctly.
4.2 Quick Installation Check
Start up the NHHDA front-end and select the Help About menu option. The
dialogue box should contain the version numbers shown here:
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 28 of
29
5 NHHDA Amendments in this release
None
NHHDA Software Release Notes Version 1.0
© ELEXON Limited 2013 Page 29 of 29
6 Known defects not in this release
Please note the following behaviour of this release of the system. These
observations are not classified as defects; however we are in the process of
resolving the first observation.
ELEXON
Reference
Description
NA In NHHDA application, the report “Load Timetable Exceptions
report” can be displayed by clicking the Display button and the
Print button. We observed on one occasion that the report did
not open correctly after clicking the print button. If this happens,
restarting the web logic server will resolve the issue.
NA From 11g version, the Oracle database does not allow any
testing based on changing system date before 2000. The
database stops from booting properly when any such attempt is
made.