Opening the Applications Manager Client and Logging In

You must download the 
Applications Manager
 client from the URL 
 set during the installation
 
 your 
Applications Manager
 sent you
 . Before logging in the first time, you need to configure the client for the Automation Engine(s) you will be logging into. Once configured, you open an executable 
.jar
 file. To log into the client, you must enter your User name, password, and select an Automation Engine.
Downloading and Opening the 
Applications Manager
 Client
To download and open the 
Applications Manager
 client:
  1. Open your browser and enter the URL 
     set during the installation
     
     your 
    Applications Manager
     sent you
    . The screen shown below is displayed.
    The default format for the URL is 
    http://<Automation Engine IP address>:<Web Server port number>/<Automation Engine name>/Intro.html
    For example, if the Automation Engine IP address is 200.2.2.123, the port number is 5050, and the Automation Engine name is PROD1, the URL would look like the following:
    http://200.2.2.123:5050/PROD1/Intro.html
      
    The 
    Applications Manager
     client requires a supported version of the Java Runtime Environment (JRE). For a list of compatible Java versions, click the 
    Compatibility Matrix
     link.
  2. From this page, click the 
    Download the Applications Manager Client
     link.
    This downloads the 
    Client.zip
     file. 
  3. Create a directory on your local PC for the client, for example, 
    C:\AM_Client
    .
  4. Move the 
    Client.zip
     file to the directory you created and unzip the contents in that location.
  5. Copy 
    connections.properties.template
     to 
    connections.properties
    .
  6. Edit 
    connections.properties
    . Replace 
    {MASTER}
     with the name of your Applications Manager Automation Engine and 
    {URL}
     with the URL to your Applications Manager Automation Engine, such as, 
    http://127.0.0.1:5050/AMPROD
    .
    For example, you might replace...
    {MASTER}={URL}
    With...
    AMPROD=http://127.0.0.1:5050/AMPROD
    To add connection information for additional clients, simply add additional lines in the same format. 
  7. Copy 
    client.properties.template
     to 
    client.properties
    .
  8. Optionally, edit 
    client.properties
     to set client properties.
    Text from a sample 
    client.properties
     file is shown below. 
    #localOptions=true #debug=true #logDir=log #JAVA_HOME=C:/Program Files/Java/jdk-11 runOptions=-Xmx256m
    The 
    client.properties
     file includes the following settings: 
    • localOptions:
       When set to 
      true
      Applications Manager
       uses a local 
      Options.properties
       file on your PC. The local 
      Options.properties
       file will be in a sub-directory for the client with the master's name. The local 
      Options.properties
       file will be download once. The advantage of using a local 
      Options.properties
       file is that you can specify settings for yourself without affecting other users. When set to 
      false
      , commented out (default), or otherwise not set to 
      true
      , the 
      Options.properties
       file on the Automation Engine machine is used.
    • debug:
       Allows you to turn on client debug by entering 
      debug=true
      . When client debug is set, debug information is written to the files in the log sub-directory or a different sub-directory is one is specified under 
      logDir
      .
      To turn debug off, comment out 
      debug=true
       in the 
      client.properties
       file like the following. 
      #debug=true
      It is also possible to set client debug from the 
      About Applications Manager
       window once you are logged into the client. However, it is advantageous to set it here, so that debug is on for the client start-up.
    • logDir:
       Allows you to override the name of the sub-directory where client log files are written.
      The client 
      log
       sub-directory includes the following files: 
      • client.log:
         Includes all client standard and debug logging up until you click 
        OK
         on the 
        Logon
         window.
      • <master or connection name>_client.log:
         Includes all client standard and debug logging for your client session. 
    • JAVA_HOME:
       Allows you to use a different Java than your PC's default Java.
      You must use either forward slashes (recommenced) or double backslashes in the path. This is the standard for Java properties files. 
      To see your PC's default Java, open a command prompt and type 
      java -version
      .
    • runOptions:
       Used to increase the memory for your client. Don't make any changes to this setting unless directed to by 
      Applications Manager
       support.
    • TheuserLanguageFiles:
       This setting is hidden in the 
      client.properties
       file and in the documentation by default. It allows you to specify a master name to use language translations on. When a master is specified, there will be a drop-down with the languages, which are specified in the 
      Options.properties
       file for the master. We believe no one uses this desupported feature anymore.
  9. Use 
    RunClient.jar
     to start the Applications Manager client.
    Applications Manager
     displays the 
    Login
     window shown below.
      
    Optionally, you may create a shortcut of 
    RunClient.jar
     and place the shortcut on your desktop.
    If the 
    Logon
     window does not come up, open command window, navigate to the client directory, and enter 
    java -jar RunClient.jar
     to see the output. This information will help you or 
    Applications Manager
     support troubleshoot the problem.
    When starting the local client by double clicking on 
    RunClient.jar
     (or a shortcut to it) in version 9.3.1 or above, if it fails to start the error will now be in the 
    startClient.log
     file.
  10. On the 
    Logon
     window, specify your User, password, automation engine.
    User names are not case sensitive, but passwords are.
    If you do not know your User name and password, check with your 
    Applications Manager
     administrator.
  11. If the 
    Language
     field is available, select your language.
    Specifying languages for the client is a desupported feature. The 
    Language
     field is only available in 
    Applications Manager
     systems where languages were translated in a previous version.
  12. On the 
    Logon
     window, specify the following:
    • The default user name SQLOPER.
    • The default password is s0pass, where "0" is zero.
  13. To have 
    Applications Manager
     remember your User name and Automation Engine, select the 
    Remember logon
     button.
  14. To accept the entered information and log on to 
    Applications Manager
    , click 
    OK
    .
    If you have a large number of output files or tasks in the Backlog, 
    Applications Manager
     will display a message alerting you that the display has been truncated.
    When you log out of 
    Applications Manager
    , the following settings are remembered the next time you log back in:
    • The size and position of 
      Explorer
       and 
      Backlog Gantt View
       windows.
    • The size and position of the main 
      Applications Manager
       client window.
    • The content pane of the 
      Explorer
       window (if open).
    • Whether a saved Backlog/History Filter was selected.
Upgrading the Client
To upgrade to a new version of the client: 
  1. Download the new version of the client 
    Client.zip
     from the URL
     set during the installation
     your 
    Applications Manager
     sent you
    .
  2. Delete everything except the 
    connections.properties
     and 
    client.properties
     files from your client directory.
  3. Put the files from the new version of the 
    Client.zip
     file into your client directory.
Receiving RmiServer Error Broadcasts
If the 
Receive RmiServer Error Broadcasts
 User Option is assigned to your User, the 
RmiServer Errors
 window might pop up with one or more errors when you log in.
  
When the 
Receive RmiServer Error Broadcasts
 User Option is assigned to a User, any RMI errors will be displayed in a pop-up window as they occur. Additionally, if any RMI errors occurred since the last time the RMI server was started, the last ten errors will be displayed in a pop-up window each time the User logs on.
If you have the DBA User Group, you can clear the RMI errors without stopping the RMI server by selecting 
Clear RMI Errors
 from the 
View
 menu on the 
Applications Manager
 Desktop.
Re-Logging on to 
Applications Manager
There may be times when you want to log on to 
Applications Manager
 under a different user name or connect to a different Automation Engine. To change your logon from the desktop, go to the 
File
 menu and select 
Re-Login
. You will have to re-enter your password when you re-log in, unless the 
Disable clearing of login passwords on re-login
 Automation Engine option is checked.
Changing Your Password
You can change your password at any time. Your 
Applications Manager
 administrator can also set your password to expire after a certain period of time.
To change your 
Applications Manager
 password go to the 
Options
 menu on the 
Applications Manager
 desktop and click 
Change Password
.
Accessing the Client Through a Firewall
If you will be accessing the 
Applications Manager
 client through a corporate firewall, you must open the appropriate ports, and specify those ports in the 
Options.properties
 file on the host machine.
For details, see the 
Installation Guide
.