Installing the Agentry Server for Windows

Prerequisites
Address the following items prior to performing this procedure:
  • Included in the SAP Mobile SDK 2.3 bundle is a text file named DeveloperLicense_ReadMe.txt containing a limited user license. This license information is needed for this installation process.
  • Verify you have the proper installer for your target host system. There are two separate installers for the Agentry Server for Windows, which can be found in the SAP Mobile SDK 2.3 package:
    • Agentry_6.1.0.x_Server_win32.exe - For 32-bit builds of Windows
    • Agentry_6.1.0.x_Server_x64.exe - For 64-bit builds of Windows
  • Establish connectivity between the host for the Agentry Server and the back end system or systems with which it is to connect. This includes network access, ODBC System DSNs, Oracle TNS names, account access for file system access, and any other system connectivity items related to any back end system to which the Server will connect.
  • Record any connectivity information needed by the Agentry Server to connect to the back end system or systems. This can include user ID and password information, network addresses, network names or IP addresses, and port numbers or names.
  • Place additional code libraries, Java resources, or similar items on the host and note their locations. These items are needed during the configuration of the Agentry Server.
  • Determine if the Production Server, Development Server, or both are to be installed to the host system. This is necessary information required by the installer.
Task

This procedure describes the steps to install the Agentry Server as provided in the SAP Mobile SDK 2.3 to a Windows host system. The installation wizard will prompt for information including licensing keys, the location to install the Agentry Server instance(s), and any desired shortcuts to the executable. The same installer can be used to install the Agentry Production Server, Agentry Development Server, or both. If both are selected, two separate instances of the Agentry Server will be installed.

Once the installation process is complete, there are several configuration tasks to accomplish specific to the implementation environment and mobile application needs. These are addressed separately from this installation procedure.

This server instance should never be installed to the same location as the SAP Mobile Platform. The purpose of the Agentry Server installer provided in the SAP Mobile SDK is to allow for development of mobile applications on Agentry without the need to install all of the SAP Mobile Platform components.

  1. Launch the installer executable matching the needs of the host system; i.e. either the 32-bit or 64-bit Agentry Server installer.

    The Welcome screen displays.



  2. Click [Next] to begin the Agentry Server installation.

    The License Agreement screen displays.



  3. Review the license agreement text and click [Yes] to continue.

    The Customer Information window displays.



  4. Enter the User Name of the administrator for the Agentry Server and the Company Name in the appropriate fields. In the Serial Number field, enter the serial number found in the license text file DeveloperLicense_ReadMe.txt provided with the SAP Mobile SDK 2.3. You will not be able to proceed until a valid serial number has been entered. Click [Next] to continue.

    The Enter Product Keys window displays.



  5. Enter the User key, Device key, and Expiration keys list in the license text file DeveloperLicense_ReadMe.txt provided in the SAP Mobile SDK 2.3. Click [Next] to continue.

    The Choose Server Type window displays.



  6. Select the type of Server(s) to install. Select Production Server if it will be necessary to perform a production publish for the purposes of migration or upgrade. Otherwise, select Development Server for development work. Development is the more common selection and must be selected for development work, as a server configured for production should not be used for development publishes. If both are selected, two separate Agentry Servers will be installed in different locations. Click [Next >] to continue.

    The Choose Install Location window displays.



  7. Specify the destination folder for the Agentry Server. To change the default folder, click [Browse] and navigate to the desired folder. Click [Next] to continue. At this point if both a product and development Server were selected for installation, the destination screen is displayed again. Select the destination for the development Server and click [Next] to continue.

    The Shortcuts for [Production or Development] Server window displays.

  8. You are prompted to add shortcuts to various locations of the Windows desktop. Make the desired selections and then click [Next] to continue.
    Note: This step and the previous step are repeated if you opted to install both a production and a development Server. Repeat these steps as necessary.

    The Choose Start Menu Folder window displays.



  9. If you selected to create a shortcut in the Windows Start Menu, you are prompted for a folder where the shortcuts will be placed. You can select an existing folder or create a new one by entering the folder name in the field provided. If you did not select to create a shortcut in the Windows Start Menu, the previous screen is not displayed and the installation will begin. Otherwise, click [Install] to start the Server installation.

    The Installation wizard installs the Agentry Server.



  10. Click the [Finish] to complete the installation.

  11. Depending on the security settings of the system to which the Server is installed, it may be necessary to modify how the Server and some of its related components are run; specifically they may need to be run with Administrator privileges. The following should be modified to run as an administrator if issues are encountered at startup:
    • AgentryGUI.exe
    • AgentryServer.exe
    • AgentryCmd.exe

The Agentry Server is installed with the options selected within the installer. The installation may include one or two instances of the Agentry Server configured for production and/or development use. Additionally, certain command line utilities are installed into the Agentry Server’s installation directory, as well as the Agentry Administration Client.

Next
Once the Agentry Server has been installed, address the following items:
  • Configure the Agentry Server’s connection options related to the back end systems with which it is to connect. These should match the system connections defined in the Agentry application project and can be created during a publish from the Agentry Editor.
  • Configure the Client-Server connectivity options based on the specific needs of the implementation environment.