8 Operational Boundaries

This chapter describes the DIVArchive 7.5 operational boundaries and includes the following information:

Number of Manager Connections

The number of connections to the DIVArchive Manager is limited by the Manager and set in the Manager configuration file. The default configuration limit is two hundred. This boundary includes connections to GUIs, Actors and all API clients. When the configured limit is reached, the API will not create additional connections.

See the manager.conf file for more information.

Number of Simultaneous Manager Requests

The maximum number of simultaneous requests processed by the Manager is configurable in the manager.conf file as the value of the DIVAMANAGER_MAX_SIMULTANEOUS_REQUESTS parameter. The default value has been raised from two hundred to five hundred in DIVArchive 7.5. The maximum number has been verified up to two thousand. Additional simultaneous requests beyond the value set in this parameter are rejected by the Manager.

Number of API Tasks

The number of API tasks that will be accepted to the API Processing Queue is configurable in the manager.conf file as the value of the DIVAMANAGER_API_TASK_QUEUE_SIZE parameter. The default value is two thousand and DIVArchive 7.5 has been verified at this value. If the queue is full subsequent commands are rejected.

Recommended API Connection Use

Oracle recommends that a new connection between the Manager and an API client not be created for each request or command sent to the Manager. Whenever possible, let the connection remain open for the lifetime of the session or application.

Special Authorized Characters

Many requests require alpha numeric text parameters. Special characters can be used in these fields as defined in the following table. The request is rejected if an invalid special character is used. In a Windows environment, file and folder names cannot consist of one or more spaces, and cannot contain a double-quotation mark.

Table 8-1 Special Authorized Characters in DIVArchive

Field (across)Character (down) Name Category Source Media Path File Comments Options

~

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

'

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

!

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

@

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

#

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

$

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

%

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

^

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

&

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

*

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

(

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

_

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

-

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

+

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

=

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

|

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

\

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

}

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

]

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

{

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

[

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

:

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

;

Yes

Yes

Yes

Yes

YesFoot 1 

Yes

Yes

Yes

"

Yes

Yes

Yes

Yes

No

Yes

Yes

No

'

Yes

Yes

No

No

YesFootref 1

Yes

Yes

Yes

<

Yes

Yes

Yes

Yes

No

Yes

Yes

No

,

Yes

Yes

Yes

Yes

YesFootref 1

Yes

Yes

Yes

>

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

.

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

?

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

/

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

Space

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes


Footnote 1 Depends on file system restrictions.

Maximum Number of Allowed Characters

The maximum number of characters that can be used for request parameters is displayed in the following list. If these limits are exceeded, the request will be rejected.

Name

Maximum of 192 characters.

Category

Maximum of 96 characters.

Source

Maximum of 96 characters.

Media

Maximum of 96 characters.

Path and File Name

Maximum of 1536 characters.

Comments

Maximum of 4000 characters.

Options

Maximum of 768 characters.

File Path Limitations

DIVArchive 7.5 supports absolute path names on both Windows and Linux up to a maximum of four thousand characters. Relative path names are limited to two hundred fifty-six characters on Windows systems (only).

A DIVArchive Windows local path is structured in the following order and terminated with a NUL character:

Drive_Letter:\Component_Name\Component_Name\File_Name.Extension

A DIVArchive Linux local path is structured in the following order:

/Component_Name/Component_Name/File_Name.Extension

The following are several example paths used in DIVArchive - Windows first and then Linux. The <NUL> character used in the example represents the invisible terminating null character for the current system code page and need not be typed in. The < and > characters are used in the examples for clarity only and must not be part of a valid path string.

Generic Path:

D:\Some_256-Character_Path_String<NUL>

/Some_4000-Character_Path_String

Actor Executable:

D:\diva\diva\Program\Actor\bin\DIVArchive.exe

/home/diva/diva/std_linux

Manager Configuration:

D:\diva\74\Program\conf\manager\manager.conf

/home/diva/DIVA/Program/conf/manager/manager.conf