Consider the following factors before you set up OpenEdge Management for the first time:

  • Determine the names and locations of the resources that you need to monitor and the properties you want to configure. You can configure properties for resources associated with local and remote AdminServers. With OpenEdge Management, you can also monitor certain resources running under a local or remote AdminServer.
  • Determine whether to save monitoring information to the OpenEdge Management Trend Database and, if saving the monitoring information, decide where to locate the database.

    The OpenEdge Management Trend Database stores the monitoring information that OpenEdge Management collects for databases, system resources, file resource, network resources, and the application server. During configuration, you can choose whether to save monitoring information locally or not at all. Before installation, you should decide if you want to save this data and where you want to save it.

    OpenEdge Management automatically creates the OpenEdge Management Trend Database if you have an OpenEdge Enterprise RDBMS, an OpenEdge Workgroup RDBMS, or an OpenEdge Personal database installed on the same machine where you are installing OpenEdge Management.

  • Determine how monitoring might affect system performance.

    The more resources you monitor, the more system resources OpenEdge Management uses. If you plan to monitor a large number of database servers and network services in your configuration, you might want to consider configuring additional OpenEdge Management instances, both locally and remotely.

    See OpenEdge Management CPU and memory requirements for more information.

  • Your resources can be administered by OpenEdge Management and command-line utilities, such as dbman or asbman. Therefore, you should be familiar with the AdminServer functionality.

    You can access online help while working in the management console. For details about the dbman or asbman utility, see Manage the OpenEdge Database.

  • Start the AdminServer to access your resources. You can start or stop the AdminServer using the following commands:
    proadsv -start
    proadsv -stop
    In Windows, AdminServer is registered as a Windows service. You can start or stop the  Progress OpenEdge AdminServer Service service from the Windows Services utility.
  • Start the OpenEdge Management. You can start and stop using the following commands:
    fathom -start
    fathom -stop
    In Windows, OpenEdge Management is registered as a Windows service. You can start or stop the  Progress OpenEdge Management Service for OpenEdge service from the Windows Services utility.

    To access OpenEdge Management from a browser, select Start > Programs (or All Programs) > Progress > OpenEdge > Management Console.

    The initial user name and password are admin/admin.

    For details about using command-line options with OpenEdge Management, see Use the command-line interface.