Configure the Agentry
Server to
connect to the host system.
Prerequisites
Before executing this procedure, the following
items and information should be addressed:
- Obtain and
record the numeric identifier for the File System connection definition
from the Agentry
Editor.
- Determine whether or not users will be authenticated during
synchronization by logging them into the host system.
- Obtain and record the Windows User Domain for user authentication.
- Determine the desired location for the Agentry
Server to
store temporary script files for execution. The default location
is the Windows TEMP folder as configured for the system.
- Determine whether or not the previous user should be connected
to the Windows system when a user change occurs on the Clients.
It may be desirable to omit this portion of synchronization for the
sake of expediency when file transfer functionality is in use.
Task
This procedure provides a typical implementation example. Certain settings within the
[File-n] section may be modified in relation to
implementation-specific behaviors or needs.
- This process begins by publishing the application
project from the Agentry
Editor to
the Agentry
Server.
This will create the section [File-n] for the File
system connection. It will also automatically add the proper option
to the [System Connections] section.
- Start the SAP
Control Center.
Connect to the system where the SAP Mobile Platform with the running Agentry
Server is
installed.
- In the navigation pane of SAP
Control Center,
expand the Applications node and select the Agentry application.
- In the administration pane, click the Configurations
tab.
- Select the section File-n, where n corresponds
to the system connection definition in the Agentry application project.
Click the Properties button above the list of configuration sections.
This displays a list of the settings for the system
connection to a database.
- Edit the settings on this screen to allow the Agentry
Server to
connect to host’s file system.
In this list many of the settings are set as shown
in most cases, regardless of the implementation environment. The
following lists those settings that are set specific to the environment,
along with a description of their values:
- enableAuthentication:
This setting controls whether or not users are authenticated with the
Windows system upon which the Agentry
Server is
running. When set to true, the user ID and password
from the Client will be used to attempt to authenticate the user,
meaning all users must have an account on the Server’s host system.
- userDomain: This setting contains the name
of the domain to which users belong. If the enableAuthentication option
is set to true, the value in userDomain determines
which domain users are authenticated with. If userDomain is
left set to an empty string, or is not present, the Agentry
Server will
attempt to determine which domain to use. It is recommended that
this option be set to the proper domain, rather than being left
blank.
- tempPath: This configuration setting is optional
and may be set to any valid path on the host system of the Agentry
Server.
When set to a valid path, any temporary batch files generated by
the Agentry
Server to
be executed as a part of Client-Server synchronization will be stored in
and executed from this location. If this setting is left blank or
omitted the TEMP folder of the host system will be used.
- allowPreviousUserLogin: This setting controls
whether the previous user is logged into this system connection
when a user change occurs on the Client. When this is false, the previous
user will not be logged into the file system, and any Step definitions
for this system connection within the application are not executed.
- Unlike other system connection types, there can be only
one File System connection type defined for an application.
When this procedure is complete the Agentry
Server will
be configured to connect to its host system. This connection allows
the Server to execute commands, read in file data, and transfer
files as defined by an application. This can be down for both upstream
and downstream synchronization.
Next
Once this procedure is complete the following items
may be necessary:
- If any additional system connections of
a different type are required by the application they should be
configured before starting the Agentry
Server.
- A basic connectivity test can be performed by starting the Agentry
Server and
verifying it is able to connect to the host operating system.