OpenEdge Management and OpenEdge Explorer: Configuration

4. Type the name of the new AppServer in the field provided.
AppServer configuration and administration
Note: The AppServer name is case sensitive and can include any character except a
period (.) or square brackets ([ ]). The name must be unique among all configured
AppServer names.
5. Click Save. The AppServer Configuration page appears, allowing you to configure the
AppServer’s properties.
Each new AppServer instance you create uses the default configuration. However, the port
number must be unique for each AppServer instance in order for the instance to operate
properly. Once you create a new instance, you are prompted to change the port number.
Starting and stopping an AppServer
From the management console, you can start either a local or a remote AppServer. You must
first connect to the AdminServer that manages the AppServer you want to start.
You can also choose to start an AppServer automatically when the AdminServer starts.
Note: Prior to starting an AppServer using SonicMQ ServerConnect, you must first
configure the AppServer as SonicMQ ServerConnect enabled.
To start an AppServer:
1. Click Resources in the management console menu bar. The main resource types appear in
the list frame.
2. In the list frame, browse to and click the AppServer instance you want to start. The Details
page for that instance appears in the detail frame.
3. Click Broker Control. The instance’s Control page appears.
4. Click Start AppServer.
Starting an AppServer automatically
You can set an AppServer to start automatically when the AdminServer starts.
To start an AppServer automatically:
1. Click Resources in the management console menu bar. The main resource types appear in
the list frame.
2. In the list frame, browse to and click the AppServer instance you want to start
automatically. The Details page for that instance appears in the detail frame.
3. Click Configuration. The AppServer Configuration page appears.
5–25