1. Administering Oracle WebLogic Server with Fusion Middleware Control
  2. WebLogic Servers

3 WebLogic Servers

This chapter describes the tasks you can perform to monitor, control and configure server instances. A server is an instance of WebLogic Server that runs in its own Java Virtual Machine (JVM) and has its own configuration.

When you create a domain, you also create an Administration Server, which distributes configuration changes to other servers in the domain. In a typical production environment, you create one or more Managed Servers in the domain to host business applications and use the Administration Server only to configure and monitor the Managed Servers.

Note:

If you are logged into a domain partition, navigate from the Domain Partition menu. Note that WebLogic Server Multitenant domain partitions, resource groups, resource group templates, and virtual targets are deprecated in WebLogic Server 12.2.1.4.0 and will be removed in the next release.

This chapter includes the following sections:

Create servers

To create a new server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.

    The Servers table displays information about the Administration Server and any Managed Servers that have been configured in the current domain.

    Note:

    You can also access this detailed monitoring page directly from the Target Navigation pane:

    • From the Target Navigation pane, expand the farm, then expand WebLogic Domain.

    • Expand the domain, then select the name of the server instance for which you want to view detailed monitoring information.

  2. Click Create.
  3. Define the configuration options for your server on each of the following pages:
  4. Click Create.

Server Properties

On the Server Properties page, you can define general configuration settings for your new server instance:

  • Name: enter the desired name for your new server instance.

  • Server Listen Address: if you want to limit the valid addresses for a server instance, enter an IP address or DNS name. Otherwise, URLs to the server can specify any of the host computer's IP address, any DNS name that maps to one of the IP addresses, or the localhost string.

  • Server Listen Port: enter the port number from which you want to access the server instance.

  • Cluster Membership: specify whether or not this server will be a stand alone server or will belong to a cluster. If this server is not part of a cluster, then select No, this is a stand-alone server.

    If this server is part of a cluster, then select Yes, make this server a member of an existing cluster. Select the desired cluster from the Select a cluster menu or click Create a new cluster. For more information on creating a new cluster, see Create clusters.

For more information about these fields, see Configuration Options.

Machine Binding

On the Machine Binding page, you can optionally select a machine to associate your new server with. Use the Select a machine menu or click Create a machine. For more information on creating machines, see Create machines.

For more information about this field, see Configuration Options.

Review

On the Review page, review the configuration for this server instance.

For more information about these fields, see Configuration Options.

Monitor servers

This section describes how to monitor server instances. This section includes the following tasks:

Monitor status of all server instances

To monitor the runtime status of all server instances in a domain:

  1. From the WebLogic Domain menu, select Environment, then select Servers.

    The Servers table displays information about the Administration Server and any Managed Servers that have been configured in the current domain, such as:

    • Server Name

    • Type

    • Status

    • Cluster

    • Machine

    • State

    • Administration Port

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  2. Select the name of the server instance for which you want to view configuration information, such as the server's default network communications.

    Note:

    You can also access this detailed monitoring page directly from the Target Navigation pane:

    • From the Target Navigation pane, expand the farm, then expand WebLogic Domain.

    • Expand the domain, then select the name of the server instance for which you want to view detailed monitoring information.

Monitor server environment

To monitor the status of a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select Environment Monitoring.
  4. To monitor specific aspects associated with this server instance, select the appropriate pages:

    • General: general runtime information about the server

      See Configuration Options.

    • Channels: monitor channel information for this server

      See Configuration Options.

    • Performance: monitor performance information about this server; can also force garbage collection or a thread dump from this page

      See Configuration Options.

    • Threads: monitor the status of the thread pool and individual threads for this server

      See Configuration Options.

    • Timers: monitor the timers being used by this server

      See Configuration Options.

    • Jobs: monitor information about jobs scheduled with the job scheduler on a specific clustered server

      See Configuration Options.

    • Security: monitor user lockout management statistics for this server

      See Configuration Options.

    • Default Store: monitor runtime statistics for the default store and all of the active default store connections for this server

      For more information on default store connections, see Configuration Options.

    • JMS: monitor statistics on all the active JMS connections for this server

      See Configuration Options.

    • Workload: monitor Work Managers, constraints, and request classes associated with this server

      See Configuration Options.

Monitor channel information

To monitor channel connection information for a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select Environment Monitoring.
  4. Select the Channels page.

    The Channels table allows you to monitor information about all the channel connections for this server, such as:

    • Name

    • Connections

    • Messages Received

    • Messages Sent

    • Bytes Received

    • Bytes Sent

    • Accept Count

    For more information about these fields, see Configuration Options.

  5. In the Channels table, select the name of a channel to monitor more detailed information.

Monitor server health

To monitor the health of a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select Health.

    The Health summary page allows you to monitor health information for the server instance and its subsystems.

    See Configuration Options.

Monitor server transactions

To monitor the JTA transactions of a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select Java Transaction API (JTA).
  4. To monitor the following server information, select the appropriate pages:

    • Summary: summary of all transaction information for all resource types on this server

      See Configuration Options.

    • Transaction Log Store Statistics: monitor runtime statistics for the transaction log store used by this server

      See Configuration Options.

    • Transaction Log Store Connections: summary of all transaction information for all resource types on the server

      See Configuration Options.

    • Transactions by Name: monitor runtime statistics for all of the active transaction log store connections for this server

      See Configuration Options.

    • XA Resources: monitor transactions coordinated by this server

      See Configuration Options.

    • Non-XA Resources: monitor transactions coordinated by this server

      See Configuration Options.

    • Transactions: monitor information about current transactions coordinated by this server or in which this server's resources participate; you can force a local commit, global commit, local rollback, or global rollback from this page

      See Configuration Options.

    • Recovery Services: monitor information about transactions that were processed by the server as part of recovery on server startup or after a crash

      See Configuration Options.

Monitor server JDBC data sources

To monitor the JDBC data sources associated with a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select JDBC Data Sources.

    The JDBC Data Sources table displays information about the status of all JDBC data sources, such as:

    • Name

    • Type

    • Resource

    • Scope

    • Server

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Monitor server messaging

To monitor the status of JMS servers associated with a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select Messaging.

    The JMS Servers table displays information about the status of all JMS servers in a domain, such as:

    • JMS Server Name

    • Health

    • Health Reason

    • Target

    • Current Target

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

    To monitor the following server messaging resources or modules, select the appropriate pages:

    • Store-and-Forward Agents: monitor SAF agent statistics and perform message management operations, such as pausing incoming requests to the agent

      See Configuration Options.

    • JMS Resources: monitor all JMS resources that have been created for all the JMS system modules, including queue and topic destinations, connection factories, JMS templates, destination sort keys, destination quota, distributed destinations, foreign servers, and store-and-forward parameters

      See Configuration Options.

    • JMS Modules: monitor the JMS modules created for this domain

      See Configuration Options.

    • Messaging Bridges: monitor the status of all messaging bridges configured on active servers in this domain

      See Configuration Options.

Monitor server deployments

To monitor all deployments on a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select Deployments.

    Under the Summary page, the Deployments table displays information about all active applications and modules deployed to the server, such as:

    • Name

    • State

    • Health

    • Type

    • Deployment Order

    • Scope

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

    To monitor server deployments, select the appropriate pages:

    • Web Applications: monitor Web applications deployed to your server; includes information about the application such as the machine and server on which the application is deployed and statistics about the servlets and sessions associated with the Web application

      See Configuration Options.

    • Resource Adapters: monitor the status of inbound listeners and outbound connection pools

      See Configuration Options.

    • EJBs: monitor statistics and information about stateless, stateful, singleton, entity, and message-driven EJBs

      See Configuration Options.

    • Web Services: monitor all the Web services that are deployed to this domain

      See Configuration Options.

    • Web Service Clients: monitor all Web service clients in this server

      See Configuration Options.

    • JAX-RS Applications: monitor all the JAX-RS applications that are running on this server

      See Configuration Options.

    • Workload: monitor statistics for the Work Managers, constraints, and policies that are configured for application deployments in this server

      See Configuration Options.

Monitor server performance summary

To monitor the performance summary of a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select Performance Summary.

    The Performance Summary page displays general performance information, as well as performance information about the servlets, JSPs, and data sources associated with this server instance.

    • Click Show Metric Palette to select the metrics you want to view.

    • Select View to access table options.

    • Select Overlay to access additional table options.

Monitor server resource performance

To monitor the resource performance of a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select Resource Performance.

    The Resource Performance page displays general performance information, as well as performance information about the data sources and JMS servers associated with the server instance.

    • Click Show Metric Palette to select the metrics you want to view.

    • Select View to access table options.

    • Select Overlay to access additional table options.

Monitor server JVM performance

To monitor the JVM performance of a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select JVM Performance.

    The JVM Performance page displays performance information about memory, heap usage, garbage collectors, and threads associated with a server instance.

    • Click Show Metric Palette to select the metrics you want to view.

    • Select View to access table options.

    • Select Overlay to access additional table options.

Monitor server asynchronous tasks

Because some administrative tasks (such as deployments, service migrations, and attempts to start or stop Managed Servers) are completed immediately and others take varying amounts of time to complete, the Asynchronous Tasks summary page allows you to monitor the completion status of all tasks.

To monitor the status of asynchronous tasks in a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to monitor.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Monitoring, then select Asynchronous Tasks.

    The Asynchronous Tasks summary page allows you to monitor the completion status of all tasks by displaying information such as:

    • Description

    • Type

    • Status

    • Begin Time

    • End Time

    • Targets

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Control servers

This section describes how to control server instances. You can start, resume, suspend, or shutdown the server instances in a domain. For information on how the server transitions from STANDBY or ADMIN to the RUNNING state, see Understanding Server Life Cycle in Managing Server Startup and Shutdown for Oracle WebLogic Server.

Before you begin

Control operations on Managed Servers require starting the Node Manager. Starting Managed Servers in Standby mode requires the domain-wide administration port.

This section includes the following tasks:

Control server state

To change the state of a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.

    The Servers table displays information about the server instances that have been configured in the current domain.

  2. In the table, select the name of the server instance you want to control.
  3. From the WebLogic Server menu, select Control, then select Control Operations.

    The Servers Control table is displayed.

  4. In the table, highlight the row containing the name of the server instance you want to control. The control options are displayed above the table.
  5. Select one of the server control operations:

    • Start: moves server instances from the SHUTDOWN state to RUNNING.

    • Resume: moves server instances from the STANDBY or the ADMIN state to RUNNING.

    • Suspend: select an option to transition a server instance from the RUNNING state to the ADMIN state:

      • When work completes: moves server instances from the RUNNING state to the ADMIN state, allowing work in process to be handled gracefully. While in the SUSPENDING state, Work Managers complete in-flight processing for pending work in application threads.

      • Force shutdown now: immediately moves server instances from the RUNNING state to the ADMIN state, without handling work in process gracefully.

    • Shutdown: select an option to shutdown a server instance:

      • When work completes: gracefully stops server instances in the domain. New requests are rejected but in-flight requests are completed before the server stops.

      • Force suspend now: immediately stops server instances in the domain. In-flight requests are dropped, no new requests are accepted, and the server immediately stops.

    • Restart SSL: restarts the SSL listen sockets so that keystore changes take effect.

    See Configuration Options.

Control server JTA transactions

To control transactions coordinated by a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.

    The Servers table displays information about the server instances that have been configured in the current domain.

  2. In the table, select the name of the server instance you want to control.
  3. From the WebLogic Server menu, select Control, then select Java Transaction API (JTA).

    The JTA table displays information about the transactions coordinated by the server or in which server resources participate.

  4. In the table, highlight the row containing the name of the transaction you want to control. The control options are displayed above the table.
  5. Click one of the server control operations:

    • Force Local Commit: Forces the transaction represented by XID to be committed at the local SubCoordinator only.

    • Force Global Commit: Forces the transaction represented by XID to be committed at all participating SubCoordinators.

    • Force Local Rollback: Forces the transaction represented by XID to be rolled-back at the local SubCoordinator only.

    • Force Global Rollback: Forces the transaction represented by XID to be rolled-back at all participating SubCoordinators.

    See Configuration Options.

Control clustered server migration

To migrate a clustered server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.

    The Servers table displays information about the server instances that have been configured in the current domain.

  2. In the table, select the name of the server instance you want to control.
  3. From the WebLogic Server menu, select Control, then select Migration.

    From the Migration page, you can manually restart (migrate) the server instance and its services to another machine. Alternatively, you can migrate the JMS-related services and the JTA Transaction Recovery Service on this server instance to another server instance in the cluster.

  4. From the Migrate to Machine menu, select the machine you want to migrate this server instance and its services to.
  5. Click the Migrate button.

Control clustered server job scheduling

To control job scheduling for a clustered server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.

    The Servers table displays information about the server instances that have been configured in the current domain.

  2. In the table, select the name of the server instance you want to control.
  3. From the WebLogic Server menu, select Control, then select Jobs.

    The Jobs table displays information about jobs scheduled on this server and allows you to remove these jobs from future execution.

    See Configuration Options.

  4. In the table, highlight the row containing the name of the job you want to remove. The Cancel button is displayed above the table.
  5. Click Cancel.

Configure servers

This section describes how to configure servers. This section includes the following tasks:

Define general server configuration

To configure general settings for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select General Settings.
  4. From the General Settings page, you can define the configuration settings for this server instance, such as:

    • Template

    • Machine

    • Cluster

    • Listen Address

    • Listen Port Enabled

    • Listen Port

    • SSL Listen Port Enabled

    • SSL Listen Port

    • Client Cert Proxy Enabled

    • Java Compiler

    • Diagnostic Volume

    • Default Data Source

    For more information about these fields, see Configuration Options.

  5. Optionally, expand Advanced to define advanced configuration settings for this server instance.
  6. Click Save.
Change server template

To change the server template associated with a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select General Settings.
  4. Click Change and select the server template from the Server Templates menu.
  5. Click Save.
Specify a startup mode

The startup mode specifies the state in which a server instance should be started. The default is to start in the RUNNING state.

To specify the startup mode for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select General Settings.
  4. On the General page, expand Advanced at the bottom of the page to display the advanced configuration options.
  5. In the Startup Mode field, select:

    • Running: In the RUNNING state, a server offers its services to clients and can operate as a full member of a cluster.

    • Administration: In the ADMIN state, the server is up and running, but available only for administration operations, allowing you to perform server and application-level administration tasks without risk to running applications.

    • Standby: In the STANDBY mode, the server listens for administrative requests only on the domain-wide administration port and only accepts life cycle commands that transition the server instance to either the RUNNING or SHUTDOWN state. Other administration requests are not accepted. If you specify STANDBY, then you must also enable the domain-wide administration port.

    See Configuration Options.

  6. Click Save.
Configure listen addresses

To configure the listen address of a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select General Settings.
  4. On the General Settings page, enter a value in Listen Address.
  5. Click Save.
Configure listen ports

To configure the listen ports of a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select General Settings.
  4. If you want to disable the non-SSL listen port so that the server listens only on the SSL listen port, then deselect Listen Port Enabled. If you want to disable the SSL listen port so that the server listens only on the non-SSL listen port, then deselect SSL Listen Port Enabled.

    Note:

    You cannot disable both the non-SSL listen port and the SSL listen port. At least one port must be active.

  5. If you are using the non-SSL listen port and you want to modify the default port number, then change the value in Listen Port.
  6. If you want to modify the default SSL listen port number, then change the value in SSL Listen Port.
  7. Click Save.
Change server compiler options

To change the standard Java compiler values for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select General Settings.
  4. On the General Settings page, update the Java Compiler field with the full path of the compiler to use for all applications hosted on this server that need to compile Java code.
  5. Expand Advanced to display advanced configuration options.
  6. Update the following compile options as necessary:

    • Prepend to Classpath: Options to prepend to the Java compiler classpath when compiling Java code.

    • Append to Classpath: Options to append to the Java compiler classpath when compiling Java code.

    • Extra RMI Compiler Options: Options passed to the RMIC compiler during server-side generation.

    • Extra EJB Compiler Options: Options passed to the EJB compiler during server-side generation.

    For more information about these fields, see Configuration Options.

  7. Click Save.

Configure cluster settings

A WebLogic Server cluster is a group of servers that work together to provide a scalable and reliable application platform.

To configure cluster settings for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Clusters.
  4. From the Cluster page, you can define the cluster configuration settings for this server instance, such as:

    • Replication Group

    • Preferred Secondary Group

    • Cluster Weight

    • Interface Address

    • Replication Ports

    For more information about these fields, see Configuration Options.

  5. Click Save.

Configure server services

To configure WebLogic service settings for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Services.
  4. From the Services page, you can define the service configuration settings for this server instance, such as:

    • JMS Configuration

    • Default Store

    • Transaction Log Store

    • Messaging Bridge Configuration

    • XML Services Configuration

    For more information about these fields, see Configuration Options.

  5. Click Save.

Configure server keystores

Keystores ensure the secure storage and management of private keys and trusted certificate authorities (CAs). You can view and define various keystore configurations which help you manage the security of message transmissions.

To configure keystore settings for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.

  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Keystores.

  4. To change your keystore configuration:

    1. Click Change.

    2. From the Keystores menu, select the keystore configuration you want to use.

    3. Click Save.

  5. From the Keystore page, you can define other keystore configuration settings for this server instance, such as:

    • Keystores

    • Demo Identity Keystore

    • Demo Identity Keystore Type

    • Demo Identity Keystore Passphrase

    • Demo Trust Keystore

    • Demo Trust Keystore Type

    • Demo Trust Keystore Passphrase

    • Java Standard Trust Keystore

    • Java Standard Trust Keystore Type

    • Java Standard Trust Keystore Passphrase

    For more information about these fields, see Configuration Options.

  6. Click Save.

Configure server SSL settings

You can view and define various Secure Sockets Layer (SSL) settings for a server instance, which help you manage the security of message transmissions.

To configure SSL settings for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select SSL.
  4. From the SSL page, you can define the SSL configuration settings for this server instance, such as:

    • Identity and Trust Locations

    • Private Key Location

    • Private Key Alias

    • Private Key Passphrase

    • Certificate Location

    • Trusted Certificate Authorities

    For more information about these fields, see Configuration Options.

  5. Optionally, expand Advanced to define advanced configuration settings for this server instance.
  6. Click Save.

Configure server SAML Federation Services

You can configure a WebLogic Server instance to function as a producer or as a consumer of SAML assertions that can be used for the following:

  • Web single sign-on between online business partners

  • Exchange of identity information in Web services security

The general process of configuring Federation Services depends upon the version of SAML you are using. WebLogic Server supports both SAML 1.1 and SAML 2.0.

To configure WebLogic Server to serve as a SAML 1.1 federated partner:

To configure WebLogic Server to serve as a SAML 2.0 federated partner:

Configure SAML 1.1 source services

Before you begin

You must first configure a SAML Credential Mapper V2 security provider in the server's security realm.

You can configure a WebLogic Server instance to function as a SAML source site. A SAML source site is a site that provides an Intersite Transfer Service (ITS). A source site generates assertions that are conveyed to a destination site using one of the single sign-on profiles.

To configure a server as a SAML source site:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Federation Services.
  4. Select the SAML 1.1 Source Site page.
  5. Select the Source Site Enabled attribute to cause this server to act as a source for SAML assertions.
  6. From the SAML 1.1 Source Site page, you can also define other desired configuration settings for this server instance, such as:

    • Source Site URL

    • Signing Key Alias

    • Intersite Transfer URIs

    • ITS Requires SSL

    • Assertion Retrieval URIs

    • ARS Requires SSL

    • ARS Requires Two-Way SSL Authentication

    • Assertion Store Class Name

    • Assertion Store Properties

    For more information about these fields, see Configuration Options.

  7. Click Save.
Configure SAML 1.1 destination services

Before you begin

You must first configure a SAML Identity Asserter V2 security provider in the server's security realm.

You can configure a WebLogic Server instance to function as a SAML destination site. A destination site can receive SAML assertions and use them to authenticate local subjects.

To configure a server as a SAML destination site:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Federation Services.
  4. Select the SAML 1.1 Destination Site page.
  5. Select the Destination Site Enabled attribute to enable the Assertion Consumer Service.
  6. From the SAML 1.1 Destination Site page, you can also define other desired configuration settings for this server instance, such as:

    • Assertion Consumer URIs

    • ACS Requires SSL

    • SSL Client Identity Alias

    • POST Recipient Check Enabled

    • POST One-Use Check Enabled

    • Used Assertion Cache Class Name

    • Used Assertion Cache Properties

    For more information about these fields, see Configuration Options.

  7. Click Save.
Configure SAML 2.0 general services

You can configure general SAML 2.0 services for a server. If you are configuring SAML 2.0 Web single sign-on services with your federated partners, then the site information you configure is published in a metadata file that you send to your federated partners.

To configure the general SAML 2.0 properties of this server:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Federation Services.
  4. Select the SAML 2.0 General page.
  5. Select the Replicated Cache Enabled attribute to use the persistent cache for storing SAML 2.0 artifacts.

    This option is required if you are configuring SAML 2.0 services in two or more WebLogic Server instances in your domain. For example, if you are configuring SAML 2.0 services in a cluster, you must enable this option in each Managed Server instance individually.

    Note:

    If you are configuring SAML 2.0 services in two or more WebLogic Server instances in your domain, then you must configure the RDBMS security store. The embedded LDAP server is not supported in these configurations.

  6. In the Site Info section, enter the following information about your SAML 2.0 site:

    • Contact person details

    • Your organization's name and URL

    • The Published Site URL, which is the top-level URL for your site's SAML 2.0 service endpoints. This URL must be appended with the string /saml2, which will be automatically combined with constant suffixes to create full endpoint URLs.

  7. In the Bindings section, enter the common binding information to be used by this SAML 2.0 server instance.

    If you do not specify a Transport Layer Security key alias and passphrase, then the server's configured SSL private key alias and passphrase from the server's SSL configuration is used for the TLS alias by default.

  8. If the Artifact binding is enabled for any SAML 2.0 security provider hosted on this server instance, then define the Artifact Resolution Service settings in the Artifact Resolution Service section.
  9. In the Single Sign-on section, enter the keystore alias and passphrase for the key to be used for signing documents sent to federated partners.

    If you do not specify a single sign-on signing key alias and passphrase, then the server's configured SSL private key alias and passphrase from the server's SSL configuration is used by default.

    See Configuration Options.

  10. Click Save.

After you finish

After you have configured this server's general SAML 2.0 services, select the SAML 2.0 Identity Provider page or the SAML 2.0 Service Provider page to configure this server as an Identity Provider or Service Provider, respectively.

See Configure SAML 2.0 Identity Provider services and Configure SAML 2.0 Service Provider services.

Configure SAML 2.0 Identity Provider services

You can configure a server instance in the role of SAML 2.0 Identity Provider. A SAML 2.0 Identity Provider creates, maintains, and manages identity information for principals, and provides principal authentication to other Service Provider partners within a federation by generating SAML 2.0 assertions for those partners.

To configure a server as a SAML 2.0 Identity Provider:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Federation Services.
  4. Select the SAML 2.0 Identity Provider page.
  5. Select the Enabled attribute to activate this server's SAML 2.0 services in the role of Identity Provider.
  6. Select Only Accept Signed Authentication Requests if you want to ensure that any incoming authentication requests must be signed.
  7. If you are using a custom login Web application to which unauthenticated requests are directed:

    • Select Login Customized.

    • Enter the URL of the custom login Web application.

    • Enter the login return query parameter

      The query parameter is a unique string that the SAML 2.0 services uses to hold the login return URL for the local single sign-on service servlet. (Note that, as an alternative, the login return URL can also be specified in the login Web application.)

  8. Set the SAML bindings for which this server instance is enabled, and select the preferred binding type.
  9. Click Save.

After you finish

Coordinate with your federated partners to ensure that the SAML bindings you have enabled for this SAML authority, as well as your requirements for signed documents, are compatible with your partners.

Configure SAML 2.0 Service Provider services

You can configure a WebLogic Server instances as a SAML 2.0 Service Provider. A Service Provider is a SAML authority that can receive SAML assertions and extract identity information from those assertions. The identity information can then be mapped to local Subjects, and optionally groups as well, that can be authenticated.

To configure a server as a SAML 2.0 Service Provider:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Federation Services.
  4. Select the SAML 2.0 Service Provider page.
  5. Select the Enabled attribute to activate SAML 2.0 services in this server instance in the role of Identity Provider.
  6. Set the configuration options for the local SAML 2.0 Service Provider services as appropriate. Note the following:

    • Choose options for Always Sign Authentication Requests and Only Accept Signed Assertions as desired and in a manner that is coordinated with your federated partners so that authentication requests and assertions are accepted.

    • Communicate the SAML bindings settings for this server instance with your federated partners to ensure compatibility.

    See Configuration Options.

  7. Click Save.

After you finish

Coordinate with your federated partners to ensure that the SAML bindings you have enabled for this SAML authority, as well as your requirements for signed documents, are compatible with your partners.

Configure server deployment staging

To configure the default deployment staging on a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Deployment.
  4. From the Deployment page, you can define the default deployment staging configuration for this server instance, such as:

    • Staging Mode

    • Staging Directory Mode

    • Upload Directory Name

    For more information about these fields, see Configuration Options.

  5. Click Save.

Configure server migration

To configure migration settings for clustered servers:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Migration.
  4. From the Migration page, you can define the configuration settings for this server instance, such as:

    • Automatic Server Migration Enabled

    • Candidate Machines

    • JMS Service Candidate Servers

    • JTA Migration Policy

    • JTA Candidate Servers

    • Pre-Migration Script Path

    • Post-Migration Script Path

    • Post-Migration Script Fail Cancels Automatic Migration

    • Allow Post-Migration Script to Run on a Different Machine

    • Enable Strict Ownership Check

    For more information about these fields, see Configuration Options.

  5. Click Save.

Configure server tuning

You can tune the performance and functionality of a server instance by configuring the tuning settings.

To configure tuning settings for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Tuning.
  4. From the Tuning page, you can define the tuning configuration settings for this server instance, such as:

    • Enable Native IO

    • JavaSocketMuxer Socket Readers

    • Enable Gathered Writes

    • Enable Scattered Reads

    • Maximum Open Sockets

    • Stuck Thread Max Time

    • Stuck Thread Timer Interval

    • Accept Backlog

    • Login Timeout

    • SSL Login Timeout

    • Reverse DNS Allowed

    For more information about these fields, see Configuration Options.

  5. Optionally, expand Advanced to define advanced configuration settings for this server instance.
  6. Click Save.
Enable native IO

To enable native IO for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Tuning.
  4. On the Tuning page, if the Enable Native IO check box is not selected, select the check box.
  5. Click Save.
Enable NIOSocketMuxer

To enable non-blocking IO for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Tuning.
  4. Expand Advanced to access advanced tuning parameters.
  5. Enter weblogic.socket.NIOSocketMuxer in the Muxer Class field.
  6. Click Save.
Tune connection backlog buffering

You can tune the number of connection requests that a WebLogic Server instance will accept before refusing additional requests.

To tune connection backlog buffering for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Tuning.
  4. Modify the Accept Backlog value as necessary to tune the number of TCP connections the server instance can buffer in the wait queue.

    • If many connections are dropped or refused at the client, and no other error messages are on the server, then the Accept Backlog value might be set too low.

    • If you receive "connection refused" messages when you try to access WebLogic Server, then raise the Accept Backlog value from the default by 25 percent. Continue increasing the value by 25 percent until the messages cease to appear.

    For more information about these fields, see Configuration Options.

  5. Click Save.
Tune stuck thread detection behavior

WebLogic Server diagnoses a thread as stuck if it is continually working (not idle) for a set period of time. You can tune a server's thread detection behavior by changing the length of time before a thread is diagnosed as stuck, and by changing the frequency with which the server checks for stuck threads.

To configure stuck thread detection behavior for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Tuning.
  4. From the Tuning page, update the following options as necessary:

    • Stuck Thread Max Time: amount of time, in seconds, that a thread must be continually working before a server instance diagnoses a thread as being stuck.

    • Stuck Thread Timer Interval: amount of time, in seconds, after which a server instance periodically scans threads to see if they have been continually working for the configured Stuck Thread Max Time.

    For more information about these fields, see Configuration Options.

  5. Click Save.
Replicate domain configuration files for Managed Server independence

The server instance for which you configure Managed Server Independence (MSI) replication does not need to be running.

To configure a Managed Server to replicate a domain's configuration files:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Tuning.
  4. On the Tuning page, click Advanced at the bottom of the page to display advanced configuration settings.
  5. Ensure that the Managed Server Independence Enabled check box is selected.
  6. Click Save.

After you finish

If the Managed Server is running, then restart it.

Configure server overload

You can configure how WebLogic Server should react in the case of an overload or failure condition.

To configure overload settings for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Overload.
  4. From the Overload page, you can define the overload configuration settings for this server, such as:

    • Shared Capacity for Work Managers

    • Failure Action

    • Panic Action

    • Free Memory Percent High Threshold

    • Free Memory Percent Low Threshold

    • Max Stuck Thread Time

    • Stuck Thread Count

    For more information about these fields, see Configuration Options.

  5. Click Save.

Configure server health monitoring

WebLogic Server provides a self-health monitoring capability to improve the reliability and availability of servers in a WebLogic Server domain. Selected subsystems within each server monitor their health status based on criteria specific to the subsystem.

You can configure the frequency of a server's automated health checks and the frequency with which the Node Manager application (optional) checks the server's health state. You can also use this page to specify whether Node Manager automatically stops and restarts the server if the server reaches the "failed" health state.

To configure health monitoring settings for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Health Monitoring.
  4. From the Health Monitoring page, you can define the health monitoring configuration settings for this server instance, such as:

    • Health Check Interval

    • Auto Kill If Failed

    • Auto Restart

    • Restart Interval

    • Max Restarts Within Interval

    • Restart Delay Seconds

    For more information about these fields, see Configuration Options.

  5. Click Save.

Configure server startup

Node Manager is a WebLogic Server utility that you can use to start, suspend, shut down, and restart servers in normal or unexpected conditions. You can configure the startup settings that Node Manager will use to start this server on a remote machine.

To configure the startup options that Node Manager uses to start a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Server Start.
  4. From the Server Start page, you can define the startup configuration settings for this server instance, such as:

    • Java Home

    • Java Vendor

    • BEA Home

    • Root Directory

    • Class Path

    • Arguments

    • Security Policy File

    • User Name

    • Password

    • Confirm Password

    For more information about these fields, see Configuration Options.

  5. Click Save.

Configure server startup and shutdown settings

To configure the startup and shutdown settings for a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Start/Stop.
  4. From the Start/Stop page, you can define the startup and shutdown configuration settings for this server instance, such as:

    • Ignore Sessions During Shutdown

    • Graceful Shutdown Timeout

    • Startup Timeout

    • Server LifeCycle Timeout

    For more information about these fields, see Configuration Options.

  5. Click Save.

Configure server Web Services

You must install a Web service before you can view and modify its configuration. This section includes the following tasks:

Configure message buffering for Web services

To configure message buffering for Web services:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Web Services.
  4. Select the Buffering page.
  5. From the Buffering page, you can define the message buffering configuration properties for this server instance, such as:

    • Retry Count

    • Retry Delay

    • Request Queue Enabled

    • Request Queue Connection Factory JNDI Name

    • Request Queue Transaction Enabled

    • Response Queue Enabled

    • Response Queue Connection Factory JNDI Name

    • Response Queue Transaction Enabled

    For more information about these fields, see Configuration Options.

  6. Click Save.
Configure Web service reliable messaging

Web service reliable messaging is a framework that enables an application running on one application server to reliably invoke a Web service running on another application server, assuming that both servers implement the WS-Reliable Messaging specification. Reliable is defined as the ability to guarantee message delivery between the two Web services. Use this page to customize reliable messaging configuration on the Web service endpoint.

To configure reliable messaging for Web services:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Web Services.
  4. Select the Reliable Message page.
  5. From the Reliable Messaging page, you can define the reliable messaging configuration properties for this server instance, such as:

    • Base Retransmission Interval

    • Enable Retransmission Exponential Backoff

    • Non-buffered Source

    • Non-buffered Destination

    • Acknowledgement Interval

    • Inactivity Timeout

    • Sequence Expiration

    For more information about these fields, see Configuration Options.

  6. Click Save.
View logical stores

A logical store is a named unit of storage that provides the business configuration requirements and connects the Web service to the physical store and buffering queue.

To view the logical stores configured for this server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Web Services.
  4. Select the Logical Stores page.
  5. From the Logical Stores page, you can view configuration information for each logical store configured for this server instance, such as:

    • Name

    • Persistence Strategy

    • Request Buffering Queue JNDI Name

    • Response Buffering Queue JNDI Name

    • Default

    For more information about these fields, see Configuration Options.

Configure server Coherence cluster settings

To configure Coherence for a specific server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Coherence.
  4. From the Coherence page, you can specify the Coherence cluster you want to use for this server instance and also define configuration settings such as:

    • Unicast Listen Address

    • Unicast Listen Port

    • Unicast Port Auto Adjust

    • Local Storage Enabled

    • Coherence Web Logical Storage Enabled

    • Is Coherence Management Node

    • Site Name

    • Rack Name

    • Role Name

  5. Click Save.

Configure server protocol settings

This section describes how to configure server protocols.

This section includes the following tasks:

Configure server protocol general settings

To configure general protocol settings for a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Protocols.
  4. Select the General Settings page.
  5. From the General Settings page, you can define connections settings for various communication protocols that this server instance uses, such as:

    • Complete Message Timeout

    • Idle Connection Timeout

    • Enable Tunneling

    • Tunneling Client Ping

    • Tunneling Client Timeout

    • Maximum Message Size

    For more information about these fields, see Configuration Options.

  6. Click Save.
Configure server HTTP settings

To configure HTTP protocol settings for a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Protocols.
  4. Select the HTTP page.
  5. From the HTTP page, you can define the HTTP settings for this server instance, such as:

    • Default WebApp Context Root

    • Post Timeout

    • Max Post Size

    • Enable Keepalives

    • Duration

    • HTTPS Duration

    • Frontend Host

    • Frontend HTTP Port

    • Frontend HTTPS Port

    • WAP Enabled

    • Remote Address Override

    • Send Server Header

    • Accept Context Path in Get Real Path

    • HTTP Max Message Size

    • Enable Tunneling

    • Tunneling Client Ping

    • Tunneling Client Timeout

    For more information about these fields, see Configuration Options.

  6. Click Save.
Configure server IIOP settings

To configure Internet Inter-ORB Protocol (IIOP) settings for a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Protocols.
  4. Select the IIOP page.
  5. From the IIOP page, you can enable IIOP for this server instance.

    For more information about these fields, see Configuration Options.

    Optionally, expand Advanced to define advanced configuration settings for this server instance.

  6. Click Save.
Monitor server network channel settings

To monitor network channel protocol settings for a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Protocols.
  4. Select the Channels page.
  5. The Channels table displays information about each network channel that has been configured for this server instance, such as:

    • Name

    • Protocol

    • Enabled

    • Listen Address

    • Listen Port

    • Public Address

    • Public Port

    For more information about these fields, see Configuration Options.

  6. Click Save.
Monitor a specific network channel

To monitor a specific network channel:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Protocols.
  4. Select the Channels page.
  5. In the Channels table, select the name of the channel you want to monitor.
  6. Select Monitoring.
  7. From the Overview page, you can monitor current statistics for this network channel, such as:

    • Name

    • Connections

    • Messages Received

    • Messages Sent

    • Bytes Received

    • Bytes Sent

    • Accept Count

    For more information about these fields, see Configuration Options.

  8. From the Connections page, you can monitor current connection statistics for this network channel, such as:

    • Connect Time

    • Messages Received

    • Messages Sent

    • Bytes Received

    • Bytes Sent

    • Local Address

    • Local Port

    • Remote Address

    • Remote Port

    For more information about these fields, see Configuration Options.

Configure server network channel settings

To configure network channel protocol settings for a server instance:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance you want to configure.

    An overview page displays information related to the server instance.

  3. From the WebLogic Server menu, select Administration, then select Protocols.
  4. Select the Channels page.
  5. In the Channels table, select the name of the channel you want to configure.
  6. Select Configuration.
  7. From the General page, you can define general configuration settings for the network channel, such as:

    • Name

    • Protocol

    • Listen Port

    • Listen Address

    • External Listen Address

    • External Listen Port

    • Enabled

    For more information about these fields, see Configuration Options.

    Optionally, expand Advanced to define advanced configuration settings for this network channel.

  8. Click Save.
  9. From the Security page, you can define security configuration options for the network channel, such as:

    • Two Way SSL Enabled

    • Client Certificate Enforced

    For more information about these fields, see Configuration Options.

    Optionally, expand Advanced to define advanced configuration settings for this network channel.

  10. Click Save.

Note:

For information about configuring server template network channel settings, see Configure server template network channel settings.

Create server notes

To create notes for server configuration:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, click the name of the server you want to configure.

    An overview page displays information related to the server.

  3. From the WebLogic Server menu, select Administration, then select Notes.
  4. On the Notes page, enter your notes.
  5. Click Save.

See Configuration Options.

Configure the server template for a dynamic server

To view or change the server template configuration for a dynamic server:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, click the name of the dynamic server you want to configure.

    An overview page displays information related to the server.

  3. From the WebLogic Server menu, select Administration, then select Server Template.
  4. To view or change the configuration for the server template associated with this dynamic server, click the Server Template link.

See Configuration Options.

View the JNDI tree

The JNDI browser is a central location where you can find the JNDI names of all the WebLogic Server resources. Typically, while writing WLS client programs, you would search the JNDI browser for JNDI names. The JNDI browser displays a tree of resources in the domain, a server, or a partition. Selecting a node or an object in the tree, displays JNDI information including Binding Name, Object Class, Object Hash Code, and Object to String Results entries.

To view objects in a server's JNDI tree:

  1. From the WebLogic Domain menu, select Environment, then select Servers.
  2. In the Servers table, select the name of the server instance for which you want to view JNDI objects.
  3. From the upper left WebLogic Server menu, select JNDI Browser.
  4. Use the left pane to navigate the JNDI tree.

    For a selected node or object, the details appear in the right pane.

For more information about JNDI, see Understanding WebLogic JNDI in Developing JNDI Applications for Oracle WebLogic Server.