The communications between the
Agentry
Server and
the back end system are represented within the application by the
system connection definition type. Within the
Agentry.ini configuration
file for the
Agentry
Server,
each system connection has a corresponding section. Within this
section are the configuration options specific to the type of back-end
system. The settings for these options are then dependent on the
specific system to which the Server will connect. The four types
of sections within the file are:
- [SQL-n] -
For SQL database system connections (Both MS SQL Server and Oracle)
- [Java-n] - For Java Virtual Machine system
connections
- [HTTPXML-n] - For HTTP-XML Server (a.k.a. Web
Service) system connections
- [File-n] - For connections to the operating
system upon which the Server is installed
Another section controlling these communications is
[System
Connections]. Listed in this section needs to be one entry
for each back end system with which the
Agentry
Server will
connect. The specific entry within this section for a system connection
consists of the system connection definition’s ID (assigned automatically
and displayed in the
Agentry
Editor)
and the data link library, or DLL file for that system connection
type. This will be one of the following values:
- ag3sqlbe.dll -
For SQL database system connections
- ag3javabe.dll - For Java Virtual Machine system
connections
- ag3httpxmlbe.dll - For HTTP-XML Server system
connections
- ag3filebe.dll - For connections to the Windows
system upon which the Server is installed.
Tying each of these three components for a system connection
together is the unique numeric identifier generated by the Agentry
Editor for
the system connection definition. The definition itself is referenced internally
by this identifier at run-time. The entries in the [System
Connections] section are also identified by this value,
as in 1=ag3sqlbe.dll. Finally, the names of the
configuration sections for a system connection within the Agentry.ini file
also include this identifier, as in [SQL-1]. The
numeric value 1 in each of the preceding examples
must also be the same numeric identifier for the SQL Database system
connection in the Editor.
By default the
Agentry.ini file for a newly
installed
Agentry
Server contains
no settings for a system connection. The
[System Connections] section
exists but is empty. The connection-specific sections (
[SQL-1],
[Java-2],
etc.) are not included in the default
Agentry.ini file.
These sections and their configuration options must be added to
the file as a part of the configuration process. To set these configuration
options the
Agentry
Editor and
the
SAP
Control Center are
used. The overall process is as follows:
- After the application
project is in a state suitable for publishing, perform a publish
from the Agentry
Editor.
The Agentry
Editor will
prompt to create the necessary configuration sections in the Agentry.ini file.
This will be those related to all system connections defined in
the application project. The sections will be created with initial
settings likely in need of further modification after the publish
is complete.
- After the initial publish, the SAP
Control Center is
used to set the final settings for each system connection, as well
as the client-server communications. This includes changes to the
sections for each system connection and the ANGEL (Agentry Next
Generation Encryption Layer) settings, that dictate the behavior
of the Client-Server communications.
- Setting the options related to log files and log message categories
is also performed using the SAP
Control Center.
The specifics of these settings will depend on the type of Agentry
Server, Development
or Production, being configured and the overall log needs of the
system. Many of these log categories are related to the Agentry
Server-back
end communications, as well as other log messages.