Technical data

17 Managing JMS
17-4 Administration Guide
Starting the Default WebLogic Server
The default role for a WebLogic Server is the Administration Server. If a domain
consists of only one WebLogic Server, that server is the Administration Server. If a
domain consists of multiple WebLogic Servers, you must start the Administration
Server first, and then you start the Managed Servers.
For complete information about starting the Administration Server, see “Starting and
Stopping WebLogic Servers” on page 2-1.
Starting the Administration Console
The Administration Console is the Web-based administrator front-end (administrator
client interface) to WebLogic Server. You must start the server before you can access
the Administration Console for a server.
For complete details about using the Administration Console to configure a WebLogic
Server, see “Administration Console” on page 1-4.
Configuring a Basic JMS Implementation
This section describes how to configure a basic JMS implementation using the
Administration Console.
1. Under the Services node in the left pane, click the JMS node to expand the list.
2. Optionally, create a File Store for storing persistent messages in a flat file, and/or
a Paging Store for swapping messages out to memory:
a. Click the Stores node in the left pane, and then click the Configure a new
JMSFile Store link in the right pane.
b. On the General tab, give the store a name, specify a directory, and then click the
Create button.
c. Repeat these steps to create a Paging Store.
Note: For more information on configuring stores, see “Configuring Stores” on
page 17-12.
3. Optionally, create a JDBC Store for storing persistent messages in a database:
a. Click the JDBC node in the left pane to expand it.