Industrial IT, 800xa - Information Management, Configuration - 05

Editing Data Provider Configuration Files Section 15 Configuring Data Providers
Table 61. Arguments Common to All Data Providers
Argument(1) Description
-name This name is used by certain data access applications to identify a specific
data provider when there are more than one data provider of that type.
Specifically, the -name argument is used by DataDirect when the Use
Channel Numbers option is disabled, and by display scripts that use the
Data statement.
When you connect more than one Data Provider of the same type, each
Data Provider MUST have a unique name. Assigning a new channel number
also assigns a new name. Therefore, if you assign a new channel number,
you are not required to edit the name unless you do not want to use the
assigned default name.
-channel This also uniquely identifies a specific data provider when there are more
than one data provider of that type. The -channel argument is used by
DataDirect when the Use Channel Numbers option is enabled, and by
display scripts that do not use the Data statement.
Default data providers are assigned CHANNEL 0. If an application client
specifies an invalid channel, the application defaults to channel 0. If you do
not want to default to channel 0 in the event of an invalid channel
specification, you must ensure that no data providers are assigned channel
number 0. You must change the channel number of the default data
providers, and do not use channel number 0 for additional data providers.
NOTE: On the Windows 2000 Display Server, the Active Data Object (ADO)
takes the place of the Dynamic Oracle Data Provider and uses the same
channel number.
-server This is the name or IP address of the service provider. For a local node
installation, this should be the name of the local node. If you do not want the
data provider to start automatically when the corresponding Display server is
started, set the value for Server in Arguments to NoNode. NOTE: If the
service provider platform is Windows 2000, in order to use the host name,
the host name must be included in C:\WINNT\system32\drivers\etc\hosts.
(1) For specific arguments for each type of service, see Table 62 for ADSspCOM.EXE, Table 63 for
ADSdpDDR.EXE, Table 64 for ADSdpADO.EXE, Table 65 for ADSdpOPCHDA.EXE, Table 66 for
ADSdpDCS.EXE, Table 67 for ADSdpDCS.EXE, Table 68 for ADSdpOPC.EXE
710 3BUF001092R4001
Section 15 Configuring Data Providers Editing Data Provider Configuration Files
Table 62 describes the arguments that are unique for the ADSspCOM.EXE data
provider. This data provider also has arguments common to all data providers as
described in Table 61.
Table 62. ADSspCOM.EXE Arguments
Argument Description
-server The host name or TCP/IP address where the service provider runs. For a local
node installation, this should be the name of the local node. If you do not want
the service provider to start automatically when the corresponding ADSS is
started, set the value for Server to NoNode.
NOTE: If the service provider platform is Windows 2000, in order to use the host
name, the host name must be included in
C:\WINNT\system32\drivers\etc.
-port The TCP/IP socket port number. Three sockets are used, starting from the one
specified.
Default: 19014
Range: 1000<= n <= 65000
-AliveTimeOut Used to disconnect clients if they are quiet for the time specified.
Default: 60
Range: 0 <= x <= ...
Unit: Seconds
-license_key & These are the license key and text as entered when you install the display
-license_text server, or when you update the license. The key is entered in quotes.
3BUF001092R4001 711
Table 63 describes the arguments that are unique for the ADSdpDDR.EXE data
Table 63. ADSdpDDR.EXE Arguments
-server The host name or TCP/IP address where the service provider runs.
For a local node installation, this should be the name of the local
node. If you do not want the data provider to start automatically
when the corresponding ADSS is started, set the value for Server to
NoNode.
NOTE: If the service provider platform is Windows 2000, in order to
use the host name, the host name must be included in
-port The TCP/IP socket port number. Three sockets are used, starting
from the one specified.
Default: 19014
Range: 1000<= n <= 65000
-datapath This is the path to the directory where the display files reside. The
default is: c:\Program Files\ABB Industrial IT\ Inform
IT\Display Services\Server\Data
-Allow_System_Access This argument is required to support bulk data export for client
applications such as DataDirect. This argument is provided by
default. In addition to this argument, the SYSTEMACCESS user
preference must be enabled. This is the default setting for this
preference.
712 3BUF001092R4001
Table 64 describes the arguments that are unique for the ADSdpADO.EXE data
Table 64. ADSdpADO.EXE Arguments
-server The host name or TCP/IP address where the service provider runs. For a
local node installation, this should be the name of the local node. If you
do not want the data provider to start automatically when the
corresponding ADSS is started, set the value for Server to NoNode.
NOTE: If the service provider platform is Windows 2000, in order to use
the host name, the host name must be included in
-port The TCP/IP socket port number. Three sockets are used, starting from
the one specified.
Default: 19014
Range: 1000<= n <= 65000
-dbtype This is the type of database to which this data provider connects. The
choices are: MDB, ODBC, and GENERIC. For MDB and ODBC
databases, you must also configure the corresponding username and
password. For GENERIC databases, you must specify the connection
string (-constr argument).
-dbname This is the name or full path to the database. For dbtype MDB, use the full
path. For dbtype ODBC, use the ODBC name.
-user This is the user name for logging into the database. This is required when
the dbtype is ODBC or MDB.
-password This is the password for logging into the database. This is required when
the dbtype is ODBC or MDB.
disallow_sql_write You may add this argument to the argument list to NOT allow any SQL
statements other than those that begin with the SELECT keyword.
-constr This is the full connect string. This is only required when the dbtype is
GENERIC.
3BUF001092R4001 713
Table 64. ADSdpADO.EXE Arguments
-CmdTMO <n> This is the command timeout in seconds (n = number of seconds). The
default is 30 seconds
ReConnINT <n> This is the reconnect interval in seconds (n = number of seconds). The
default is 0. When n = 0, reconnect is disabled, otherwise the provider will
attempt connecting the database at the specified interval, until successful
connection or the reconnect timeout period (if specified) is exceeded.
-ReConnTMO <n> This is the Reconnect timeout period in seconds (n = number of
seconds). The default is 0. When n = 0 there's no timeout and the
provider will keep on trying to connect to the database. If the reconnect
timeout period is exceeded, the provider will terminate.
FatalErrors This is a listing of error codes which should be treated as Fatal (for
"<n1>;<n2>;....;<nX example, missing connection to the database). If such an error occurs,
>" the data provider will terminate. The format to specify error codes is a list
of numbers separated by semicolons (;) and enclosed in quotation marks.
For example: -FatalErrors "11; 567;-26"
Entering an asterisk in place of error codes will cause the provider to
terminate at any error. For example: –FatalErrors “*”
-ReturnAllErrors See ReturnAllErrors Argument below.
"TRUE|FALSE"
714 3BUF001092R4001
ReturnAllErrors Argument
Normally, on errors the ADO provider returns an array containing:
ADS Error Header DP Error Header DP Error Text
ADS specific Error code Last DP specific Error code Last DP specific Error Text
Some data base providers are capable of generating several errors as a result of one
request. If ‘ReturnAllErrors’ is FALSE (default), only the last error code/text is
returned. If ‘ReturnAllErrors’ is TRUE, the returned array will contain all the error
codes/texts encountered:
ADS Error Header DP Error Header DP Error Text
ADS specific Error code 1st DP specific Error code 1st DP specific Error Text
ADS specific Error code 2nd DP specific Error code 2nd DP specific Error Text
Example:
The connection to the SQL server fails. If ReturnAllErrors FALSE (default):
ADS Error ADO Error Text
-106 11 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
General network error. Check your network documentation.
If ReturnAllErrors TRUE:
ADS Error ADO Error Text
ConnectionWrite (send()).
General network error. Check your network documentation.
3BUF001092R4001 715
Table 65 describes the arguments that are unique for the ADSdpOPCHDA.EXE data
Table 65. ADSdpOPCHDA.EXE Arguments
-OPCHDAServer <xxx> ProgID for OPCHDA server.
If you are using the AIPOPCHDA Server, the Server ProgID is
ABB.AfwOpcDaSurrogate.
If you are using the IMOPCHDA Server, the Server ProgID is
HsHDAServer.HDAServer.
-OPCHDAServerHost <xxx> H Host name of the PC where the OPCHDA server resides. This
is only required if OPCHDA server is on a remote host.
-ALLOW_LOG_WRITE If this argument is not specified, clients cannot write to history
logs. In addition to this argument, the LOGWRITE user
preference must be enabled. The default setting for this
preference is disabled. For details on how to set this user
preference, refer to Configuring User Preferences on page 758.
-Browser_Separator This applies to the AIPHDA data provider and is used when an
Aspect System has properties being historized whose name
contains the forward slash (/) character, or whose ancestor
objects contain that character. One application for this is the
Harmony Connectivity Server where the default separator
cannot be used.
The OPCHDA browser uses the forward slash character as a
separator by default, and will not parse objects and properties
correctly if they use this character. In this case, the OPCHDA
browser must use a different separator character. The
supported separator characters are "/", "\","-" , "," and ".".
As an example, to declare the backslash as the separator, add
the argument as follows: -Browser_Separator \
For Aspect Systems where the / character is not used in the
property names nor in ancestor object names, no change in
configuration is necessary.
716 3BUF001092R4001
Table 66 describes the arguments that are unique for the ADSdpDCS.EXE data
Table 66. ADSdpDCS.EXE Arguments
server The host name or TCP/IP address where the service provider runs. For
a local node installation, this should be the name of the local node. If
you do not want the data provider to start automatically when the
corresponding Display server is started, set the value for Server to
NoNode.
the one specified.
Default: 19014
Range: 1000<= n <= 65000
-name This is the assigned name for the data provider.
-Allow_Object_Write If this argument is specified, clients can write to process objects. If this
argument is not specified, write transactions are not allowed.
In addition to this argument, the OBJECTWRITE user preference must
be enabled. The default setting for this preference is disabled.
For details on how to set this user preference, refer to the section on
configuring user preferences in Configuring User Preferences on page
758.
3BUF001092R4001 717
Table 67 describes the arguments that are unique for the ADSdpLOG.EXE data
Table 67. ADSdpLOG.EXE Arguments
server The host name or TCP/IP address where the service provider runs. For
a local node installation, this should be the name of the local node. If
you do not want the data provider to start automatically when the
corresponding Display server is started, set the value for Server to
NoNode.
the one specified.
Default: 19014
Range: 1000<= n <= 65000
-name This is the assigned name for the data provider.
LogHandler
-Allow_Log_Write If this argument is specified, clients can modify existing log entries, and
add new log entries. If this argument is not specified, write transactions
are not allowed.
In addition to this argument, the LOGWRITE user preference must be
enabled. The default setting for this preference is disabled.
758.
718 3BUF001092R4001
Table 68 describes the arguments that are unique for the ADSdpOPC.EXE data
Table 68. ADSdpOPC.EXE Arguments
-OPCprogID <xxx> Logical name for OPC server.
For remote OPC servers such as Symphony, Freelance, or SattLine, use
the Data Provider Configuration Wizard to get this information. For details,
refer to Configuring Access to Realtime OPC Data on page 684.
-OPChost <xxx> Host name of the PC where the OPC server resides. This is only required if
OPC server is on a remote host. Do not specify if OPC server and data
provider are on the same host.
For remote OPC servers such as Symphony, Freelance, or SattLine, use
the Data Provider Configuration Wizard to get this information. For details,
refer to Configuring Access to Realtime OPC Data on page 684.
-Allow_Object_Write If this argument is specified, clients can write to OPC objects. If this
argument is not specified, write transactions are not allowed.
In addition to this argument, the OBJECTWRITE user preference must be
enabled. The default setting for this preference is disabled.
758.
-EventUpdateRate There is no event subscription on OPC, but a low update rate can simulate
<nnn> this. Default: 250, Unit: milliseconds
-EventDeadBand Percent of difference between low and high engineering units range of
<nnn> analog values. (EU values are specified on the OPC server). Default: 0.00,
Unit: Percent
-CacheWrites If true, the OPC initialization and setup for write commands will never be
removed, resulting in better performance for following writes to the same
object. This uses more memory. Default: Not specified not cached). Range:
Specified | Not specified
3BUF001092R4001 719
ADO Data Provider for Oracle Access Section 15 Configuring Data Providers
ADO Data Provider for Oracle Access

Table 69 indicates the ADO data provider configuration to support Oracle access. If
you are adding another ADO data provider to support SQL access for Oracle-based
numeric logs, copy the existing data provider with the configuration shown in
Table 69, and change the -name argument (for example: DBA2).
Table 69. ADO Data Provider Set-up for Oracle Access
Argument Value
-port 19014
-channel 0
-pass history - Password for the history user.
-server localhost
-dbtype ODBC
-ReconnINT 10 - Retry interval (in seconds) for reconnecting to the Oracle database if the
data provider is disconnected from the Oracle database.
-user history - Username for the history user.
-dbname Defaults to localhost. DO NOT change this specification
-name DBA
-FatalErrors “03114” (quotation marks required) - Indicates that oracle error code “03114” for
disconnect will be considered fatal.
-dbname matches ODBC Data Source Name
Figure 550. Detailed View of ADO Arguments
720 3BUF001092R4001
Section 15 Configuring Data Providers Starting and Stopping Providers
Starting and Stopping Providers

To manually start or stop a data provider, select the data provider, right-click, and
then choose Start Provider or Stop Provider from the context menu.
Deleting a Data Provider

To delete a data provider, use the browser to select the data provider, right-click, and
then choose Delete Provider from the context menu.
The data provider will be deleted immediately (after the specified

TerminateDelay time). You will NOT be prompted to confirm or
cancel.
Adding Arguments to a Data Provider

For some data providers, you can add arguments, which are then displayed in the
configuration dialog. To add arguments, you must first stop the provider. Then right-
click, and choose Add arguments from the context menu. This displays a dialog for
selecting the argument to add. Figure 551 show the add arguments dialog for an
ADO data provider.
Figure 551. Example Add Arguments Dialog
3BUF001092R4001 721
Checking Display Server Status Section 15 Configuring Data Providers
Checking Display Server Status

To check server status, from the Windows task bar, Figure 552, choose
Start>Programs>ABB Industrial IT 800xA>Information Mgmt>
Display Services>Server Status.
Figure 552. Checking Server Status
This displays a dialog for specifying the server hostname, Figure 553.
Figure 553. Specifying Server Hostname
Enter the hostname, then click OK. As an option you can specify the maximum time
to wait for the server to respond.
Leaving the hostname blank defaults to localhost.
722 3BUF001092R4001
Section 15 Configuring Data Providers Checking Display Server Status
This displays the server status window, Figure 554.
Number of Client Licenses
Number of Data Providers

List of Connected
Data Providers
Number & List of Connected Clients
Figure 554. Display Server:COMM Window
This window provides the following information related to the Display Server:
License Text This field indicates the license text.
License Will This indicates when the current license is scheduled to
Expire expire. After you enter the permanent license, this should
indicate your permanent license will never expire.
Started This field indicates when the server was started.
Facilities This is not applicable at this time.
3BUF001092R4001 723
Checking Display Server Status Section 15 Configuring Data Providers
Licenses These fields show the total number of purchased licenses,

and the available licenses not currently being used:
• Build - When you log in with Build access you can use
Display Services both in the Build mode and the Run
mode.
• MDI - Multiple Document (Display) Interface. When you
log with MDI Run access, you can run multiple displays
at the same time.
• SDI - Single Document (Display) Interface. When you
log with SDI Run access, you can only run one display
at a time.
• ADD - DataDirect.
• DP - This is the number of data providers. See Data
Providers Connected.
Data Providers This shows the number of data providers connected. Display
Connected Services must have one data provider connected.
Clients Connected This shows how many clients are connected to this server.
The information provided includes the node name, type (MDI
or SDI), and date and time when the client connected.
724 3BUF001092R4001
Section 16 Authentication
You can configure authentication for certain operations related to Information

Management to help meet FDA 21CFR part 11 requirements. Authentication
determines whether or not approval will be required before a user will be allowed to
perform a certain function, for example: activating logs in a log set.
Authentication may be set to one of three levels: none, reauthentication requires one
user to be approved (by entering user name and password), and double
authentication requires two users to be approved. If authentication for an operation
is configured, a dialog is displayed when the operation is attempted, Figure 555, and
the user must enter the proper credentials before the operation can proceed.
The standard authentication mechanism used by other 800xA system functions is

NOT used by Information Management. This section describes how to use
The
authentication specifically for Information Management.
Authentication for runtime operations related to softpoint signals is configured
via the signal configuration aspect. This is described in Configuring
Authentication for Signal Types on page 62.
For aspects related softpoint configuration, see Configuring Authentication for
Aspects Related to Softpoint Configuration on page 730.
3BUF001092R4001 725
Section 16 Authentication
Single Authentication Dialog
Double Authentication Dialog
Figure 555. Authentication Dialogs
726 3BUF001092R4001
Section 16 Authentication Configuring Authentication
Configuring Authentication
Authentication may be configured on an individual basis the operations associated
with aspect categories. These aspect categories are located in the Aspect System
structure. Table 70 lists the operations for which authentication may be configured.
The operations are listed by aspect category, which are grouped by aspect system.
Authentication is configured via an aspect category’s Inform IT Authentication
Category aspect. Typically, this aspect already exists in the aspect category’s aspect
list, and all operations will be preset to None. It this case, you may change the
authentication level for an aspect category operation by displaying the aspect’s
configuration view, selecting the operation, selecting the authentication level, and
then clicking Apply. This is illustrated in Figure 556.
1) Display Inform IT Authentication Category Aspect for an Aspect Category
2) Select an
Operation
3) Select the
Authentication
Level
Figure 556. Configuring Authentication
3BUF001092R4001 727
Configuring Authentication Section 16 Authentication
If the Inform IT Authentication Category aspect does not yet exist, you must add it
to the aspect category’s aspect list. If the list of operations for the aspect category is
not complete, you may add any missing operations. To do this, click Add, then enter
the operation name and click OK, Figure 557.
Figure 557. Adding an Operation
Table 70. Operations for which Authentication may be Configured
Aspect System Aspect Category Operations

Inform IT Authentication Inform IT Authentication Modify
History Admin Modify
Log List Activate
Log Set Modify
Activate
Message Log Modify
Inform IT Historian
Activate
Report Log Modify
Activate
View Logs Activate
View PDL Modify
Delete PDL
728 3BUF001092R4001
Section 16 Authentication Configuring Authentication

Archive Device Modify
Publish
Unpublish
Initialize
Remount
Override Backup
Industrial IT Archive Archive Group Modify
Rescan
Reset Last Archive Time
Manual Archive
Archive Volume Modify
Restore
Initialize
Publish
Unpublish
Copy Volume
Action Aspect Modify
Scheduler Read
Job Description Modify
Read
Manage
Scheduling Definition Modify
Read
Start
Calculation Enable
Modify
Execute
Calculation
Calculation Status View Enable
Modify
Execute
3BUF001092R4001 729
Configuring Authentication for Aspects Related to Softpoint Configuration Section 16 Authentication

OLE DB Data Access Tables OLE DB DA Tables Modify
OLE DB HIstory Access Tables Modify
Configuring Authentication for Aspects Related to Softpoint Configuration

This section describes how to configure authentication for aspects related to
softpoints. This procedure is different than the one used to configure authentication
for aspects related to other Information Management functions.
Authentication for runtime operations for softpoint signals is configured as

described in Configuring Authentication for Signal Types on page 62.
You can configure authentication for the following aspect types related to softpoint
configuration:
• In the PCA Aspect System:
Binary
Integer
Object
Real
String
• In the Softpoint System Aspect System:
Alarm Event Configuration
Alarm Event Setting
Collection
Deploy
Generic Control Network
Process Object Configuration
Signal Configuration
For these aspect types, when you configure authentication, that configuration
applies to all operations which may be performed on those aspects (unlike the other
Information Management aspects where you can apply authentication on an
operation-by-operation basis.
730 3BUF001092R4001
Section 16 Authentication Configuring Authentication for Aspects Related to Softpoint Configuration
To configure authentication for one or more of the above aspect types:

1. Set the Advanced Access Control to True. This is done via the System Settings
aspect for the Domain object in the Admin structure, Figure 558.
This will enable authentication for all aspect categories which have been
configured to be enabled. If you had set the Advanced Access Control to false to
disable authentication on those aspect categories, they will now be enabled.
Figure 558. Setting Advanced Access Control to True
2. Then (reference Figure 559):

a. Go to the Aspect System structure.
b. Select the applicable aspect type under the PCA or Softpoint aspect
system.
c. Select the Aspect category Definition aspect.
3BUF001092R4001 731
Configuring Authentication for Aspects Related to Softpoint Configuration Section 16 Authentication
d. Check the check box for the authentication level that you desire:
Re-authentication Required or Double Authentication Required.
Figure 559. Configuring Authentication
732 3BUF001092R4001
Section 17 System Administration
This section describes administrative procedures for Information Management

applications in the 800xA system. Access to most of these functions is via the
Administrative Tools utility on the Windows Control Panel, Figure 560. To access
the PAS administrative tools, from the Windows task bar choose:
Start>Settings>Control Panel>Administrative Tools>PAS, Figure 561.
Figure 560. Accessing Information Management System Administration Functions
3BUF001092R4001 733
Figure 561. Accessing the Information Management Administrative Tools
To use these system administration functions you must have

Domain Administrator privileges in the Windows 2000 system. The
user name that you use must have Domain Administrator rights.
For consolidation nodes, you may use a domain user with domain
administrator privileges, or a locally-defined user with
administrator privileges, depending on whether or not the
consolidation node resides in a domain.
The following is a brief description of these administrative procedures.
Start Up, Shutdown and Supervision of ABB Software Processes

See Start-up and Shutdown on page 736 for guidelines on starting, stopping, and
supervising the Information Management software processes on the Windows 2000
platform. See Stopping Oracle on page 742 to stop Oracle processes.
734 3BUF001092R4001
Managing Users
The Information Management installation creates default user accounts and user
groups. If you need to add, remove, or otherwise edit any user accounts, see
Managing Users on page 744.
Certain Windows and Oracle users installed with your system should have their
default passwords changed in order to prevent unauthorized access. For details, see
Securing Your System on page 748.
Configuring OMF Shared Memory

OMF Shared memory size defines the size of shared memory for processes that use
the OMF software. If the shared memory is too small, processes may be aborted
without any error messages (the Process Administration Services will discover that
the process has been aborted). The default shared memory size is 8,192 Kbytes. To
adjust OMF shared memory size, see OMF Shared Memory Size on page 797.
Supervising Display Server Status

See Checking Display Server Status on page 766.
Software Version Information

This tool lets you check version information for all ABB software products and Set
Up for Viewing On-line Documentation
On-line documentation for Information Management software is provided in
Acrobat Reader PDF format. File handling in Windows Explorer must be set up to
start Acrobat Reader when you open a PDF file. Your computer should be set up this
way when you install Acrobat Reader. If PDF files do not open with Acrobat
Reader, see Handling PDF (Acrobat Reader) Documents on page 770.
Disk Maintenance - Defragmenting

See Disk Maintenance - Defragmenting on page 772 for recommendations.
3BUF001092R4001 735
Start-up and Shutdown Section 17 System Administration
Start-up and Shutdown

This section describes how to start up, shut down, and manage the Information
Management processes.
Information Management software processes are started and supervised by the
Process Administration Services (PAS).
Once History Services has been started and is collecting data, if you
need to restart or shut down your PC, you MUST first stop PAS.
PAS will perform an orderly shutdown of the ABB software and
any user processes under its supervision. Failure to stop PAS before
you restart or shut down your PC will result in loss of History data,
and may corrupt History data files.
The Process Administration Service window, Figure 562, lets you shut down ABB
processes independent of Windows.
Figure 562. Process Administration Service Window
736 3BUF001092R4001
Section 17 System Administration PAS Window
PAS Window
To access the PAS window you must be logged in as an Domain Administrator-level
user, or a user in the PAS operator list. To open the PAS window, from the
Windows task bar, choose: Start>Settings>Control Panel>Administrative Tools
>PAS>Process Administration.
This window is for starting and stopping all processes under PAS supervision. It
also provides access to advanced functions for debugging.
The process list shows all processes specified in the Windows registry under
HKEY_LOCAL_MACHINE\SOFTWARE\ABB\PAS\Startup. The information
provided in this list is described in Table 71. PAS Window controls are described in
Table 72.
Table 71. PAS Process List
Field Description
Process Name Name of the processes.
Supervision Enabled When a process is removed from PAS supervision (Advanced Functions
or Disabled on page 738), an X icon is placed to the left of the process name.
Process State State of the supervised process, normally Started or Stopped.
Priority Order in which processes run. When the processor is busy, this
determines which processes will be run at all.
3BUF001092R4001 737
Starting and Stopping All Processes Section 17 System Administration
Table 72. PAS Window Controls
Button Description
Start All/Stop All Start or stop all processes. See Starting and Stopping All Processes.
Restart All Stop and then restart all processes.
Reset Resets failed processes to the Stopped state.
Refresh Clears the process list and queries PAS for the current process list. This
may be used if the list gets out of sync with the PAS internal state.
Advanced>> Expands the window to show controls for advanced functions. See
Advanced Functions on page 738.
Connect This button is only visible when the PAS window is disconnected from PAS.
If this occurs, use this button to reconnect the PAS window to PAS
Starting and Stopping All Processes

To stop all PAS processes without shutting down the PC, open the PAS window,
from the Windows task bar. Choose Start>Settings>Control Panel>
Administrative Tools>PAS>Process Administration. Then click Stop All. PAS
is still active when you stop all processes. To restart all stopped processes, click
Start All.
Processes start in the order specified by their respective WhenToStart parameters.
This order corresponds to the order in which the processes are listed in the PAS
window. The processes are stopped in the reverse order from which they are started.
Advanced Functions
Click Advanced>> in the PAS Window to show the Advanced functions,
Figure 563.
738 3BUF001092R4001
Section 17 System Administration Advanced Functions
Figure 563. Advanced Dialog
The advanced functions are organized on three levels:

• Process Control - Table 73
• PAS Service Control - Table 74
3BUF001092R4001 739
Advanced Functions Section 17 System Administration
Table 73. Advanced Functions for Individual Processes
Button Description
Start Process/Stop Start or stop the selected process.
Process CAUTION: PAS does not perform dependency checks before
starting/stopping an individual process. Therefore you should
generally stop or start all processes rather than individual processes.
Disable/Enable This button alternately disables and re-enables PAS supervision for a
Administration process. For example, if a process fails to start for some reason, you
may want to remove it from PAS supervision so as not to affect the
start-up of other processes. This is generally used for troubleshooting.
Reinitialize Settings This is for technical support personnel. It is used when the registry
information for a process has been changed. When this occurs, the
process must be reinitialized in order for the changes to take effect.
740 3BUF001092R4001
Section 17 System Administration Advanced Functions
Table 74. Advanced Functions for PAS Service
Button Description
Stop PAS/Start PAS Start PAS starts PAS. If Autostart flag in the registry is set or is not
specified, PAS will begin the Start All sequence as soon as it starts.
Stop PAS stops PAS. Before PAS service stops, it will shutdown all
processes including the ones that have disabled administration.
NOTE: Only Domain Administrator users are permitted to start/stop
the PAS service. Users specified in the PAS Operator list are not
permitted to start/stop PAS.
Global Reinitialize This command can only be issued when all processes are stopped.
It tells the PAS service to completely erase all its data structures and
reinitialize them with current registry settings. Any changes in the
registry including PAS global setting, Node Type, and individual
process settings will take effect when this command is issued.
Send Message This displays a dialog for sending messages as an alternative
method for interacting with the PAS service, Figure 564. You can
also read the messages that have been sent to a process. This
functionality is generally reserved for debugging by technical
support personnel.
View Logs Displays execution log for PAS service.
Figure 564. Send Message Dialog
3BUF001092R4001 741
Stopping Oracle Section 17 System Administration
Stopping Oracle
To stop Oracle you must stop the Windows services for the Oracle database instance
and Listener. This is done via the Services utility in the Administrative Tools on the
Windows Control Panel. To do this:
1. First launch the Services utility as shown in Figure 565.
Figure 565. Accessing the Windows Services Utility
742 3BUF001092R4001
Section 17 System Administration Stopping Oracle
2. Scroll to the OracleServiceADVA service, right-click and choose Stop

from the context menu. Figure 566.
Figure 566. Stopping OracleServiceADVA
3. Scroll to the service named OracleTNSListener, right-click and choose Stop

from the context menu.
3BUF001092R4001 743
Managing Users Section 17 System Administration
Managing Users
This section describes how to manage user access for the Information Management
server. User access is handled on four levels:
• Windows User - The PC where the server software is installed requires you to
log on with a Windows username and password. Windows users are created
and managed via the User Manager on the Windows control panel. A default
user configuration is created by the Windows 2000 installation. Other
Windows users may be created by the installing user as described in the section
on creating users and groups in Industrial IT 800xA System Installation.
The Information Management and Oracle software installations create
additional users and groups. These are described in Windows Users and Groups
for Information Management on page 745.
• Oracle Access - Oracle user authority is required by certain Information
Management processes for access to the Oracle database. A default user
configuration is created by the Information Management and Oracle software
installations. These users are described in Oracle Users on page 747.
• Display Client Users - Standard user files are provided for the desktop
applications - DataDirect, Desktop Trends, and Display Client. You can create
additional users by copying and renaming an existing user file. You can also
specify new passwords, configure user preferences, and customize language
translations. See Managing Users for Display Services on page 753.
You should change the default passwords for certain Windows users
and Oracle users immediately after installing the Information
Management software. This is to protect your system from
unauthorized access. Guidelines are provided in Securing Your
System on page 748.
To support Information Management applications such as historical database

maintenance, and other administrative procedures one or more Industrial IT users
must be added to the HistoryAdmin Group.
744 3BUF001092R4001
Section 17 System Administration Windows Users and Groups for Information Management
Windows Users and Groups for Information Management

The default user configuration following installation of Information Management
and Oracle software is illustrated in Figure 567, and described below.
Figure 567. Default Windows Users
This default user configuration is sufficient to support all Information Management

operation, configuration, and administration activities. You may create additional
users and modify user accounts as required via the Windows User manager.
ocshis User
This user is created by the Information Management software installation It is used
by Information Management processes that require Oracle access. This user is
assigned to the ORA_DBA, HistoryAdmin, and Administrator user groups. It is
recommended that you change the default password for the ocshis user as soon as
possible. This procedure is described in Securing Your System on page 748.
3BUF001092R4001 745
Windows Users and Groups for Information Management Section 17 System Administration
HistoryAdmin Group
This group is created by the Information Management software installation. Users
in this group have access to History configuration and History database
maintenance functions. These users can access History database maintenance
functions and other Information Management administrative procedures seamlessly
without having to change users, or enter Oracle passwords.
This group is included in the PAS OperatorList by default. This grants all users in
the HistoryAdmin group access to PAS, even if these users are not Domain
Administrator-level users. This enables HistoryAdmin users to start and stop PAS
services as required by certain History database maintenance functions.
To grant HistoryAdmin users access to History database configuration, but deny
access to PAS, you must remove this group from the PAS OperatorList. Instructions
for editing the PAS OperatorList are provided in PAS OperatorList on page 751.
User for 800xA System Service Account

When the 800xA core software is installed, an 800xA service account is configured.
The user for this account is assigned to the ORA_DBA and HistoryAdmin user
groups and all History services will run as this user. To support this, this user must
also be specified for the log-in accounts for these services. This is done when you
configure the History database instance. The IM History Service Account dialog
used to set up this account may also be launched from the Windows task bar
Start>Settings>Control Panel>Administrative Tools>PAS>
Password Administration). This method for launching the IM History Service
Account dialog should only be used for certain upgrade procedures. Instructions for
using the dialog will be provided in the applicable upgrade instructions.
ORA_DBA Group
This group is created by the Oracle software installation. Users in this group have
Oracle access for database maintenance functions. Such access is generally reserved
for technical support personnel.
746 3BUF001092R4001
Section 17 System Administration Oracle Users
Oracle Users
The default Oracle user configuration created by the Oracle and Information
Management software installations is described in Table 75.
Table 75. Oracle Users
User(1) Description
SYS Created by Oracle.
SYSTEM Created by Oracle.
OUTLN Created by Oracle.
DBSNMP Created by Oracle.
HISTORY This user is created when the Oracle database instance is created.
This user has read access to Oracle tables and views.
OPS$OCSHIS This is an Oracle user account created for the ocshis Windows user.
OPS$_____ This is an Oracle user account created for the Windows user that
installed the Information Management software. This user account is
classified as EXTERNAL, meaning it does not have an Oracle
password. When you are logged in as the Windows user that installed
the Information Management software (for example, tar238), to log
into Oracle, you merely have to enter a slash(/) following the sqlplus
command, for example sqlplus /.
(1) Since Information Management users are not licensed for write access to Oracle tables, the HISTORY
user account is the only Oracle user that operators should use.
You are not required to alter this default Oracle user configuration; however, it is
strongly recommended that you change the default passwords for all Oracle users
with the exception of the HISTORY user, and users whose password is indicated as
EXTERNAL. This procedure is described in Securing Your System on page 748.
3BUF001092R4001 747
Securing Your System Section 17 System Administration
Securing Your System

You should change the passwords for Windows and Oracle users as soon as possible
after software installation to protect your system from unauthorized access.
Changing Passwords for Oracle Users

The default Oracle users are described in Oracle Users on page 747. The current
Oracle user information resides in the Oracle table named dba_users. You can use
sqlplus to access the contents of this table as shown in Figure 568.
The passwords for the following users need to be changed to make your system
secure: SYS, SYSTEM, OUTLN, DBSNMP, and OPS$OCSHIS.
DO NOT change the password for the HISTORY user. The history account has read
only access and the password MUST remain unchanged for compatibility with
existing and new READ ONLY clients. Changing this password will break
applications.
The OPS$____ (Windows user that installed Information Management software)
does not have an associated password, and therefore does not need to be modified.
Use the following procedure to change the passwords for the other Oracle users:
1. Log in to sqlplus as the SYS user. The default password is change_on_install:
sqlplus sys/change_on_install
2. To change the password for this user enter:
alter user sys identified by password1 ;
where password1 is the new password.
3. repeat this for the other Oracle users whose passwords must be changed:
alter user system identified by password2 ;
alter user outln identified by password3 ;
alter user dbsnmp identified by password4 ;
alter user ops$ocshis identified by password5 ;
You can use the same password for all users.
748 3BUF001092R4001
Section 17 System Administration Securing Your System
Figure 568. Displaying Oracle Users and Changing Passwords
Changing Passwords for Windows Users

The default Windows users are described in Windows Users and Groups for
Information Management on page 745. The ocshis user has Domain Administrator
privileges. Change the ocshis user password if you need to protect Oracle and OMF
data, as well as certain administrative tasks from unauthorized access.
Use the following procedure to change the password for ocshis:
1. Launch the Windows User Manager from the Windows control panel. To do
this, from the Windows task bar choose Start>Settings>Control Panel>Users
and Passwords, Figure 569.
Figure 569. Launching the Windows User Manager
3BUF001092R4001 749
Securing Your System Section 17 System Administration
2. Select the ocshis user and click Set Password, Figure 571.
Select ocshis user
Click here to display

Set Password dialog
Figure 570. Selecting the ocshis User
3. Enter the new password for ocshis, enter it again to confirm, then click OK,
Figure 571.
Figure 571. Setting the ocshis Password
750 3BUF001092R4001
Section 17 System Administration PAS OperatorList
PAS OperatorList
OperatorList is a configuration parameter for the PAS Service in the Windows
Registry. This parameter specifies a list of groups and users other than Domain
Administrator-level users who can use the PAS window to start and stop processes
under PAS supervision. Groups and users in this list have complete access to all
functions in the PAS window, except starting and stopping the PAS service itself.
Only Domain Administrator users can start and stop PAS. You can edit this list to
grant/deny users and groups access to PAS.
The HistoryAdmin Group is included in the PAS OperatorList by

default. If you want to grant HistoryAdmin users access to History
database configuration, but deny access to PAS, you must remove
this group from the PAS OperatorList.
To edit the PAS OperatorList:

1. Open the Registry Editor. From the Windows task bar, choose Start>Run.
Then enter regedit in the Run dialog, Figure 572.
Figure 572. Opening the Registry Editor
2. Navigate to the location in the registry where the processes under PAS
supervision are specified -
HKEY_LOCAL_MACHINE\SOFTWARE\ABB\PAS, Figure 573.
3BUF001092R4001 751
PAS OperatorList Section 17 System Administration
Figure 573. Locations of PAS Processes
3. Double-click the OperatorList parameter.

The list is specified as names separated by pipe( | ) character with no spaces
between the name and the pipe. Example: HistoryAdmin|User1|User2
752 3BUF001092R4001
Section 17 System Administration Managing Users for Display Services
Managing Users for Display Services

Display Services comes with the following default users: aid, mdi, sdi. These users
are used when logging into Displays Services, a display client, DataDirect (Excel
Data Access), and Desktop Trends.
User configurations are maintained in a separate Preferences.svd file for each
user. These files are located in .svg folders in:
C: \Program Files\ABB Industrial IT\Inform IT\Display Services\Server\Data
The user name is the second word in the name (following the underscore),
Figure 574.
Preferences.svd file for aid user
Figure 574. User Configuration Data
The following user management procedures are covered here:

• Creating New Users
• Creating User Passwords
• Configuring User Preferences
• Customizing Language Translations
3BUF001092R4001 753
Creating New Users Section 17 System Administration
Creating New Users

To create additional users, copy and then rename an existing user folder. For
instance, navigate to the AID_aid.svg folder as shown in Figure 574. Then right-
click on the folder and use the context menu to copy and rename the folder,
Figure 575.
Copy and Rename this folder

to create a new user
Figure 575. Copying and Renaming a User
When you copy and rename a folder, the user name is the second
word in the name (following the underscore, for example in
AID_aid.svg, the user name is aid).
When you create a new user, you should create a unique password for that user. See
Creating User Passwords on page 755.
You may also want to configure user preferences and/or customize language
translations for that user. See Configuring User Preferences on page 758, and
Customizing Language Translations on page 763.
754 3BUF001092R4001
Section 17 System Administration Creating User Passwords
Creating User Passwords

This describes how to change the password for an existing user, or assign a unique
password for a new user. This is a two-step process. First run the Create User
Password utility to get an encrypted password key. Then, associate the new
password with a specific user by entering the password key in the
Preferences.svd file for the user.
Create User Password

To run the Create User Password utility, from the Windows task bar, choose:
Display Services>Server>Create Password, Figure 576.
Figure 576. Creating a User Password
This displays the Create Password dialog. Enter the new password in the Typed
Password field. The encrypted password key is displayed in the AdvaInform
Display Password field, Figure 577.
3BUF001092R4001 755
Creating User Passwords Section 17 System Administration
Figure 577. Password Key
Associate New Password with a Specific User

To associate a new password with a specific user, record the password key (from
AdvaInform Display field in Create Password dialog), and enter it in the user’s
Preferences.svd file.
Navigate to the applicable user folder (directory) as described in Managing Users
for Display Services on page 753. Then open the applicable folder, for example,
AID_AID.svg. This folder contains Preferences.svd for the AID user,
Figure 578.
Figure 578. Navigating to the Preferences.svd File
756 3BUF001092R4001
Section 17 System Administration Creating User Passwords
To enter the new password, open the Preferences.svd file with a text editor,
and then edit the file. An example is shown in Figure 579.
You can copy the value from the AdvaInform Display Password
field and then paste it in the Preferences.svd file, or simply enter the
value directly.
This is where you enter the encrypted password

(from AdvaInform Display Password field in
Create Password dialog).
Figure 579. Editing the Preferences.svd File
3BUF001092R4001 757
Configuring User Preferences Section 17 System Administration
Configuring User Preferences

By configuring user preferences, Table 76, you can customize the user interface
according to the specific user that logs in to Display Services (or one of the desktop
applications).
If you want to allow users to change preferences, the corresponding

preferences file must have read/write access, Figure 580. To find
how to access a preferences file, see Managing Users for Display
Services on page 753.
RO = Read Only
RW = Read/Write
Figure 580. Configuring a Preference for Read-Only or Read/Write Access
To configure a user preference:

1. Start the Windows client.
2. From the menu bar, choose User > Preferences. This displays the User
Preferences dialog.
3. Use the navigation tool to find the user preference you want to configure.
4. Click on the preference. When you make a selection, the dialog displays
interactive widgets as required to configure the selected preference. For
instance, if you select TEXTCOLOR under EDITOR, the dialog displays the
current color selection, and a Change button. Clicking this button displays the
color palette so you can change the color, Figure 581.
Any changes you make to user preferences will not take affect until
you restart the computer.
758 3BUF001092R4001
Section 17 System Administration Configuring User Preferences
Button to display color palette
Current Color Selection Color palette
Figure 581. Configuring TEXTCOLOR
3BUF001092R4001 759
Table 76. User Preferences
Name Default Description

AID-PASSWORD 47D2D5F8 Encrypted password, not accessible via the User
Preferences dialog. See Creating User Passwords on
page 755.
AID-STARTUP-DISPLAY- Group name of the display presented when you start
GROUP up the application. By default, no startup display is
specified. If you specify a startup display, it is
generally from the Batch group. Display groups are
listed under the host root in the Object Browser.
AID-STARTUP-DISPLAY- Name of the display presented when you start up the
DISPLAY application. By default, no startup display is specified.
If you specify a startup display, it is generally from the
Batch group.
AID-STARTUP- Group name of the base display presented when you
BASE_DISPLAY-GROUP start up the application.The base display is shown in a
third frame at the bottom of the main window. By
default, no base display is specified. If you specify a
base display, it is generally from the Batch group.
AID-STARTUP- Name of the base display presented when you start
BASE_DISPLAY-DISPLAY up the application.The base display is shown in a third
frame at the bottom of the main window. By default,
no base display is specified. A command application
is to specify the MessageDisplay as the base display.
AID-BROWSER- False This toggles between the normal browser view
ROOTASTAB (default) and the tabbed view where roots on the tree
are displayed as tabs.
AID-BROWSER- 5 This adjusts the scroll speed for the browser.
SCROLLSPEED
AID-BROWSER- 2 This adjusts the delay (in seconds) for expanding a
SPRINGLOADDELAY folder in the browser when you drag-and-drop.
760 3BUF001092R4001
Section 17 System Administration Configuring User Preferences

AID-EDITOR-FONT 49 Font used in Display Services. This is only applicable
when you have a build license for Display Services.
AID-EDITOR-TEXTCOLOR 0 Color for text in Display Services. This is only
applicable when you have a build license for Display
Services.
AID-EDITOR- 255 Color for strings in Display Services. This is only
STRINGCOLOR applicable when you have a build license for Display
Services.
AID-EDITOR- 35328 Color for comments in Display Services. This is only
COMMENTCOLOR applicable when you have a build license for Display
Services.
AID-EDITOR-WORDCOLOR 16000000 Color for keywords in Display Services. This is only
applicable when you have a build license for Display
Services.
AID-VIEW-TOOLBAR True Show or hide the toolbar.
AID-VIEW-ELEMENTBAR True Show or hide the element bar. This is only applicable
AID-VIEW-USERBAR True Show or hide the user bar.This is only applicable
AID-VIEW-STATUSBAR True Show or hide the status bar.
AID-VIEW-BROWSER True Show or hide the browser.
AID-VIEW- True Use the old-style or new-style frame.This is only
OLDSTYLEFRAME applicable when you have a build license for Display
Services.
AID-VIEW- 1 Color of display boarder.
DISPLAYBOARDERCOLOR
AID-VIEW- 1 Color of the inactive area.
INACTIVEAREACOLOR
3BUF001092R4001 761

AID-AUTOLOGOFF- 15 Minutes This lets you configure a user to be automatically
AFTERMINUTES logged off after a period of inactivity. The autologoff
function must be enabled for this setting to take affect.
AID-AUTOLOGOFF- False (0) This lets you enable or disable the AUTOLOGOFF
ENABLED function.
False(0) = Disabled
True (1) = Enabled
AID-DATARETRIEVAL- NORMAL This lets you specify whether numeric display
DCSDATA elements will query process objects directly for real-
time data, or whether the numeric elements will query
the process object’s associated History log.
The default is to get real-time data directly from
process objects (NORMAL). If you set this preference
to HISTORY, the query returns the last History value
that was logged for the process object.
The numeric element is configured the same way,
whether you are querying for real-time data, or
Historical data.
AID-RIGHTS-OBJECTWRITE False (0) This lets you enable or disable write access to
process and/or OPC objects.
False(0) = Disabled - no write access
True (1) = Enabled - write access allowed
AID-RIGHTS-LOGWRITE False (0) This lets you enable or disable write access to
numeric history logs (modify or add entries).
False(0) = Disabled - no write access
True (1) = Enabled - write access allowed
AID-RIGHTS- True (1) This lets you enable or disable the System function in
SYSTEMACCESS a Display script. This must also be enabled for Bulk
Data Export.
False(0) = Disabled
True (1) = Enabled
762 3BUF001092R4001
Section 17 System Administration Customizing Language Translations
Customizing Language Translations

The language for the user interface is determined by the language file you select
when you log in to a client application. An ENGLISH language file is provided as
standard. You can create additional language files by copying, renaming, and then
editing this standard file.
The language files reside in C:\ProgramFiles\ABB Industrial
IT\Inform IT\Display Services\Client\Lang as shown in
Figure 582.
Figure 582. Navigating to Language Files
The first time you log in using a custom language, you will be prompted to define
any unknown text strings, Figure 583. You can either define the strings at this time,
skip some strings on an individual basis, or skip all definitions at this time.
3BUF001092R4001 763
Customizing Language Translations Section 17 System Administration
Figure 583. Prompt to Define Unknown Text
To customize the language, choose User > Language from the menu bar and then
use the Edit Language dialog, Figure 584.
The Texts list displays the English version of all text used in the user interface.
Selecting a text line from the list displays the translation for that text according to
the language you have chosen for this session. English text is the default. Edit the
translation in the Translation field, and then click Apply.
764 3BUF001092R4001
Section 17 System Administration Customizing Language Translations
Some texts have special characters:

• & is used in menu texts to indicate that the next character is a
mnemonic key.
• % is used by the system to fill in additional text such as the
name of a display.
DO NOT remove these special characters
Figure 584. Edit Language Dialog
3BUF001092R4001 765
Checking Display Server Status Section 17 System Administration
Checking Display Server Status

To check server status, from the Windows task bar, Figure 585, choose
Display Services>Server Status.
Figure 585. Checking Server Status
This displays a dialog for specifying the server hostname, Figure 586.
Figure 586. Specifying Server Hostname
Enter the hostname, then click OK. As an option you can specify the maximum time
to wait for the server to respond.
Leaving the hostname blank defaults to localhost.
This displays the server status window, Figure 587.
766 3BUF001092R4001
Section 17 System Administration Checking Display Server Status
Number of Client Licenses
Number of Data Providers

List of Connected
Data Providers
Number & List of Connected Clients
Figure 587. Display Server:COMM Window
This window provides the following information related to the Server:

License Text This field indicates the license text.
License Will This indicates when the current license is scheduled to
Expire expire. After you enter the permanent license, this should
indicate your permanent license will never expire.
Started This field indicates when the server was started.
Facilities This is not applicable at this time.
3BUF001092R4001 767
Checking Display Server Status Section 17 System Administration
Licenses These fields show the total number of purchased licenses,

and the available licenses not currently being used:
• Build - When you log in with Build access you can use
Display Services both in the Build mode and the Run
mode.
• MDI - Multiple Document (Display) Interface. When you
log with MDI Run access, you can run multiple displays
at the same time.
• SDI - Single Document (Display) Interface. When you
log with SDI Run access, you can only run one display
at a time.
• ADD - DataDirect.
• DP - This is the number of data providers. See Data
Providers Connected. For information regarding data
providers, refer to Industrial IT 800xA - Information
Configuration.
Data Providers This shows the number of data providers connected. Display
Connected Services must have one data provider connected.
Clients Connected This shows how many clients are connected to this server.
The information provided includes the node name, type (MDI
or SDI as described in Licenses), and date and time when
the client connected.
768 3BUF001092R4001
Section 17 System Administration Software Version Information
Software Version Information

To check software version information for Information Management products and
components, from the Windows task bar choose: Start>Programs>ABB
Industrial IT 800xA>Information Mgmt>Version Info, Figure 588.
Figure 588. Opening the Software Version Information Tool
This displays the Version Information window, Figure 589. To save the version
information to a text file, choose File>Save As and specify the text file path.
Figure 589. Software Version Information Tool
3BUF001092R4001 769
Handling PDF (Acrobat Reader) Documents Section 17 System Administration
Handling PDF (Acrobat Reader) Documents

On-line documentation is supplied in Acrobat Reader (PDF) format. Windows 2000
must be configured to start-up the Acrobat Reader for PDF files. Installing Acrobat
Reader should configure your computer to do this. If your computer does not open
PDF files with Acrobat Reader, you can try re-installing Acrobat Reader, or
configure Folder Options for the PDF file extension. This is done via the
Tools>Folder Options function in Windows Explorer.
The File Types tab in the Folder Options dialog lets you select and configure
options for all Windows file types, including PDF, Figure 590.
Figure 590. Options Dialog
If the configuration needs to be changed, click the Advanced button. Then use the
Edit File Type dialog to specify AcroRd32.exe as the application to perform the
Open, Print, and Printto actions, Figure 591.
770 3BUF001092R4001
Section 17 System Administration Handling PDF (Acrobat Reader) Documents
Figure 591. Specifying Application to Perform Action
3BUF001092R4001 771
Disk Maintenance - Defragmenting Section 17 System Administration
Disk Maintenance - Defragmenting

Information Management configuration procedures that involve the creating,
deleting, and then recreating of a large quantity of objects may cause the associated
disks to become fragmented. This, in turn, may impair the response time and
general performance of your system.
One such procedure is the configuration of the History database using the Bulk
Import tool which as added as an ABB add-in to Microsoft Excel. Another
procedure which causes fragmented files is deleting and then recreating an Aspect
System.
It is recommended that you check your system for fragmented files after any such
procedure, and defragment your disks as required.
History configuration impacts not only the Information

Management disk(s), but also the disk(s) on any Connectivity
Servers where the operator trend function runs. Therefore you
should check the disks on those Connectivity Servers as well as the
Information Management.
772 3BUF001092R4001
Appendix A Terminology
The following is a list of terms related to the 800xA system. The list contains terms
and abbreviations that are unique to ABB or have a usage or definition that is
different from standard industry usage.
Table 77. 800xA System Terminology
Term Description
ActiveX Microsoft standard for user interface components, based on definition of
software interfaces.
Aspect An aspect is a description of some properties of a real world entity. The
properties described could be mechanical layout, how the object is controlled,
a live video image, name of the object etc. In the Aspect Integrator Platform is
an aspect residing in an aspect object. Some examples of aspects are circuit
diagram, process display and control logic.
Aspect Category A specialization of an aspect type. For example, the aspect type Graphic
Display includes the categories Overview, Group and Object Display.
Aspect Integrator A collection of software that forms the basis for an Industrial IT System, and
Platform provides the development and execution environment for Industrial IT
Compliant applications. The Aspect Integrator Platform includes the Aspect
Framework.
Aspect Objects A computer representation of a real world entity like a pump, a valve, an order
or a virtual object like a service. This computer representation is implemented
by the Aspect Integrator Platform. An aspect object works like an information
container for it’s aspects.
3BUF001092R4001 773
Term Description
Aspect Object An aspect object type defines certain characteristics that are shared between
Type several aspect object instances, such as a basic set of common aspects. This
makes it possible to create and efficiently re-use standardized solutions to
frequently recurring problems. For example, rather than building an aspect
object from scratch for every valve in a plant, you can define a set of valve
types, and then create all valve objects of these instances.
Aspect Server A server that runs the central functions of the aspect object architecture, such
as Aspect Directory, Structure and Name Server, Cross Referencing, File Set
Distribution, etc. The Aspect Server is normally used as Windows domain
controller for the control and client/server networks.
Aspect System A software system, which implements one or several aspect types by
providing one or several aspect system objects.
Client Client is the part of the software that supply data to a subscriber.
Client/Server A client/server network is used for communication between servers, and
Network between workplaces and servers.
COM Microsoft’s Common Object Model that is used for exchanging information
within the Windows 2000 system.
Connectivity Connectivity components, up-loader, supporting aspect systems (e.g for the
Product configuration), and graphical elements, faceplates, aspect object types, etc.,
bundled together to provide the integration of a certain type of devices into the
Industrial IT system.
Connectivity A server that provides access to controllers and other sources for real-time
Server data, historical data, and alarm and event data. A Connectivity Server runs
services related to OPC/DA, APC/AE, OPC/HAD and SysMag.
Faceplate A faceplate is an aspect that provides a graphical representation of a certain
aspect object, with presentation of certain properties related to the object, and
mechanism for operator interaction such as on/off, increase/decrease, etc.
aspect object types often include several faceplate aspects, providing different
presentation and interaction possibilities.
774 3BUF001092R4001
Term Description
Graphic Display A graphic display is an aspect that provides a visual presentation. It consists
of static graphics representing for example tanks, pipes etc., and graphic
elements that present dynamic information. Graphic displays are often used to
present the state of a process or a part of a process, but are useful in any
context where dynamic graphical information is needed.
Industrial IT Industrial IT is the umbrella concept for ABB’s vision for enterprise
automation.
Industrial IT A computer system that implements (part of) the Industrial IT vision. Aspect
System Integrator Platform is an example of such a system.
Node A computer communicating on a network e.g. the Internet, Plant, Control or IO
network. Each node typically has a unique node address with a format
depending on the network it is connected to.
OMF ABB proprietary software that supports creation of and access to History and
Process objects in the ABB OCS. For detailed information regarding OMF
objects, refer to the AdvaInform Object Types Reference Manual.
OPC An application programming interface defined by the standardization group
OPC Foundation. The standard defines how to access large amounts of real-
time data between applications. The OPC standard interface is used between
automation/control applications, field systems/devices and business/office
application.
Plant Explorer An application that is used to create, delete and organize aspect objects and
aspects within the Aspect Integrator Platform. The plant explorer organizes
the aspect objects in structures according to functionality, location etc.You can
also use it to browse and search the structures of the plant.
Process Portal A Product containing functionality for efficient control and supervision of an
automated process. Key functions are presentation of process graphics,
process dialogs and presentation of alarms and trends.
Permission A permission groups a set of operations that require the same authority. For
each operation defined for an aspect, the aspect category specifies the
permission needed to use that interface.
Process Object A process concept/equipment e.g. valve, motor, conveyor or tank.
3BUF001092R4001 775
Term Description
Product Family A range of products within a Product Suite, forming a scalable offering.
Examples: a range of controllers, a family of I/O Products.
Product Suite Product with similar functionality are kept together in a suite. Suite names
have a superscripted IT-suffix. Examples: Operate IT , Control IT , Integrate IT
etc. Property A data field on an aspect of an aspect object that can be
accessed through OPC using the standard Aspect
Object reference A data field on an ActiveX control accessible from the Visual Basic editor.
syntax.
Security Security controls a user’s authority to perform different operations on aspect
objects, depending on several parameters: • The user’s credentials, as
provided by Windows • The node where the user is logged in. This makes it
possible to give a user different authority depending on where he/she is
located, e.g. close to the process equipment, in a control room, or at home
accessing the system through Internet. • The operation the user wants to
perform the operation on.
Server A node that runs one or several Afw Services. It is the part of the software that
supply data to a subscriber.
Structure A hierarchical tree organization of aspect objects. Each structure is used to
define a certain kind of relation between aspect object. The functional
structure defines how a function can be divided into sub functions, the location
structure defines how different objects are located within each other. The
control structure defines how functions are executed by tasks, controllers etc.
An aspect object can be located in several structures, for example both in a
functional structure and in a location structure.
System A software package that provides functionality in the Industrial IT System.
Application System applications cooperate according to rules defined by the Industrial IT
architecture, using mechanism provided by the Aspect Integrator Platform.
They are normally bundled into System Products. To participate in aspect
object operations, and thus be an integrated part of an Industrial IT system, a
system application must present itself as an aspect system. When there is no
risk for confusion with user application, the term application may be used
instead of system application.
776 3BUF001092R4001
Term Description
System A system Extension consists of one or more applications that are bundled as
Extension an extension to one or several existing System Product(s). A System
extension can only be installed if (one of) the corresponding System
Product(s) has been installed previously.
System Product A system product consists of applications bundled together with relevant parts
of the Aspect Integrator Platform. It is complete from installation point-of-view,
and requires only Windows 2000. Several System Products can be installed
on the same physical node.
Uploader An upload is used to import a configuration from devices, to read in and build
a set of aspect objects from information present in the devices.
User application A configuration of software and hardware components that applies to a
specific problem, e.g. a specific process control problem. A user application
consists of a set of simple and composite Aspect Object instances, with
parameter values and other configuration data for the aspects, e.g control
logic, process graphics, alarm and event specifications, reports etc.
View An Aspect can have several ways to be presented depending on the task
performed, like viewing or configuration. Each presentation form is called a
view.
Workplace 1. User interactive functions that are combined for a particular use, e.g,
Operator Workplace. 2. A node that runs one or several workplace
applications.
3BUF001092R4001 777
778 3BUF001092R4001
Appendix B Extending OMF Domain to TCP/IP
Certain Information Management functions require you to extend the OMF domain
to the TCP/IP network and all other ABB nodes that exist on the TCP/IP network.
Some of these functions are:
• consolidating history data from different Information Management servers.
• using one Information Management server to schedule event-triggered data
collection for logs that reside on a different node.
• using a Display client to view History trend data for any Information
Management node within the OMF domain.
The OMF TCP/IP domain can be defined by Multicast communication, point-to-
point communication, or a combination of Multicast and point-to-point
communication. Example applications are described in:
• OMF TCP/IP Domain with Multicast Communication
• OMF TCP/IP Domain with Point-to-Point and Multicast
• OMF TCP/IP Domain with Point-to-Point Exclusively
OMF TCP/IP Domain with Multicast Communication

There may be many Information Management nodes on a large company’s intranet.
To keep separate logical areas of the system from conflicting with each other, OMF
uses Ethernet’s Multicasting capabilities to establish Domains on the TCP/IP
network. This is done by configuring OMF on Information Management nodes that
you wish to be in the same domain with the same Multicast address. This prevents
OMF from communicating with any other OMF on the TCP/IP network having a
different Multicast address.
3BUF001092R4001 779
Multicast addresses look very similar to IP addresses. In fact, Multicast addresses

occupy a reserved section of the IP address range: 224.0.0.2 to 239.225.225.225.
The default Multicast address used when multicasting is first enabled is 226.1.2.3.
The default address is okay for systems that have their own TCP/IP
network (for small plants with no company intranet). For large
companies with complex intranets connecting multiple sites, the
default address is NOT recommended.
OMF TCP/IP Domain Defined By PLC Interface

Multicast Address 226.1.3.4. Display Services
Trend Displays
EH - 1 IM
226.1.3.4 DI AI
Primary History Logs-> 226.1.3.4 PLCs
TCP/IP Network Distributed History Logs
EH - 2
(HP- UX) EH - 3
(2000)
226.1.3.4
226.1.3.4
ABB Control System ABB Control System
Figure 592. Example System Configuration Using Multicast Only to Establish Domain
780 3BUF001092R4001
Any valid address may be selected and assigned to each of the Information
Management nodes that are required to be in the same Domain. Some companies
have the network administrator maintain control over usage of Multicast addresses.
This helps prevent crossing of Multicast defined Domains, and the problems that
may result.
Once you have defined the OMF TCP/IP Domain where your Information
Management node will reside, use the Communication Settings dialog to enable the
OMF TCP/IP socket, and assign the Multicast address. Use the following three
fields in the lower left corner of this dialog: TCP/IP Multicast enabled, Multicast
address, MulticastTTL. This procedure is described in Configuring OMF for
TCP/IP on page 789.
TCP/IP protocol must be configured before you can configure the

Multicast address, and enable the OMF TCP/IP socket. This is
described in Configuring TCP/IP Protocol on page 787.
OMF TCP/IP Domain with Point-to-Point and Multicast

Point-to-point may be used in combination with Multicast to restrict access between
certain nodes in the Multicast OMF TCP/IP domain. This is illustrated in
Figure 593. EH1 must have OMF access to both EH2 and EH3, but at the same time
OMF access must be prohibited between EH2 and EH3.
Again, you must use the Communication Settings dialog to configure TCP/IP
Multicast enabled, Multicast address, MulticastTTL. This procedure is described in
Configuring OMF for TCP/IP on page 789.
For point-to-point communication, you must also modify the Socket Configuration
List to match the table shown in Figure 593. This is described in Configuring OMF
Socket Communication Parameters on page 792.
3BUF001092R4001 781
Domain 1 Domain 2
EH1 EH1 - EH3
EH1 - EH2
Multicast Address = 226.1.3.4
IP Address = 172.28.66.190
TCP/IP Network
EH2 EH3
Multicast Address = 226.1.3.4 Multicast Address = 226.1.3.4

IP Address = 172.28.66.191 IP Address = 172.28.66.192
Socket Configuration Lists for EH1, EH2 & EH3
NODE IP CONFIG SEND/RECEIVE

EH1 172.28.66.191 RECEIVE
172.28.66.192 RECEIVE
multicast SEND
EH2 172.28.66.190 SEND

multicast RECEIVE
EH3 172.28.66.190 SEND

multicast RECEIVE
Figure 593. Example 1 - Point-to-Point Communication w/Multicast
782 3BUF001092R4001
Another application where point-to-point is used in combination with Multicast is

where one node is located in an area where the network hardware does not allow
Multicast. This is illustrated in Figure 594. EH1, EH2 and EH3 reside in an
OMF/TCP/IP domain defined by multicast communication. EH4 is isolated from
this domain by network hardware that does not support multicast. Therefore a
second domain is established for EH1 and EH4 for point-to-point communication.
In this case use the Communication Settings dialog to configure TCP/IP Multicast
enabled, Multicast address, and MulticastTTL for EH1, EH2, and EH3. This
procedure is described in Configuring OMF for TCP/IP on page 789.
The Socket Configuration Lists on EH1 and EH4 must be configured for point-to-
point communication. For EH4, because all OMF communication to this node
should be via point-to-point, Multicast should be disabled to prevent unwanted
OMF communication on the default Multicast address. Do this by deleting
Multicast from the Socket Configuration List. This is described in Configuring
OMF Socket Communication Parameters on page 792. For EH2 and EH3, leave the
Socket Configurations at the default values.
3BUF001092R4001 783
Domain 1 Domain 2
EH1 EH1 - EH4
EH1 - EH2 - EH3
IP Address = 172.28.66.190 Bridge Gateway w/
Multicast Disabled
TCP/IP Network
EH2 EH3 EH4

IP Address = 172.28.66.192
ABB Control System


NOTE: If you specify one TCP/IP address as
RECEIVE, all other addresses from which NODE IP CONFIG SEND/RECEIVE
you want to receive must also be specified as
EH1 multicast SEND/RECEIVE
receive. This includes all multicast senders.
172.28.66.193 RECEIVE
For example, the socket configuration list for 172.28.66.193 SEND
EH1 has a multicast SEND/RECEIVE 172.28.66.191 RECEIVE
specification, but must also include a 172.28.66.192 RECEIVE
RECEIVE specification for EH4 since EH4
cannot use multicast. Therefore EH1 must EH2 multicast SEND/RECEIVE
also have RECEIVE specifications for
all other nodes it is receiving from EH3 multicast SEND/RECEIVE
(EH2 and EH3).
EH4 172.28.66.190 RECEIVE
Figure 594. Example 2 - Point-to-Point Communication w/Multicast
784 3BUF001092R4001
OMF TCP/IP Domain with Point-to-Point Exclusively

This is required when your network hardware does not support, or is configured to
not allow Multicast communication. Exclusive point-to-point communication is
illustrated in Figure 595.
EH1, EH2 and EH3 reside in an OMF/TCP/IP domain defined by point-to-point
communication. In this case, use the Communication Settings dialog to configure
the Socket Configuration Lists in EH1, EH2, and EH3 for point-to-point
communication. This is described in Configuring OMF Socket Communication
Parameters on page 792.
All OMF communication to these nodes should be via point-to-point. Therefore,
Multicast should be disabled to prevent unwanted OMF communication on the
default Multicast addresses. Do this by deleting Multicast from the Socket
Configuration Lists on each node. This is described in Configuring OMF Socket
Communication Parameters on page 792.
3BUF001092R4001 785
Domain 1 EH1
EH1 - EH2 - EH3
IP Address = 172.28.66.190
TCP/IP Network
EH2 EH3

EH1 172.28.66.191 RECEIVE
172.28.66.191 SEND
172.28.66.192 RECEIVE
172.28.66.192 SEND
EH2 172.28.66.190 RECEIVE
172.28.66.190 SEND
172.28.66.192 RECEIVE
172.28.66.192 SEND
EH3 172.28.66.191 RECEIVE
172.28.66.191 SEND
172.28.66.190 RECEIVE
172.28.66.190 SEND
Figure 595. Example - Exclusive Point-to-point Communication
786 3BUF001092R4001
Appendix B Extending OMF Domain to TCP/IP Configuring TCP/IP Protocol
Configuring TCP/IP Protocol

TCP/IP protocol must be configured before you configure the Multicast address,
and enable the OMF TCP/IP socket. Typically, TCP/IP protocol is configured by a
network administrator. Consult your network administrator to obtain the proper
setting for the TCP/IP protocol, then check your TCPIP configuration for IP
Address, Subnet Mask, and Default Gateway.
The TCPIP configuration properties are accessible via the Network and Dialup
Connections Tool in the Windows Control Panel. The path is illustrated in
Figure 596.
Do not enable the TCP/IP socket unless you are using this
functionality. If the TCP/IP socket is enabled and the TCP/IP
connection is not operational, or a default gateway is not configured
for routing, OMF will not start.
From the Windows Control Panel:
1. Select Network and Dialup Connections.
2. In the network and Dialup Connections list, select Local Area Connection.
3. In the Local Area Connection Status dialog, click Properties.
4. In the LAN properties dialog, select Internet Protocol (TCPIP), then click
Properties. This displays the TCPIP properties dialog.
3BUF001092R4001 787
Configuring TCP/IP Protocol Appendix B Extending OMF Domain to TCP/IP
Figure 596. Accessing TCPIP Configuration
788 3BUF001092R4001
Appendix B Extending OMF Domain to TCP/IP Configuring OMF for TCP/IP
Configuring OMF for TCP/IP

The OMF parameters related to extending the OMF domain to TCP/IP are the
Multicast address and TTL. In addition, you MUST enable OMF on TCP/IP. This is
done via the Communication Settings dialog, Figure 597. To launch this tool, from
the Windows task bar, choose Start>Settings>Control Panel
Administrative Tools>PAS>Settings.
Figure 597. Communication Settings Dialog
Use the TCP/IP Configuration section to configure the required parameters and
enable OMF on TCP/IP. See Table 78 for details.
All processes under PAS supervision must be stopped and then

restarted for any changes to take affect. See Starting and Stopping
History on page 517.
3BUF001092R4001 789
Configuring OMF for TCP/IP Appendix B Extending OMF Domain to TCP/IP
Table 78. Communication Settings dialog
Field Description
TCP/IP Multicast You can enable or disable OMF for TCP/IP network via this check box
enabled (check indicates enabled). Do not enable this parameter, unless you
plan to use this functionality.
If you are using distributed History logs, you must check TCP/IP Multicast
enabled, and you must increase the OMF shared memory:
• for History nodes that send History data to a consolidation node, add
5 meg to the OMF shared memory requirement.
• for a consolidation node that collects from one or more History nodes,
add 5 meg to the OMF shared memory requirement for each node
from which it collects History data. For example, if a consolidation
node is receiving from eight History nodes, the consolidation node will
require 8*5 = 40 meg additional OMF shared memory.
Multicast address This is the Multicast address used by OMF (omfNetworkExt and
omfNameProc). To extend the OMF domain to TCP/IP, the Multicast
Address must be the same in all nodes on a network, otherwise the nodes
will not be able to see each other.
A valid multicast group address that enables routing of multicast
messages must be in the range: 224.0.0.2 to 239.225.225.225. The
default multicast address is 226.1.2.3. This is a valid multicast address
and can be used by OMF; however, it is recommended that this default
address NOT be used. Not using the default minimizes the possibility of
conflicts with other unknown nodes on the TCP/IP network with which you
do not wish to establish communication. You should contact your network
administrator to obtain an appropriate multicast address to ensure secure
communication between intended nodes.
790 3BUF001092R4001
Table 78. Communication Settings dialog
Field Description
MulticastTTL This is the time-to-live value which indicates the number of router hops to
do before a message is discarded (not sent any more). This prevents
endless message loops that may occur as a result of unexpected or
unusual network partitioning.
0 = multicast messages are not sent at all
1 = multicast messages are sent only on the local subnet
>1 = multicast messages are forwarded to one or more hops
To extend the OMF domain to TCP/IP, this must be set >= 1; otherwise,
nodes will not hear each other.
Socket The socket configuration specifies this node’s scope of OMF access to
Configuration List other nodes in the domain.
The default is Multicast Send Receive. This means this node can see
and be seen by all other nodes in its multicast domain.
You can restrict OMF access between certain nodes in a multicast domain
by configuring their respective socket configurations. For details on how to
do this, see Configuring OMF Socket Communication Parameters on page
792.
3BUF001092R4001 791
Configuring OMF Socket Communication Parameters

Within an OMF domain, nodes establish OMF access with each other by
periodically sending and receiving network maintenance messages that inform the
respective nodes of each other’s existence on the TCP/IP network. Each node must
be capable of both sending messages to, and receiving messages from any node with
which it wants to have OMF access. When the OMF communication socket is
enabled, these OMF network maintenance messages are sent/received by either
Multicast protocol (one message to many nodes), or point-to-point protocol (one
message from one node to another).
By default, all nodes in a Multicast domain have access to each other. You can
change OMF access between nodes, or change the communication protocol for
OMF maintenance messages in an OMF TCP/IP domain by configuring their
respective socket configurations. To do this, click the Modify List button below the
MulticastTTL field. This displays the Socket Configuration dialog, Figure 598.
Figure 598. Socket Configuration Dialog
The default setting is multicast Send Receive. This means this node can see
(receive the signal from) and be seen by (send the signal to) all other nodes in its
domain.
792 3BUF001092R4001
To change access within the domain, edit the socket configuration list for all nodes
in the domain. A summary of the possible entries is provided in Table 79
Table 79. Socket Configuration Options
multicast SEND This node can be seen by other nodes in the domain
that are configured to RECEIVE network maintenance
messages from this node. To do this, enter multicast
in the IPconfig field, click the Send check box, then
click Add.
multicast RECEIVE This node can see other nodes in the domain that are
configured to SEND network maintenance messages
to this node. To do this, enter multicast in the IPconfig
field, click the Receive check box, then click Add.
point-to-point SEND This node can only be seen by (send network
maintenance messages to) the node whose IP
address is specified. To do this, enter the node’s IP
address, click the Send check box, then click Add.
point-to-point RECEIVE This node can only see (receive network maintenance
messages from) the node whose IP address is
specified. To do this, enter the node’s IP address, click
the Receive check box, then click Add.
Example Changing the Socket Configuration

In Figure 599, EH1 must have OMF access to both EH2 and EH3, but at the same
time OMF access must be prohibited between EH2 and EH3. To implement OMF
access in this way, each node’s Socket Configuration List must be configured as
described in the table in Figure 599. How to do this is described in the procedure
following Figure 599.
3BUF001092R4001 793
Domain 1 Domain 2
EH1 EH1 - EH3
EH1 - EH2
IP Address = 172.28.66.190
TCP/IP Network
EH2 EH3


EH1 172.28.66.191 RECEIVE
172.28.66.192 RECEIVE
multicast SEND
EH2 172.28.66.190 SEND

multicast RECEIVE
EH3 172.28.66.190 SEND

multicast RECEIVE
Figure 599. Example - Changing the Socket Configuration
794 3BUF001092R4001
To edit the Socket Configuration List for EH1:

1. Modify the default entry. To do this:
a. Select the entry in the list. This puts the value for each of the configuration
parameters (IP config, Send, and Receive) in their respective fields.
b. Remove the check from the Receive box, Figure 600, then click Add.
Figure 600. Modifying the Default Entry
This changes the entry to multicast Send. EH1 can now be seen by other nodes in
the domain configured to receive from EH1; however, EH1 can only see nodes from
which it is specifically configured to Receive.
2. Add an entry for EH2 to specify it as a node from which EH1 can receive:
a. Enter the IP address for EH2, 172.28.66.191, in the IP config field.
b. Enter a check in the Receive check box, and make sure the Send box is
unchecked. This configuration is shown in Figure 601.
Figure 601. Adding an Entry for EH2
c. Click Add. This adds a new entry: 172.28.66.191 Receive.
3BUF001092R4001 795
3. Repeat step 2 for EH3, substituting the correct IP address (172.28.66.192) in

the IP config field. The finished configuration for EH1 is shown in Figure 602.
Figure 602. Socket Configuration for EH1
Repeat the above procedure to modify the socket configurations for EH2 and EH3.
Refer to Figure 599 for the respective socket configurations.
If you want to remove an entry from the Socket Configuration List,

select the entry then click Remove.
796 3BUF001092R4001
Appendix B Extending OMF Domain to TCP/IP OMF Shared Memory Size
OMF Shared Memory Size

The OMF shared memory size defines the size of shared memory for processes that
use the OMF software. If the shared memory is too small, processes may be aborted
without any error messages (PAS will discover that the process has been aborted).
The default size for OMF shared memory is 8,192 Kbytes (8 MBytes). Use the
Communications Settings dialog to adjust the size. To launch this tool, from the
Windows task bar, choose Start>Settings>Control Panel>
Administrative Tools>PASS>Settings.
The OMF Shared Memory section on this tool displays the current size of the OMF
shared memory in Megabytes. Enter a new value (in Mbytes) if necessary. (For
details regarding this dialog, see Configuring OMF for TCP/IP on page 789.)
If you are implementing distributed History logs (this requires you to check the
TCP/IP Enabled option in the Communication Settings dialog), you must increase
the OMF shared memory:
• for History nodes that send History data to a consolidation node, add 5 meg to
the OMF shared memory requirement.
• for a consolidation node that collects from History nodes, add 5 meg to the
OMF shared memory requirement for each node from which it collects data.
For example, if a consolidation node receives from eight History nodes, the
consolidation node will require 8*5 = 40 meg additional OMF shared memory.
If you change the OMF Shared Memory size and you want to set it back to the
default, click Set Default. When you are finished, click OK.
Processes under PAS must be stopped and restarted for changes to

take affect. See Starting and Stopping History on page 517.
Shutdown Delay
This delays the Windows shutdown to let PAS shut down processes for History
Services. The default is 20 seconds. You may need to increase the delay depending
on the size of your History database. Use the Communication Settings dialog. To
launch this tool, from the Windows task bar, choose Start>Settings>
Control Panel>Administrative Tools>PAS>Settings.
3BUF001092R4001 797
Shutdown Delay Appendix B Extending OMF Domain to TCP/IP
798 3BUF001092R4001
INDEX
A API 273
access name 267 Archive
Acrobat Reader Group 191, 211, 271
setup 770 archive 35, 383
active volume 397 CD ROM 398
add-ins 348 configure 35
ADO data provider for Oracle database 670 device 384, 392
ADSS 678, 694 DVD 398
AID-BROWSER-ROOTASTAB 760 group 384, 401
AID-BROWSER-SCROLLSPEED 760 guidelines 385 to 386
AID-BROWSER-SPRINGLOADDELAY 760 media 35, 383, 392
AID-EDITOR-COMMENTCOLOR 761 archive backup 398
AID-EDITOR-FONT 761 archive device attributes 395
AID-EDITOR-STRINGCOLOR 761 archive entry 384
AID-EDITOR-TEXTCOLOR 761 archive path 396
AID-EDITOR-WORDCOLOR 761 archived logs access 385
AID-PASSWORD 760 argument 709
AID-STARTUP-BASE_DISPLAY- Aspect 773
DISPLAY 760 Category 773
AID-STARTUP-BASE_DISPLAY-GROUP 760 Objects 773
AID-STARTUP-DISPLAY-DISPLAY 760 Server 774
AID-STARTUP-DISPLAY-GROUP 760 System 774
AID-VIEW-BROWSER 761 aspect system 44
AID-VIEW-DISPLAYBOARDERCOLOR 761 authentication 725
AID-VIEW-ELEMENTBAR 761 softponts 62
AID-VIEW-INACTIVEAREACOLOR 761 autologoff
AID-VIEW-OLDSTYLEFRAME 761 enable 762
AID-VIEW-STATUSBAR 761 interval 762
AID-VIEW-TOOLBAR 761 auto-publish 397
AID-VIEW-USERBAR 761 available licenses 724, 768
alarm acknowledge 67, 70
alarm configuration 67 B
alarm/event configuration 63 backup archive path 399
Alignment 192, 289 backup path 489
allocating disk space 228 backup type 399
3BUF001092R4001 799
Index
Bad Data Quality Limit 290 Cascade Attributes 567

blocking rate 281 clean history database 587
Browser_Separator 671 clear trace 120
build 724, 768 Client 774
bulk configuration 322 Collection Mode 272
bulk data export 574 collection mode 272
API 273
C OPC 273
calculation 260, 288 Collection Type 273
trace window 120 collection type 273
Calculation Algorithm 285 COM 774
calculation aspect 98 communication settings dialog 789
view 104 Compaction Ratio 294
calculation scheduler 123 COMPACTION_RATIO 547
Calculations 288, 301, 303 composite log name 267
calculations 97 Connectivity Server 774
adding a new calculation 103 controllable
aspect 102 binary 60
bulk changes 133 real and integer 61
cloning 133 cyclic schedule 124
configuring 102, 105
cycle base rate 101 D
cycle offset percentage 101 Data
editor 106 Collection 518
enable/disable 150 Entry 308
manual execution 125 data
on object types 131 archive 384
opc access 132 presentation 217
OPC base rate 101 purge 588
performance tracking 152 data access 673
phasing 101 Data Collection
script 110 Storing Calculated Values 301
service provider definition aspect 100 Storing Calculated Values with
Settings.UpdateStatus 111 Compaction 304
set-up 99 Storing instantaneous values using
status information 149 compaction 299
status viewer 147 Storing Instantaneous values, no
user interface 99 compaction 298
variable mapping 107 data collection
VBScript editor 110 event-driven 219, 252
800 3BUF001092R4001
Index
starting and stopping 518 event 109

data collection examples 297 event configuration 67
data provider 673 event text 78
adding 699 event-driven data collection 219, 252
adding a remote service 702
adding new 705 F
argument 709 file storage 307
deleting 721 file-based storage 559
name 676 free space report 543
starting/stopping 721
data quality 119 G
data service supervision 678 grade change 368
data source 270
data type 247
H
Database
Harmony Connectivity 671, 716
create 585
hierarchical log 215, 318
database
hierarchical log type 237
drop&create 585
History
Deadband 291
Manager
deadband compaction 291
Status 536
Deadband Storage Interval 294
history
Defragmenting 772
data type 247
device behavior 396
log template 214
device type 395
service provider 44
direct log 317
history log 34, 213, 215, 237
direct log type 214, 234
history manager
direction 109
list 536
disable 82
status 536
disappears with acknowledge 71
history software version 536
display server status 723, 766
history source aspect 220
Documentation, On-line 30
History Status 536
domain 779
HS_CONFIG 613
dual log 216, 250
HS_DATA 613
HS_HOME 613
E hsDBMaint 537
effective log period 293 hysteresis 66
entry tables report 545
environment variables 612
I
EST_LOG_TIME_PER 294, 547
Is an alarm 70
Estimated Period 295
Is an event 68
3BUF001092R4001 801
Index
ISO image 400 log period 279, 364

log set 35, 173
L assignment 318
lab data log 214, 251, 272 log set attributes 176
language 763 to 764 log set configuration 35, 173
language extensions 118 log template 214
last history value 762 Logs in Set 177
limiters 64
Log M
Access Name 191, 210 MDI 724, 768
activation/deactivation 518 memory resources 600
Attributes 262 message data access 181
Capacity 191, 211, 279, 284, 364 message log
Description 191, 210 consolidation 181
Log Set 192, 271 Microsoft Excel add-ins 348
Name 191, 210 MO drive 35, 383
Period 279, 364 modify log configuration 262, 317
Start-up State 192, 272 multicast 779
State 192 multicast address 790
log multicast TTL 791
activation 320, 519
data type 247 N
direct 214, 234 Name 265, 271
directories 559 new log template 263
hierarchical 215, 237 no acknowledge 71
history 34, 213, 215, 237 no data 351
lab data 251 NO_DATA 280
numeric 214 Node 775
property 34, 213 to 214 normal acknowledge 71
report 205
trend 34, 213 to 214, 234 O
log attributes Object Root 650
data collection 277 off-line execution 125
log capacity 279, 284, 364 offline value 109
log configuration aspect 214 OMF
Log Entry communication settings 789
Time Stamp 308 domain 779
Universal Time (UTC) 308 for TCP/IP 789
Value 309 omf
log name 271 shared memory size 735, 797
802 3BUF001092R4001
Index
on line value 109 S

On-line Documentation 30 sample blocking rate 281
on-line execution 125 Sample Interval 280
OPC 775 sample interval 280
OPC connection 593, 684 sample rate 608
Oracle database access 670 schedule
overwrite timeout 396 cyclic 124
time-based 124
P scheduling server service 44
PAS window 736 SDI 724, 768
password 755 Server 776
PDL archive 420 server configuration 100
PDL Archive Configuration Window 420 server status 722, 766
Plant Explore 775 service
Plant Explorer workplace 38 adding arguments 721
point-to-point communication 781 configuration file 708
process administration services 736 service group 44
Process Object 775 Service Provider 32, 37
Process Portal A 775 service provider 44, 673
profile logs 353 Set Name 177
activating 381 shadow copy 400
archiving 380 signal type
configuration 355 adding a new signal 53
data source 359 single magnetic/optical drive 35, 383
log set 355 socket configuration 791 to 792
property log 34, 213 softpoint
purge 588 adding a softpoint object type 51
adding signals 53
Q adjust properties 82
quality 119 adjusting alarm and event properties 77
alarm event configuration aspect 63
R alarm text groups 84
reel report configuration tool 368 alarm/event 64
reel turn-up 368 alarm/event settings aspect 84
report log 36, 205 authentication 62
Reset Object Status 565 bring on line 88
resource usage 603 character map 59
restored log access 385 configuration 49
result 113, 132 configuring signal properties 56
runtime history status 523 configuringobject types 53
3BUF001092R4001 803
Index
deleting a signal 55 System Extension 777

deleting an object type 56
deploy 88 T
disable signal 82 Tablespace
engineering unit 58 Inform_HS_Runtime 548
event text 79 TCP/IP
faceplates 91 OMF parameters 789
import/export 94 protocol 787
limiters 63 TCP/IP Multicast enabled 790
log operator actions 60 time drift 280
making a signal controllable 59 time-based schedule 124
name rules 90 tool bar 121
object dialog 91 translation 764
process object configuration aspect 53 trend log 34, 213 to 214, 234
runtime 91 troubleshooting 351
set-up 48
signal configuration aspect 56 U
signal range 58 update deadband ratio 546
softpoint object user
instantiate 72 adding a new application user 754
softpoint object type enterprise historian application users 753
adding a new object type 51 preferences 758
configuration aspect 53 user access 744
softpoints 47 user password 755
software version information 769 user preferences
stagger collection 568 Windows 2000 758
start state 272 USER_SUPPLIED 273
start-up 736
state 109
V
Storage Interval 281
variable 108
storage interval 281
Version 536
Storage Type 282
version 536
Storage type 307
View 777
ORACLE 307
volume 397
TYPE1 307
volume name counter 397
TYPE2 307
volume name format 397
storage type 307
volume quota 397
store as is calculation 218, 242, 285 to 286
Structure 776
synchronous data collection 214 W
system administration 734 Windows settings for Acrobat Reader 766
Workplace 777
804 3BUF001092R4001
3BUF001092R4001. Printed in Sweden October 2004
Copyright © 2003-2004 by ABB. All Rights Reserved
® Registered Trademark of ABB.
™ Trademark of ABB.
http://www.abb.com
Automation Technology Products Automation Technology Products Automation Technology Products

Wickliffe, Ohio, USA Västerås, Sweden Mannheim, Germany
www.abb.com/controlsystems www.abb.com/controlsystems www.abb.de/controlsystems

Industrial IT, 800xa - Information Management, Configuration - 05

Uploaded by

Copyright:

Available Formats

Industrial IT, 800xa - Information Management, Configuration - 05

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Industrial IT, 800xa - Information Management, Configuration - 05

Uploaded by

Copyright:

Available Formats

Editing Data Provider Configuration Files Section 15 Configuring Data Providers

Table 61. Arguments Common to All Data Providers

Table 62. ADSspCOM.EXE Arguments

Table 63. ADSdpDDR.EXE Arguments

Table 64. ADSdpADO.EXE Arguments

Table 64. ADSdpADO.EXE Arguments

Table 65. ADSdpOPCHDA.EXE Arguments

Table 66. ADSdpDCS.EXE Arguments

Table 67. ADSdpLOG.EXE Arguments

Table 68. ADSdpOPC.EXE Arguments

ADO Data Provider for Oracle Access

Table 69. ADO Data Provider Set-up for Oracle Access

-dbname matches ODBC Data Source Name

Figure 550. Detailed View of ADO Arguments

Starting and Stopping Providers

Deleting a Data Provider

The data provider will be deleted immediately (after the specified

Adding Arguments to a Data Provider

Figure 551. Example Add Arguments Dialog

Checking Display Server Status

Figure 552. Checking Server Status

Figure 553. Specifying Server Hostname

Leaving the hostname blank defaults to localhost.

This displays the server status window, Figure 554.

Number of Client Licenses

Number of Data Providers

Number & List of Connected Clients

Figure 554. Display Server:COMM Window

Licenses These fields show the total number of purchased licenses,

You can configure authentication for certain operations related to Information

The standard authentication mechanism used by other 800xA system functions is

Single Authentication Dialog

Double Authentication Dialog

Figure 555. Authentication Dialogs

1) Display Inform IT Authentication Category Aspect for an Aspect Category

Figure 556. Configuring Authentication

Figure 557. Adding an Operation

Table 70. Operations for which Authentication may be Configured

Aspect System Aspect Category Operations

Table 70. Operations for which Authentication may be Configured

Aspect System Aspect Category Operations

Table 70. Operations for which Authentication may be Configured

Aspect System Aspect Category Operations

Configuring Authentication for Aspects Related to Softpoint Configuration

Authentication for runtime operations for softpoint signals is configured as

To configure authentication for one or more of the above aspect types:

Figure 558. Setting Advanced Access Control to True

2. Then (reference Figure 559):

Figure 559. Configuring Authentication

This section describes administrative procedures for Information Management

Figure 560. Accessing Information Management System Administration Functions

Figure 561. Accessing the Information Management Administrative Tools

To use these system administration functions you must have

The following is a brief description of these administrative procedures.

Start Up, Shutdown and Supervision of ABB Software Processes

Configuring OMF Shared Memory

Supervising Display Server Status

Software Version Information

Disk Maintenance - Defragmenting